Privacy Considerations for IPv6 Adaptation-Layer Mechanisms
RFC 8065

Received changes through RFC Editor sync (created alias RFC 8065, changed title to 'Privacy Considerations for IPv6 Adaptation-Layer Mechanisms', changed abstract to 'This document discusses how a number of privacy threats apply to technologies designed for IPv6 over various link-layer protocols, and it provides advice to protocol designers on how to address such threats in adaptation-layer specifications for IPv6 over such links.', changed pages to 10, changed standardization level to Informational, changed state to RFC, added RFC published event at 2017-02-22, changed IESG state to RFC Published)

[Ballot comment]

intro, 1st bullet: doesn't that same issue arise with
prefixes as well as IIDs? (At least if there are few hosts
per /48 or /56.) It may be worth making that point
somewhere separate from points about IIDs.

(Via drafts-lastcall-comment@iana.org): IESG/Authors/WG Chairs:

The IANA Services Operator has reviewed draft-ietf-6lo-privacy-considerations-04.txt, which is currently in Last Call, and has the following comments:

We understand that this document doesn't require any registry actions.

While it's often helpful for a document's IANA Considerations section to remain in place upon publication even if there are no actions, if the authors strongly prefer to remove it, we do not object.

If this assessment is not accurate, please respond as soon as possible.

Thank you,

Sabrina Tanamal
IANA Services Specialist
PTI

The following Last Call announcement was sent out:

From: The IESG
To: "IETF-Announce"
CC: 6lo-chairs@ietf.org, suresh.krishnan@ericsson.com, Gabriel.Montenegro@microsoft.com, "Gabriel Montenegro" , 6lo@ietf.org, draft-ietf-6lo-privacy-considerations@ietf.org
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Privacy Considerations for IPv6 Adaptation Layer Mechanisms) to Informational RFC


The IESG has received a request from the IPv6 over Networks of
Resource-constrained Nodes WG (6lo) to consider the following document:
- 'Privacy Considerations for IPv6 Adaptation Layer Mechanisms'
  as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2016-11-30. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


  This document discusses how a number of privacy threats apply to
  technologies designed for IPv6 over various link layer protocols, and
  provides advice to protocol designers on how to address such threats
  in adaptation layer specifications for IPv6 over such links.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-6lo-privacy-considerations/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-6lo-privacy-considerations/ballot/


No IPR declarations have been submitted directly on this I-D.

As required by RFC 4858, this is the current template for the Document
Shepherd Write-Up.

Changes are expected over time. This version is dated 24 February 2012.

(1) What type of RFC is being requested (BCP, Proposed Standard,
Internet Standard, Informational, Experimental, or Historic)?  Why
is this the proper type of RFC?  Is this type of RFC indicated in the
title page header?

Informational, as noted in the document itself. This document gives advice to authors of other 6lo documents about how to think about privacy issues, the different threats and the kinds of mechanisms to consider in order to mitigate them. Nothing prescriptive, though.

(2) The IESG approval announcement includes a Document Announcement
Write-Up. Please provide such a Document Announcement Write-Up. Recent
examples can be found in the "Action" announcements for approved
documents. The approval announcement contains the following sections:

Technical Summary

  Relevant content can frequently be found in the abstract
  and/or introduction of the document. If not, this may be
  an indication that there are deficiencies in the abstract
  or introduction.

  This document discusses how a number of privacy threats apply to
  technologies designed for IPv6 over networks of resource-constrained
  nodes, and provides advice to protocol designers on how to address
  such threats in adaptation layer specifications for IPv6 over such
  links.

Working Group Summary

  Was there anything in WG process that is worth noting? For
  example, was there controversy about particular points or
  were there decisions where the consensus was particularly
  rough?

This document educates the 6lo community in that it lists potential threats to privacy and some potential mitigations. It also has guidance for different adaptation layers on how to evaluate how relevant are the threats and how practical are the mitigations. In this sense, this document is also about tradeoffs, as such it has benefitted from f2f and email list discussion. In the process it has benefitted and has also helped ongoing document in the working group address privacy issues.

