RFC 4176 on Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management

rfc-editor@rfc-editor.org Sat, 08 October 2005 00:55 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EO2zo-0005EV-7J; Fri, 07 Oct 2005 20:55:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EO2zm-0005Dy-3k; Fri, 07 Oct 2005 20:55:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06989; Fri, 7 Oct 2005 20:55:24 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EO399-0004Hf-Lc; Fri, 07 Oct 2005 21:05:09 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j980sML11044; Fri, 7 Oct 2005 17:54:22 -0700 (PDT)
Message-Id: <200510080054.j980sML11044@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 07 Oct 2005 17:54:22 -0700
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b
Cc: l3vpn@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 4176 on Framework for Layer 3 Virtual Private Networks (L3VPN) Operations and Management
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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


        RFC 4176

        Title:      Framework for Layer 3 Virtual Private Networks
                    (L3VPN) Operations and Management
        Author(s):  Y. El Mghazli, Ed., T. Nadeau, M. Boucadair,
                    K. Chan, A. Gonguet
        Status:     Informational
        Date:       October 2005
        Mailbox:    yacine.el_mghazli@alcatel.fr, tnadeau@cisco.com,
                    mohamed.boucadair@francetelecom.com,
                    khchan@nortel.com, arnaud.gonguet@alcatel.fr
        Pages:      21
        Characters: 46348
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-l3vpn-mgt-fwk-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4176.txt


This document provides a framework for the operation and management of
Layer 3 Virtual Private Networks (L3VPNs).  This framework intends to
produce a coherent description of the significant technical issues
that are important in the design of L3VPN management solutions.
The selection of specific approaches, and making choices among
information models and protocols are outside the scope of this
document. 

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

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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
ftp://ftp.isi.edu/in-notes/rfc4176.txt"><ftp://ftp.isi.edu/in-notes/rfc4176.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce