1 / 6

MI-ISIS Introduction

Multi-Instance ISIS draft-previdi-isis-mi-mt-01.txt Stefano Previdi - sprevidi@cisco.com Les Ginsberg - ginsberg@cisco.com Mike Shand - mshand@cisco.com Abhay Roy - akr@cisco.com Dave Ward - dward@cisco.com IETF-66 Montreal - July 11, 2006. MI-ISIS Introduction. ISIS extension (YAT)

marlee
Download Presentation

MI-ISIS Introduction

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. Multi-Instance ISISdraft-previdi-isis-mi-mt-01.txtStefano Previdi - sprevidi@cisco.comLes Ginsberg - ginsberg@cisco.com Mike Shand - mshand@cisco.comAbhay Roy - akr@cisco.comDave Ward - dward@cisco.comIETF-66Montreal - July 11, 2006

  2. MI-ISISIntroduction • ISIS extension (YAT) • Allows separate ISIS instances to share nodes and links • Full Topology isolation • Ships in the night approach • Mechanism used to mark packets with instance membership

  3. Update to first version • Dino’s suggestion: • Use of dedicated MAC/Mcast address for MI-ISIS extension • Routers not supporting MI-ISIS extension will ignore packets • Hannes suggestion: work on PDU Version Number • Practically difficult as IETF do not “own” ISIS spec • Door open to many other extension request that would probably indefinitely delay MI-ISIS extension

  4. Update to first version • Possible interoperability issues • Misconfiguration of routers may cause MI-router and non-MI router to flood LSPs • Non-MI-router doesn’t consider IID TLV • Same issue if multiple standard ISIS instances are used and misconfigured • Solution proposed by Les: • Use different System-IDs for different instances

  5. MI-ISIS • Other alternatives have been investigated • New NLPID • New PDU type • New CLNS Header… • IID TLV seems the more straightforward to implement and support • No major interoperability issue • Careful deployment… as usual • Backward compatibility… as usual • Requirement: all routers must support this extension

  6. Multi-Instance ISISdraft-previdi-isis-mi-mt-01.txtStefano Previdi - sprevidi@cisco.comLes Ginsberg - ginsberg@cisco.com Mike Shand - mshand@cisco.comAbhay Roy - akr@cisco.comDave Ward - dward@cisco.comIETF-66Montreal - July 11, 2006

More Related