Technical Summary
This specification provides for a method for a single router to share one or
more circuits among multiple IS-IS routing protocol instances. This allows for
the isolation of resources into distinct instances.
Working Group Summary
The consensus was strong for this specification. While there was healthy
discussion and development over multiple revisions of the draft, no strong
objections were present during the development process.
Document Quality
There are no known current implementations of the draft; however, there has been
a large interest expressed in the WG by both vendors and operators for this
specification to be completed.
Personnel
Chris Hopps (chopps@rawdofmt.org) is the Document Shepherd
Adrian Farrel (adrian@olddog.co.uk) is the Responsible AD
IANA Note
Please note that this document requests allocation from the IS-IS TLV registry that requires
expert review. The designated experts are Chris Hopps and Dave Ward, the current ISIS WG
co-chairs. Chris is also the Document Shepherd. Thus, expert review has been performed.
Additionally, please note that this document requests allocation from the Ethernet Numbers
registry that requires application by form and expert review. The designated expert is
Dan Romascanu, and he has performed expert review and confirmed he is OK with the
allocation. A copy of the application form is presented here:
> Contact Name:
> Les Ginsberg
>
> Contact Email:
> ginsberg@cisco.com
>
> Type of Assignment:
> Two EUI-48 bit multicast MAC layer addresses.
> (Block size is 2)
>
> Registry:
> Ethernet numbers as specified in RFC 5342
>
> http://www.iana.org/assignments/ethernet-numbers/ethernet-
> numbers.xml
>
> Description:
> Unique MAC multicast destination addresses are required for support
> of IS-IS Multi-Instance. These new addresses are used to isolate IS-IS
> PDUs associated with non-zero instances of the protocol from the
> legacy instance of the protocol. In this way the non-zero instance PDUs
> will not be seen by legacy instances. This is necessary to prevent
> operation of the non-zero instances from interfering with operation of
> the legacy instances.
>
> Two addresses are required. One for all level 1 MI routers (AllL1MI-
> ISs) and one for all level 2 MI routers (AllL2MI-ISs)
>
> Additional Info:
> http://datatracker.ietf.org/doc/draft-ietf-isis-mi/