RFC 4365 on Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs)

rfc-editor@rfc-editor.org Sat, 04 February 2006 00:27 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 1F5BH2-0000z0-CL; Fri, 03 Feb 2006 19:27:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BGx-0000ws-Sz; Fri, 03 Feb 2006 19:27:27 -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 TAA02484; Fri, 3 Feb 2006 19:25:32 -0500 (EST)
Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F5BSN-0006Wl-Vt; Fri, 03 Feb 2006 19:39:16 -0500
Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140RA55009705; Fri, 3 Feb 2006 16:27:10 -0800
Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k140RADD009704; Fri, 3 Feb 2006 16:27:10 -0800
Date: Fri, 03 Feb 2006 16:27:10 -0800
Message-Id: <200602040027.k140RADD009704@nit.isi.edu>
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="19f9bcac8770d2066f22c43e7af4c8fc"
X-Spam-Score: -13.9 (-------------)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4365 on Applicability Statement for BGP/MPLS IP Virtual Private Networks (VPNs)
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 Request for Comments is now available in online RFC libraries.

        
        RFC 4365

        Title:      Applicability Statement for BGP/MPLS IP 
                    Virtual Private Networks (VPNs) 
        Author:     E. Rosen
        Status:     Informational
        Date:       February 2006
        Mailbox:    erosen@cisco.com
        Pages:      32
        Characters: 77924
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-as2547-07.txt

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

This document provides an Applicability Statement for the
Virtual Private Network (VPN) solution described in RFC 4364
and other documents listed in the References section.  This memo provides information for the Internet community.

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

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 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.

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 Sandy Ginoza
USC/Information Sciences Institute

...

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

        
        RFC 4365

        Title:      Applicability Statement for BGP/MPLS IP 
                    Virtual Private Networks (VPNs) 
        Author:     E. Rosen
        Status:     Informational
        Date:       February 2006
        Mailbox:    erosen@cisco.com
        Pages:      32
        Characters: 77924
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l3vpn-as2547-07.txt

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

This document provides an Applicability Statement for the
Virtual Private Network (VPN) solution described in RFC 4364
and other documents listed in the References section.  This memo provides information for the Internet community.

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

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 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.

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 Sandy Ginoza
USC/Information Sciences Institute

...