[netext] RFC 6909 on IPv4 Traffic Offload Selector Option for Proxy Mobile IPv6

rfc-editor@rfc-editor.org Mon, 29 April 2013 18:49 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 426E421F9AD6; Mon, 29 Apr 2013 11:49:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level:
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7+zCSq5H7Wtd; Mon, 29 Apr 2013 11:49:51 -0700 (PDT)
Received: from rfc-editor.org (unknown [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id D842E21F9AC5; Mon, 29 Apr 2013 11:49:51 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4A143B1E004; Mon, 29 Apr 2013 11:49:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20130429184926.4A143B1E004@rfc-editor.org>
Date: Mon, 29 Apr 2013 11:49:26 -0700 (PDT)
Cc: netext@ietf.org, rfc-editor@rfc-editor.org
Subject: [netext] RFC 6909 on IPv4 Traffic Offload Selector Option for Proxy Mobile IPv6
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2013 18:49:52 -0000

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

        
        RFC 6909

        Title:      IPv4 Traffic Offload Selector Option 
                    for Proxy Mobile IPv6 
        Author:     S. Gundavelli, Ed.,
                    X. Zhou, J. Korhonen,
                    G. Feige, R. Koodli
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2013
        Mailbox:    sgundave@cisco.com, 
                    zhou.xingyue@zte.com.cn, 
                    jouni.nospam@gmail.com,
                    gfeige@cisco.com, 
                    rkoodli@cisco.com
        Pages:      14
        Characters: 34575
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-netext-pmipv6-sipto-option-12.txt

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

This specification defines a new mobility option, the IPv4 Traffic
Offload Selector option, for Proxy Mobile IPv6.  This option can be
used by the local mobility anchor and the mobile access gateway for
negotiating IPv4 traffic offload policy for a mobility session.
Based on the negotiated IPv4 traffic offload policy, a mobile access
gateway can selectively offload some of the IPv4 traffic flows in the
access network instead of tunneling back to the local mobility anchor
in the home network.

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

This is now a Proposed Standard.

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