datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Non-Penultimate Hop Popping Behavior and Out-of-Band Mapping for RSVP-TE Label Switched Paths
draft-ietf-mpls-rsvp-te-no-php-oob-mapping-09

RFC
Document Stream: IETF
Last updated: 2011-08-17
Replaces: draft-ali-mpls-rsvp-te-no-php-oob-mapping
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (mpls)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6511
IANA Action State: RFC-Ed-Ack 
Responsible AD: Adrian Farrel
IESG Note: Martin Vigoureux (martin.vigoureux@alcatel-lucent.com) is the document shepherd.
Send notices to: mpls-chairs@tools.ietf.org, draft-ietf-mpls-rsvp-te-no-php-oob-mapping@tools.ietf.org, martin.vigoureux@alcatel-lucent.com

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-mpls-rsvp-te-no-php-oob-mapping.

Abstract:
There are many deployment scenarios that require an egress Label Switching Router (LSR) to receive binding of the Resource Reservation Protocol - Traffic Engineering (RSVP-TE) Label Switched Path (LSP) to an application and a payload identifier using some "out-of-band" (OOB) mechanism. This document defines 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. [STANDARDS-TRACK]

Authors:
Zafar Ali <zali@cisco.com>
Rahul Aggarwal <raggarwa_1@yahoo.com>
George Swallow <swallow@cisco.com>

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