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

[Grant Mills]

A quick query regarding draft-ietf-isis-traffic-01.

In RFC 1195 we implement the Internal and External IP reachibilty TLVs in LSPs for ISIS routes (Internal), Non ISIS routes
(External), for example (depending on route propagation policies). In addition the TLV allows the specification of metrics as being
internal or external as well.

In the traffic engineering draft a single TLV (135) is used to hold IP reachibility information. However I do not see any bit field
for specifying External/Internal for these routes. The internal/external bit for metrics I can live without but how do I map the old
scheme to the daft proposal? Is there an unspecified Sub-TLV for doing this? Is the idea to go from old world Level1 Internal,
Level2 Internal/External routes to just flat Level1 and Level2 routes?

Regards,


Grant.


-- 
______________________________________________________________________

Grant Mills,                            Tel:   +44 (1252) 360013
Lucent Technologies Inc.,       __      Fax:   +44 (1252) 360077
InterNetworking Systems UK,   //  \\
Suites 11/12, First Base,     ||  ||    URL:   http://www.lucent.com
Beacontree Plaza,             \\__//           
Gillette Way,                           Email: 
Reading, Berks, RG2 0BS,                     grant.mills@lucent.com
United Kingdom.                              grant.mills@bell-labs.com
______________________________________________________________________