Re: [Pppext] [rbridge] 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> Wed, 26 January 2011 19:44 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 51E8C3A688B for <pppext@core3.amsl.com>; Wed, 26 Jan 2011 11:44:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.445
X-Spam-Level:
X-Spam-Status: No, score=-102.445 tagged_above=-999 required=5 tests=[AWL=0.154, 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 WDWG7r+12Ioa for <pppext@core3.amsl.com>; Wed, 26 Jan 2011 11:44:13 -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 4F5733A6870 for <pppext@ietf.org>; Wed, 26 Jan 2011 11:44:13 -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 p0QJlAHX020020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 14:47:11 -0500 (EST)
Message-ID: <4D407A3E.2000708@workingcode.com>
Date: Wed, 26 Jan 2011 14:47:10 -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> <4D3DB16B.5080803@workingcode.com> <4D3DC516.1000105@gmail.com> <4D3DCD97.7040005@gmail.com> <4D3DE413.80908@workingcode.com> <4D3E00B9.7050509@gmail.com> <4D3E247D.9090201@workingcode.com> <AANLkTi=+K-Kzsc+kahrmBoj1oC0WBzj7DYquS5ySCpP6@mail.gmail.com> <4D3F13B3.9070706@workingcode.com> <AANLkTikJjMcc1es7qyabddcXBFS93sRwcRO7XvPQzbe2@mail.gmail.com> <4D3F1EAD.5040901@workingcode.com> <4D4065F2.3080305@gmail.com>
In-Reply-To: <4D4065F2.3080305@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] [rbridge] 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: Wed, 26 Jan 2011 19:44:14 -0000

William Allen Simpson wrote:
> On 1/25/11 2:04 PM, James Carlson wrote:
>> I find I'm walking a narrow line.  I want to provide a little guidance
>> so that it's clear what's expected here, but I also want to avoid either
>> just copying hunks of the TRILL and IS-IS documentation or (worse)
>> carving out special exceptions.  I probably can't please everyone.
>>
> Probably not.  But it's fundamentally wrong to specify a configuration
> requirement for two protocols that are both premised on auto-configuration!

The other possible solution to avoid manual configuration (as I think I
mentioned) is to outlaw the use of TRILL systems that have only PPP
links and that also have no built-in (implementation-dependent) means of
acquiring a System ID automatically.

That's obviously possible, but besides being draconian in nature (how is
it my business how you plan to work with network administrators?), it
seems to strike a bit too close to the fundamentals of IS-IS.

In other words, I think I can point out the potential issue that exists
over in IS-IS to readers who might not be aware that (as part of an
overall system design, not as part of PPP TRILL itself) they could be
stepping in an area that lacks good solutions, but I don't think I
should say anything here that's at the level of requirement.  It's not
my place to repeat IS-IS requirements.  I can only do so badly and
out-of-sync with the original.  ;-}

Informative works for me on this issue, but normative doesn't.

> I'm sorry that I was off-line yesterday.  We've had responses about the
> requirements, and that clarifies things immensely.  But I'm busy
> cleaning up
> yesterday's mess today.  I promise some text tomorrow....  TIA!

Delay is not a problem.  I set a standard two-week timer to make sure
that folks would follow up.  But if there's still discussion going on at
that point, I'll continue with it as long as necessary to close it out.
 (Or until I remember that I have other things to do, I suppose ...)

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