RFC 6732 on 6to4 Provider Managed Tunnels

rfc-editor@rfc-editor.org Sun, 30 September 2012 16:34 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 9A7F821F86F1 for <ietf-announce@ietfa.amsl.com>; Sun, 30 Sep 2012 09:34:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[AWL=0.271, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xfk8ZVuH8fIi for <ietf-announce@ietfa.amsl.com>; Sun, 30 Sep 2012 09:34:57 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id EACE721F86F0 for <ietf-announce@ietf.org>; Sun, 30 Sep 2012 09:34:56 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6EFAE72E110; Sun, 30 Sep 2012 09:30:41 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6732 on 6to4 Provider Managed Tunnels
From: rfc-editor@rfc-editor.org
Message-Id: <20120930163041.6EFAE72E110@rfc-editor.org>
Date: Sun, 30 Sep 2012 09:30:41 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Sun, 30 Sep 2012 16:34:57 -0000

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

        RFC 6732

        Title:      6to4 Provider Managed Tunnels 
        Author:     V. Kuarsingh, Ed.,
                    Y. Lee, O. Vautrin
        Status:     Informational
        Stream:     Independent
        Date:       September 2012
        Mailbox:    victor.kuarsingh@gmail.com, 
        Pages:      12
        Characters: 28156
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-kuarsingh-v6ops-6to4-provider-managed-tunnel-07.txt

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

6to4 Provider Managed Tunnels (6to4-PMT) provide a framework that
can help manage 6to4 tunnels operating in an anycast configuration.
The 6to4-PMT framework is intended to serve as an option for operators 
to help improve the experience of 6to4 operation when conditions of the 
network may provide sub-optimal performance or break normal 6to4 
operation. 6to4-PMT supplies a stable provider prefix and forwarding 
environment by utilizing existing 6to4 relays with an added function of 
IPv6 Prefix Translation.  This operation may be particularly important in 
NAT444 infrastructures where a customer endpoint may be assigned a 
non-RFC1918 address, thus breaking the return path for anycast-based 6to4 
operation.  6to4-PMT has been successfully used in a production network, 
implemented as open source code, and implemented by a major routing 
vendor.  This document is not an Internet Standards Track specification; 
it is published for informational purposes.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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