1 / 5

Multiplexing Payloads Over RSVP-TE LSP: Insights and Use Cases

This draft addresses the complexities arising when an RSVP-TE LSP carries multiple payloads, such as both IPv4 and IPv6 flows. Current standards, namely RFC3209 and RFC3471/73, permit signaling for only one payload (L3PID or GPID) at a time, leading to ambiguities in payload value signaling. The document outlines practical use cases for multiplexing these payloads and seeks community feedback for acceptance as a Working Group document at the 73rd IETF MPLS Working Group in Hiroshima, Japan, November 2009.

aine
Télécharger la présentation

Multiplexing Payloads Over RSVP-TE LSP: Insights and Use Cases

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Signaled PID When Multiplexing Multiple Payloads over RSVP-TE LSPsdraft-ali-mpls-sig-pid-multiplexing-case-03.txtZafar Ali, Cisco Systems

  2. Problem Statement • There are many deployment scenarios where an RSVP-TE LSP carries multiple payloads, e.g., IPv4 and IPv6 flows on the same LSP. • RFC3209 and RFC3471/73 allows signaling for only one payload (L3PID or GPID) carried by the LSP. • It gets ambiguous on what Payload value should be signaled in RSVP-TE, when LSP is to carry multiple payloads. • This draft documents some use cases that allow multiplexing of multiple payloads. 73th IETF, MPLS WG, Hiroshima , JapanNovember 2009

  3. Use Cases 73th IETF, MPLS WG, Hiroshima , JapanNovember 2009

  4. Next Steps • Looking for comments/ feedback on the document. • Would like the document to be accepted as a WG document. 73th IETF, MPLS WG, Hiroshima , JapanNovember 2009

  5. Thank You. 73th IETF, MPLS WG, Hiroshima , JapanNovember 2009

More Related