Re: [netext] Last Call: <draft-ietf-netext-update-notifications-07.txt> (Update Notifications for Proxy Mobile IPv6) to Proposed Standard

Carlos Jesús Bernardos Cano <> Fri, 23 August 2013 01:29 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1C14F11E82B0; Thu, 22 Aug 2013 18:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.299
X-Spam-Status: No, score=-6.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id kPMFsyXErRkA; Thu, 22 Aug 2013 18:28:54 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 9FB1A11E8141; Thu, 22 Aug 2013 18:28:53 -0700 (PDT)
Received: from (localhost []) by (Postfix) with ESMTP id 1F90310BCE9E; Fri, 23 Aug 2013 03:28:53 +0200 (CEST)
X-uc3m-safe: yes
X-uc3m-safe: yes
Received: from [] (unknown []) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: by (Postfix) with ESMTPSA id 7B5791079375; Fri, 23 Aug 2013 03:28:52 +0200 (CEST)
Message-ID: <>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <>
In-Reply-To: <>
References: <>
Organization: Universidad Carlos III de Madrid
Content-Type: text/plain; charset="UTF-8"
Date: Fri, 23 Aug 2013 03:28:36 +0200
Mime-Version: 1.0
X-Mailer: Evolution 3.4.4-3
Content-Transfer-Encoding: 7bit
X-TM-AS-Product-Ver: IMSS-
X-TM-AS-Result: No--40.936-7.0-31-1
X-imss-scan-details: No--40.936-7.0-31-1
Subject: Re: [netext] Last Call: <draft-ietf-netext-update-notifications-07.txt> (Update Notifications for Proxy Mobile IPv6) to Proposed Standard
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 23 Aug 2013 01:29:00 -0000


I've taken a look at the current version of the draft and I think it is
in good shape.

I have a couple of comments:

- I think it might be useful to include an additional NR
Code for obtaining Updated Access Network Identifier (ANI) parameters.
The LMA would send a UPN message to the MAG with
NR=Updated-ANI-Parameters and then the MAG would send the PBU with the
updated ANI parameters.

- In the last NETEXT session we discussed about using the update
notifications for the flow mobility solution draft
(draft-ietf-netext-pmipv6-flowmob). I think it might be good to add a
Notification Reason related to flow mobility updates, or at least a
reference to the flowmob document (we can also define the Notification
Reason in draft-ietf-netext-pmipv6-flowmob).



On Thu, 2013-08-15 at 11:32 -0700, The IESG wrote:
> The IESG has received a request from the Network-Based Mobility
> Extensions WG (netext) to consider the following document:
> - 'Update Notifications for Proxy Mobile IPv6'
>   <draft-ietf-netext-update-notifications-07.txt> as Proposed Standard
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> mailing lists by 2013-08-29. Exceptionally, comments may be
> sent to instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
> Abstract
>    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
>    purpose.
> The file can be obtained via
> IESG discussion can be tracked via
> No IPR declarations have been submitted directly on this I-D.