Re: [rbridge] two minor issues with the isis-02 draft

James Carlson <james.d.carlson@sun.com> Wed, 25 February 2009 17:07 UTC

Return-Path: <rbridge-bounces@postel.org>
X-Original-To: ietfarch-trill-archive-Osh9cae4@core3.amsl.com
Delivered-To: ietfarch-trill-archive-Osh9cae4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0338A28C1BE for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 25 Feb 2009 09:07:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level:
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[AWL=-0.112, BAYES_00=-2.599]
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 i5ST9TB47EwE for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 25 Feb 2009 09:07:38 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 073FE28C19F for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 25 Feb 2009 09:07:37 -0800 (PST)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n1PGZmm5006942; Wed, 25 Feb 2009 08:35:48 -0800 (PST)
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n1PGYv9X006521 for <rbridge@postel.org>; Wed, 25 Feb 2009 08:34:58 -0800 (PST)
Received: from dm-east-02.east.sun.com ([129.148.13.5]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n1PGYuB2000476 for <rbridge@postel.org>; Wed, 25 Feb 2009 16:34:56 GMT
Received: from phorcys.east.sun.com (phorcys.East.Sun.COM [129.148.174.143]) by dm-east-02.east.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id n1PGYtu7021750 for <rbridge@postel.org>; Wed, 25 Feb 2009 11:34:55 -0500 (EST)
Received: from phorcys.east.sun.com (localhost [127.0.0.1]) by phorcys.east.sun.com (8.14.3+Sun/8.14.3) with ESMTP id n1PGG0xh013403; Wed, 25 Feb 2009 11:16:00 -0500 (EST)
Received: (from carlsonj@localhost) by phorcys.east.sun.com (8.14.3+Sun/8.14.3/Submit) id n1PGG0j4013400; Wed, 25 Feb 2009 11:16:00 -0500 (EST)
MIME-Version: 1.0
Message-ID: <18853.28352.318661.573947@gargle.gargle.HOWL>
Date: Wed, 25 Feb 2009 11:16:00 -0500
From: James Carlson <james.d.carlson@sun.com>
To: Donald Eastlake <d3e3e3@gmail.com>
In-Reply-To: <1028365c0902242109s1174d34bpc133b39fcad47ca4@mail.gmail.com>
References: <18845.48351.5175.126918@gargle.gargle.HOWL> <1028365c0902242109s1174d34bpc133b39fcad47ca4@mail.gmail.com>
X-Mailer: VM 7.01 under Emacs 21.3.1
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@phorcys.east.sun.com
Cc: TRILL/RBridge Working Group <rbridge@postel.org>
Subject: Re: [rbridge] two minor issues with the isis-02 draft
X-BeenThere: rbridge@postel.org
X-Mailman-Version: 2.1.6
Precedence: list
List-Id: "Developing a hybrid router/bridge." <rbridge.postel.org>
List-Unsubscribe: <http://mailman.postel.org/mailman/listinfo/rbridge>, <mailto:rbridge-request@postel.org?subject=unsubscribe>
List-Archive: <http://mailman.postel.org/pipermail/rbridge>
List-Post: <mailto:rbridge@postel.org>
List-Help: <mailto:rbridge-request@postel.org?subject=help>
List-Subscribe: <http://mailman.postel.org/mailman/listinfo/rbridge>, <mailto:rbridge-request@postel.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Donald Eastlake writes:
> > (I was unable to find anything in protocol-11 that supported the need
> > for this particular restriction, though it's possible I missed
> > something.)
> 
> I don't think the Extended IS Reachability TLV is particularly
> wasteful. In the common case, both the TLV #2 and #22 data for an
> adjacency is 11 bytes long so 23 will fit into a TLV for either.

OK; maybe "wasteful" is too strong.  "Needless" is better.

> I think the primary motivation for the 24 bit metric per adjacency in
> the Extended IS Reachability TLV is that you have only 6 bits of
> default metric per adjacency in the original IS Reachability TLV (it's
> an octet but one bit is used up to indicate internal/external and one
> bit is now the up/down bit [RFC 2966]). A 6 bit integer metric (1 to
> 63) is very coarse and is insufficient to express the relative costs
> of a 10 megabit versus a 1 gigabit link, let alone the existing 10
> gigabit links and the 40 and 100 gigabit links under development. [RFC
> 3784] Given this problem, mandating the Extended IS Reachability TLV
> seems reasonable to me do you can have a globally consistent link
> speed derived metric.

That's a great argument for why one *should* use the newer metric
scheme.  What's the argument for an effective "must"?

> > The protocol draft doesn't seem to indicate how large this counter
> > needs to be (is 8 bits enough or would more be better?), but I think
> > this should be added into the existing "2.d VLANs and Bridge Roots"
> > sub-TLV.
> 
> Yes, draft-eastlake-trill-rbridge-isis is no longer being updated. The
> plan is for all the TRILL IS-IS TLV and sub-TLVs to be added to the
> draft-ward-l2isis draft. I'll check that this is being included in
> that transfer.

OK; thanks.  That sounds good.

-- 
James Carlson, Solaris Networking              <james.d.carlson@sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge