[Pearg] Welcome to the Privacy Enhancements and Assessment Proposed RG mailing list!

[Sara Dickinson <[e-mail]>]

Dear All, 

We would like to announce the first meeting (a side meeting) of the Privacy Enhancements and Assessment (PEA) Proposed RG to be held at IETF 102 in Montreal. We are waiting confirmation of our time slot, we have requested 18:40 on Tuesday 17th July and will post to this list as soon as we have more details.

The chairs for this Proposed RG are:
Sara Dickinson ([e-mail] <mailto:[e-mail]>) and 
Shivan Sahib ([e-mail] <mailto:[e-mail]>)

This side meeting is planned as an informal discussion for parties interested in participating in the Proposed RG. There will be an overview of the proposed charter (see below) and we would like to solicit feedback on the charter and also possible future work in the group. 

As food for thought we believe that there are several ongoing privacy-relevant efforts and discussions in various IETF and IRTF groups that would benefit from a dedicated group for analysis, including:

- [QUIC] Privacy leaks via passive network management via the proposed QUIC spin bit.
- [QUIC] Connection migration and multipath privacy properties of exposed packet header information.
- [DoH] Privacy implications for various use cases and for server operators.
- [DRUI (BoF)] Privacy implications of DNS resolver discovery mechanisms.
- [DNSSD] Private service discovery threat model formulation and solution analysis.
- [DPRIVE] BCP for operators of DNS privacy services. Padding profile analysis.
- [ICNRG] Privacy implications of unencrypted content requests (interests).
- [TRANS] Privacy implications of certificate transparency gossiping.
- [RTCWEB] Privacy issues around exposing private IP addresses in WebRTC

Equally important, there is active research being conducted in the academic and open source communities around privacy preserving techniques that the IETF and IRTF could benefit from adopting.

We’ll also discuss scheduling future meetings, including possible co-location with events other than the IETF. 

Best regards

Sara & Shivan




# Draft Charter

## Background

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 and IAB 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. 

Alongside such work the emergence of global and region-specific legislation in this area e.g. GDPR 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. 

## Objectives

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. The PEARG serves as a bridge between theory and practice, bringing new privacy-enhancing technologies to the Internet community and promoting an understanding of the use and applicability of these mechanisms via Informational RFCs (in the tradition of HMAC [RFC 2104]).  Our goal is to provide a forum for discussion and analyzing the cryptographic and practical aspects of privacy protocols, and to offer guidance on the use of emerging techniques and new uses of existing ones.  IETF working groups developing protocols that include privacy technology elements are welcome to bring questions concerning the protocols to the PEARG for advice.

The Assessments objective of PEARG will include partaking in the following tasks:

1) Reviewing privacy properties (informed by but not limited to the analysis in RFC6973) of existing and emerging IETF protocols,

2) 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. 

## Meetings

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. 

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. 

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.  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/].

## Collaborations

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.  Example current emerging technologies where interest is solicited include:

1. Differential privacy techniques applied to networked and distributed systems
2. Anti-fingerprinting techniques
3. Potential uses of MPC for privacy 

PEARG is related to security and cryptographic protocols in the IETF and IRTF. Among the IETF working groups, PEARG will collaborate to ensure and encourage collaboration 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.