I-D ACTION:draft-ietf-l3vpn-ospf-2547-06.txt

Internet-Drafts@ietf.org Fri, 17 February 2006 23:50 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FAFMv-0002Br-18; Fri, 17 Feb 2006 18:50:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FAFMb-0001xe-Qx; Fri, 17 Feb 2006 18:50:13 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25549; Fri, 17 Feb 2006 18:48:25 -0500 (EST)
Received: from cypress.neustar.com ([209.173.57.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAFb6-0001JK-Hk; Fri, 17 Feb 2006 19:05:13 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by cypress.neustar.com (8.12.8/8.12.8) with ESMTP id k1HNo20e011035 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Feb 2006 23:50:02 GMT
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FAFMQ-0004Oq-64; Fri, 17 Feb 2006 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1FAFMQ-0004Oq-64@stiedprstage1.ietf.org>
Date: Fri, 17 Feb 2006 18:50:02 -0500
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 34d35111647d654d033d58d318c0d21a
Cc: l3vpn@ietf.org
Subject: I-D ACTION:draft-ietf-l3vpn-ospf-2547-06.txt
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: l3vpn.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Layer 3 Virtual Private Networks Working Group of the IETF.

	Title		: OSPF as the Provider/Customer Edge Protocol for BGP/MPLS IP VPNs
	Author(s)	: E. Rosen
	Filename	: draft-ietf-l3vpn-ospf-2547-06.txt
	Pages		: 26
	Date		: 2006-2-17
	
Many Service Providers offer Virtual Private Network ("VPN") services
to their customers, using a technique in which customer edge routers
("CE routers") are routing peers of provider edge routers ("PE
routers").  The Border Gateway Protocol ("BGP") is used to distribute
the customer's routes across the provider's IP backbone network, and
Multiprotocol Label Switching ("MPLS") is used to tunnel customer
packets across the provider's backbone.  This is known as a "BGP/MPLS
IP VPN".  The base specification for BGP/MPLS IP VPNs presumes that
the routing protocol on the interface between a PE router and a CE
router is BGP.  This document extends that specification by allowing
the routing protocol on the PE/CE interface to be the Open Shortest
Path First ("OSPF") protocol.

This document updates draft-ietf-l3vpn-rfc2547bis-03.txt.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ospf-2547-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-l3vpn-ospf-2547-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-l3vpn-ospf-2547-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-l3vpn-ospf-2547-06.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-l3vpn-ospf-2547-06.txt>