Skip to main content

Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs
draft-ali-mpls-sig-pid-multiplexing-case-04

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Zafar Ali
Last updated 2010-10-25
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

There are many deployment scenarios where an RSVP-TE LSP carries multiple payloads. In these cases, it gets ambiguous on what should value should be carried as L3PID in the Label Request Object [RFC3209] or G-PID in the Generalized Label Request Object [RFC3471], [RFC3473]. The document proposes use of some dedicated PID values to cover some typical cases of multiple payloads carried by the LSP.

Authors

Zafar Ali

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