-
"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).
-
"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, 20-Feb-09. ( 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", Luca Martini, Thomas Nadeau, Mustapha Aissaoui, David Allan, Yaakov Stein, 25-Jun-09. ( bytes)
- This document specifies the mapping and notification 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 Pseudowire", Luca Martini, Thomas Nadeau, Chris Metz, Michael Duckett, Matthew Bocci, Florin Balus, Mustapha Aissaoui, 3-Jun-09. ( 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, 9-Mar-09. ( 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-Feb-09. ( 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, Munefumi Tsurusawa, Ronen Solomon, David Zelig, 16-Jan-09. ( 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 common procedures for using a PW to
provide a Fibre Channel service. The mechanisms controlling the
reliable transport of Fibre Channel PW over MPLS networks are
specified in a companion document [FC-flow].
-
"Pseudowire Congestion Control Framework", Stewart Bryant, Bruce Davie, Luca Martini, Eric Rosen, 17-Jun-09. ( 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.
-
"Application of Ethernet Pseudowires to MPLS Transport Networks", Stewart Bryant, Monique Morrow, George Swallow, Thomas Nadeau, Neil Harrison, Ben Niven-Jenkins, 29-Jun-09. ( bytes)
- A requirement has been identified by the operator community for the
transparent carriage of the MPLS(-TP) network of one party over the
MPLS(-TP) network of another party. This document describes a method
of satisfying this need using the existing PWE3 Ethernet pseudowire
standard RFC4448.
-
"Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV)", Thomas Nadeau, Carlos Pignataro, 5-Jun-09. ( 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.
-
"LDP extensions for AII reachability", Luca Martini, Simon DeLord, Frederic JOUNAY, Philippe Niger, Mustapha Aissaoui, Matthew Bocci, 28-May-09. ( bytes)
- The dynamic End-to-End Multisegment pseudowire setup requires PEs to
maintain a pseudowire routing table when using FEC129. There is a
requirement to automatically advertise Attachment Individual
Identifiers to enable the pseudowire routing tables to be populated.
Two mechanisms already exist, a BGP reachability information
distribution mechanism and an IGP based one. Here we define a third
solution relying on LDP. It allows for automatic advertisement of the
Attachment Individual Identifier prefixes provisioned on a T-PE when
this node does not run BGP or IGP. The mechanism described here runs
on the T-LDP (Targeted LDP) session between the T-PE and S-PE, and is
intended to complement existing PW routing mechanisms using BGP or
OSPF.
-
"Reliable Fibre Channel Transport Over MPLS Networks", Moran Roth, Ronen Solomon, Munefumi Tsurusawa, 15-Jan-09. ( 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 mechanisms controlling the reliable transport
of Fibre Channel PW over MPLS networks. The encapsulation of Fibre
Channel PDUs within a pseudowire and the procedures for using a PW to
provide a Fibre Channel service are specified in [FC-encap].
-
"MPLS and Ethernet OAM Interworking", Dinesh Mohan, Nabil Bitar, Simon DeLord, Philippe Niger, Ali Sajassi, 28-Feb-09. ( bytes)
- This document specifies the mapping of defect states between
Ethernet Attachment Circuits (ACs) and associated Ethernet
Pseudowires (PWs) connected in accordance to the PWE3 architecture
[RFC3985] to realize an end-to-end emulated Ethernet service. This document
augments the mapping of defect states between a PW and associated AC of the
end-to-end emulated service in [PW-OAM-MSG- MAP]. In [PW-OAM-MSG-MAP], Ethernet
OAM was not covered due to lack of Ethernet OAM maturity. However, since
then, [Y.1731] and [802.1ag] have been completed, and this document specifies
the mapping of defect states between Ethernet ACs and corresponding
Ethernet PWs.
-
"Inter-Chassis Communication Protocol for L2VPN PE Redundancy", Luca Martini, Samer Salam, Ali Sajassi, Matthew Bocci, Satoru Matsushima, Thomas Nadeau, 23-Jun-09. ( bytes)
- This document specifies an inter-chassis communication protocol
(ICCP) that enables Provider Edge (PE) device redundancy for Virtual
Private Wire Service (VPWS) and Virtual Private LAN Service (VPLS)
applications. The protocol runs within a set of two or more PEs,
forming a redundancy group, for the purpose of synchronizing data
amongst the systems. It accommodates multi-chassis attachment circuit
as well as pseudowire redundancy mechanisms.
-
"Flow Aware Transport of Pseudowires over an MPLS PSN", Stewart Bryant, Clarence Filsfils, Ulrich Drafz, Vach Kompella, Joe Regan, Shane Amante, 1-Jul-09. ( bytes)
- Where the payload carried over a pseudowire carries a number of
identifiable flows it can in some circumstances be desirable to carry
those flows over the equal cost multiple paths (ECMPs) that exist in
the packet switched network. Most forwarding engines are able to
hash based on label stacks and use this to balance flows over ECMPs.
This draft describes a method of identifying the flows, or flow
groups, to the label switched routers by including an additional
label in the label stack.
IETF Secretariat - Please send questions, comments, and/or
suggestions to ietf-web@ietf.org.
Return to Internet-Draft directory.
Return to IETF home page.