[PWE3] PWE3 Charter Update - **DRAFT Charter v0.1**
Danny McPherson <danny@tcb.net> Fri, 02 May 2008 13:50 UTC
Return-Path: <pwe3-bounces@ietf.org>
X-Original-To: pwe3-archive@megatron.ietf.org
Delivered-To: ietfarch-pwe3-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80F243A6940; Fri, 2 May 2008 06:50:49 -0700 (PDT)
X-Original-To: pwe3@core3.amsl.com
Delivered-To: pwe3@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D28AD3A6940 for <pwe3@core3.amsl.com>; Fri, 2 May 2008 06:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_41=0.6]
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 QpBa664kvsrY for <pwe3@core3.amsl.com>; Fri, 2 May 2008 06:50:46 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id BDD953A6882 for <pwe3@ietf.org>; Fri, 2 May 2008 06:50:46 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id CC302268493; Fri, 2 May 2008 07:50:48 -0600 (MDT)
Received: from [192.168.1.103] (VDSL-151-118-146-11.DNVR.QWEST.NET [151.118.146.11]) (authenticated-user smtp) (TLSv1/SSLv3 AES128-SHA 128/128) by dog.tcb.net with SMTP; for pwe3@ietf.org; Fri, 02 May 2008 07:50:48 -0600 (MDT) (envelope-from danny@tcb.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=151.118.146.11; client-port=50572; syn-fingerprint=65535:55:1:64:M1316,N,W3,N,N,T,S; data-bytes=0
Message-Id: <3EBA4713-4631-4148-8DD6-B108A8BC5519@tcb.net>
From: Danny McPherson <danny@tcb.net>
To: pwe3@ietf.org
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Fri, 02 May 2008 07:50:33 -0600
X-Mailer: Apple Mail (2.919.2)
Subject: [PWE3] PWE3 Charter Update - **DRAFT Charter v0.1**
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: pwe3-bounces@ietf.org
Errors-To: pwe3-bounces@ietf.org
Folks, Time for that periodic charter refresh and update. If you've got comments, send'm along, as we'd like to get this off to the IAB for approval. Please consider this a 2 week call for input, ending on 5/16. Thanks much! -danny ---- v0.1 Pseudowire Emulation Edge to Edge (pwe3) Additional information is available at http://tools.ietf.org/wg/pwe3 Chair(s): Danny McPherson <danny@arbor.net> Stewart Bryant <stbryant@cisco.com> Internet Area Director(s): Jari Arkko <jari.arkko@piuha.net> Mark Townsley <townsley@cisco.com> Internet Area Advisor: Mark Townsley <townsley@cisco.com> Technical Advisor(s): Allison Mankin <mankin@psg.com> Secretary(ies): Matthew Bocci <matthew.bocci@alcatel-lucent.co.uk> Mailing Lists: General Discussion: pwe3@ietf.org To Subscribe: pwe3-request@ietf.org In Body: subscribe your_email_address Archive: http://www.ietf.org/mail-archive/web/pwe3/index.html Description of Working Group: Network transport service providers and their users are seeking to rationalize their networks by migrating their existing services and platforms onto IP or MPLS enabled IP packet switched networks (PSN). This migration requires communications services that can emulate the essential properties of traditional communications links over a PSN. Some service providers wish to use MPLS technology to replace existing transport network infrastructure, relying upon pseudowire technology is an integral component of these network convergence architectures. Pseudowire Emulation Edge to Edge (PWE3) will specify the encapsulation, transport, control, management, interworking and security of services emulated over IETF-specified PSNs. A pseudowire emulates a point-to-point or point-to-multipoint link, and provides a single service which is perceived by its user as an unshared link or circuit of the chosen service. It is not intended that an emulated service will be indistinguishable from the service that is being emulated. The emulation need only be sufficient for the satisfactory operation of the service. Emulation necessarily involves a degree of cost-performance trade-off. In some cases it may be necessary to design more than one emulation mechanism in order to resolve these design conflicts. All emulated service definitions must include an applicability statement describing the faithfulness of the emulation. Switching, multiplexing, modification or other operation on the traditional service, unless required as part of the emulation, is out of the scope of the PWE3 WG. PWE3 will make use of existing IETF-specified mechanisms unless there are technical reasons why the existing mechanisms are insufficient or unnecessary. PWE3 operates "edge to edge" and will not exert control on the underlying PSN, other than to use any existing QoS or path control mechanism to provide the required connectivity between the endpoints of the PW. PWE3 will specify requirements for clock recovery and other real-time signaling functions needed by PW types that it is designing. It will co-ordinate this with the AVT and TICTOC WGs. Where AVT or TICTOC require extensions to PWs to support time or frequency transfer this work will be undertaken by the PWE3 WG in co-ordination with the these WGs. A PW operating over a shared PSN does not necessarily have the same intrinsic security as a dedicated, purpose built, network. In some cases this is satisfactory, while in other cases it will be necessary to enhance the security of the PW to emulate the intrinsic security of the emulated service. PW specifications MUST include a description of how they are to be operated over a shared PSN with adequate security. PWE3 will work with the MPLS, L2VPN and other relevant WGs for definitions of common solutions for the secure operation of pseudowires. Whilst a service provider may traffic engineer their network in such a way that PW traffic will not cause significant congestion, a PW deployed by an end-user may cause congestion of the underlying PSN. Suitable congestion avoidance mechanisms are therefore needed to protect the Internet from the unconstrained deployment of PWs. PWE3 will work closely with the L2VPN WG to ensure a clear demarcation is defined for where PWE3 stops and L2VPN starts, in particular in defining point-multipoint (P2MP) PWs. PWE3 will work with MPLS and L2VPN to enhance the OAM suite for transport applications. PWE3 will coordinate very closely with any WG that is responsible for protocols which PWE3 intends to extend (e.g., the MPLS WG for LDP), as well as foster interaction with WGs that intend to extend PWE3 protocols. The IETF PWE3 WG is the design authority for pseudo-wire over IP/MPLS PSN technology. Extensions to this work by other SDOs needs to invoke the MPLS Change Process, as provided in RFC 4929. WG Objectives: Specify the following PW types: Most of the initial specific PW types have been specified (e.g., Frame Realy, Ethernet, ATM). Investigation into and specification of a "generic PW" type and/or MPLS PW should be undertaken. PWE3 will specify a PW type for the special case where the access service payloads at both ends are known to consist entirely of IP packets. PWE3 will not specify mechanisms by which a PW connects two different access services unless the Network Layer protocol is IP. Specify the control and management functions of chartered PW types, to include PW setup, configuration, maintenance and tear-down. The PWE3 WG will do this in its entirety for MPLS PSNs, and the L2TPEXT WG will develop the L2TP specifics for L2TPv3-based PWs. Specify Operations and Management (OAM) mechanisms for all PW types, suitable for operation over both IP/L2TPv3 and MPLS PSNs, and capable of providing the necessary interworking with the OAM mechanisms of the emulated service. Define requirements for and mechanisms to provide interconnection of PWs (to include inter-domain PWs). Define requirements for and mechanisms to provide protection and restoration of PWs. Publish document outlining PW-specific congestion avoidance and response guidelines. Publish document outlining PW-specific security considerations. Publish specification for enabling P2MP PWs. Publish requirements and specification for PW load-balancing mechanisms. Publish requirements and specification for enhanced OAM. Publish requirements and specifications to provide the necessary extensions to PWs to support the applications of MPLS to transport networks. _______________________________________________ pwe3 mailing list pwe3@ietf.org https://www.ietf.org/mailman/listinfo/pwe3
- [PWE3] PWE3 Charter Update - **DRAFT Charter v0.1… Danny McPherson
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Danny McPherson
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Alexander Vainshtein
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Danny McPherson
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Yaakov Stein
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Stewart Bryant
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Loa Andersson
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Alexander Vainshtein
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Stewart Bryant
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Yaakov Stein
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Ben Niven-Jenkins
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Alexander Vainshtein
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Stewart Bryant
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Rahul Aggarwal
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Yaakov Stein
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … BOCCI Matthew
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Yaakov Stein
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … BOCCI Matthew
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … frederic.jounay
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Maarten Vissers
- Re: [PWE3] PWE3 Charter Update - **DRAFT Charter … Maarten Vissers