"Pseudowire (PW) Management Information Base (MIB)", Thomas Nadeau, David Zelig, 9-Jan-08. ( bytes)
This memo defines an experimental portion of the Management Information Base for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Pseudowire Edge-to-Edge services carried over a general Packet Switched Network.
"Pseudowire (PW) over MPLS PSN Management Information Base (MIB)", David Zelig, Thomas Nadeau, 9-Jan-08. ( bytes)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes a MIB module for PW operation over Multi- Protocol Label Switching (MPLS) Label Switch Router (LSR).
"Definitions of Textual Conventions for Pseudowires (PW) Management", Thomas Nadeau, David Zelig, Orly Nicklass, 9-Jan-08. ( bytes)
This memo defines a Management Information Base (MIB) module which contains Textual Conventions (TCs) to represent commonly-used Pseudowire (PW) management information. The intent is that these TCs will be imported and used in PW-related MIB modules that would otherwise define their own representations.
"SONET/SDH Circuit Emulation Service Over Packet (CEP) Management Information Base (MIB) Using SMIv2", David Zelig, Ron Cohen, Thomas Nadeau, 9-Jan-08. ( bytes)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling SONET/SDH circuits over a Packet Switch Network (PSN).
"Ethernet Pseudowire (PW) Management Information Base (MIB)", David Zelig, Thomas Nadeau, 9-Jan-08. ( bytes)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling of Ethernet Pseudowire (PW) services.
"Managed Objects for ATM over Packet Switched Network (PSN)", Orly Nicklass, Senthilkumar Sathappan, Marichetty Venkatesan, Thomas Nadeau, 21-Oct-08. ( bytes)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling ATM Pseudowire (PW) carrying ATM cells over Packet Switch Network (PSN).
"Managed Objects for TDM over Packet Switched Network (PSN)", Orly Nicklass, 21-Oct-08. ( bytes)
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for pseudo wire encapsulation for structured or unstructured TDM (T1, E1, T3, E3) circuits over a Packet Switch Network (PSN).
"Pseudo Wire (PW) OAM Message Mapping", Thomas Nadeau, Monique Morrow, Luca Martini, Carlos Pignataro, Dinesh Mohan, 3-Nov-08. ( bytes)
This document specifies the mapping of defect states between a Pseudo Wire and the Attachment Circuits (AC) of the end-to-end emulated service. This document covers the case whereby the ACs and the PWs are of the same type in accordance to the PWE3 architecture [RFC3985] such that a homogenous PW service can be constructed.
"Segmented Pseudo Wire", Thomas Nadeau, Chris Metz, Michael Duckett, Matthew Bocci, Florin Balus, Luca Martini, 25-Jul-08. ( bytes)
This document describes how to connect pseudowires (PW) between two distinct PW control planes or PSN domains. The PW control planes may belong to independent autonomous systems, or the PSN technology is heterogeneous, or a PW might need to be aggregated at a specific PSN point. The PW packet data units are simply switched from one PW to another without changing the PW payload.
"Dynamic Placement of Multi Segment Pseudo Wires", Luca Martini, Matthew Bocci, Nabil Bitar, Himanshu Shah, Mustapha Aissaoui, Florin Balus, 25-Jul-08. ( bytes)
There is a requirement for service providers to be able to extend the reach of pseudo wires (PW) across multiple Packet Switched Network domains. A Multi-Segment PW is defined as a set of two or more contiguous PW segments that behave and function as a single point- to-point PW. This document describes extensions to the PW control protocol to dynamically place the segments of the multi segment pseudo wire among a set of Provider Edge (PE) routers.
"An Architecture for Multi-Segment Pseudowire Emulation Edge-to-Edge", Matthew Bocci, Stewart Bryant, 25-Sep-08. ( bytes)
This document describes an architecture for extending pseudowire emulation across multiple packet switched network segments. Scenarios are discussed where each segment of a given edge-to-edge emulated service spans a different provider's PSN, and where the emulated service originates and terminates on the same providers PSN, but may pass through several PSN tunnel segments in that PSN. It presents an architectural framework for such multi-segment pseudowires, defines
"Encapsulation Methods for Transport of Fibre Channel frames Over MPLS Networks", Moran Roth, Tel Aviv, David Zelig, Tel Aviv, San Jose, 19-Aug-08. ( bytes)
A Fibre Channel pseudowire (PW) is used to carry Fibre Channel frames over an MPLS network. This enables service providers to offer "emulated" Fibre Channel services over existing MPLS networks. This document specifies the encapsulation of Fibre Channel PDUs within a pseudowire. It also specifies the procedures for using a PW to provide a Fibre Channel service.
"Pseudowire Congestion Control Framework", Stewart Bryant, Bruce Davie, Luca Martini, Eric Rosen, 28-May-08. ( bytes)
Pseudowires are sometimes used to carry non-TCP data flows. In these circumstances the service payload will not react to network congestion by reducing its offered load. Pseudowires should therefore reduces their network bandwidth demands in the face of significant packet loss, including if necessary completely ceasing transmission. Since it is difficult to determine a priori the number of equivalent TCP flow that a pseudowire represents, a suitably "fair" rate of back-off cannot be pre-determined. This document describes pseudowire congestion problem and provides guidance on the development suitable solutions.
"Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)", Thomas Nadeau, Carlos Pignataro, 25-Jun-08. ( bytes)
This document describes new Connectivity Verification (CV) types using Bidirectional Forwarding Detection (BFD) with Virtual Circuit Connectivity Verification (VCCV). VCCV provides a control channel that is associated with a Pseudowire (PW), as well as the corresponding operations and management functions such as connectivity verification to be used over that control channel.
"Preferential Forwarding Status bit definition", Praveen Muley, Matthew Bocci, Luca Martini, 30-Sep-08. ( bytes)
This document describes a mechanism for standby status signaling of redundant PWs between their termination points. A set of redundant PWs is configured between PE nodes in SS-PW applications, or between T-PE nodes in MS-PW applications. In order for the PE/T-PE nodes to indicate the preferred PW path to forward to one another, a new status bit is needed to indicate a preferential forwarding status of active or standby for each PW in the redundancy set. In addition, a second status bit is defined to allow peer PE/T-PE nodes to coordinate a switchover operation of the PW/MS-PW path.
"Pseudowire (PW) Redundancy", Praveen Muley, Matthew Bocci, 30-Sep-08. ( bytes)
This document describes a framework comprised of few scenarios and associated requirements where PW redundancy is needed. A set of redundant PWs is configured between PE nodes in SS-PW applications, or between T-PE nodes in MS-PW applications. In order for the PE/T-PE nodes to indicate the preferred PW path to forward to one another, a new status is needed to indicate the preferential forwarding status of active or standby for each PW in the redundancy set.
"Requirements for Point-to-Multipoint Pseudowire", Frederic JOUNAY, Philippe Niger, Yuji Kamite, Simon DeLord, Luca Martini, 4-Sep-08. ( bytes)
This document presents a set of requirements for providing an unidirectional Point-to-Multipoint PWE3 (Pseudowire Emulation Edge to Edge) emulation. The requirements identified in this document are related to architecture, signaling and maintenance aspects of a Point-to-Multipoint PW operation. They are proposed as guidelines for the standardization of such mechanisms. Among other potential applications Point-to-Multipoint PWs SHOULD be used to optimize the support of multicast services as defined in the Layer 2 Virtual Private Network working group.

IETF Secretariat - Please send questions, comments, and/or suggestions to ietf-web@ietf.org.

Return to Internet-Draft directory.

Return to IETF home page.