Document Quality

  Are there existing implementations of the protocol? Have a
  significant number of vendors indicated their plan to
  implement the specification? Are there any reviewers that
  merit special mention as having done a thorough review,
  e.g., one that resulted in important changes or a
  conclusion that the document had no substantive issues? If
  there was a MIB Doctor, Media Type or other expert review,
  what was its course (briefly)? In the case of a Media Type
  review, on what date was the request posted?

Non prescriptive, so its guidance will influence ongoing work in more typical drafts on IPv6 adaptation, and those will get implemented in due time.
Personnel

  Who is the Document Shepherd? Who is the Responsible Area
Director?
Document shepherd: Gabriel Montenegro
Responsible AD: Suresh Krishnan

(3) Briefly describe the review of this document that was performed by
the Document Shepherd.  If this version of the document is not ready
for publication, please explain why the document is being forwarded to
the IESG.

I read several versions of the document, including the latest, 03. This version is ready for advancement.

(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?

None.


(5) Do portions of the document need review from a particular or from
broader perspective, e.g., security, operational complexity, AAA, DNS,
DHCP, XML, or internationalization? If so, describe the review that
took place.

Not applicable.

(6) Describe any specific concerns or issues that the Document Shepherd
has with this document that the Responsible Area Director and/or the
IESG should be aware of? For example, perhaps he or she is uncomfortable
with certain parts of the document, or has concerns whether there really
is a need for it. In any event, if the WG has discussed those issues and
has indicated that it still wishes to advance the document, detail those
concerns here.

None.

(7) Has each author confirmed that any and all appropriate IPR
disclosures required for full conformance with the provisions of BCP 78
and BCP 79 have already been filed. If not, explain why.

Yes, this has been confirmed.

(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.

None.

(9) How solid is the WG consensus behind this document? Does it
represent the strong concurrence of a few individuals, with others
being silent, or does the WG as a whole understand and agree with it? 

There has been healthy discussion in several f2f meetings and on the mailing list. This document has already proven useful to other standards track documents as they document and mitigate their respective privacy concerns. There is good support in the working group and appreciation for its advice.

(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarise the areas of conflict in separate
email messages to the Responsible Area Director. (It should be in a
separate email because this questionnaire is publicly available.)

None.

(11) Identify any ID nits the Document Shepherd has found in this
document. (See https://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.

None.

(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.
Not applicable.
(13) Have all references within this document been identified as
either normative or informative?

Yes.

(14) Are there normative references to documents that are not ready for
advancement or are otherwise in an unclear state? If such normative
references exist, what is the plan for their completion?

None.

(15) Are there downward normative references references (see RFC 3967)?
If so, list these downward references to support the Area Director in
the Last Call procedure.

None.

(16) Will publication of this document change the status of any
existing RFCs? Are those RFCs listed on the title page header, listed
in the abstract, and discussed in the introduction? If the RFCs are not
listed in the Abstract and Introduction, explain why, and point to the
part of the document where the relationship of this document to the
other RFCs is discussed. If this information is not in the document,
explain why the WG considers it unnecessary

Not applicable.


(17) Describe the Document Shepherd's review of the IANA considerations
section, especially with regard to its consistency with the body of the
document. Confirm that all protocol extensions that the document makes
are associated with the appropriate reservations in IANA registries.
Confirm that any referenced IANA registries have been clearly
identified. Confirm that newly created IANA registries include a
detailed specification of the initial contents for the registry, that
allocations procedures for future registrations are defined, and a
reasonable name for the new registry has been suggested (see RFC 5226).

Not applicable.

(18) List any new IANA registries that require Expert Review for future
allocations. Provide any public guidance that the IESG would find
useful in selecting the IANA Experts for these new registries.

Not applicable.

(19) Describe reviews and automated checks performed by the Document
Shepherd to validate sections of the document written in a formal
language, such as XML code, BNF rules, MIB definitions, etc.

Not applicable.