[Mipshop] RFC 6058 on Transient Binding for Proxy Mobile IPv6
rfc-editor@rfc-editor.org Thu, 03 March 2011 18:02 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mipshop@core3.amsl.com
Delivered-To: mipshop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A85D83A69FD; Thu, 3 Mar 2011 10:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.405
X-Spam-Level:
X-Spam-Status: No, score=-102.405 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VWeszYpaGhuL; Thu, 3 Mar 2011 10:02:54 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id D230A3A695F; Thu, 3 Mar 2011 10:02:54 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 172B9E06F7; Thu, 3 Mar 2011 10:04:03 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110303180403.172B9E06F7@rfc-editor.org>
Date: Thu, 03 Mar 2011 10:04:03 -0800
Cc: mipshop@ietf.org, rfc-editor@rfc-editor.org
Subject: [Mipshop] RFC 6058 on Transient Binding for Proxy Mobile IPv6
X-BeenThere: mipshop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <mipshop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mipshop>
List-Post: <mailto:mipshop@ietf.org>
List-Help: <mailto:mipshop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mipshop>, <mailto:mipshop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2011 18:02:55 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6058
Title: Transient Binding for Proxy Mobile
IPv6
Author: M. Liebsch, Ed.,
A. Muhanna, O. Blume
Status: Experimental
Stream: IETF
Date: March 2011
Mailbox: marco.liebsch@neclab.eu,
ahmad.muhanna@ericsson.com,
oliver.blume@alcatel-lucent.de
Pages: 35
Characters: 90201
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mipshop-transient-bce-pmipv6-07.txt
URL: http://www.rfc-editor.org/rfc/rfc6058.txt
This document specifies a mechanism that enhances Proxy Mobile IPv6
protocol signaling to support the creation of a transient binding
cache entry that is used to optimize the performance of dual radio
handover, as well as single radio handover. This mechanism is
applicable to the mobile node's inter-MAG (Mobility Access Gateway)
handover while using a single interface or different interfaces. The
handover problem space using the Proxy Mobile IPv6 base protocol is
analyzed and the use of transient binding cache entries at the local
mobility anchor is described. The specified extension to the Proxy
Mobile IPv6 protocol ensures optimized forwarding of downlink as well
as uplink packets between mobile nodes and the network infrastructure
and avoids superfluous packet forwarding delay or even packet loss.
This document defines an Experimental Protocol for the Internet
community.
This document is a product of the Mobility for IP: Performance, Signaling and Handoff Optimization Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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/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