The MPLS WG Archive

[Yakov Rekhter <yakov@cisco.com>]

Bora,

> The definition of interface ID in this draft as 16 bits conflicts with
> OSPF-TE draft which recommends using SNMPifindex at 3 bytes for this
> purpose. 

The OSPF-TE draft needs to be fixed.

> ISIS-TE draft does not cover this case at all.

I think it does - from draft-ietf-isis-traffic-02.txt: 

5.3 Sub-TLV 8: IPv4 neighbor address


   This sub-TLV contains a single IPv4 address for a neighboring router
   on this link.  This sub-TLV can occur multiple times.

   If the interface being advertised for Traffic Engineering purposes is
   unnumbered, the first two octets of the IPv4 neighbor address sub-TLV
   are set to zero and the next two octets are set to the interface ID
   of the unnumbered interface. 

> Can we reconcile to something that is consistent?

I'll get in touch with the authors of OSPF-TE and ask them to
fix their document.

Yakov.