[Isis-wg] IS-IS Extensions for Traffic Engineering

[Henk Smit]

> >   draft-ietf-isis-traffic-01 allows us to specify sub-TLVs for
> >  IP prefixes. One thing we plan to do is define a sub-TLV to
> >  tag or color IP prefixes. Those tags/colors can be used to
> >  distinquish between internal and external routes. Then you
> >  can use those tags/colors to control redistribution. We could
> >  even define one or more "well-known colors", like well-known
> >  BGP communities like no-advertise, etc.
> 
> When do you plan to publish the sub-TLV options. I assume this
> sub-TLV is similar to the one that appears in the extended IS
> reachability TLV?

  The idea was that draft-ietf-isis-traffic-01 only defines the
 things that are needed to do traffic engineering (with MPLS).
 That would be the new IS neighbor TLV that has the ability to
 do sub-TLVs. Plus the sub-TLVs that are needed for TE. While
 we were at this, we wanted to extend the metric space. To make
 sure the wider metric space was usable between areas, we also
 needed to define a new IP prefix TLV. This is where we stopped
 with our new additions.
  Anything else new that is not directly related to TE should
 go into a separate drafts. The downside would be that we end up
 with many new RFCs and drafts. The upside would be that we can
 continue moving the older drafts through the standards track
 while developing new technologies.
 
  If you want to implement a new sub-TLV for route tagging/coloring,
 feel free to document your implementation in a new draft. Otherwise
 it would probably take a few months before I, or someone else at
 cisco, would implement and document this.

     Cheers,

             henk.