@techreport{ali-mpls-sig-pid-multiplexing-case-04,
    number =    {draft-ali-mpls-sig-pid-multiplexing-case-04},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-ali-mpls-sig-pid-multiplexing-case/04/},
    author =    {Zafar Ali},
    title =     {{Signaled PID When Multiplexing Multiple PIDs over RSVP-TE LSPs}},
    pagetotal = 5,
    year =      2010,
    month =     oct,
    day =       25,
    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.},
}