RFC 6973: Privacy Considerations for Internet Protocols
In plain English — editorial summary, not part of the RFC
This document offers guidance for developing privacy considerations for inclusion in protocol specifications. It aims to make designers, implementers, and users of Internet protocols aware of privacy-related design choices. It suggests that whether any individual RFC warrants a specific privacy considerations section will depend on the document's content.
Document record
- Document ID
- RFC6973
- Published
- July 2013
- Authors
- A. Cooper; H. Tschofenig; B. Aboba; J. Peterson; J. Morris; M. Hansen; R. Smith
- Status
- INFORMATIONAL
- Stream
- IAB
- Area
- —
- Pages
- 36
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6806Kerberos Principal Name Canonicalization and Cross-Realm ReferralsCurrent
November 2012
- RFC 6711An IANA Registry for Level of Assurance (LoA) ProfilesCurrent
August 2012
- RFC 7458Extensible Authentication Protocol (EAP) Attributes for Wi-Fi Integration with the Evolved Packet CoreCurrent
February 2015
- RFC 6377DomainKeys Identified Mail (DKIM) and Mailing ListsCurrent
September 2011
- RFC 6376DomainKeys Identified Mail (DKIM) SignaturesUpdated
September 2011
- RFC 7626DNS Privacy ConsiderationsObsoleted
August 2015
- RFC 7643System for Cross-domain Identity Management: Core SchemaUpdated
September 2015
- RFC 7844Anonymity Profiles for DHCP ClientsCurrent
May 2016
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?