IETF Logo Mail Archive

Re: [Pppext] working group last call for PPP TRILL protocol control protocol [was Re: I-D Action:draft-ietf-pppext-trill-protocol-02.txt]

James Carlson <carlsonj@workingcode.com> Mon, 24 January 2011 17:03 UTC

Return-Path: <carlsonj@workingcode.com>
X-Original-To: pppext@core3.amsl.com
Delivered-To: pppext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 451E93A6B08 for <pppext@core3.amsl.com>; Mon, 24 Jan 2011 09:03:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.24
X-Spam-Level:
X-Spam-Status: No, score=-102.24 tagged_above=-999 required=5 tests=[AWL=0.359, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iwp6X8UxMs91 for <pppext@core3.amsl.com>; Mon, 24 Jan 2011 09:03:01 -0800 (PST)
Received: from carlson.workingcode.com (carlsonj-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1d9::2]) by core3.amsl.com (Postfix) with ESMTP id 493653A6B02 for <pppext@ietf.org>; Mon, 24 Jan 2011 09:03:01 -0800 (PST)
Received: from [10.50.23.149] (gate.abinitio.com [65.170.40.132]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id p0OH5lK5006319 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jan 2011 12:05:48 -0500 (EST)
Message-ID: <4D3DB16B.5080803@workingcode.com>
Date: Mon, 24 Jan 2011 12:05:47 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: William Allen Simpson <william.allen.simpson@gmail.com>
References: <20110106154501.15655.20204.idtracker@localhost> <4D334595.3030507@workingcode.com> <4D3DADF9.4040009@gmail.com>
In-Reply-To: <4D3DADF9.4040009@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [Pppext] working group last call for PPP TRILL protocol control protocol [was Re: I-D Action:draft-ietf-pppext-trill-protocol-02.txt]
X-BeenThere: pppext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: PPP Extensions <pppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 24 Jan 2011 17:03:02 -0000

William Allen Simpson wrote:
> In any case, I disagree with section 3 item 3 regarding the OUI.  I'm a big
> fan of completely finishing a specification, not leaving holes for later.
> And a bigger fan of zero configuration that eliminates even the possibility
> of an additional operational consideration!

I agree that it'd be nice to fill in this hole, but I'm not so sure how
to accomplish that task.  I don't think IETF OUI plus LCP Magic Number
works -- the Magic Number value is unique for a given endpoint on a
given link, but is not guaranteed to be unique across a network.  But
the IS-IS System ID number does need to be unique across the network,
and its construction based on MAC addresses normally protects that
requirement.

One way to avoid the hole would be to outlaw the use of systems that
lack any way to form an IS-IS System ID, but that seems a little harsh.
 Forcing that corner case to use manual configuration is distasteful,
but the alternatives seem worse, at least to me.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

v2.8.7 | Report a Bug | By Email