As required by RFC 4858, this is the current template for the Document
Changes are expected over time. This version is dated 24 February 2012.
Shepherd writeup for:
Keyed IPv6 Tunnel
(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?
The intended status is Proposed Standard in the Standards Track. This is clearly indicated in the title page header.
Initially, the document was targeting Informational status. However, it was moved to Standards Track as it is making normative recommendations on L2TPv3. This was prompted by an on-list review of the document.
(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:
Keyed IPv6 Tunnel:
This document describes a simple L2 Ethernet over IPv6 tunnel
encapsulation with mandatory 64-bit cookie for connecting L2 Ethernet
attachment circuits identified by IPv6 addresses. The encapsulation
is based on L2TPv3 over IP.
Implementing L2TPv3 over IPv6 [RFC2460] provides the opportunity to
utilize unique IPv6 addresses to identify Ethernet attachment
circuits directly, leveraging the key property that IPv6 offers, a
vast number of unique IP addresses. In this case, processing of the
L2TPv3 Session ID may be bypassed upon receipt as each tunnel has one
and only one associated session. This local optimization does not
hinder the ability to continue supporting the multiplexing of
circuits via the Session ID on the same router for other L2TPv3
Working Group Summary
The WG process as it relates to this document has been smooth and without major controversies. One of the key goals of the WG has been to ensure compliance, compatibility and continued support of demultiplexing based on Session ID.
There are multiple interoperable implementations of the solution described in this document, among four major router vendors. These implementations are deployed and running in production. Further, there is additional interop done with other vendors, and implementations in Linux.
Significant cross-WG and cross-Area review were performed on this document.
Most notable, the 6MAN WG reviewed this document and posted review comments on the L2TPExt mailing list. Further, this document was presented in PWE3/PALS, and one of the PALS chairs provided also a most thorough review.
Carlos Pignataro is the Document Shepherd, Deborah Brungard is the Responsible AD.
(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 document shepherd has reviewed the draft numerous times, before adoption, during WG progress, and during and after WG LC, and finds that it is ready to advance to the IESG. All issues that were raised in the working group have been addressed.
(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?
No such concerns. See Document Quality above.
(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
No such reviews needed.
(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
No such concerns, all the outstanding issues have been resolved.
(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. Each author and contributor have provided an IPR disclosure confirmation.
(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
(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?
The WG consensus behind this document has been pretty stable and is strong.
(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.)
(11) Identify any ID nits the Document Shepherd has found in this
document. (See http://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
No errors were found on the ID nits check.
(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.
(13) Have all references within this document been identified as
either normative or informative?
(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?
(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.
(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.
(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).
The document requests no IANA actions.
(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.
(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.