OAM Configuration Framework and Requirements for GMPLS RSVP-TE

Document Type Replaced Internet-Draft (individual)
Last updated 2008-12-23 (latest revision 2008-11-03)
Replaced by draft-ietf-ccamp-oam-configuration-fwk
Stream (None)
Intended RFC status (None)
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-ccamp-oam-configuration-fwk
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


OAM functions are essential to ensure that the desired service level of traffic engineered connections are met. In certain technologies OAM entities are inherently established once the connection is set up. However other technologies, especially OAM for packet switched networks, require an extra configuration step after connection establishment to setup OAM entities. This document specifies extensions to RSVP-TE to support the establishment and configuration of OAM entities along with LSP signalling.Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in


Attila Takacs (attila.takacs@ericsson.com)
Don Fedyk (dwfedyk@nortel.com)
He Jia (hejia@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)