RFC 5747 on 4over6 Transit Solution Using IP Encapsulation and MP-BGP Extensions

rfc-editor@rfc-editor.org Wed, 10 March 2010 19:18 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 7ECB83A6C47 for <ietf-announce@core3.amsl.com>; Wed, 10 Mar 2010 11:18:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.478
X-Spam-Level:
X-Spam-Status: No, score=-2.478 tagged_above=-999 required=5 tests=[AWL=0.122, BAYES_00=-2.599, 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 Wm2kETWxA9Yw for <ietf-announce@core3.amsl.com>; Wed, 10 Mar 2010 11:18:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 78D633A6A10 for <ietf-announce@ietf.org>; Wed, 10 Mar 2010 11:18:08 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id EB1CCE073B; Wed, 10 Mar 2010 11:18:13 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5747 on 4over6 Transit Solution Using IP Encapsulation and MP-BGP Extensions
From: rfc-editor@rfc-editor.org
Message-Id: <20100310191813.EB1CCE073B@rfc-editor.org>
Date: Wed, 10 Mar 2010 11:18:13 -0800 (PST)
Cc: 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: Wed, 10 Mar 2010 19:18:43 -0000

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

        
        RFC 5747

        Title:      4over6 Transit Solution Using IP 
                    Encapsulation and MP-BGP Extensions 
        Author:     J. Wu, Y. Cui,
                    X. Li, M. Xu,
                    C. Metz
        Status:     Experimental
        Date:       March 2010
        Mailbox:    jianping@cernet.edu.cn, 
                    cy@csnet1.cs.tsinghua.edu.cn, 
                    xing@cernet.edu.cn,  xmw@csnet1.cs.tsinghua.edu.cn, 
                    chmetz@cisco.com
        Pages:      15
        Characters: 33768
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-wu-softwire-4over6-04.txt

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

The emerging and growing deployment of IPv6 networks will introduce
cases where connectivity with IPv4 networks crossing IPv6 transit
backbones is desired.  This document describes a mechanism for
automatic discovery and creation of IPv4-over-IPv6 tunnels via
extensions to multiprotocol BGP.  It is targeted at connecting
islands of IPv4 networks across an IPv6-only backbone without the
need for a manually configured overlay of tunnels.  The mechanisms
described in this document have been implemented, tested, and
deployed on the large research IPv6 network in China.  This document
defines an Experimental Protocol for the Internet community.

This document is an Independent Submission.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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