Pseudowire Emulation Edge to Edge (pwe3)

In addition to this official charter maintained by the IETF Secretariat, there is additional information about this working group on the Web at:

       MPLS Architectural Considerations for a Transport Profile (PDF)

Last Modified: 2008-04-23

Additional information is available at 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.

    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 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 two endpoints of the PW.

    PWE3 will investigate mechanisms necessary to perform clock
    recovery and other real-time signaling functions. This work will
    be coordinated with the AVT WG and RTP will be used where
    appropriate.

    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.

    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.
    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.

    WG Objectives:

    Specify the following PW types:

    Ethernet, Frame Relay, PPP, HDLC, ATM, low-rate TDM,
    SONET/SDH and Fibre Channel.

    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.

    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.

    Further enhance PW specifications to enable more transparent
    emulation when necessary, for example the retention of FCS
    across a PW.

    Define a mechanism for MPLS PWs that provides interoperability
    with currently deployed equal cost multiple path (ECMP)
    algorithms such that packets for a given PW follow the same
    path through an MPLS PSN.

    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.

    Goals and Milestones:

    Done  PWE3 WG started, organize editing teams.
    Done  Hold interim meeting, including discussion of priority of service-specific documents and consider pruning some deliverables
    Done  Accept drafts of service-specific documents as WG items
    Done  PW Requirements Document Last Call
    Done  TDM Circuit Documents Last Call
    Done  ATM Documents Last Call
    Done  Ethernet Documents Last Call
    Done  Fragmentation LC
    Done  TDM Requirements LC
    Done  SONET Documents Last Call
    Done  TDM Documents Last Call
    Done  Frame Relay Documents Last Call
    Done  FCS retention Last Call
    Done  Multi-Segment PW Requirements LC
    Done  VCCV LC
    Done  PWE3 Services MIBs LC
    Done  PPP/HDLC PW LC
    Done  Wildcard FEC LC
    Apr 2007  PW OAM Mapping LC
    May 2007  Fiber Channel LC
    May 2007  Multi-Segment PW Architecture LC
    Jun 2007  TDM Signaling LC
    Sep 2007  PW Protection and Restoration Architecture
    Sep 2007  PW Protection and Restoration Requirements LC
    Nov 2007  Multi-Segment PW LC
    May 2008  PW Protection and Restoration LC

    Internet-Drafts:

    Pseudowire (PW) Management Information Base (MIB) (128939 bytes)
    Pseudowire (PW) over MPLS PSN Management Information Base (MIB) (62692 bytes)
    Definitions of Textual Conventions for Pseudowires (PW) Management (21643 bytes)
    SONET/SDH Circuit Emulation Service Over Packet (CEP) Management Information Base (MIB) Using SMIv2 (131124 bytes)
    Ethernet Pseudowire (PW) Management Information Base (MIB) (44473 bytes)
    Managed Objects for ATM over Packet Switched Network (PSN) (72733 bytes)
    Managed Objects for TDM over Packet Switched Network (PSN) (80323 bytes)
    Pseudo Wire (PW) OAM Message Mapping (66030 bytes)
    Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge (PWE3) (61006 bytes)
    Segmented Pseudo Wire (89579 bytes)
    Control Protocol Extensions for Setup of TDM Pseudowires in MPLS Networks (33166 bytes)
    Dynamic Placement of Multi Segment Pseudo Wires (40762 bytes)
    Encapsulation Methods for Transport of Fibre Channel frames Over MPLS Networks (122055 bytes)
    Application of Ethernet Pseudowires to MPLS Transport Networks (24319 bytes)
    Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV) (28048 bytes)
    Preferential Forwarding Status bit definition (66683 bytes)
    Pseudowire (PW) Redundancy (32794 bytes)

    Request For Comments:

    Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3) (RFC 3916) (43856 bytes)
    PWE3 Architecture (RFC 3985) (95062 bytes)
    Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks (RFC 4197) (47937 bytes)
    Pseudowire Emulation Edge-to-Edge (PWE3) Control Word for Use over an MPLS PSN (RFC 4385) (22440 bytes)
    Encapsulation Methods for Transport of Ethernet Over MPLS Networks (RFC 4448) (49012 bytes)
    Pseudowire Setup and Maintenance using the Label Distribution Protocol (LDP) (RFC 4447) (76204 bytes)
    IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3) (RFC 4446) (19782 bytes)
    Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) (RFC 4553) (58141 bytes)
    Pseudowire Emulation Edge-to-Edge (PWE3) Fragmentation and Reassembly (RFC 4623) (36369 bytes)
    Encapsulation Methods for Transport of PPP/High-Level Data Link Control (HDLC) over MPLS Networks (RFC 4618) (33141 bytes)
    Encapsulation Methods for Transport of Frame Relay Over MPLS Networks (RFC 4619) (38193 bytes)
    Pseudowire Emulation Edge-to-Edge (PWE3) Frame Check Sequence Retention (RFC 4720) (18248 bytes)
    Encapsulation Methods for Transport of Asynchronous Transfer Mode (ATM) over MPLS Networks (RFC 4717) (86173 bytes)
    Pseudowire Emulation Edge-to-Edge (PWE3) Asynchronous Transfer Mode (ATM) Transparent Cell Transport Service (RFC 4816) (10269 bytes)
    Synchronous Optical Network/Synchronous Digital Hierarchy SONET/SDH) Circuit Emulation over Packet (CEP)) (RFC 4842) (96719 bytes) obsoletes RFC 5143
    Wildcard Pseudowire Type (RFC 4863) (11321 bytes)
    Attachment Individual Identifier (AII) Types for Aggregation (RFC 5003) (14559 bytes)
    Time Division Multiplexing over IP (TDMoIP) (RFC 5087) (113071 bytes)
    Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN) (RFC 5086) (83233 bytes)
    Pseudowire Virtual Circuit Connectivity Verification (VCCV) A Control Channel for Pseudowires (RFC 5085) (67853 bytes)
    IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

    Return to working group directory.

    Return to IETF home page.