The primary motivation is to allow for a compact form for the Tunnel MEP_ID. A secondary motivation is compatibility with existing MPLS/GMPLS Session objects.
...George On 7/1/11 9:07 AM, "Joel M. Halpern" <j...@joelhalpern.com> wrote: > In performing a gen-art review of this document, which seems quite good > over all, I noticed a minor question, but did not remember to include it > in my gen-art review. > > The defines a Tunnel-Identifier, identifying the end-point of a tunnel > within a node. > That identifier is defined as 16 bits. > In one sense, that seems sufficient. But it is more restrictive than > the number of parallel LSPs that the node could be an end-point for (by > a factor of 16.) So it seems that there ought to at least be an > explanation for the mismatch. > > Thank you, > Joel > > _______________________________________________ > mpls mailing list > m...@ietf.org > https://www.ietf.org/mailman/listinfo/mpls >
_______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
