Non PHP Behavior and out-of-band mapping for RSVP-TE LSPs
draft-ali-mpls-rsvp-te-no-php-oob-mapping-01

 
Document Type Replaced Internet-Draft (individual)
Last updated 2010-01-05 (latest revision 2007-07-12)
Replaced by draft-ietf-mpls-rsvp-te-no-php-oob-mapping
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-mpls-rsvp-te-no-php-oob-mapping
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
https://www.ietf.org/archive/id/draft-ali-mpls-rsvp-te-no-php-oob-mapping-01.txt

Abstract

There are many deployment scenarios which require Egress LSR to receive binding of the RSVP-TE LSP to an application, and payload identification, using some "out-of-band" (OOB) mechanism. This document proposes protocol mechanisms to address this requirement. The procedures described in this document are equally applicable for point-to-point (P2P) and point-to- multipoint (P2MP) LSPs.

Authors

Zafar Ali (zali@cisco.com)

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