RFC 5195 on BGP-Based Auto-Discovery for Layer-1 VPNs

rfc-editor@rfc-editor.org Sat, 07 June 2008 00:03 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id B4C3E3A68C7; Fri, 6 Jun 2008 17:03:00 -0700 (PDT)
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 E86863A6A38 for <ietf-announce@core3.amsl.com>; Fri, 6 Jun 2008 17:02:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.106
X-Spam-Status: No, score=-16.106 tagged_above=-999 required=5 tests=[AWL=-0.307, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_14=0.6, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id EDrPPHn34XXG for <ietf-announce@core3.amsl.com>; Fri, 6 Jun 2008 17:02:58 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id 23C053A6830 for <ietf-announce@ietf.org>; Fri, 6 Jun 2008 17:02:58 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id F0C67135881; Fri, 6 Jun 2008 17:03:08 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5195 on BGP-Based Auto-Discovery for Layer-1 VPNs
From: rfc-editor@rfc-editor.org
Message-Id: <20080607000308.F0C67135881@bosco.isi.edu>
Date: Fri, 6 Jun 2008 17:03:08 -0700 (PDT)
Cc: l1vpn-chairs@tools.ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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 5195

        Title:      BGP-Based Auto-Discovery for Layer-1 VPNs 
        Author:     H. Ould-Brahim, D. Fedyk,
                    Y. Rekhter
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    hbrahim@nortel.com, 
        Pages:      10
        Characters: 21480
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-l1vpn-bgp-auto-discovery-05.txt

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

The purpose of this document is to define a BGP-based auto-discovery
mechanism for Layer-1 VPNs (L1VPNs).  The
auto-discovery mechanism for L1VPNs allows the provider network
devices to dynamically discover the set of Provider Edges (PEs) having
ports attached to Customer Edge (CE) members of the same VPN.  That
information is necessary for completing the signaling phase of L1VPN
connections.  One main objective of a L1VPN auto-discovery mechanism is
to support the "single-end provisioning" model, where addition of a
new port to a given L1VPN would involve configuration changes only on
the PE that has this port and on the CE that is connected to the PE
via this port.  [STANDARDS TRACK]

This document is a product of the Layer 1 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
USC/Information Sciences Institute

IETF-Announce mailing list