(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 draft is intended to be at, and requests, Informational status.
(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:
This document summarizes a proposed framework for enterprise network
architects and administrators as they plan the introduction of IPv6
support in their environments, specifically dual stack and eventually IPv6
only.
Working Group Summary:
This draft was first submitted as
draft-ietf-v6ops-enterprise-incremental-ipv6-00.txt in August 2012. The
document has been revised several times since introduced. The document
outlines considerations, both technical and logistical, that enterprise
adopters of IPv6 should consider as they advance or even begin introducing
support for IPv6 across their respective enterprises.
The draft has been discussed at length and in detail.
Document Quality:
As specified in the abstract, the document is not a protocol or procedure;
the document outlines topics that enterprise adopters should consider when
planning for the adoption of IPv6. The document touches on areas that
would be typically be present when planning an IPv6 adoption project so
several are the items focus on non-technical aspects of an enterprise IPv6
deployment.
Personnel:
The document shepherd is John Jason Brzozowski. The responsible AD is Joel
Jaegli.
(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.
In the view of the chairs, this document is ready for publication, having
been reviewed and commented on by the working group. The shepherd tracked
working group commentary. The shepherd also read the document and ran it
through idnits.
(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?
No.
(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.
No.
(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.
I have no issues with the document as it stands.
(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?
The authors tell me that they know of no outstanding IPR disclosures.
(8) Has an IPR disclosure been filed that references this document? If so,
summarize any WG discussion and conclusion regarding the IPR disclosures.
Per
http://datatracker.ietf.org/ipr/search/?option=document_search&id=draft-iet
f-v6ops-enterprise-incremental-ipv6, there are no relevant IPR disclosures.
(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?
WG consensus is solid for this document. Since it is largely focused
planning and logistics for enterprise IPv6 deployments there seemed to be
little contention around the document. Various comments and edits from
adopters have been factored into the document to help with completeness.
(10) Has anyone threatened an appeal or otherwise indicated extreme
discontent? If so, please summarize 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.)
No.
(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
thorough.
idnits was run on draft-ietf-v6ops-enterprise-incremental-ipv6-05, no
issues were reported.
(12) Describe how the document meets any required formal review criteria,
such as the MIB Doctor, media type, and URI type reviews.
Irrelevant.
(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?
Not applicable.
(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.
The normative references are all to informational, BCP, or standards track
documents. As an informational document, these are not downward references.
(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.
The document doesn't change the status of any RFCs.
(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).
This memo includes no request to IANA, and says as much.
(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.
There are none.
(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.
None. There is no formal language in the document.