[Fwd: RFC 4664 on Framework for Layer 2 Virtual Private Networks (L2VPNs)]

Shane Amante <shane@castlepoint.net> Sun, 01 October 2006 16:51 UTC

Message-ID: <451FF208.4040506@castlepoint.net>
Date: Sun, 01 Oct 2006 10:51:20 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: l2vpn@ietf.org
Content-Type: multipart/mixed; boundary="------------030308010409020807040904"
Subject: [Fwd: RFC 4664 on Framework for Layer 2 Virtual Private Networks (L2VPNs)]
Precedence: list
Errors-To: l2vpn-bounces@ietf.org

Congratulations folks!  This looks like the first of a series of L2VPN 
RFC's to be published.

-shane

--- Begin Message ---

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

        
        RFC 4664

        Title:      Framework for Layer 2 Virtual 
                    Private Networks (L2VPNs) 
        Author:     L. Andersson, Ed.,
                    E. Rosen, Ed.
        Status:     Informational
        Date:       September 2006
        Mailbox:    loa@pi.se, 
                    erosen@cisco.com
        Pages:      44
        Characters: 97768
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2vpn-l2-framework-05.txt

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

This document provides a framework for Layer 2 Provider Provisioned
Virtual Private Networks (L2VPNs).  This framework is intended to aid
in standardizing protocols and mechanisms to support interoperable
L2VPNs.  This memo provides information for the Internet community.

This document is a product of the Layer 2 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

...

--- End Message ---

[Fwd: RFC 4664 on Framework for Layer 2 Virtual P… Shane Amante