Changes between Version 8 and Version 9 of pearg


Ignore:
Timestamp:
Oct 10, 2018, 5:24:28 AM (13 months ago)
Author:
sara@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • pearg

    v8 v9  
    1414== Background
    1515
    16 Privacy is an increasingly desirable and often necessary property for Internet technologies. Evidence suggests that attacks on societal, community, and individual privacy occur with non-negligible frequency, as discussed in detail in RFC 7258 and in protocol-specific documents such as RFC 7626. Pervasive monitoring [RFC 7258], is a well known attack on privacy at incredible scale.  The IETF’s and IAB’s responses to such attacks is to push for widespread end-to-end encryption. Understanding attacks on privacy and the costs of addressing them is critical for ensuring the longevity, usability, and viability of Internet technologies.
     16Privacy is an increasingly desirable and often necessary property for Internet technologies. Evidence suggests that attacks on societal, community, and individual privacy occur with non-negligible frequency, as discussed in detail in RFC 7258 and in protocol-specific documents such as RFC 7626. Pervasive monitoring [RFC 7258], is a well known attack on privacy at incredible scale.  The IETF’s and IAB’s responses to such attacks are to push for widespread end-to-end encryption along with encouraging effort in numerous working groups around reducing privacy leakage. Understanding attacks on privacy and the costs of addressing them is critical for ensuring the longevity, usability, and viability of Internet technologies.
    1717
    1818Alongside such work global and region-specific legislation is evolving in this area (GDPR and the ePrivacy Directive are two such examples applicable to Europe). While the full impact of such legislative changes is not understood, this provides further motivation for enhancing available privacy techniques (beyond end-to-end encryption), advancing the state-of-the-art for privacy in protocols, and for assessing privacy of existing protocols.
     
    2626The PEARG serves to:
    27271. Be a bridge between theory and practice, bringing new privacy-enhancing technologies from open source or academic communities to the wider Internet community and promoting an understanding of the use and applicability of these mechanisms via Informational or Experimental RFCs (in the tradition of HMAC [RFC 2104]). 
    28 2. Reviewing privacy properties (informed by but not limited to the analysis in RFC6973) of existing and emerging IETF protocols. In particular, engagement in review early in the design process is highly desirable.
    29283. Developing specifications in the tradition of RFC 6973 that offer guidance for protocol design and development and advice on privacy-enhancement.  This work will involve outreach to ensure close cooperation with similar and related efforts in IETF.
    30294. Providing a forum for discussion and analysis of the cryptographic and practical aspects of privacy protocols e.g.
     
    4342
    4443== Collaborations
    45 PEARG will actively engage with academic and open source (e.g. Tor project, EFF, OTF) communities and encourage specification of key privacy-enhancing technologies in Informational or Experimental RFCs. It will also engage with other standards bodies e.g. PETS, SOUPS, W3C and the Privacy Interest Group therein.
     44PEARG will actively engage with academic and open source (e.g. Tor project, EFF, OTF) communities and encourage specification of key privacy-enhancing technologies in Informational or Experimental RFCs. It will also engage with other organisations e.g. PETS, SOUPS, W3C and the Privacy Interest Group therein.
    4645
    4746The range of potential topics the group could invite work on is large; some examples of current emerging technologies where interest is solicited include:
     
    5453* ESA (Encode, Shuffle, Analyze architecture) for privacy-preserving software monitoring as proposed by Google
    5554
    56 PEARG is related to security and cryptographic protocols in the IETF and IRTF. Among the IETF working groups, PEARG will participate and encourage participation so that desirable privacy properties are upheld for the Internet community. PEARG will also collaborate with the CFRG to ensure cryptographic techniques and algorithms are used appropriately for their intended purpose.
     55PEARG is related to security and cryptographic protocols in the IETF and IRTF. Among the IETF working groups, PEARG will encourage participation so that desirable privacy properties are upheld for the Internet community. PEARG will also collaborate with the CFRG to ensure cryptographic techniques and algorithms are used appropriately for their intended purpose.
    5756
    5857
     
    7170Minutes
    7271* [https://mailarchive.ietf.org/arch/msg/pearg/7W19JyCB0BySB31vfku2mYXRJMk Meeting minutes are available in the mail archive.]
    73