[L1vpn] First basic Mode Protocol RFC Published
"Adrian Farrel" <adrian@olddog.co.uk> Sat, 07 June 2008 01:01 UTC
Return-Path: <l1vpn-bounces@ietf.org>
X-Original-To: l1vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l1vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C87553A6AEE; Fri, 6 Jun 2008 18:01:45 -0700 (PDT)
X-Original-To: l1vpn@core3.amsl.com
Delivered-To: l1vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 35F613A6BC6 for <l1vpn@core3.amsl.com>; Fri, 6 Jun 2008 18:01:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[AWL=-0.900, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_14=0.6, J_CHICKENPOX_93=0.6, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cTy93fJ5SALK for <l1vpn@core3.amsl.com>; Fri, 6 Jun 2008 18:01:44 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by core3.amsl.com (Postfix) with ESMTP id DCBE23A6AEE for <l1vpn@ietf.org>; Fri, 6 Jun 2008 18:01:43 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.8) with ESMTP id m5711q6D021689 for <l1vpn@ietf.org>; Sat, 7 Jun 2008 02:01:52 +0100
Received: from your029b8cecfe (softbank221017113241.bbtec.net [221.17.113.241]) (authenticated bits=0) by asmtp1.iomartmail.com (8.12.11.20060308/8.12.11) with ESMTP id m5711mIp021682 for <l1vpn@ietf.org>; Sat, 7 Jun 2008 02:01:51 +0100
Message-ID: <003101c8c83a$1085ed50$1d01fe0a@your029b8cecfe>
From: Adrian Farrel <adrian@olddog.co.uk>
To: l1vpn@ietf.org
Date: Sat, 07 Jun 2008 02:01:43 +0100
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198
Subject: [L1vpn] First basic Mode Protocol RFC Published
X-BeenThere: l1vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Adrian Farrel <adrian@olddog.co.uk>
List-Id: Layer 1 Virtual Private Networks <l1vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/l1vpn>
List-Post: <mailto:l1vpn@ietf.org>
List-Help: <mailto:l1vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l1vpn>, <mailto:l1vpn-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: l1vpn-bounces@ietf.org
Errors-To: l1vpn-bounces@ietf.org
Hi, After a long IESG review process, the RFC Editor has been remarkably efficient, and the working group has a new RFC. Many thanks to the authors for their hard work. Adrian per pro Tomonori and Hamid ----- Original Message ----- From: <rfc-editor@rfc-editor.org> To: <ietf-announce@ietf.org>; <rfc-dist@rfc-editor.org> Cc: <rfc-editor@rfc-editor.org>; <l1vpn-chairs@tools.ietf.org> Sent: Saturday, June 07, 2008 1:03 AM Subject: RFC 5195 on BGP-Based Auto-Discovery for Layer-1 VPNs > 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, > yakov@juniper.net, > dwfedyk@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. _______________________________________________ L1vpn mailing list L1vpn@ietf.org https://www.ietf.org/mailman/listinfo/l1vpn
- [L1vpn] First basic Mode Protocol RFC Published Adrian Farrel