Shepherd writeup
rfc7618-09

Write up for draft-ietf-dhc-dynamic-shared-v4allocation(-05).txt:

(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? 

Standards Track. This is the proper type because this document specifies
a mechanism for DHCPv4, when used over DHCPv6 (see RFC 7341), to obtain
a shared portion of an IPv4 address (see RFC 6346). This is also related
to the Softwire WG MAP work. The type is indicated in the title page
header.

(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 specifies a mechanism for obtaining shared IPv4 address
and IPv4 configuration information dynamically via DHCPv4 (over
DHCPv6).


Working Group Summary: 

This work is an extension to DHCPv4 to allow for a shared IPv4 address
to be allocated and renewed by a client.

Document Quality: 

This document has had thorough reviews by many interested and
knowledgeable folks (beyond those mentioned in the acknowledgements
section). There were no significant points of difficulty or
controversy with the contents of the document.

Personnel: 

Bernie Volz is the document shepherd. Ted Lemon 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 IESG. 

I read the document thoroughly, and submitted editorial and technical 
suggestions to the authors, which they implemented. I believe it is
ready for publication.

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

No, the document has had a good deal of careful review.

(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. 

This is strictly a DHCP document, and has had sufficient review from
DHCP experts. And, some of those involved also are active in the
Softwire WG.

(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 think the document is good as written, and serves a useful purpose.
See section (3) above for a minor nit.

(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. However, please see (8).


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

Yes. There are 3 IPR statements (one directly associated with this
document and 2 indirectly from earlier related efforts).

The directly associated IPR was late (after the WGLC) as the ones from
the earlier documents did not get properly associated with this new
work. The DHC WG was notified of this issue and there were no
objections to proceeding with this work because of 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? 

There is a strong consensus behind this document and in particular from
very active WG participants (i.e. "DHCP experts").

(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.) 

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. 

The document passes the idnits tool. There is one warning regarding
a non-RFC5737-complaint IPv4 address, but that is on purpose since
it is referencing the auto-configuration address range
(169.254.0.0/16), see RFC 6890 (Table 5).

(12) Describe how the document meets any required formal review 
    criteria, such as the MIB Doctor, media type, and URI type 
    reviews. 

The DHCPv4 option defined by this document uses the same format for
the port parameters as used by draft-ietf-softwire-map-dhcp (see
section 4.5) and both of these follow RFC 7227 (Guidelines for
Creating New DHCPv6 Options). 

(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? 

There are two drafts referenced, draft-ietf-softwire-map-12 and
draft-ietf-softwire-lw4over6-13, which are both flagged as
"Approved-announcement to be sent" as of 02/13/2015 as they
received enough positions to pass.


(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. 

No downward normative 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. 

No.

(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). 

I reviewed the IANA Considerations section and it is fine and clear; the
actions are to define a new DHCPv4 option and the appropriate
registry is clearly identified to IANA.

(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 no new IANA registries requested by this draft.

(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. 

There are no such parts to the document.
Back