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

Stewart Bryant <stbryant@cisco.com> Wed, 01 June 2011 16:10 UTC

Return-Path: <stbryant@cisco.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 7089FE07DC for <pppext@ietfa.amsl.com>; Wed, 1 Jun 2011 09:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.461
X-Spam-Level:
X-Spam-Status: No, score=-110.461 tagged_above=-999 required=5 tests=[AWL=0.138, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, 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 63qvzbSYKy7V for <pppext@ietfa.amsl.com>; Wed, 1 Jun 2011 09:10:52 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id 82639E05D3 for <pppext@ietf.org>; Wed, 1 Jun 2011 09:10:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=stbryant@cisco.com; l=1477; q=dns/txt; s=iport; t=1306944652; x=1308154252; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=aYVhnmas6xfOxpmeY1OBgP5o3Jp5RdGKH1MtCOiHM24=; b=KXb5V3G4SqvXg3gmj4CpMJUtz1vBokcK+5l2TLa5cKEY2Ikk9clbQTDD +GiP7HC6xNojgr8IzMBAC2mW/8i3jhjHONQ0TCFSgoYC4nXNN6gUubHrY gMLb13tqfGKO49gMYICGOH5P2kC2EyY/mmJQw3jIgF7jSPqOO/2uXtjwm A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAFBj5k2Q/khR/2dsb2JhbABTpiR3iHGgb4J6DwGaQ4YgBJBVjyw
X-IronPort-AV: E=Sophos;i="4.65,304,1304294400"; d="scan'208";a="33289482"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 01 Jun 2011 16:10:51 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id p51GAmIk015413; Wed, 1 Jun 2011 16:10:51 GMT
Received: from dhcp-gpk02-vlan300-64-103-65-100.cisco.com (localhost [127.0.0.1]) by cisco.com (8.11.7p3+Sun/8.8.8) with ESMTP id p51GAgW07612; Wed, 1 Jun 2011 17:10:46 +0100 (BST)
Message-ID: <4DE6648E.7040605@cisco.com>
Date: Wed, 01 Jun 2011 17:10:54 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Lightning/1.0b2 Thunderbird/3.1.10
MIME-Version: 1.0
To: James Carlson <carlsonj@workingcode.com>
References: <4DE51FC3.2070301@workingcode.com> <BANLkTikrJ217TLvKz61mCBcacgQUs317MA@mail.gmail.com> <4DE63C68.9070102@gmail.com> <4DE6528B.7070501@workingcode.com> <4DE659C1.2050306@cisco.com> <4DE65FD8.1090702@workingcode.com>
In-Reply-To: <4DE65FD8.1090702@workingcode.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: PPP Extensions <pppext@ietf.org>, rbridge@postel.org, William Allen Simpson <william.allen.simpson@gmail.com>
Subject: Re: [Pppext] TRILL, IS-IS, and System ID
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
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: Wed, 01 Jun 2011 16:10:53 -0000

On 01/06/2011 16:50, James Carlson wrote:
> Stewart Bryant wrote:
>>> All that said, I don't really care.  This is a tempest in a teapot.  I
>>> can mash together both texts if the Routing ADs are willing to accept a
>>> passing reference here to a draft that, in their words, hasn't even been
>>> considered by the IS-IS community.
>> James,
>>
>> I believe that any departure from the text in ISO10589 needs
>> to be discussed in the ISIS WG.
> "Any" departure?  No matter how subservient?  That seems as inflexible
> as the other end of this spectrum.
> If I suggested text like this, would it require ISIS WG discussion, and,
> if so, what's the chance that this discussion would terminate in a
> positive way?
>
>     3. An implementation that has only PPP links might have no
>        Organizationally Unique Identifier (OUI) that can form an IS-IS
>        System ID.  Resolving that issue is outside the scope of this
>        document, however it is strongly RECOMMENDED that all TRILL
>        implementations have at least one zero-configuration mechanism to
>        obtain a valid System ID.  Refer to ISO/IEC 10589 regarding System
>        ID uniqueness requirements.
You are OK up to here since you conform to the current ISIS spec.

> Alternative solutions to this issue
>        may also be defined in the future; see [8] for an example.
This needs to be discussed in the ISIS WG, and I cannot vouch
for the outcome.

- Stewart