RFC 5846 on Binding Revocation for IPv6 Mobility

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

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 693F728C159; Fri, 11 Jun 2010 16:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.631
X-Spam-Level:
X-Spam-Status: No, score=-1.631 tagged_above=-999 required=5 tests=[AWL=0.369, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001]
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 E29187520Odr; Fri, 11 Jun 2010 16:23:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 4DFD028C0FE; Fri, 11 Jun 2010 16:23:47 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 01C17E06A1; Fri, 11 Jun 2010 16:23:49 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5846 on Binding Revocation for IPv6 Mobility
From: rfc-editor@rfc-editor.org
Message-Id: <20100611232350.01C17E06A1@rfc-editor.org>
Date: Fri, 11 Jun 2010 16:23:49 -0700
Cc: mext@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 11 Jun 2010 23:23:48 -0000

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

        
        RFC 5846

        Title:      Binding Revocation for IPv6 Mobility 
        Author:     A. Muhanna, M. Khalil,
                    S. Gundavelli, K. Chowdhury,
                    P. Yegani
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2010
        Mailbox:    ahmad.muhanna@ericsson.com, 
                    mohamed.khalil@ericsson.com, 
                    sgundave@cisco.com,  kchowdhu@cisco.com, 
                    pyegani@juniper.net
        Pages:      39
        Characters: 95467
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mext-binding-revocation-14.txt

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

This document defines a binding revocation mechanism to terminate a
mobile node's mobility session and the associated resources.  This
mechanism can be used both with base Mobile IPv6 and its extensions,
such as Proxy Mobile IPv6.  The mechanism allows the mobility entity
which initiates the revocation procedure to request its peer to
terminate either one, multiple or all specified Binding Cache
entries.  [STANDARDS TRACK]

This document is a product of the Mobility EXTensions for IPv6 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
  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