[netext] RFC 7077 on Update Notifications for Proxy Mobile IPv6

rfc-editor@rfc-editor.org Wed, 27 November 2013 20:12 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC95E1AE1CC; Wed, 27 Nov 2013 12:12:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C-5ATTEWqVsr; Wed, 27 Nov 2013 12:12:19 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:126c::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 5BEE51AE076; Wed, 27 Nov 2013 12:05:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 10B9A726005; Wed, 27 Nov 2013 12:05:49 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20131127200549.10B9A726005@rfc-editor.org>
Date: Wed, 27 Nov 2013 12:05:49 -0800
Cc: drafts-update-ref@iana.org, netext@ietf.org, rfc-editor@rfc-editor.org
Subject: [netext] RFC 7077 on Update Notifications for Proxy Mobile IPv6
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 27 Nov 2013 20:12:22 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7077

        Title:      Update Notifications for Proxy Mobile IPv6 
        Author:     S. Krishnan, S. Gundavelli,
                    M. Liebsch, H. Yokota,
                    J. Korhonen
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2013
        Mailbox:    suresh.krishnan@ericsson.com, 
                    sgundave@cisco.com, 
                    marco.liebsch@neclab.eu,
                    yokota@kddilabs.jp, 
                    jouni.nospam@gmail.com
        Pages:      21
        Characters: 49176
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netext-update-notifications-12.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7077.txt

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.

This document is a product of the Network-Based Mobility Extensions Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/search/rfc_search.php
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC