IETF Logo Mail Archive

Re: [Pppext] TRILL, IS-IS, and System ID

Donald Eastlake <d3e3e3@gmail.com> Tue, 31 May 2011 18:20 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: pppext@ietfa.amsl.com
Delivered-To: pppext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E686E08C7 for <pppext@ietfa.amsl.com>; Tue, 31 May 2011 11:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.741
X-Spam-Level:
X-Spam-Status: No, score=-104.741 tagged_above=-999 required=5 tests=[AWL=-1.142, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DawX2GX2AjEt for <pppext@ietfa.amsl.com>; Tue, 31 May 2011 11:20:38 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 66584E08C6 for <pppext@ietf.org>; Tue, 31 May 2011 11:20:38 -0700 (PDT)
Received: by yxk30 with SMTP id 30so2588190yxk.31 for <pppext@ietf.org>; Tue, 31 May 2011 11:20:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=mQRvsffsogWbhMmwWTZhmw84m8+KeU+Ryggsk9qUIZM=; b=tI7oGqhOnQfpcxa1iPz0xsQxodrbDehx11ekomscpyhk3Fg0neAUZ1qrWNY2DlEX0I 2Yevujn9+eqS884BIV8MCEb3F8hYJYlLPUa7Dxiub0gaIZWwZ8uCy/d/Be5/KxKF5j7O Rm+e45cESTmVcxCu+IpEqKXZzHa2Z9Yv3VB98=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=vlnNE9cgqpfPfMiukDtntnjzgrKIqLHEcY1hCSVK17B9Q4HM6i0pZPIZryr2KXXje4 gOyqW5A71MsBI1WB82fEFne5H+QzGDmvdCQjYHx2vXQpnpiHtfkuWvqAoBKHgw1D18tb b9sVk6+mA5gYh/uvktYQ1BWnvhmbRWBVZPNE8=
Received: by 10.150.208.11 with SMTP id f11mr5206026ybg.206.1306866036091; Tue, 31 May 2011 11:20:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.51.2 with HTTP; Tue, 31 May 2011 11:20:16 -0700 (PDT)
In-Reply-To: <4DE51FC3.2070301@workingcode.com>
References: <4DE51FC3.2070301@workingcode.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 31 May 2011 14:20:16 -0400
Message-ID: <BANLkTikrJ217TLvKz61mCBcacgQUs317MA@mail.gmail.com>
To: James Carlson <carlsonj@workingcode.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: PPP Extensions <pppext@ietf.org>
Subject: Re: [Pppext] TRILL, IS-IS, and System ID
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pppext>, <mailto:pppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pppext>
List-Post: <mailto:pppext@ietf.org>
List-Help: <mailto:pppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pppext>, <mailto:pppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 May 2011 18:20:39 -0000

James,

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

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street
 Milford, MA 01757 USA
 d3e3e3@gmail.com


On Tue, May 31, 2011 at 1:05 PM, James Carlson <carlsonj@workingcode.com> wrote:
> As part of IETF review, the Routing ADs are looking over
> draft-ietf-pppext-trill-protocol-06.  Not 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.  See 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:
>
>  ISO/IEC 10589 states that it is the responsibility of the routeing
>  domain administrative authority to enforce the uniqueness of the
>  system ID. In cases where a zero configuration system is
>  supplied the system manufacturer MUST install a suitable
>  unique identifier at manufacturing time. One way to achieve
>  this is for the manufacturer to use a unique IEEE MAC address
>  following the allocation procedures normally used in the
>  manufacture 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?  Or do we have to
> start over?
>
> --
> James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
> _______________________________________________
> Pppext mailing list
> Pppext@ietf.org
> https://www.ietf.org/mailman/listinfo/pppext
>

v2.23.0 | Report a Bug | By Email