Shepherd writeup
draft-ietf-dmm-distributed-mobility-anchoring-14

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. This is appropriate given the informative nature of the work.
 
 
(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 describes architectural considerations and approaches for realizing distributed mobility management systems. These techniques can are applicable to any access specific and access agnostic mobility architectures.
 
 
 
Working Group Summary
 
This document has been in development, first as an individual submission in the DMM WG and later as a working group document.
The document has gone through around 14 revisions.
 
 
Document Quality
 
The current version of the document is well-written. Some sections of the document can be drafted in a better way, but that just reflects a specific writing style.  The work was completed by the authors in the earlier versions, however the chairs were not comfortable moving the document forward due to editorial issues. The chairs had to therefore appoint an editor for rewriting the document and had to put through WG reviews. We believe the quality of this document is good.
 
Personnel
 
Dapeng(Max) Liu is the document shepherd.
Suresh Krishnan is the current 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, understood the content and have also discussed with the authors. I believe this version of the document is ready for publication.
 
 
(4) Does the document Shepherd have any concerns about the depth or
breadth of the reviews that have been performed?
 
This document has been reviewed by experts that active in DMM working group.
 
 
(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.
 
The document addresses an important topic related to IP Mobility architectures. The DMM WG has the expertise in this area, and we therefore believe the reviews from the WG are sufficient.
 (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.
 
We do not have any concerns forwarding this document to IESG for reviews.
 
(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.
 
(8) Has an IPR disclosure been filed that references this document?
If so, summarize any WG discussion and conclusion regarding the IPR
disclosures.
 
There was one IPR disclosure related to this document.  
 
https://datatracker.ietf.org/ipr/3030/
 
WG is aware of these disclosures, but no one in the WG has expressed any concerns.
 
 
(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 rough consensus behind this document and no objections have
been raised.
 
(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 https://www.ietf.org/tools/idnits/ and the Internet-Drafts
Checklist). Boilerplate checks are not enough; this check needs to be
thorough.
 
There are no issues reported by the tool. All the reported issues have been addressed in the prior versions.
 
(12) Describe how the document meets any required formal review
criteria, such as the MIB Doctor, media type, and URI type reviews.
 
N/A
 
 
(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?
 
No
 
 
(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
 
(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).
 
This document does not require 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.
 
There are no new registries defined.
 
(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.
 
This document does not use formal language.
Back