RFC 6705 on Localized Routing for Proxy Mobile IPv6

rfc-editor@rfc-editor.org Thu, 20 September 2012 00:35 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B5EDA21E8041; Wed, 19 Sep 2012 17:35:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.01
X-Spam-Status: No, score=-102.01 tagged_above=-999 required=5 tests=[AWL=-0.010, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 70Ft13KTcU2l; Wed, 19 Sep 2012 17:35:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 1461021E8048; Wed, 19 Sep 2012 17:35:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3CA4EB1E003; Wed, 19 Sep 2012 17:32:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6705 on Localized Routing for Proxy Mobile IPv6
From: rfc-editor@rfc-editor.org
Message-Id: <20120920003202.3CA4EB1E003@rfc-editor.org>
Date: Wed, 19 Sep 2012 17:32:02 -0700
Cc: netext@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Sep 2012 00:35:46 -0000

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

        RFC 6705

        Title:      Localized Routing for Proxy Mobile IPv6 
        Author:     S. Krishnan, R. Koodli,
                    P. Loureiro, Q. Wu,
                    A. Dutta
        Status:     Standards Track
        Stream:     IETF
        Date:       September 2012
        Mailbox:    suresh.krishnan@ericsson.com, 
        Pages:      20
        Characters: 43309
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netext-pmip-lr-10.txt

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

Proxy Mobile IPv6 (PMIPv6) is a network based mobility management
protocol that enables IP mobility for a host without requiring its
participation in any mobility-related signaling.  PMIPv6 requires all
communications to go through the local mobility anchor.  As this can
be suboptimal, Localized Routing (LR) allows Mobile Nodes (MNs) attached to
the same or different Mobile Access Gateways (MAGs) to route traffic by
using localized forwarding or a direct tunnel between the gateways.
This document proposes initiation, utilization, and termination
mechanisms for localized routing between mobile access gateways
within a proxy mobile IPv6 domain.  It defines two new signaling
messages, Localized Routing Initiation (LRI) and Local Routing
Acknowledgment (LRA), that are used to realize this mechanism.

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

This is now a Proposed Standard Protocol.

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

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
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