One document matched: draft-rosen-vpn-mpls-01.txt

Differences from draft-rosen-vpn-mpls-00.txt

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


        RFC 2547: 

        Title:	    BGP/MPLS VPNs    
	Author(s):  E. Rosen, Y. Rekhter
        Status:     Informational
	Date:       March 1999
        Mailbox:    erosen@cisco.com, yakov@cisco.com
	Pages:      25
        Characters: 63270
        Updates/Obsoletes/See Also: None  
        I-D Tag:    draft-rose-vpm-mpls-01.txt


        URL:        ftp://ftp.isi.edu/in-notes/rfc2547.txt


This document describes a method by which a Service Provider with an
IP backbone may provide VPNs (Virtual Private Networks) for its
customers.  MPLS (Multiprotocol Label Switching) is used for
forwarding packets over the backbone, and BGP (Border Gateway
Protocol) is used for distributing routes over the backbone.  The
primary goal of this method is to support the outsourcing of IP
backbone services for enterprise networks. It does so in a manner
which is simple for the enterprise, while still scalable and flexible
for the Service Provider, and while allowing the Service Provider to
add value. These techniques can also be used to provide a VPN which
itself provides IP service to customers.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Alegre Ramos
USC/Information Sciences Institute