1 / 12

ISIS Extensions for MRT

ISIS Extensions for MRT. Zhenbin Li, Nan Wu, Quintin Zhao (Huawei) Alia Atlas, Chris Bowers(Juniper) Jeff Tantsura(Ericsson) IETF 88, Vancouver , Canada. Outline: Discussing ISIS-MRT Draft. Overview of ISIS-MRT IS-IS extension for MRT Capability IS-IS extension advertising & parsing

marc
Download Presentation

ISIS Extensions for MRT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ISIS Extensions for MRT Zhenbin Li, Nan Wu, Quintin Zhao (Huawei) Alia Atlas, Chris Bowers(Juniper) Jeff Tantsura(Ericsson) IETF 88, Vancouver, Canada

  2. Outline: Discussing ISIS-MRT Draft Overview of ISIS-MRT IS-IS extension for MRT Capability IS-IS extension advertising & parsing Next step

  3. Overview of ISIS-MRT • MRT Capability advertisement • Default profile: A new M-bit introduced into MT-TLV(229) . • Non-default profile: A new Sub-TLV planned. • Electing GADAG root • An unique root must be chosed for MRT domain. • One priority is planned for each MRT node. • Root is chosed based on priority comparing.

  4. Overview of ISIS-MRT • MRT Ineligible link advertisement • Option is provided for certain links do not involved into MRT. • A new Sub-TLV is planned for these links. • MRT computation trigger • Topology changes • MRT Capability changes

  5. Outline: Discussing ISIS-MRT Draft Overview of ISIS-MRT IS-IS extension for MRT Capability IS-IS extension advertising & parsing Next step

  6. IS-IS extension for MRT Capability No. of Octets +--------------------------------+ |O |A |M |R | MT ID | 2 +--------------------------------+ M-bit in MT-TLV(229) is used to identify MRT-Capable for default profile. Multiple MT support MRT can have its corresponding M-bit SET. MT-TLV is carried in LSP #0 fragment. MRT-Capability can be updated soon when it changed.

  7. IS-IS extension for MRT Capability No. of Octets +--------------------------------+ |R |R |R |R | MT ID | 2 +----------------+---------------+ | Profile ID | 1 +----------------+ | Priority | 1 +----------------+---------------+ | MRT-Blue MT ID | 2 +--------------------------------+ | MRT-Red MT ID | 2 +--------------------------------+ Sub-TLV is planned in Router CAPABILITY TLV(242) to advertise MRT profile. Extra MRT Blue&Red MT ID is used for customized profile. Multi-instance of Sub-TLV are used to advertise supporting for multiple MRT profile.

  8. IS-IS extension for MRT Capability No. of Octets +--------------------------------+ |R |R |R |R | MT ID | 2 +----------------+---------------+ | Profile ID | 1 +----------------+ | Priority | 1 +----------------+---------------+ | MRT-Blue MT ID | 2 +--------------------------------+ | MRT-Red MT ID | 2 +--------------------------------+ Profile ID is in range [0, 255] with zero as the default profile. Priority is in range [0, 255] with 128 as the default priority. Biggest value win as the root with system-Id as tie-breaker. Non-zero Blue&Red MT ID will overwrite the two ID defined in profile.

  9. IS-IS extension for MRT Capability No. of Octets +--------------------------------+ |R |R |R |R | MT ID | 2 +--------------------------------+----------------+ |System ID and pseudo-node number | 7 +--------------------------------+----------------+ | Default metric | 3 +--------------------------------+ . . . . +--------------------------------+----------------+ |System ID and pseudo-node number | 7 +--------------------------------+----------------+ | Default metric | 3 +--------------------------------+ Sub-TLV is planned in Router CAPABILITY TLV(242) to advertise MRT Ineligible Links. IS-IS links are described as IS Reachability without IP info. Multi-instance of Sub-TLV are allowed. If ineligible-link split MRT Island then need to trigger new computation.

  10. Outline: Discussing ISIS-MRT Draft Overview of ISIS-MRT IS-IS extension for MRT Capability IS-IS extension advertising & parsing Next step

  11. IS-IS extension advertising & parsing MRT should not affect normal IS-IS behavior. MRT info should be ignored if not recognized. MRT info is in level scope. Default MRT profile can be carried MT-TLV in LSP #0 fragment(M-bit). Capability & Ineligible Sub-TLV is optional and carried in Router Capability TLV(242). Multi-instance of MRT is allowed. But care that Blue & Red MT-ID should not conflict in different profile.

  12. Next step Comments and suggestion are welcomed for this draft. Request to be accepted as WG draft.

More Related