OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

pmrm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [pmrm] FYI: IETF Draft on "Privacy Requirements" for protocol specs


Robin,
Thanks for this, very useful. Of course the IETF work has a strong tech and engineering focus while PMRM, as you know, tackles more governance and policy questions. That said, there seems to be strong complementarity and we should definitely talk with them and comment on the draft.
Cheers,
Peter

Sent from a Phone. Apologies for brevity - it's not easy writing on a moving planet.

From: Robin Cover
Sent: ‎21/‎09/‎2013 14:34
To: OASIS PMRM TC List
Cc: Robin Cover
Subject: [pmrm] FYI: IETF Draft on "Privacy Requirements" for protocol specs

Of possible interest to members of the PMRM TC:

Privacy Requirements for IETF Protocols
https://datatracker.ietf.org/doc/draft-cooper-ietf-privacy-requirements/
http://tools.ietf.org/html/draft-cooper-ietf-privacy-requirements-00

It is the consensus of the IETF that IETF protocols be designed to
avoid privacy violations to the extent possible.  This document
establishes a number of protocol design choices as Best Current
Practices for the purpose of avoiding such violations....

The IETF has long-standing principles that support strong security in
protocol design and a tradition of encouraging protocol designers to
take these principles into account.  [RFC1984] articulated the view
that encryption is an important tool to protect the cofidentiality of
communications, and that as such it should be encouraged and
available to all.  [RFC3365] requires that all protocols implement
strong security.  [RFC3552] provides guidance about how to consider
security in protocol design and how to document security choices.  In
[RFC2804], the IETF established a policy of not considering
wiretapping requirements in IETF protocols.  [RFC6973] explains the
many different aspects of privacy that can be affected by Internet
protocol design and provides guidance to help designers consider
privacy in their work.  This document extends the existing body of
IETF principles concerning security by articulating Best Current
Practices for avoiding egregious privacy violations and establishing
support for privacy as a principle of IETF protocol design.

These principles, old and new, should be applied when designing new
protocols, and where applicable, should be considered for updates of
existing protocols.

Discussion of this draft is directed to the ietf-privacy@ietf.org
list."

[
ietf-privacy -- Internet Privacy Discussion List
http://www.ietf.org/mail-archive/web/ietf-privacy/current/maillist.html ]

Cheers,

- Robin Cover

--
Robin Cover
OASIS, Director of Information Services
Editor, Cover Pages and XML Daily Newslink
Email: robin@oasis-open.org
Staff bio: http://www.oasis-open.org/people/staff/robin-cover
Cover Pages: http://xml.coverpages.org/
Newsletter: http://xml.coverpages.org/newsletterArchive.html
Tel: +1 972-296-1783


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]