<div dir="ltr">Thank you Adiel for this information<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Feb 4, 2014 at 2:07 AM, Adiel Akplogan <span dir="ltr"><<a href="mailto:adiel@afrinic.net" target="_blank">adiel@afrinic.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">You may be interested.<br>
<br>
- a.<br>
<br>
Begin forwarded message:<br>
<br>
> From: IAB Chair <<a href="mailto:iab-chair@iab.org">iab-chair@iab.org</a>><br>
> Subject: W3C/IAB workshop on Strengthening the Internet Against Pervasive Monitoring (STRINT)<br>
> Date: 1 December, 2013 19:48:15 PM GMT+04:00<br>
> To: IETF Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>
> Cc: IAB <<a href="mailto:iab@iab.org">iab@iab.org</a>>, IETF <<a href="mailto:ietf@ietf.org">ietf@ietf.org</a>><br>
><br>
><br>
> W3C/IAB workshop on Strengthening the Internet<br>
> Against Pervasive Monitoring (STRINT)<br>
> ======================================<br>
><br>
> Logistics/Dates:<br>
><br>
> Submissions due: Jan 15 2014<br>
> Invitations issued: Jan 31 2014<br>
> Workshop Date: Feb 28 (pm) & Mar 1 (am) 2014<br>
> To be Confirmed - could be all day Mar 1<br>
> Location: Central London, UK. IETF Hotel or nearby (TBC)<br>
> For queries, contact: <a href="mailto:stephen.farrell@cs.tcd.ie">stephen.farrell@cs.tcd.ie</a>, <a href="mailto:tech@strews.eu">tech@strews.eu</a><br>
> Send submissions to: <a href="mailto:group-strint-submission@w3.org">group-strint-submission@w3.org</a><br>
> Workshop web site: <a href="http://www.w3.org/2014/strint/" target="_blank">http://www.w3.org/2014/strint/</a><br>
><br>
> The Vancouver IETF plenary concluded that pervasive monitoring<br>
> represents an attack on the Internet, and the IETF has begun to<br>
> carry out various of the more obvious actions [1] required to<br>
> try to handle this attack. However, there are additional much<br>
> more complex questions arising that need further consideration<br>
> before any additional concrete plans can be made.<br>
><br>
> The W3C and IAB will therefore host a one-day workshop on the<br>
> topic of "Strengthening the Internet Against Pervasive<br>
> Monitoring" before IETF-89 in London in March 2014, with support<br>
> from the EU FP7 STREWS [2] project.<br>
><br>
> Pervasive monitoring targets protocol data that we also need for<br>
> network manageability and security. This data is captured and<br>
> correlated with other data. There is an open problem as to how<br>
> to enhance protocols so as to maintain network manageability and<br>
> security but still limit data capture and correlation.<br>
><br>
> The overall goal of the workshop is to steer IETF and W3C work<br>
> so as to be able to improve or "strengthen" the Internet in the<br>
> face of pervasive monitoring. A workshop report in the form of<br>
> an IAB RFC will be produced after the event.<br>
><br>
> Technical questions for the workshop include:<br>
><br>
> - What are the pervasive monitoring threat models, and what is<br>
> their effect on web and Internet protocol security and privacy?<br>
> - What is needed so that web developers can better consider the<br>
> pervasive monitoring context?<br>
> - How are WebRTC and IoT impacted, and how can they be better<br>
> protected? Are other key Internet and web technologies<br>
> potentially impacted?<br>
> - What gaps exist in current tool sets and operational best<br>
> practices that could address some of these potential impacts?<br>
> - What trade-offs exist between strengthening measures, (e.g.<br>
> more encryption) and performance, operational or network<br>
> management issues?<br>
> - How do we guard against pervasive monitoring while maintaining<br>
> network manageability?<br>
> - Can lower layer changes (e.g., to IPv6, LISP, MPLS) or<br>
> additions to overlay networks help?<br>
> - How realistic is it to not be fingerprintable on the web and<br>
> Internet?<br>
> - How can W3C, the IETF and the IRTF better deal with new<br>
> cryptographic algorithm proposals in future?<br>
> - What are the practical benefits and limits of "opportunistic<br>
> encryption"?<br>
> - Can we deploy end-to-end crypto for email, SIP, the web, all<br>
> TCP applications or other applications so that we mitigate<br>
> pervasive monitoring usefully?<br>
> - How might pervasive monitoring take form or be addressed in<br>
> embedded systems or different industrial verticals?<br>
> - How do we reconcile caching, proxies and other intermediaries<br>
> with end-to-end encryption?<br>
> - Can we obfuscate metadata with less overhead than TOR?<br>
> - Considering meta-data: are there relevant differences between<br>
> protocol artefacts, message sizes and patterns and payloads?<br>
><br>
> Position papers (maximum of 5 pages using 10pt font or any<br>
> length Internet-Drafts) from academia, industry and others that<br>
> focus on the broader picture and that warrant the kind of<br>
> extended discussion that a full day workshop offers are the most<br>
> welcome. Papers that reflect experience based on running code<br>
> and deployed services are also very welcome. Papers that are<br>
> proposals for point-solutions are less useful in this context,<br>
> and can simply be submitted as Internet-Drafts and discussed on<br>
> relevant IETF or W3C lists, e.g. the IETF perpass list. [3]<br>
><br>
> The workshop will be by invitation only. Those wishing to attend<br>
> should submit a position paper or Internet-Draft. All inputs<br>
> submitted and considered relevant will be published on the<br>
> workshop web page. The organisers (STREWS project participants,<br>
> IAB and W3C staff) will decide whom to invite based on the<br>
> submissions received. Sessions will be organized according to<br>
> content, and not every accepted submission or invited attendee<br>
> will have an opportunity to present as the intent is to foster<br>
> discussion and not simply to have a sequence of presentations.<br>
><br>
> [1] <a href="http://down.dsg.cs.tcd.ie/misc/perpass.txt" target="_blank">http://down.dsg.cs.tcd.ie/misc/perpass.txt</a><br>
> [2] <a href="http://www.strews.eu/" target="_blank">http://www.strews.eu/</a><br>
> [3] <a href="https://www.ietf.org/mailman/listinfo/perpass" target="_blank">https://www.ietf.org/mailman/listinfo/perpass</a><br>
><br>
><br>
<br>
<br>_______________________________________________<br>
AfrICANN mailing list<br>
<a href="mailto:AfrICANN@afrinic.net">AfrICANN@afrinic.net</a><br>
<a href="https://lists.afrinic.net/mailman/listinfo.cgi/africann" target="_blank">https://lists.afrinic.net/mailman/listinfo.cgi/africann</a><br>
<br></blockquote></div><br></div>