[netlmm] RFC 5845 on Generic Routing Encapsulation (GRE) Key Option for Proxy Mobile IPv6

rfc-editor@rfc-editor.org Mon, 07 June 2010 14:52 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D2113A6821; Mon, 7 Jun 2010 07:52:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.599
X-Spam-Level:
X-Spam-Status: No, score=0.599 tagged_above=-999 required=5 tests=[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 zO9LHzCWPYf1; Mon, 7 Jun 2010 07:52:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 62CF228C104; Sun, 6 Jun 2010 19:50:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 3FD62E0671; Sun, 6 Jun 2010 19:50:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100607025056.3FD62E0671@rfc-editor.org>
Date: Sun, 6 Jun 2010 19:50:56 -0700 (PDT)
Cc: netlmm@ietf.org, rfc-editor@rfc-editor.org
Subject: [netlmm] RFC 5845 on Generic Routing Encapsulation (GRE) Key Option 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: Mon, 07 Jun 2010 14:52:53 -0000

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

        
        RFC 5845

        Title:      Generic Routing Encapsulation (GRE) Key 
                    Option for Proxy Mobile IPv6 
        Author:     A. Muhanna, M. Khalil,
                    S. Gundavelli, K. Leung
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2010
        Mailbox:    ahmad.muhanna@ericsson.com, 
                    Mohamed.khalil@ericsson.com, 
                    sgundave@cisco.com,  kleung@cisco.com
        Pages:      25
        Characters: 56198
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netlmm-grekey-option-09.txt

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

This specification defines a new mobility option for allowing the
mobile access gateway and the local mobility anchor to negotiate
Generic Routing Encapsulation (GRE) encapsulation mode and exchange
the downlink and uplink GRE keys that are used for marking the
downlink and uplink traffic that belong to a specific mobility
session.  In addition, the same mobility option can be used to
negotiate the GRE encapsulation mode without exchanging the GRE keys.
[STANDARDS TRACK]

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
  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