Download
1 / 5
50 likes | 169 Views
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.
E N D
Signaled PID When Multiplexing Multiple Payloads over RSVP-TE LSPsdraft-ali-mpls-sig-pid-multiplexing-case-03.txtZafar Ali, Cisco Systems
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
Use Cases 73th IETF, MPLS WG, Hiroshima , JapanNovember 2009
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
Thank You. 73th IETF, MPLS WG, Hiroshima , JapanNovember 2009
