RE: Protocol Action: 'OSPFv3 as a PE-CE routing protocol' to Proposed Standard
Ross Callon <rcallon@juniper.net> Fri, 05 February 2010 17:41 UTC
Return-Path: <rcallon@juniper.net>
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4FB7B28C1DC; Fri, 5 Feb 2010 09:41:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.027
X-Spam-Level:
X-Spam-Status: No, score=-6.027 tagged_above=-999 required=5 tests=[AWL=-0.028, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 riRHAnN3eHKf; Fri, 5 Feb 2010 09:41:42 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by core3.amsl.com (Postfix) with ESMTP id 41D0628C189; Fri, 5 Feb 2010 09:41:38 -0800 (PST)
Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKS2xYhFjvpwyLVMrM8IXTk9pJX41fuXI3@postini.com; Fri, 05 Feb 2010 09:42:33 PST
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.1.393.1; Fri, 5 Feb 2010 09:41:19 -0800
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 5 Feb 2010 12:41:18 -0500
From: Ross Callon <rcallon@juniper.net>
To: The IESG <iesg-secretary@ietf.org>, IETF-Announce <ietf-announce@ietf.org>
Date: Fri, 05 Feb 2010 12:39:29 -0500
Subject: RE: Protocol Action: 'OSPFv3 as a PE-CE routing protocol' to Proposed Standard
Thread-Topic: Protocol Action: 'OSPFv3 as a PE-CE routing protocol' to Proposed Standard
Thread-Index: AcqCYwurkGappoAxTYqyUIRItTZ5gQkJGv3Q
Message-ID: <DF7F294AF4153D498141CBEFADB177049A1B7CBB5B@EMBX01-WF.jnpr.net>
References: <20091221172849.625393A6A64@core3.amsl.com>
In-Reply-To: <20091221172849.625393A6A64@core3.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "ospf@ietf.org" <ospf@ietf.org>, l3vpn chair <l3vpn-chairs@tools.ietf.org>, Internet Architecture Board <iab@iab.org>, l3vpn mailing list <l3vpn@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Feb 2010 17:41:43 -0000
The authors, in response to comments received since this approval, have decided to make a further update to this document (as has been announced to the L3VPN and OSPF email lists in recent mail from the authors). We have therefore taken the unusual step of unapproving this document and returning it to the WG for additional work. Thanks, Ross (as AD for the L3VPN WG) -----Original Message----- From: ietf-announce-bounces@ietf.org [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The IESG Sent: 21 December 2009 12:29 To: IETF-Announce Cc: l3vpn chair; Internet Architecture Board; l3vpn mailing list; RFC Editor Subject: Protocol Action: 'OSPFv3 as a PE-CE routing protocol' to Proposed Standard The IESG has approved the following document: - 'OSPFv3 as a PE-CE routing protocol ' <draft-ietf-l3vpn-ospfv3-pece-04.txt> as a Proposed Standard This document is the product of the Layer 3 Virtual Private Networks Working Group. The IESG contact persons are Ross Callon and Adrian Farrel. A URL of this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-l3vpn-ospfv3-pece-04.txt Technical Summary Many Service Providers (SPs) offer Virtual Private Network (VPN) services to their customers using a technique in which Customer Edge (CE) routers are routing peers of Provider Edge (PE) routers. The Border Gateway Protocol (BGP) is used to distribute the customer's routes across the provider's IP backbone network, and Multiprotocol Label Switching (MPLS) is used to tunnel customer packets across the provider's backbone. This is known as a "BGP/MPLS IP VPN". Originally only IPv4 was supported and it was later extended to support IPv6 VPNs as well. Extensions were later added for the support of the Open Shortest Path First protocol version 2 (OSPFv2) as a PE-CE routing protocol for the IPv4 VPNs. This document extends those specifications to support OSPF version 3 (OSPFv3) as a PE-CE routing protocol. The OSPFv3 PE-CE functionality is very similar to the previously-specified approached for OSPFv2. Working Group Summary No controversy reported (see PROTO writeup by Danny McPherson in the ID Tracker). There were no objections during the WG Last Call on the document, and the utility of this specification is straight-forward, as well as both obvious and intuitive. Document Quality No known implementations. Personnel Danny McPherson is the Document Shepherd for this document. Ross Callon is the Responsible Area Director. RFC Editor Note All references to [BGP-EXTCOMM-IPV6] should be replaced by a references to [RFC5701]. In the informative references section (11.2), please remove the reference to [BGP-EXTCOMM-IPV6]. Please add a reference to RFC5701 in the normative references section (11.1). _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce