[netext] Request to progress the Netext WG I-D: draft-ietf-netext-update-notifications

Basavaraj Patil <bpatil1@gmail.com> Thu, 18 July 2013 20:28 UTC

Return-Path: <bpatil1@gmail.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id CAD4E11E80F2; Thu, 18 Jul 2013 13:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id iChHtL7pxaqh; Thu, 18 Jul 2013 13:28:18 -0700 (PDT)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 2122711E8183; Thu, 18 Jul 2013 13:28:18 -0700 (PDT)
Received: by mail-ob0-f169.google.com with SMTP id up14so4278797obb.28 for <multiple recipients>; Thu, 18 Jul 2013 13:28:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=Xbd8iI+ujXJEhpeHcnOdv+zEYV+SY53A0i+OeXREeNc=; b=m+Uvgnd4GxWK3bt63fgUCHoQ+NSRCCH0GeaVO8D0BqT0Qru4wXdPW5CkCDkmjy516q LD0BfbJZPQQMNaOwsPpfRKyHjzR+02zia41QvZ6TD/jKZuZ7iAU7WN9YnaFqwvEZuC63 VVHm4kWnv8R3YNzkR1x79b8HqIqRh4cUIRszfmDmdP8pwdXgYwTPjOzIccvaASckAVuZ E5KRVpLkKRAAecJ2J1dIeroJuyG8FaqEya3XyJqT5neJdCWG+ly4a0T2cYctub8uWIt9 YwyWLV32R6fes/AydOTlpc6pS2kX+cVZXdbkLobd6qeXxAIVbMmbfP+g1g79e/gQlpNX UuuQ==
MIME-Version: 1.0
X-Received: by with SMTP id d2mr15520203oel.28.1374179297553; Thu, 18 Jul 2013 13:28:17 -0700 (PDT)
Received: by with HTTP; Thu, 18 Jul 2013 13:28:17 -0700 (PDT)
Date: Thu, 18 Jul 2013 15:28:17 -0500
Message-ID: <CAA5F1T1yMzei2ZAO1aT1uhNPU3AX_ScO3dRB1VbA5ij2WMb3Jg@mail.gmail.com>
From: Basavaraj Patil <bpatil1@gmail.com>
To: iesg-secretary@ietf.org
Content-Type: multipart/alternative; boundary=089e0149c800e3736f04e1cf0ca5
Cc: "netext@ietf.org" <netext@ietf.org>, draft-ietf-netext-update-notifications@tools.ietf.org
Subject: [netext] Request to progress the Netext WG I-D: draft-ietf-netext-update-notifications
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Jul 2013 20:28:19 -0000


The Netext WG I-D: Update Notifications for Proxy Mobile IPv6
<draft-ietf-netext-update-notifications-05> has completed working
group last call and is ready for IESG review and approval. Below is
the completed proto writeup for the I-D.



(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 protocol enhancements for allowing the local
   mobility anchor in a Proxy Mobile IPv6 domain to asynchronously
   notify the mobile access gateway about changes related to a mobility
   session.  These update notification messages are exchanged using a
   new Mobility Header message type specifically designed for this

Working Group Summary:

The extension to Proxy Mobile IPv6 was viewed as essential to the
protocol and hence was adopted by the working group and progressed
with no issues.

Document Quality:

The document has been reviewed by multiple experts within the working
group and has been updated based on the feedback received. The quality
of the document itself is good and ready for IESG review. All
reviewers have been acknowledged in the I-D. The extension is relevant
and has been requested by 3GPP as an enhancement to the
protocol. Multiple vendors are likely to implement this extension to
Proxy Mobile IPv6.

Are there existing

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 multiple times during the course of the work
being progressed in the working group. The authors have been receptive
to the suggestions and have updated the draft accordingly. At this
time I am satisfied with the quality of the I-D and believe that it is
ready for IESG review.

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

No. The I-D has been reviewed sufficiently.

(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. The I-D proposes an extension to the base protocol (Proxy Mobile
IPv6) and hence does not need any additional review from experts in
other areas.

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

The WG does not have any concerns with this I-D. No major issues or
concerns have been raised that would need to be flagged here.

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

Each author has confirmed that they are in line with the provisions of
BCP 78, 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 have been filed w.r.t this I-D.

(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 broad WG consensus on the need for this extension to Proxy
Mobile IPv6. I believe most of the active WG participants understand
the need for this extension and are supportive of 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 http://www.ietf.org/tools/idnits/ and the
Internet-Drafts Checklist). Boilerplate checks are not enough; this
check needs to be thorough.

I have checked the I-D for nits with the following result:

    Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 1 comment

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

The I-D does not specify any MIB, media type or URI types.

(13) Have all references within this document been identified as
either normative or informative?

Yes. The I-D splits the references into normative and 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 normative references exist which are pending advancement.

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

Status of existing Proxy Mobile IPv6 RFCs will not be affected. This
is an extension to the base protocol and hence there is no impact
caused to the base protocol itself.

(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 complete and includes all the
information that would be required by IANA.
A new registry is required. And the details for this are specified in
the IANA considerations section.

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

A new IANA registry called : "Update Notification Reasons Registry" is
required. Experts who can assist IANA for these registries include the
current working group chairs (Basavaraj Patil/Rajeev Koodli) as well
as other active participants in this WG such as: Charles Perkins, Kent
Leung, Pete McCann.

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

Not required for this I-D.

Basavaraj Patil