[netlmm] RFC 5847 on Heartbeat Mechanism for Proxy Mobile IPv6

rfc-editor@rfc-editor.org Fri, 11 June 2010 23:23 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 9D47D28C17C; Fri, 11 Jun 2010 16:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.948
X-Spam-Status: No, score=-0.948 tagged_above=-999 required=5 tests=[AWL=-0.437, BAYES_05=-1.11, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id xc120pOr5d9q; Fri, 11 Jun 2010 16:23:58 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id CE42528C17A; Fri, 11 Jun 2010 16:23:58 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C8AA8E06AC; Fri, 11 Jun 2010 16:24:01 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100611232401.C8AA8E06AC@rfc-editor.org>
Date: Fri, 11 Jun 2010 16:24:01 -0700 (PDT)
Cc: netlmm@ietf.org, rfc-editor@rfc-editor.org
Subject: [netlmm] RFC 5847 on Heartbeat Mechanism for Proxy Mobile IPv6
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jun 2010 23:23:59 -0000

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

        RFC 5847

        Title:      Heartbeat Mechanism for Proxy Mobile 
        Author:     V. Devarapalli, Ed.,
                    R. Koodli, Ed.,
                    H. Lim, N. Kant,
                    S. Krishnan, J. Laganier
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2010
        Mailbox:    vijay@wichorus.com, 
                    hlim@stoke.com,  nishi@stoke.com, 
                    suresh.krishnan@ericsson.com,  julienl@qualcomm.com
        Pages:      11
        Characters: 23317
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netlmm-pmipv6-heartbeat-07.txt

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

Proxy Mobile IPv6 (PMIPv6) is a network-based mobility management
protocol.  The mobility entities involved in the Proxy Mobile IPv6
protocol, the mobile access gateway (MAG) and the local mobility
anchor (LMA), set up tunnels dynamically to manage mobility for a
mobile node within the Proxy Mobile IPv6 domain.  This document
describes a heartbeat mechanism between the MAG and the LMA to detect
failures, quickly inform peers in the event of a recovery from node
failures, and allow a peer to take appropriate action.  [STANDARDS 

This document is a product of the Network-based Localized Mobility Management 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