MPLS-TP OAM Maintenance Points
draft-koike-ietf-mpls-tp-oam-maintenance-points-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Yoshinori Koike , Manuel Paul | ||
| Last updated | 2010-03-09 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
MPLS transport profile (MPLS-TP) is designed to enable carrier grade packet transport and complement converged packet network deployments. Among the most important features of MPLS-TP are comprehensive OAM functions which enable network operators or service providers to provide various kinds of service characteristics such as prompt fault location, substantial survivability, performance monitoring and preliminary or in-service measurements. For the realization of those features by the MPLS Transport Profile, the definition of the maintenance points at which OAM messages are initiated, terminated and processed is very important. Based on the MPLS-TP OAM requirements this document elaborates on and gives guidance about maintenance points in MPLS-TP networks. This document is a product of a joint Internet Engineering Task Force (IETF) / International Telecommunications Union Telecommunications Standardization Sector (ITU-T) effort to include an MPLS Transport Profile within the IETF MPLS and PWE3 architectures to support the capabilities and functionalities of a packet transport network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)