RFC 6074 on Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)

rfc-editor@rfc-editor.org Tue, 18 January 2011 20:30 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id E8D7828C1C6; Tue, 18 Jan 2011 12:30:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.811
X-Spam-Status: No, score=-101.811 tagged_above=-999 required=5 tests=[AWL=-0.734, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id gk0NxuoQqMuj; Tue, 18 Jan 2011 12:30:18 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com []) by core3.amsl.com (Postfix) with ESMTP id 0CAF528C1D1; Tue, 18 Jan 2011 12:30:18 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4A9F3E0741; Tue, 18 Jan 2011 12:32:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6074 on Provisioning, Auto-Discovery, and Signaling in Layer 2 Virtual Private Networks (L2VPNs)
From: rfc-editor@rfc-editor.org
Message-Id: <20110118203256.4A9F3E0741@rfc-editor.org>
Date: Tue, 18 Jan 2011 12:32:56 -0800
Cc: l2vpn@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jan 2011 20:30:19 -0000

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

        RFC 6074

        Title:      Provisioning, Auto-Discovery, and Signaling in 
                    Layer 2 Virtual Private Networks (L2VPNs) 
        Author:     E. Rosen, B. Davie,
                    V. Radoaca, W. Luo
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2011
        Mailbox:    erosen@cisco.com, 
                    vasile.radoaca@alcatel-lucent.com,  luo@weiluo.net
        Pages:      32
        Characters: 76543
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l2vpn-signaling-08.txt

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

Provider Provisioned Layer 2 Virtual Private Networks (L2VPNs) may
have different "provisioning models", i.e., models for what
information needs to be configured in what entities.  Once
configured, the provisioning information is distributed by a
"discovery process".  When the discovery process is complete, a
signaling protocol is automatically invoked to set up the mesh of
pseudowires (PWs) that form the (virtual) backbone of the L2VPN.
This document specifies a number of L2VPN provisioning models, and
further specifies the semantic structure of the endpoint identifiers
required by each model.  It discusses the distribution of these
identifiers by the discovery process, especially when discovery is
based on the Border Gateway Protocol (BGP).  It then specifies how
the endpoint identifiers are carried in the two signaling protocols
that are used to set up PWs, the Label Distribution Protocol (LDP),
and the Layer 2 Tunneling Protocol version 3 (L2TPv3).  [STANDARDS-

This document is a product of the Layer 2 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC