RFC 4364 on BGP/MPLS IP Virtual Private Networks (VPNs)

[[e-mail]]

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

        
        RFC 4364

        Title:      BGP/MPLS IP Virtual Private Networks 
                    (VPNs) 
        Author:     E. Rosen,  Y. Rekhter
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    [e-mail], 
                    [e-mail]
        Pages:      47
        Characters: 116446
        Obsoletes:  RFC2547
        See-Also:   

        I-D Tag:    draft-ietf-l3vpn-rfc2547bis-03.txt

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

This document describes a method by which a Service Provider may use
an IP backbone to provide IP Virtual Private Networks (VPNs) for its
customers.  This method uses a \"peer model\", in which the customers\'
edge routers (CE routers) send their routes to the Service
Provider\'s edge routers (PE routers); there is no \"overlay\" visible
to the customer\'s routing algorithm, and CE routers at different
sites do not peer with each other.  Data packets are tunneled through
the backbone, so that the core routers do not need to know the VPN
routes.  [STANDARDS TRACK]

This document is a product of the Layer 3 Virtual Private Networks Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 

help: ways_to_get_rfcs. For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

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

        
        RFC 4364

        Title:      BGP/MPLS IP Virtual Private Networks 
                    (VPNs) 
        Author:     E. Rosen,  Y. Rekhter
        Status:     Standards Track
        Date:       February 2006
        Mailbox:    [e-mail], 
                    [e-mail]
        Pages:      47
        Characters: 116446
        Obsoletes:  RFC2547
        See-Also:   

        I-D Tag:    draft-ietf-l3vpn-rfc2547bis-03.txt

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

This document describes a method by which a Service Provider may use
an IP backbone to provide IP Virtual Private Networks (VPNs) for its
customers.  This method uses a \"peer model\", in which the customers\'
edge routers (CE routers) send their routes to the Service
Provider\'s edge routers (PE routers); there is no \"overlay\" visible
to the customer\'s routing algorithm, and CE routers at different
sites do not peer with each other.  Data packets are tunneled through
the backbone, so that the core routers do not need to know the VPN
routes.  [STANDARDS TRACK]

This document is a product of the Layer 3 Virtual Private Networks Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body 

help: ways_to_get_rfcs. For example:

        To: [e-mail]
        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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ietf-announce