Another question on draft-ietf-tewg-diff-te-proto-01.txt

["David Allan" <dallan@nortelnetworks.com>]

Section 3.3.1 states:
...LSRs MUST support for every LSP, an additional configurable parameter
which indicates the Class Type of the Traffic trunk transported by the
LSP...

This implies a 1:1 relationship between TTs and LSPs, this wouldn't
necessarily be true for an E-LSP. Now the mechanisms don't currently exist
to support associating multiple class types/bandwidth constraints for an
E-LSP, but if traffic trunk is exclusively an L-LSP concept, couldn't we pin
this down a bit more explicitly..?

thanks
Dave