Skip to main content

Shepherd writeup


The Netext working group I-D: Separation of Control and User Plane for
Proxy Mobile IPv6 d<raft-ietf-netext-pmip-cp-up-separation-03.txt> has
completed working group last call. The authors have addressed all
review comments and submitted a revised I-D. It is now ready for IESG
review and IETF last call. Please process accordingly. 

The protol writeup for this I-D is included below.


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

Proposed Standard

(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 method to split the Control Plane (CP) and
   User Plane (UP) for a Proxy Mobile IPv6 based network infrastructure.
   Existing specifications allow a Mobile Access Gateway (MAG) to
   separate its control and user plane using the Alternate Care of
   address mobility option for IPv6, or Alternate IPv4 Care of Address
   option for IPv4.  However, the current specification does not provide
   any mechanism allowing the Local Mobility Anchor (LMA) to perform an
   analogous functional split.  To remedy that shortcoming, this
   document specifies a mobility option enabling a LMA to provide an
   alternate LMA address to be used for the bi-directional user plane
   traffic between the MAG and LMA.  With this new option, a LMA will be
   able to use an IP address for its user plane which is different than
   the IP address used for the control plane.

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 has sailed through the WG process because the problem
that it aims to solve is clear and has strong consensus among the WG

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? 

No known implementations of the protocol exist at this time. No
vendors have expressly stated a plan to implement this specification
The I-D acknowledges the reviewers who have helped improve the I-D.


Who is the Document Shepherd? Who is the Responsible Area Director?

Document Shepherd: Basavaraj Patil

Responsible AD: Brian Haberman

(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 have reviewed the I-D prior to the WG last call and provided input
to the authors which has been implemented in the version that is now
ready for submission to the IESG. The document is clearly ready for
IESG review and publication.

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


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

Broader reviews of this I-D are not required.

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

No special concerns about this document. It has strong WG consensus.

(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 has confirmed conformance to the provisions of BCP 78
and 79.

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

No IPR disclosures associated with this I-D have been filed.

(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 is strong and the larger WG understand the
specification and agrees with it.

(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 and the
Internet-Drafts Checklist). Boilerplate checks are not enough; this
check needs to be thorough. 

No special concern w.r.t ID-nits

     Summary: 0 errors (**), 0 flaws (~~), 0 warnings (==), 2 comments (--).

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

The document does not specify a MIB, media type or URI type.

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

No. All normative references are published RFCs.

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

Publishing this I-D will not have an impact on the status of any
existing 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

The IANA considerations section is clear and has sufficient
information for IANA to complete the actions. The registry to be used
is specified in this section as well.

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

No new IANA registries will be required.

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

No XML code, BNF rules or MIB definitions have been specified in this document.