Changes between Version 11 and Version 12 of pearg


Ignore:
Timestamp:
Nov 16, 2018, 4:58:22 AM (2 months ago)
Author:
sara@…
Comment:

Remove charter since now published on the datatracker, re-org page

Legend:

Unmodified
Added
Removed
Modified
  • pearg

    v11 v12  
    11= Proposed Research Group: Privacy Enhancements and Assessments (PEA)
    22
    3 Chairs:
     3This is the wiki for the proposed Privacy Enhancements and Assessments Research Group
     4
     5= Admistration information
     6
     7* [https://datatracker.ietf.org/rg/pearg/about/ Official PEARG Datatracker page]
     8* [https://www.irtf.org/mailman/listinfo/pearg Mailing list]  pearg at irtf.org
     9* [https://datatracker.ietf.org/doc/charter-irtf-pearg/ Charter]
     10
     11== Chairs:
    412
    513* Sara Dickinson (sara at sinodun.com)
    614* Shivan Sahib (ssahib at salesforce.com)
    715
    8 Mailing list:
     16= Documents
    917
    10 The PEA mailing list is pearg at irtf.org. To subscribe or access the list archives, visit[https://www.irtf.org/mailman/listinfo/pearg the mailman page].
     18* See the [https://datatracker.ietf.org/rg/pearg/documents/ Datatracker] for the latest status and progress
    1119
    12 = Draft Charter
     20= Past meetings and presentation material
    1321
    14 == Background
     22* See the [https://datatracker.ietf.org/rg/pearg/meetings/ Meeting materials] for official meeting agendas, minutes and presentations.
    1523
    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 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.
     24= Upcoming events
    1725
    18 Alongside 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.
    19 
    20 Furthermore, there are varying definitions of privacy and confidentiality with different scope and context since it is often seen technically as an aspect of security analysis whereas it is in fact inherently a social, technical, economic, and legal construct.
    21 
    22 == Objectives
    23 
    24 The Privacy Enhancements and Assessments Research Group (PEARG) is a general forum for discussing and reviewing privacy enhancing technologies for network protocols and distributed systems in general, and for the IETF in particular.
    25 
    26 The PEARG serves to:
    27 1. 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 3. Document research on new and existing privacy assessment methodologies. One goal of this work would be to inform future development of additional specifications in the tradition of RFC 6973 by the IETF or IAB. This work will involve outreach to ensure close cooperation with similar and related efforts in IETF.
    29 4. Providing a forum for discussion and analysis of the cryptographic and practical aspects of privacy protocols e.g.
    30   a. Analyse dependencies between protocols in the larger Internet ecosystem and understand the privacy implications in a wider context
    31   b. Understand why some protocol design efforts have succeeded and other have not
    32   c. Formulate better models for analyzing and quantifying privacy risks
    33   d. Offer guidance on the use of emerging techniques and new uses of existing ones. 
    34 5. Provide a forum for IETF working groups developing protocols that include privacy technology elements to bring questions concerning the protocols to the PEARG for advice.
    35 
    36 == Meetings
    37 The PEARG will meet two to three times per year, as deemed necessary by the chairs and according to demand. At least one PEARG meeting will be co-located with an IETF meeting per year. The PEARG will also meet collocated with relevant academic conferences, such as the Privacy Enhancing Technologies Symposium (PETS), yearly if possible.  Participation is open to all.
    38 
    39 Meetings are by default open with open attendance and published proceedings, with remote participation and recording as provided by the meeting venue, according to the IRTF’s IPR policy.
    40 
    41 The chairs may at times appoint at their pleasure “closed” design teams with lesser reporting requirements (though results will be open).  This will allow for some limited discussions in which participants require extra privacy/confidentiality.  This does not relax the Note Well:  for all activities of the RG, as for all other activities of IRTF, the Note Well applies [https://www.ietf.org/about/note-well/].
    42 
    43 == Collaborations
    44 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 organisations e.g. PETS, SOUPS, W3C and the Privacy Interest Group therein.
    45 
    46 The range of potential topics the group could invite work on is large; some examples of current emerging technologies where interest is solicited include:
    47 
    48 *  Statistical Inference e.g.
    49   1. Differential privacy (DP) techniques applied to networked and distributed systems (Chrome and Apple are known to have implementations of DP)
    50   2. Anti-fingerprinting techniques
    51 * Potential uses of multi-party computation (MPC) for privacy
    52 * Privacy preserving reputation systems
    53 * ESA (Encode, Shuffle, Analyze architecture) for privacy-preserving software monitoring as proposed by Google
    54 
    55 PEARG 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.
     26PEARG is currently planning to meet again at IETF 104 (Prague) in  March 2019.
    5627
    5728
    58 = Meeting at IETF 103
     29= Side Meetings
    5930
    60 PEARG is scheduled for 15:40 - 17:10 pm (Bangkok time; ICT GMT+7) on Wednesday, Nov 7. We'll be on the 7th floor, meeting 1 breakout room.
    61 MeetEcho link (for remote participation): https://www.meetecho.com/ietf103/pearg/
    62 
    63 = Side meeting at IETF 102
     31== Side meeting at IETF 102
    6432
    6533Saint-Denis room from 1820-1900 on Tuesday 17th July 2018