Re: TRILL, IS-IS, and System ID

Donald Eastlake <[email protected]> Tue, 31 May 2011 14:20:16 -0400
Newsgroups gmane.ietf.pppext
Message-ID <[email protected]>
James,

I'm fine with your suggested tweak of Stewart Bryant's wording.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
[email protected]


On Tue, May 31, 2011 at 1:05 PM, James Carlson <[email protected]> w=
rote:
> As part of IETF review, the Routing ADs are looking over
> draft-ietf-pppext-trill-protocol-06. =A0Not too surprising to me -- given
> that I still think it's far out of scope -- the text concerning IS-IS
> System IDs is causing trouble in that review. =A0See this thread:
>
> http://www.ietf.org/mail-archive/web/rtg-dir/current/threads.html#01533
>
> I wish I could leave the worms safely in the can, but it's looking like
> that might not be one of the options.
>
> Instead of the reference to Bill Simpson's draft, Stewart Bryant
> suggested replacement text like this:
>
> =A0ISO/IEC 10589 states that it is the responsibility of the routeing
> =A0domain administrative authority to enforce the uniqueness of the
> =A0system ID. In cases where a zero configuration system is
> =A0supplied the system manufacturer MUST install a suitable
> =A0unique identifier at manufacturing time. One way to achieve
> =A0this is for the manufacturer to use a unique IEEE MAC address
> =A0following the allocation procedures normally used in the
> =A0manufacture of an Ethernet interface.
>
> This tosses the issue back into the implementor's lap (which,
> incidentally, is exactly where I think the problem belongs), and
> suggests an existing and known solution where a MAC identifier may be
> allocated for the system itself and used as a global ID to construct the
> necessary IS-IS System ID.
>
> For use in this draft, I would alter the wording slightly to indicate
> that zero-configuration is strongly preferred for TRILL (as guidance),
> and that obtaining a suitable identifier is the implementor's
> responsibility, rather than just saying "in cases where."
>
> Would this change fly without breaking consensus? =A0Or do we have to
> start over?
>
> --
> James Carlson =A0 =A0 =A0 =A0 42.703N 71.076W =A0 =A0 =A0 =A0 <carlsonj@w=
orkingcode.com>
> _______________________________________________
> Pppext mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/pppext
>
_______________________________________________
Pppext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/pppext