
From rbridge-bounces@postel.org  Sun Jan  2 20:01:16 2011
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 9AAF03A69C2 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun,  2 Jan 2011 20:01:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.593
X-Spam-Level: 
X-Spam-Status: No, score=-102.593 tagged_above=-999 required=5 tests=[AWL=0.006, 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 wvF6WQ8HxngM for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun,  2 Jan 2011 20:00:22 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 647B63A697F for <trill-archive-Osh9cae4@lists.ietf.org>; Sun,  2 Jan 2011 20:00:22 -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 p033m14S022835; Sun, 2 Jan 2011 19:48:01 -0800 (PST)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p033ljei022795 for <rbridge@postel.org>; Sun, 2 Jan 2011 19:47:54 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A2C0928C0EB for <rbridge@postel.org>; Sun,  2 Jan 2011 19:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
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 Hj4jDPv0zoMR; Sun,  2 Jan 2011 19:45:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 19AA53A6933; Sun,  2 Jan 2011 19:45:02 -0800 (PST)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110103034502.26291.28724.idtracker@localhost>
Date: Sun, 02 Jan 2011 19:45:02 -0800
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: internet-drafts@ietf.org
Cc: rbridge@postel.org
Subject: [rbridge] I-D Action:draft-ietf-trill-adj-01.txt
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>
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Transparent Interconnection of Lots of Links Working Group of the IETF.


	Title           : RBridges: Adjacency
	Author(s)       : D. Eastlake 3rd, et al.
	Filename        : draft-ietf-trill-adj-01.txt
	Pages           : 26
	Date            : 2011-01-02

The IETF TRILL protocol provides optimal pair-wise data forwarding
without configuration, safe forwarding even during periods of
temporary loops, and support for multipathing of both unicast and
multicast traffic. TRILL accomplishes this by using IS-IS link state
routing and by encapsulating traffic using a header that includes a
hop count. Devices that implement TRILL are called RBridges.

TRILL supports multi-access LAN links that can have multiple end
stations and RBridges attached. This document describes the TRILL LAN
Hello protocol used on such links as regards adjacency, designated
RBridge selection, and MTU procedures, with state machines. There is
no change for IS-IS point-to-point Hellos used on links configured as
point-to-point in TRILL.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-trill-adj-01.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-trill-adj-01.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-01-02193135.I-D@ietf.org>


--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

--NextPart--

From rbridge-bounces@postel.org  Mon Jan  3 08:34:14 2011
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 E89903A6926 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  3 Jan 2011 08:34:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.672
X-Spam-Level: 
X-Spam-Status: No, score=-101.672 tagged_above=-999 required=5 tests=[AWL=-0.826, BAYES_00=-2.599, MIME_BASE64_TEXT=1.753, 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 Y1xnhR1qr5h0 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  3 Jan 2011 08:34:11 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 82B2E3A6981 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon,  3 Jan 2011 08:34:07 -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 p03GBSSr000560; Mon, 3 Jan 2011 08:11:29 -0800 (PST)
Received: from p-us1-iereast-outbound-tmp.us1.avaya.com (nj300815-nj-outbound.net.avaya.com [135.11.29.16]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p03GAwCJ000466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Mon, 3 Jan 2011 08:11:07 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAGuDIU2HCzI1/2dsb2JhbACkNHOkfwKWPIVKBI47
X-IronPort-AV: E=Sophos;i="4.60,267,1291611600"; d="scan'208";a="52638628"
Received: from unknown (HELO p-us1-erheast.us1.avaya.com) ([135.11.50.53]) by p-us1-iereast-outbound-tmp.us1.avaya.com with ESMTP; 03 Jan 2011 11:10:57 -0500
X-IronPort-AV: E=Sophos;i="4.60,267,1291611600"; d="scan'208";a="576154521"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by p-us1-erheast-out.us1.avaya.com with ESMTP; 03 Jan 2011 11:10:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 3 Jan 2011 17:09:55 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402A2C768@307622ANEX5.global.avaya.com>
In-Reply-To: <AANLkTinR4jaqvEaFDnPYKS38H1zPMba17aN8fQbmTtr3@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rbridge] Request for review ofdraft-ietf-trill-rbridge-mib-01.txt
Thread-Index: AcumQX/dwe0pAwp5TL6LS/xn0ksF/QFHQcLg
References: <4D08ED04.2050503@acm.org> <AANLkTinR4jaqvEaFDnPYKS38H1zPMba17aN8fQbmTtr3@mail.gmail.com>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>, "Developing a hybrid router/bridge." <rbridge@postel.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: dromasca@avaya.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p03GAwCJ000466
Subject: Re: [rbridge] Request for review ofdraft-ietf-trill-rbridge-mib-01.txt
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="windows-1255"
Content-Transfer-Encoding: base64
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

SSBkaWQgbm90IGhhdmUgdGltZSBmb3IgYSBmdWxsIHJldmlldywgYnV0IGhlcmUgYXJlIG15IGNv
bW1lbnRzIGZyb20gYSBmaXJzdCBxdWljayBleGFtaW5hdGlvbiBvZiB0aGUgZG9jdW1lbnQKCjEu
IFRoZSByZWxhdGlvbnNoaXAgd2l0aCBvdGhlciBNSUIgbW9kdWxlIHNlY3Rpb25zIHJlZmVyIHRv
IHRoZSBJRVRGIFJGQ3MuIEhvd2V2ZXIsIHNpbmNlIDIwMDYgdGhlIGRldmVsb3BtZW50IG9mIHRo
ZSBCcmlkZ2UgTUlCIG1vZHVsZXMgYW5kIHRoZWlyIHN1Y2Nlc3NvcnMgd2VyZSB0cmFuc2ZlcnJl
ZCB0byBJRUVFIDgwMi4xLiBJIHN1Z2dlc3QgdG8gZGVmaW5lIHRoZSByZWxhdGlvbnNoaXAgc2Vj
dGlvbnMgaW4gcmVsYXRpb24gdG8gdGhlIElFRUUgTUlCIG1vZHVsZXMgZGVmaW5lZCBpbiBJRUVF
IDgwMi4xYXAKCjIuIFNvbWUgb2YgdGhlIG9iamVjdHMgd2l0aCByZWFkLWNyZWF0ZSBNQVgtQUND
RVNTIG5lZWQgREVGQVVMVCBjbGF1c2VzLiBJbiBzb21lIGNhc2VzIHRoZSBkZWZhdWx0IGlzIG1l
bnRpb24gaW4gdGhlIERFU0NSSVBUSU9OIGNsYXVzZSAtIHRoaXMgaXMgbm90IHN1ZmZpY2llbnQK
CjMuIE1JQiBzdHJ1Y3R1cmUgLSBiZXR0ZXIgZ3JvdXAgYWxsIE1JQiBncm91cHMgdGhhdCBkZWZp
bmUgb2JqZWN0cyB1bmRlciBvbmUgc3ViLXRyZWUgCgpyYnJpZGdlT2JqZWN0cyAgICAgICAgICAg
T0JKRUNUIElERU5USUZJRVIgOjo9IHsgcmJyaWRnZU1JQiAxIH0gCgo0LiBUaGUgY3VycmVudCBs
ZXZlbCBvZiBkZXRhaWwgaW4gdGhlIFNlY3VyaXR5IENvbnNpZGVyYXRpb25zIHNlY3Rpb24gaXMg
bm90IHN1ZmZpY2llbnQuIAoKNS4gcnVubmluZyBsaWJzbWkgY29tcGlsYXRpb24gbGVhZHMgdG8g
YSBudW1iZXIgb2YgZXJyb3JzIGFuZCB3YXJuaW5ncyB0aGF0IG5lZWQgdG8gYmUgZml4ZWQuIAoK
UmVnYXJkcywKCkRhbgoKCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0KPiBGcm9tOiByYnJp
ZGdlLWJvdW5jZXNAcG9zdGVsLm9yZyAKPiBbbWFpbHRvOnJicmlkZ2UtYm91bmNlc0Bwb3N0ZWwu
b3JnXSBPbiBCZWhhbGYgT2YgRG9uYWxkIEVhc3RsYWtlCj4gU2VudDogVHVlc2RheSwgRGVjZW1i
ZXIgMjgsIDIwMTAgNToyNiBBTQo+IFRvOiBEZXZlbG9waW5nIGEgaHlicmlkIHJvdXRlci9icmlk
Z2UuCj4gU3ViamVjdDogUmU6IFtyYnJpZGdlXSBSZXF1ZXN0IGZvciByZXZpZXcgCj4gb2ZkcmFm
dC1pZXRmLXRyaWxsLXJicmlkZ2UtbWliLTAxLnR4dAo+IAo+IEhpLAo+IAo+IEl0IHdvdWxkIGJl
IGhlbHBmdWwgaWYgcGVvcGxlIHdvdWxkIHJldmlldyB0aGUgTUlCIGRvY3VtZW50LiAKPiBIZXJl
IGlzIGEgY29tbWVudCBvZiBtaW5lOgo+IAo+IEkgdGhpbmsgdGhhdCBTeiwgdGhlIGNhbXB1cyB3
aWRlIG1pbmltdW0gTVRVIHRoYXQgYW4gUkJyaWRnZSAKPiBoYXMgY2FsY3VsYXRlZCwgc2hvdWxk
IGJlIGEgcmVhZC1vbmx5IHBlci1SQnJpZGdlIE1JQiBvYmplY3QgCj4gYW5kIHRoYXQgaXQgc2hv
dWxkIGJlIHBvc3NpYmxlIGZvciBhIGNoYW5nZSBpbiBTeiB0byBjYXVzZSBhIAo+IG5vdGlmaWNh
dGlvbi4KPiAKPiBUaGFua3MsCj4gRG9uYWxkCj4gCj4gT24gV2VkLCBEZWMgMTUsIDIwMTAgYXQg
MTE6MjkgQU0sIEVyaWsgTm9yZG1hcmsgCj4gPG5vcmRtYXJrQGFjbS5vcmc+IHdyb3RlOgo+ID4K
PiA+IEluIEJlaWppbmcgdGhlcmUgd2VyZSBub3QgdGhhdCBtYW55IHRoYXQgaGFkIHJlYWQgdGhl
IE1JQiBkb2N1bWVudC4KPiA+IEJpbGwgRmVubmVyIHZvbHVudGVlcmVkIHRvIHJlYWQgaXQgYW5k
IHNlbmQgY29tbWVudHMsIGJ1dCAKPiBpdCB3b3VsZCBiZSAKPiA+IGdvb2QgdG8gZ2V0IHNvbWUg
b3RoZXIgcmV2aWV3ZXJzLgo+ID4KPiA+IEFueSBhZGRpdGlvbmFsIHZvbHVudGVlcnM/Cj4gPgo+
ID4gUGFydGljdWxhciB0aGluZ3MgdG8gbG9vayBhdCBpcyB3aGV0aGVyIHRoZXJlIGFyZSBvdGhl
ciB0cmFwcyB0aGF0IAo+ID4gd291bGQgYmUgdXNlZnVsIGZvciBhbiBvcGVyYXRvci4KPiA+Cj4g
PiCgIEVyaWsKPiA+Cj4gPgo+ID4KPiAKPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fXwo+IHJicmlkZ2UgbWFpbGluZyBsaXN0Cj4gcmJyaWRnZUBwb3N0ZWwu
b3JnCj4gaHR0cDovL21haWxtYW4ucG9zdGVsLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JicmlkZ2UK
PiAKCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCnJicmlk
Z2UgbWFpbGluZyBsaXN0CnJicmlkZ2VAcG9zdGVsLm9yZwpodHRwOi8vbWFpbG1hbi5wb3N0ZWwu
b3JnL21haWxtYW4vbGlzdGluZm8vcmJyaWRnZQo=

From rbridge-bounces@postel.org  Mon Jan  3 11:13:29 2011
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 5C7793A6AFF for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  3 Jan 2011 11:13:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.43
X-Spam-Level: 
X-Spam-Status: No, score=-102.43 tagged_above=-999 required=5 tests=[AWL=0.169, 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 0xZ2pBb04ZER for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  3 Jan 2011 11:13:28 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 00D853A6AF8 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon,  3 Jan 2011 11:13:27 -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 p03Irmaw027499; Mon, 3 Jan 2011 10:53:49 -0800 (PST)
Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p03IrI5x027449 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Mon, 3 Jan 2011 10:53:27 -0800 (PST)
Received: from [10.10.10.104] (70-36-183-22.dsl.dynamic.sonic.net [70.36.183.22]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id p03IrFSU017478 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Jan 2011 10:53:16 -0800
Message-ID: <4D221B2B.2020207@acm.org>
Date: Mon, 03 Jan 2011 10:53:31 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.9) Gecko/20101025 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: "Developing a hybrid router/bridge." <rbridge@postel.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: nordmark@acm.org
Subject: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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

This starts a two-week WG last call on "RBridges: Adjacency"
<draft-ietf-trill-adj-01.txt>, available at
http://tools.ietf.org/html/draft-ietf-trill-adj-01

The last call ends on 1/17/2011.

Send any comments to the TRILL WG mailing list.

     Erik


_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Jan  3 12:00:56 2011
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 959CF3A6B58 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  3 Jan 2011 12:00:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.456
X-Spam-Level: 
X-Spam-Status: No, score=-102.456 tagged_above=-999 required=5 tests=[AWL=0.143, 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 BTP+O9rW2ImE for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  3 Jan 2011 12:00:55 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 21A7D3A6B5B for <trill-archive-Osh9cae4@lists.ietf.org>; Mon,  3 Jan 2011 12:00:52 -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 p03JiKJK005289; Mon, 3 Jan 2011 11:44:21 -0800 (PST)
Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p03JheoW005225 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Mon, 3 Jan 2011 11:43:49 -0800 (PST)
Received: from [10.10.10.104] (70-36-183-22.dsl.dynamic.sonic.net [70.36.183.22]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id p03JhcbH022979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 3 Jan 2011 11:43:39 -0800
Message-ID: <4D2226FA.3040001@acm.org>
Date: Mon, 03 Jan 2011 11:43:54 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.2.9) Gecko/20101025 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: rbridge@postel.org
References: <4D221B2B.2020207@acm.org>
In-Reply-To: <4D221B2B.2020207@acm.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: nordmark@acm.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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

On 01/ 3/11 10:53 AM, Erik Nordmark wrote:
>
> This starts a two-week WG last call on "RBridges: Adjacency"
> <draft-ietf-trill-adj-01.txt>, available at
> http://tools.ietf.org/html/draft-ietf-trill-adj-01
>
> The last call ends on 1/17/2011.
>
> Send any comments to the TRILL WG mailing list.

I have a small editorial suggestion for the draft.

Currently the events are numbered 1-8 and 1-5. Thus "event 5" isn't 
sufficient to specify the name of an event. It would be more clear if 
they were numbered A1-A8 and D1-D5 (or P1-P5).

That means we don't need text like e.g., "an adjacency event 5 occurs 
for the adjacency", but can instead say "an event A5 occurs for the 
adjacency".

    Erik
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Sun Jan  9 19:04:41 2011
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 AB74428C0E4 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun,  9 Jan 2011 19:04:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.836
X-Spam-Level: 
X-Spam-Status: No, score=-102.836 tagged_above=-999 required=5 tests=[AWL=-0.237, 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 M63OAaY8NrYX for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun,  9 Jan 2011 19:04:40 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id ACECF28C0D9 for <trill-archive-Osh9cae4@lists.ietf.org>; Sun,  9 Jan 2011 19:04: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 p0A2maxs026664; Sun, 9 Jan 2011 18:48:37 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0A2mNU9026642 for <rbridge@postel.org>; Sun, 9 Jan 2011 18:48:32 -0800 (PST)
Received: by wwd20 with SMTP id 20so20631641wwd.21 for <rbridge@postel.org>; Sun, 09 Jan 2011 18:48:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=eulaXcCJNBJT8KBcO6/5eGUQdkfjDO4886lsN9MaDrU=; b=uvOWpS1e9W6c6t6knqJd77V4BzI8kw68mJ2wh++Msx2UEmkgTN5Ys1P2ewiL1mWdmD S2YS+b+fC4P4ujTKPoPMLJHsGfomjfw23ZBEqH1C1pkRi6IfspXJaxclpcCJumjMGHL8 /dtGC6vqs6wHsH3DJK7W/R3f3MjovvZCaMDsA=
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 :content-type:content-transfer-encoding; b=f2f+oJA1X32I/CtmnlAYJYOxXKJ8m3W3JDRCMcV7tGByFLcij54SXHAv/x6fTC2reW ND33vkBciJj0D/PItyS4bBMHd3x6ni4EJq5j+Tx3kAfXVuNmV9WMffdxo7e0WBtHMp9F WLWMvoCxzj8Lb3MhLTpIFEIZumqhIUkNRq0WA=
Received: by 10.227.197.131 with SMTP id ek3mr17912163wbb.211.1294627701646; Sun, 09 Jan 2011 18:48:21 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Sun, 9 Jan 2011 18:48:01 -0800 (PST)
In-Reply-To: <20110106154501.15655.20204.idtracker@localhost>
References: <20110106154501.15655.20204.idtracker@localhost>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 9 Jan 2011 21:48:01 -0500
Message-ID: <AANLkTi=spm3QE1_rgL7obOWQPu1C3c-zPiOw-1wqau9C@mail.gmail.com>
To: rbridge@postel.org
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0A2mNU9026642
Subject: [rbridge] Fwd: [Pppext] I-D Action:draft-ietf-pppext-trill-protocol-02.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

---------- Forwarded message ----------
From:  <Internet-Drafts@ietf.org>
Date: Thu, Jan 6, 2011 at 10:45 AM
Subject: [Pppext] I-D Action:draft-ietf-pppext-trill-protocol-02.txt
To: i-d-announce@ietf.org
Cc: pppext@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the Point-to-Point Protocol Extensions
Working Group of the IETF.

=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : PPP TRILL Protocol Control Proto=
col
=A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : J. Carlson
=A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-pppext-trill-protocol-0=
2.txt
=A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 6
=A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-01-06

The Point-to-Point Protocol (PPP) [1] defines a Link Control Protocol
(LCP) and a method for negotiating the use of multi-protocol traffic
over point-to-point links. =A0This document describes support for
Transparent Interconnection of Lots of Links (TRILL) Protocol,
allowing direct communication between Routing Bridges (RBridges) via
PPP links.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-pppext-trill-protocol-02.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/
_______________________________________________
Pppext mailing list
Pppext@ietf.org
https://www.ietf.org/mailman/listinfo/pppext

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Wed Jan 12 11:22:19 2011
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 0562B3A6A79 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 12 Jan 2011 11:22:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 2cRn-5g7nGtx for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 12 Jan 2011 11:22:17 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id BDEFD3A69A4 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 12 Jan 2011 11:22:17 -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 p0CJ1lin013654; Wed, 12 Jan 2011 11:01:47 -0800 (PST)
Received: from a.mail.sonic.net (a.mail.sonic.net [64.142.16.245]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0CJ1BB1013232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Wed, 12 Jan 2011 11:01:20 -0800 (PST)
Received: from [128.107.115.202] ([128.107.115.202]) (authenticated bits=0) by a.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id p0CJ11KP020030 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Wed, 12 Jan 2011 11:01:02 -0800
Message-ID: <4D2DFA6F.1000807@acm.org>
Date: Wed, 12 Jan 2011 11:01:03 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: rbridge@postel.org
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: nordmark@acm.org
Cc: Jari Arkko <jari.arkko@piuha.net>, rdroms@cisco.com
Subject: [rbridge] Change of affiliation
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

Just to keep everyone informed.
As of this week I'm an employee of Cisco Systems.

Regards,
    Erik

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Thu Jan 13 17:52:15 2011
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 E83E73A687A for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 13 Jan 2011 17:52:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.705
X-Spam-Level: 
X-Spam-Status: No, score=-5.705 tagged_above=-999 required=5 tests=[AWL=-3.106, 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 7xhvVPUkvSLA for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 13 Jan 2011 17:52:09 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 97D4F3A67FB for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 13 Jan 2011 17:52:09 -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 p0E1bb1m025308; Thu, 13 Jan 2011 17:37:39 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0E1auHa025247 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 13 Jan 2011 17:37:05 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-Files: draft-ietf-trill-adj-01_comments.txt, draft-ietf-trill-adj-01_editorial.txt : 6772, 3274
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAE43L02rRN+K/2dsb2JhbACkTXOkNphJgnSCWASEaIlQ
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-4.cisco.com with ESMTP; 14 Jan 2011 01:36:55 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p0E1atWl010883; Fri, 14 Jan 2011 01:36:55 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 13 Jan 2011 17:36:55 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01CBB38B.86D26231"
Date: Thu, 13 Jan 2011 17:36:54 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <4D221B2B.2020207@acm.org>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Thread-Index: AcureKTnd1c3crbrRlSITWfqcXoPYgHwzWzA
References: <4D221B2B.2020207@acm.org>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: <isis-wg@ietf.org>, <rbridge@postel.org>
X-OriginalArrivalTime: 14 Jan 2011 01:36:55.0978 (UTC) FILETIME=[872B50A0:01CBB38B]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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>
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

This is a multi-part message in MIME format.

------_=_NextPart_001_01CBB38B.86D26231
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

(resending w corrected TRILL WG address)

Attached please find my comments on draft-ietf-trill-adj-01.=20

The file draft-ietf-trill-adj-01_comments.txt contains substantive
comments identified by Section # - except in a couple of cases where the
remarks are more generic.

The file draft-ietf-trill-adj-01_editorial.txt is portions of the draft
annotated with editorial comments. Search for "LES:" in the file.

As context, the requirements of [TRILL] introduce the need to send a
great deal more circuit scoped information on a LAN as compared to Layer
3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
[TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
information and to provide robust loop prevention in the forwarding of
data. But I believe the extensions as currently defined have significant
scalability issues in the presence of a large number of neighbors on a
LAN and/or a large number of enabled VLANs. In my comments I have
confined myself to pointing out where I believe such issues arise. If
there is consensus that these are issues which should be addressed, then
additional discussions can be started as to how to do so.

Finally, I would like to thank the authors of draft-ietf-trill-adj-01
for the effort and diligence they obviously applied to the writing of
this draft.

   Les


------_=_NextPart_001_01CBB38B.86D26231
Content-Type: text/plain;
	name="draft-ietf-trill-adj-01_comments.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-trill-adj-01_comments.txt
Content-Disposition: attachment;
	filename="draft-ietf-trill-adj-01_comments.txt"

UmVsaWFibGUgQ2lyY3VpdCBTY29wZSBGbG9vZGluZw0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCg0KW1JGQ1RyaWxsXSBkZWZpbmVzIGEgcmVxdWlyZW1lbnQgZm9yIHJlbGlhYmxl
IGNpcmN1aXQgc2NvcGVkIGZsb29kaW5nIG9mDQpBcHBvaW50ZWQgRm9yd2FyZGVyIEluZm9ybWF0
aW9uIChTZWN0aW9uIDQuNC4yKSBidXQgaXQgaXMgbm90IHNwZWNpZmllZA0KaG93IHRoaXMgaXMg
dG8gYmUgYWNoaWV2ZWQuIEkgaGFkIGhvcGVkIHRoaXMgZG9jdW1lbnQgd291bGQgcHJvdmlkZSB0
aGF0DQpzcGVjaWZpY2F0aW9uLg0KDQpUaGUgbGFjayBvZiByZWxpYWJsZSBmbG9vZGluZyBtZWFu
cyB0aGF0IGVpdGhlcjoNCg0KYSlBcHBvaW50ZWQgZm9yd2FyZGVyIGluZm9ybWF0aW9uIE1VU1Qg
YmUgaW5jbHVkZWQgYnkgdGhlIERSQiBhbHdheXMgLQ0Kd2hpY2ggZG9lcyBub3Qgc2NhbGUgd2Vs
bA0KDQpPUg0KDQpiKUxvb3BzIGFuZC9vciBsb3NzIG9mIHRyYWZmaWMgZm9yIGEgZ2l2ZW4gVkxB
TiBNQVkgb2NjdXINCg0KUHJldmVudGluZyBNdWx0aXBsZSBEUkJzIG9uIGEgTEFODQotLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KSXQgaXMgbm90IGNsZWFyIHRvIG1lIGhvdyB0
aGUgdXNlIG9mIG11bHRpcGxlIGFubm91bmNpbmcgVkxBTnMgYWNoaWV2ZXMNCnRoZSBzdGF0ZWQg
Z29hbCBvZiBvbmUgYW5kIG9ubHkgb25lIERSQiBpbiB0aGUgcHJlc2VuY2Ugb2YgaW5jb25zaXN0
ZW50DQpjb25uZWN0aXZpdHkgLyBjb25maWd1cmF0aW9uLiBDb25zaWRlciB0aGUgZm9sbG93aW5n
IHNpbXBsZSBleGFtcGxlIHdoZXJlDQpWTEFOcygxLDIsMykgYXJlIGluIHRoZSBlbmFibGVkIHNl
dCBvbiBhbGwgUkJzOg0KDQpSQiBOYW1lLyAgICAgRFZMQU4gICBBbm5vdW5jaW5nIFZMQU5zICAg
VkxBTiBDb25uZWN0aXZpdHkNClByaW9yaXR5DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KUkIxLzUwICAgICAgICAgMSAgICAgICAxLDIg
ICAgICAgICAgICAgIDEsMiwzDQpSQjIvNjAgICAgICAgICAxICAgICAgIDEgICAgICAgICAgICAg
ICAgMQ0KUkIzLzcwICAgICAgICAgMyAgICAgICAyICAgICAgICAgICAgICAgIDIsMw0KDQpHaXZl
biB0aGUgYWJvdmUgdGhlIGZvbGxvd2luZyB3b3VsZCBlbnN1ZToNCg0KUkIgTmFtZSAgICAgTmVp
Z2hib3JzICAgICAgIERSQi8NCiAgICAgICAgICAgICBEZXRlY3RlZCAgICAgICBEVkxBTg0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NClJC
MSAgICAgICAgICAgIDIsMyAgICAgICAgICAzLzINClJCMiAgICAgICAgICAgIDEgICAgICAgICAg
ICAyLzENClJCMyAgICAgICAgICAgIDIsMyAgICAgICAgICAzLzINCg0KTm93LCBnaXZlbiB0aGUg
YWJvdmUsIGJvdGggUkIzIGFuZCBSQjIgd2lsbCB0aGluayB0aGV5IGFyZSBEUkIgYW5kIHBvdGVu
dGlhbGx5DQphc3NpZ24gbXVsdGlwbGUgQUZzIGZvciBlYWNoIG9mIHRoZSBWTEFOcy4gS2VlcGlu
ZyBpbiBtaW5kIFtUUklMTF0gDQpTZWN0aW9uIDQuNC4zDQoNCiJHcmVhdCBjYXJlIHNob3VsZCBi
ZSB0YWtlbiBpbiBjb25maWd1cmluZyBhbiBSQnJpZGdlDQogICB0byBub3Qgc2VuZCBUUklMTCBI
ZWxsb3Mgb24gYW55IFZMQU4gd2hlcmUgdGhhdCBSQnJpZGdlIGlzIGFwcG9pbnRlZA0KICAgZm9y
d2FyZGVyIGFzLCB1bmRlciBzb21lIGNpcmN1bXN0YW5jZXMsIHRoaXMgY2FuIGxlYWQgdG8gbG9v
cHMuIg0KDQppdCBiZWNvbWVzIGFwcGFyZW50IHRoYXQgYXQgYSBtaW5pbXVtIGF0IGxlYXN0IG9u
ZSBSQiBNVVNUIHNlbmQgSUlIcyBvbiBlYWNoDQplbmFibGVkIFZMQU4gaW4gb3JkZXIgdG8gaW1w
bGVtZW50IGxvb3AgcHJldmVudGlvbi4gQnV0IHRoaXMgZG9lcyBub3Qgc2NhbGUNCndlbGwuDQoN
ClNlY3Rpb24gMy4zDQotLS0tLS0tLS0tLS0tDQoNClRleHQgc2F5cyB0aGF0IGZvciBoZWxsb3Mg
cmVjZWl2ZWQgb24gYSBWTEFOIE90aGVyIHRoYW4gdGhlIEQtVkxBTg0KDQoiYW55IFRSSUxMIE5l
aWdoYm9yIFRMViBpbiBzdWNoIGEgSGVsbG8gaXMgaWdub3JlZC4uLiINCg0KSSBhc3N1bWUgdGhp
cyBtZWFucyB0aGF0IGl0IGlzIGFuIGltcGxlbWVudGF0aW9uIGNob2ljZSBhcyB0byB3aGV0aGVy
IHRvIA0KaW5jbHVkZSB0aGUgbmVpZ2hib3IgVExWIGluIHN1Y2ggaGVsbG9zPyBBIGNsZWFyIHN0
YXRlbWVudCBvZiB0aGlzIHdvdWxkDQpiZSBoZWxwZnVsLg0KDQpTZWN0aW9uIDQNCi0tLS0tLS0t
LS0NCg0KVGhlcmUgbmVlZHMgdG8gYmUgYSBkZXNjcmlwdGlvbiBvZiB0aGUgRFJCIGVsZWN0aW9u
IHByb2Nlc3MgLQ0KZXF1aXZhbGVudCB0byB3aGF0IGlzIGluIFtJUy1JU10gU2VjdGlvbiA4LjQu
NS4gRm9yIGV4YW1wbGUsIHRoZSBzZXQgb2YNCkRSQiBjYW5kaWRhdGVzIGluY2x1ZGVzIGFsbCBS
QnMgdG8gd2hpY2ggdGhlIGxvY2FsIHN5c3RlbSBoYXMgYW4gYWRqYWNlbmN5DQppbiBEZXRlY3Qs
IDItd2F5LCBvciBSZXBvcnQgU3RhdGUgLi4uY29ycmVjdD8NCg0KWW91IGFsc28gbmVlZCB0byBz
cGVjaWZ5IGluIHdoYXQgRFJCIGVsZWN0aW9uIHN0YXRlcyBhIERSQiByZXBvcnRzIG5laWdoYm9y
cyANCmluIHBzZXVkby1ub2RlIExTUHMuIEl0IHdvdWxkIHNlZW0gdGhhdCBpZiBuZWlnaGJvcnMg
YXJlIGFkdmVydGlzZWQgaW4NCnByZS1EUkIgc3RhdGUgdGhhdCB3ZSBjb3VsZCBhdHRyYWN0IHRy
YWZmaWMgd2hpY2ggd2UgYXJlIG5vdCB5ZXQgYWJsZSB0byANCmZvcndhcmQuDQoNClNlY3Rpb24g
NC4yDQotLS0tLS0tLS0tLQ0KDQpXaGVuIGEgRFJCIGNoYW5nZSBjYXVzZXMgYSBjaGFuZ2UgaW4g
RC1WTEFOLCB0aGUgZHJhZnQgc2F5czoNCg0KICAgICAgbyAgVGhlIG5vbi1EZXNpZ25hdGVkIFZM
QU4gSGVsbG8gSG9sZGluZyB0aW1lciBpcyBzZXQgdG8gdGhlDQogICAgICAgICBtYXhpbXVtIG9m
IGl0cyB0aW1lIHRvIGV4cGlyYXRpb24gYW5kIHRoZSB0aW1lIHRvIGV4cGlyYXRpb24gb2YNCiAg
ICAgICAgIHRoZSBEZXNpZ25hdGVkIFZMQU4gSGVsbG8gSG9sZGluZyB0aW1lci4NCg0KVGhlICJE
ZXNpZ25hdGVkIFZMQU4gSGVsbG8gSG9sZGluZyB0aW1lciIgcmVmZXJyZWQgdG8gaXMgdGhlIE9M
RCBEZXNpZ25hdGVkIA0KVkxBTiBIZWxsbyBIb2xkaW5nIHRpbWVyLCBjb3JyZWN0PyBJZiBzbyBh
ZGRpbmcgdGhhdCBjbGFyaWZpY2F0aW9uIHdvdWxkIGhlbHAuDQoNCkFsc28sIGlmIHdlIGFyZSBO
T1QgRFJCIGFuZCB0aGUgbmV3IEQtVkxBTiBpcyBOT1QgaW4gdGhlIHNldCBvZiBhbm5vdW5jaW5n
DQpWTEFOcyB0aGVuIHRoZSBub24tRFJCcyBoYXZlIHRvIGluY2x1ZGUgdGhlIG5ldyBELVZMQU4g
aW4gdGhlIHNldCBvZiBWTEFOUyBmb3INCndoaWNoIHRoZXkgc2VuZCBoZWxsb3MsIGNvcnJlY3Q/
IFRoaXMgc2hvdWxkIGJlIHNwZWNpZmllZC4NCg0KSXQgaXMgYWxzbyBhcHBhcmVudCB0aGF0IERS
QiBjaGFuZ2VzIGFyZSB2ZXJ5IGRpc3J1cHRpdmUgLSBldmVuIG1vcmUgc28gdGhhbiANCmF0IExh
eWVyIDMuIEluIExheWVyIDMgb24gYSBESVMgY2hhbmdlIG9wdGltYWwgYmVoYXZpb3IgaXMgdG8g
ZG8gYSAibWFrZQ0KYmVmb3JlIGJyZWFrIiB0byBtaW5pbWl6ZSBkaXNydXB0aW9uLiBIb3dldmVy
LCB0aGF0IGlzIG5vdCBwb3NzaWJsZSBoZXJlIGFzDQphbGwgYWRqYWNlbmNpZXMgd2lsbCBnbyBp
bnRvICJEZXRlY3QiIHN0YXRlIGZvbGxvd2luZyBhIERSQiBjaGFuZ2UuIFNob3VsZCBpdCBiZSBy
ZWNvbW1lbmRlZCB0aGVuIHRvIGF2b2lkIERSQiBjaGFuZ2VzIHdoZW5ldmVyIHBvc3NpYmxlIChl
LmcuDQpieSBzZXR0aW5nIExBTiBwcmlvcml0eSk/DQoNClNlY3Rpb24gNQ0KLS0tLS0tLS0tDQoN
CltUUklMTF0gNC4zLjIgc3RhdGVzOg0KDQoiVGhlIE1UVS1wcm9iZSBNQVkgYmUgbXVsdGljYXN0
IHRvIEFsbC1SQnJpZGdlcywgb3IgdW5pY2FzdCB0byBhIHNwZWNpZmljIA0KUkJyaWRnZS4gVGhl
IE1UVS1hY2sgaXMgIG5vcm1hbGx5IHVuaWNhc3QgdG8gdGhlIHNvdXJjZSBvZiB0aGUgTVRVLXBy
b2JlIA0KdG8gd2hpY2ggaXQgcmVzcG9uZHMgIGJ1dCBNQVkgYmUgbXVsdGljYXN0IHRvIEFsbC1S
QnJpZGdlcy4iDQoNCkhvdyBkb2VzIHRoZSBzZW5kZXIgb2YgdGhlIFByb2JlL0FDSyBkZXRlcm1p
bmUgd2hldGhlciB0byB1c2UgdW5pY2FzdCBvcg0KbXVsdGljYXN0IGRlc3RpbmF0aW9uIGFkZHJl
c3M/DQoNCklmIGFuIE1UVS1BQ0sgaXMgc2VudCB0byBtdWx0aWNhc3QgYWRkcmVzcyB3aGF0IHNo
b3VsZCB0aGUgcmVjZWl2ZXJzIHdobw0KZGlkIG5vdCBpbml0aWF0ZSB0aGUgcHJvYmUgZG8gd2l0
aCB0aGUgQUNLPyBJZ25vcmU/IFByb2Nlc3M/DQoNCk9uIGEgTEFOIHNob3VsZCBNVFUgcHJvYmVz
IG9ubHkgYmUgc2VudCB0by9mcm9tIHRoZSBEUkIgd2hlbiBwc2V1ZG8tbm9kZQ0KYnlwYXNzIGlz
IE5PVCBzZXQ/IEl0IHNlZW1zIHVzZWxlc3MgdG8gZG8gb3RoZXJ3aXNlIC0gYnV0IHRoaXMgaXMg
bm90IA0KZGlzY3Vzc2VkLg0KDQpBbHNvLCBkb24ndCB5b3UgbmVlZCBQT1JUIElEIGluIHRoZSBQ
cm9iZSBTb3VyY2UvQUNLIFNvdXJjZSBpbiB0aGUgTVRVIFBEVQ0KdG8gZnVsbHkgaWRlbnRpZnkg
dGhlIHNvdXJjZS9yZXNwb25kZXI/IA0KDQpJdCB3b3VsZCBoYXZlIGJlZW4gYmV0dGVyIGluIHRl
cm1zIG9mIHVzZSBvZiB0aGUgbGltaXRlZCBQRFUgdHlwZSBzcGFjZSB0byANCmRlZmluZSBvbmx5
IG9uZSBuZXcgUERVIHR5cGUgYW5kIGVuY29kZSB0aGUgcHJvYmUvYWNrIGluc2lkZSBvZiB0aGUg
UERVLg0KDQpBbHNvLCB0aGlzIHBhcnRpY3VsYXIgYXJlYSBleGVtcGxpZmllcyBob3cgZGlmZmlj
dWx0IGl0IGlzIHRvIGNvbWUgdG8gYQ0KZnVsbCB1bmRlcnN0YW5kaW5nIG9mIHByb3BlciBiZWhh
dmlvci4gW1RSSUxMXSBtdXN0IGJlIGNvbnN1bHRlZCB0byBmaW5kDQphIGRlc2NyaXB0aW9uIG9m
IGhvdyB0byBzZW5kIHRoZSBQRFVzLCBbUkZDdGlzaXNdIG11c3QgYmUgY29uc3VsdGVkIHRvIGZp
bmQNCnRoZSBQRFUgY29kZSBwb2ludHMgYW5kIGZvcm1hdHMsIGFuZCB0aGUgVFJJTEwtYWRqIGRv
Y3VtZW50IG11c3QgYmUgY29uc3VsdGVkDQp0byBmaW5kIGEgZGVzY3JpcHRpb24gb2YgaG93IHRv
IGluY29ycG9yYXRlIE1UVSB0ZXN0IHJlc3VsdHMgaW50byB0aGUgDQpoZWxsbyBwcm9jZXNzLiAN
Cg0KU2VjdGlvbiA2DQotLS0tLS0tLS0tLQ0KDQpJIGZpbmQgdGhlIGRpc2N1c3Npb24gb2Ygd2hh
dCBSQnMgc2hvdWxkIGRvIHdoZW4gdGhlIGJ5cGFzcyBiaXQgaXMgc2V0L25vdA0Kc2V0IHVuY2xl
YXIuIFRoZSBpbnRlbnQgaXMgZm9yIFJCcyB0byBhZHZlcnRpc2UgbmVpZ2hib3JzIGluIFJlcG9y
dCBzdGF0ZQ0KaW4gdGhlaXIgbm9uLXBzZXVkby1ub2RlIExTUHMgd2hlbiB0aGUgQnlwYXNzIGJp
dCBpcyBzZXQgLSBhbmQgdG8gYWR2ZXJ0aXNlDQp0aGUgbmVpZ2hib3IgdG8gdGhlIHBzZXVkby1u
b2RlIHdoZW4gQnlwYXNzIGJpdCBpcyBOT1Qgc2V0IC0gYnV0IHRoZQ0Kd29yZGluZyB1c2VkIA0K
DQoiZGlyZWN0bHkgcmVwb3J0IHRoZWlyIGFkamFjZW5jaWVzIg0KDQppc24ndCBhcyBjbGVhciBh
cyBpdCBjb3VsZCBiZS4NCg0KQWxzbywgSSBhc3N1bWUgdGhhdCB3aGVuIGFkdmVydGlzaW5nIHRo
ZSBuZWlnaGJvciB0byB0aGUgcHNldWRvLW5vZGUsIHRoZSBzdGF0ZQ0KICgyLXdheSBvciBSZXBv
cnQpIGlzIGluaGVyaXRlZCBmcm9tIHRoZSBzdGF0ZSBvZiB0aGUgYWRqYWNlbmN5IHRvIHRoZSBE
UkI/IEENCmNsZWFyIHNhdGVtZW50IG9mIHRoaXMgd291bGQgYmUgaGVscGZ1bC4NCg0KU2VjdGlv
biA3LjINCi0tLS0tLS0tLS0tLQ0KSXMgSUlIIHBhZGRpbmcgaWdub3JlZCBvbiByZWNlaXB0Pz8g
T3IgaXMgYSBwYWRkZWQgSUlIIGRpc2NhcmRlZD8NCg0KSW4gcmVnYXJkcyB0byB3aGF0IFRMVnMg
c2hvdWxkIGJlIGluIGFuIElJSCwgdGhlIHRleHQgc2F5czoNCg0KICAgSWYgdGhlcmUgYXJlIG5v
IGFkamFjZW5jaWVzIHdpdGggYSBub24temVybyBEZXNpZ25hdGVkIFZMQU4gSGVsbG8NCiAgIEhv
bGRpbmcgdGltZXIsIGFuIGVtcHR5IFRSSUxMIE5laWdoYm9yIFRMViBNVVNUIGJlIGluY2x1ZGVk
IGluIGVhY2gNCiAgIEhlbGxvLiAgSWYgdGhlcmUgYXJlIHN1Y2ggYWRqYWNlbmNpZXMsIHRoZW4g
dGhlIEhlbGxvIE1BWSBjb250YWluIGENCiAgIFRSSUxMIE5laWdoYm9yIFRMViBhcyBkZXNjcmli
ZWQgaW4gU2VjdGlvbiA0LjQuMi4xIG9mIFtSRkN0cmlsbF0uDQoNClRoZSBOZWlnaGJvciBUTFYg
aXMgT05MWSB1c2VkIHRvIHJlcG9ydCBuZWlnaGJvcnMgSSBoYXZlDQpzZWVuIGluIElJSHMgcmVj
ZWl2ZWQgb24gdGhlIEQtVkxBTiBhbmQgaWYgSSBoYXZlIE5PIHN1Y2ggbmVpZ2hib3JzIEkgTVVT
VCANCnNlbmQgYW4gZW1wdHkgbmVpZ2hib3IgVExWIC0gYnV0IGlmIEkgZG8gaGF2ZSBvbmUgb3Ig
bW9yZSBzdWNoIG5laWdoYm9ycyANCnRoZW4gc2VuZGluZyBhIG5laWdoYm9yIFRMViBpcyBvcHRp
b25hbD8/PyBXaGF0IGlzIHRoZSBtb3RpdmF0aW9uIGZvciB0aGlzPw0KDQpPbmUgb2YgdGhlIHVu
ZGVybHlpbmcgY29uY2VybnMgaXMgdGhhdCB0aGUgaW5kaWNhdGlvbiBvZiBhIGNvbm5lY3Rpdml0
eSBjaGFuZ2UNCmluIGEgaGVsbG8gbWF5IGFscmVhZHkgYmUgZGVsYXllZCBiZWNhdXNlIG9mIHNw
YWNlIGxpbWl0YXRpb25zLiBUaGUgYmVoYXZpb3INCnlvdSBzdWdnZXN0IGhlcmUgb25seSBzZWVt
cyB0byBtYWtlIHRoYXQgaXNzdWUgbW9yZSBzaWduaWZpY2FudC4NCg0KDQoNCg==

------_=_NextPart_001_01CBB38B.86D26231
Content-Type: text/plain;
	name="draft-ietf-trill-adj-01_editorial.txt"
Content-Transfer-Encoding: base64
Content-Description: draft-ietf-trill-adj-01_editorial.txt
Content-Disposition: attachment;
	filename="draft-ietf-trill-adj-01_editorial.txt"

DQoyLiBUaGUgVFJJTEwgSGVsbG8gRW52aXJvbm1lbnQgYW5kIFB1cnBvc2VzDQoNCiAgIFtJUy1J
U10gaGFzIHN1Ym5ldCBpbmRlcGVuZGVudCBmdW5jdGlvbnMgYW5kIHN1Ym5ldCBkZXBlbmRlbnQN
Cg0KTEVTOiBJIGJlbGlldmUgYWxsIG9jY3VyZW5jZXMgb2YgInN1Ym5ldCIgc2hvdWxkIHJlYWxs
eSBiZSAic3VibmV0d29yayIuDQoNCiAgIGZ1bmN0aW9ucy4gQ3VycmVudGx5IExheWVyIDMgdXNl
IG9mIElTLUlTIHN1cHBvcnRzIHR3byB0eXBlcyBvZg0KICAgc3VibmV0czogcG9pbnQtdG8tcG9p
bnQgbGluayBzdWJuZXRzIGJldHdlZW4gcm91dGVycyBhbmQgZ2VuZXJhbA0KICAgYnJvYWRjYXN0
IChMQU4pIHN1Ym5ldHMuIEJlY2F1c2Ugb2YgdGhlIGRpZmZlcmVuY2VzIGJldHdlZW4gdGhlDQog
ICBlbnZpcm9ubWVudCBvZiBMYXllciAzIHJvdXRlcnMgYW5kIHRoZSBlbnZpcm9ubWVudCBvZiBU
UklMTCBSQnJpZGdlcywNCiAgIHRoZSBUUklMTCBwcm90b2NvbCB1c2VzIGEgZGlmZmVyZW50IHR5
cGUgb2YgTEFOIHN1Ym5ldCBmcm9tIHRoZQ0KICAgYnJvYWRjYXN0IChMQU4pIHN1Ym5ldCB0eXBl
IGVuY291bnRlcmVkIGF0IExheWVyIDMuIFRoZSBlbnZpcm9ubWVudGFsDQogICBkaWZmZXJlbmNl
cyBhcmUgZGVzY3JpYmVkIGJlbG93IGZvbGxvd2VkIGJ5IGEgc3VtbWF0aW9uLCBpbiBTZWN0aW9u
DQogICAyLjUsIG9mIHRoZSBwdXJwb3NlcyBvZiB0aGUgVFJJTEwgTEFOIEhlbGxvIHByb3RvY29s
Lg0KDQpMRVM6IFN1Z2dlc3RlZCByZXdyaXRlIA0KICAidGhlIFRSSUxMIHByb3RvY29sIHVzZXMg
YSBkaWZmZXJlbnQgdHlwZSBvZiBMQU4gc3VibmV0IGZyb20gdGhlDQogICBicm9hZGNhc3QgKExB
Tikgc3VibmV0IHR5cGUgZW5jb3VudGVyZWQgYXQgTGF5ZXIgMyIgdG8gYmUNCg0KdG8gYmVjb21l
DQoNCiAgIlRoZSBUUklMTCBwcm90b2NvbCB1c2VzIGRpZmZlcmVudCBzdWJuZXR3b3JrIGRlcGVu
ZGVudCBmdW5jdGlvbnMNCiAgZnJvbSB0aG9zZSBzcGVjaWZpZWQgaW4gW0lTLUlTXSBTZWN0aW9u
IDguNC4iDQoNCi4uLg0KDQoyLjUgUHVycG9zZXMgb2YgdGhlIFRSSUxMIEhlbGxvIFByb3RvY29s
DQoNCi4uLg0KDQogICBJbiBMYXllciAzIElTLUlTIGFsbCB0aHJlZSBvZiB0aGVzZSBmdW5jdGlv
bnMgYXJlIGNvbWJpbmVkLiBIZWxsb3MNCiAgIGFyZSBwYWRkZWQgdG8gdGhlIG1heGltdW0gbGVu
Z3RoIHNvIHRoYXQgYSByb3V0ZXIgbmVpZ2hib3IgaXMgbm90DQogICBldmVuIGRpc2NvdmVyZWQg
aWYgaXQgaXMgaW1wb3NzaWJsZSB0byBjb21tdW5pY2F0ZSB3aXRoIGl0IHVzaW5nDQogICBtYXhp
bXVtIHNpemVkIHBhY2tldHMuIEFsc28sIGV2ZW4gaWYgSGVsbG9zIGZyb20gYSBuZWlnaGJvciBS
MiBhcmUNCiAgIHJlY2VpdmVkIGJ5IFIxLCBpZiBjb25uZWN0aXZpdHkgdG8gUjIgaXMgbm90IDIt
d2F5IChpLmUuLCBSMiBkb2VzIG5vdA0KDQoNCkxFUzogUGFkZGluZyBpbiBbSVMtSVNdIGlzIG9w
dGlvbmFsLiBTZWUgUkZDIDM3MTkgU2VjdGlvbiA2IGZvciBhIGRpc2N1c3Npb24uDQoNCi4uLg0K
DQo0LjIgRFJCIEVsZWN0aW9uIEV2ZW50cw0KDQogICBEZXRlcm1pbmF0aW9uIG9mIGV2ZW50cyAz
IGFuZCA0IG9jY3VycyBieSBjb21wYXJpbmcgcHJpb3JpdGllcyAod2l0aA0KICAgbmVpZ2hib3Ig
TUFDIGFkZHJlc3MgKFNOUEEpIGFzIGEgdGllIGJyZWFrZXIgYW5kIFBvcnQgSUQgYXMgYQ0KICAg
c2Vjb25kYXJ5IHRpZSBicmVha2VyKSBhY3Jvc3MgYWxsIGVudHJpZXMgaW4gdGhlIHBvcnQncyBh
ZGphY2VuY3kNCiAgIHRhYmxlIGluY2x1ZGluZyB0aG9zZSBpbiB0aGUgRGV0ZWN0IGFuZCAyLVdh
eSBzdGF0ZXMgYXMgd2VsbCBhcyB0aG9zZQ0KICAgaW4gdGhlIFJlcG9ydCBzdGF0ZS4NCg0KTEVT
OiBUaGUgaGlnaGVzdCBQb3J0IElEIGlzIHByZWZlcnJlZD8/PyBOZWVkIGFuIGV4cGxpY2l0IHN0
YXRlbWVudC4NCg0KLi4uDQoNCjUuIE1UVSBNYXRjaGluZw0KDQouLi4NCg0KICAgQW4gUkJyaWRn
ZSwgUkIxLCBkZXRlcm1pbmVzIHRoZSBkZXNpcmVkIGNhbXB1cyBsaW5rIE1UVSBieQ0KICAgY2Fs
Y3VsYXRpbmcgdGhlIG1pbmltdW0gb2YgaXRzIG9yaWdpbmF0aW5nTDFMU1BCdWZmZXJTaXplIGFu
ZCB0aGUNCiAgIG9yaWdpbmF0aW5nTFNQQnVmZmVyU2l6ZSBhZHZlcnRpc2VkIGluIHRoZSBsaW5r
IHN0YXRlIGRhdGFiYXNlIGJ5DQoNCkxFUzogVGhlc2Ugc2hvdWxkIGFsbCBiZSAib3JpZ2luYXRp
bmdMMUxTUEJ1ZmZlclNpemUiLg0KKHlvdSBoYXZlIG9taXR0ZWQgIkwxIiBpbiBzb21lIGNhc2Vz
KQ0KDQoNCjYuIFBzZXVkb25vZGVzDQoNCiAgIFRoZSBEZXNpZ25hdGVkIFJCcmlkZ2UgKERSQiks
IGRldGVybWluZWQgYXMgZGVzY3JpYmVkIGFib3ZlLCBjb250cm9scw0KICAgd2hldGhlciBhIHBz
ZXVkb25vZGUgd2lsbCBiZSB1c2VkIG9uIGEgbGluay4NCg0KICAgSXQgaXMgYW50aWNpcGF0ZWQg
dGhhdCBtYW55IGxpbmtzIGJldHdlZW4gUkJyaWRnZXMgd2lsbCBhY3R1YWxseSBiZQ0KICAgcG9p
bnQtdG8tcG9pbnQsIGluIHdoaWNoIGNhc2UgdXNpbmcgYSBwc2V1ZG9ub2RlIG1lcmVseSBhZGRz
IHRvIHRoZQ0KICAgY29tcGxleGl0eS4gSWYgdGhlIERSQiBzZXRzIHRoZSBieXBhc3MgcHNldWRv
bm9kZSBiaXQgaW4gaXRzIFRSSUxMDQogICBMQU4gSGVsbG9zLCB0aGUgUkJyaWRnZXMgb24gdGhl
IGxpbmsganVzdCBkaXJlY3RseSByZXBvcnQgdGhlaXINCiAgIGFkamFjZW5jaWVzIHRoYXQgYXJl
IGluIHRoZSBSZXBvcnQgc3RhdGUuIElmIHRoZSBEUkIgZG9lcyBub3Qgc2V0IHRoZQ0KICAgYnlw
YXNzIHBzZXVkb25vZGUgYml0IGluIGl0cyBUUklMTCBIZWxsb3MsIHRoZW4gaXQgc3BlY2lmaWVz
IGENCiAgIHBzZXVkb25vZGUgZm9yIHRoZSBsaW5rIGFuZCBzZW5kcyBMU1BzIG9uIGJlaGFsZiBv
ZiB0aGUgcHNldWRvbm9kZSBhcw0KICAgdXN1YWwuIFNldHRpbmcgdGhlIGJ5cGFzcyBwc2V1ZG9u
b2RlIGJpdCBoYXMgbm8gZWZmZWN0IG9uIGhvdyBMU1BzDQogICBhcmUgZmxvb2RlZCBvbiBhIGxp
bmsuIEl0IG9ubHkgYWZmZWN0cyB3aGF0IExTUHMgYXJlIGdlbmVyYXRlZC4NCg0KTEVTOiBUaGUg
cGhyYXNlICJzcGVjaWZpZXMgYSBwc2V1ZG8tbm9kZSBmb3IgdGhlIGxpbmsiIHN1Z2dlc3RzIHRo
YXQNCnRoZSBMQU5JRCBzZW50IGJ5IHRoZSBEUkIgbWF5IGJlIGRpZmZlcmVudCBkZXBlbmRpbmcg
b24gd2hldGhlciB0aGUNCmJ5cGFzcyBwc2V1ZG8tbm9kZSBiaXQgaXMgc2V0IG9yIG5vdC4gRG8g
eW91IHJlYWxseSBtZWFuIHRoYXQ/DQoNCg==

------_=_NextPart_001_01CBB38B.86D26231
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

------_=_NextPart_001_01CBB38B.86D26231--

From rbridge-bounces@postel.org  Thu Jan 13 20:33:13 2011
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 C55033A6C4C for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 13 Jan 2011 20:33:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.98
X-Spam-Level: 
X-Spam-Status: No, score=-2.98 tagged_above=-999 required=5 tests=[AWL=-0.381, 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 7IvOYv2IC2jH for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 13 Jan 2011 20:33:11 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 804373A6C42 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 13 Jan 2011 20:33:11 -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 p0E4Hnqm020128; Thu, 13 Jan 2011 20:17:51 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0E4GxwX020057 for <rbridge@postel.org>; Thu, 13 Jan 2011 20:17:08 -0800 (PST)
Received: by wwd20 with SMTP id 20so2664007wwd.21 for <rbridge@postel.org>; Thu, 13 Jan 2011 20:16:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=n0vVR/sBYxfirCDf9l0mJjqp0EXCAAT/zeI4Fmfoswo=; b=PT1PhnlgncAsIyzrEl3sgL+7zL1qblSHy9eArY3C6JKWZE4P1gqTQhYBjub/yuscnR 62fTJjmGtRrjRgVXrf4z7aCqnJ7JOmmP1pDOyw9o/CZDA9zZjkm6zpBxj3HrhyTv7FVe vSbXMa7F5uTDaCUJhRSp7A78uqy5GTOIFYFug=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=K4CGO2bY/pTSI4WDPUnmsEUvPoSJ7Ug4luJ6ZIsUA+pIXUKaZC0sCi5igtvff5aQHd A1jU1Trz5w2Mm8sQQHU75ZzehYTcbB5ZVAvMY97QVyiSVicP4KNnB+CIE3rt/0PKajtD Ke5nA2KgN+DE5hLKgsymIxqfknQc7oPY6O308=
MIME-Version: 1.0
Received: by 10.216.159.69 with SMTP id r47mr1224748wek.105.1294978617135; Thu, 13 Jan 2011 20:16:57 -0800 (PST)
Received: by 10.216.139.219 with HTTP; Thu, 13 Jan 2011 20:16:57 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com>
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com>
Date: Thu, 13 Jan 2011 20:16:57 -0800
Message-ID: <AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: vishwas.ietf@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0E4GxwX020057
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

My comments attached on the technical comments:

Reliable Circuit Scope Flooding
--------------------------------

[RFCTrill] defines a requirement for reliable circuit scoped flooding of
Appointed Forwarder Information (Section 4.4.2) but it is not specified
how this is to be achieved. I had hoped this document would provide that
specification.

The lack of reliable flooding means that either:

a)Appointed forwarder information MUST be included by the DRB always -
which does not scale well

OR

b)Loops and/or loss of traffic for a given VLAN MAY occur

VM> One way to do it will be to send it Hello Multiplier + 1 times in
the Hello. If a neighbor misses all the Hellos it will anyway bring
down its adjacency and it will be noticed, otherwise the information
will be reliably exchanged.

Preventing Multiple DRBs on a LAN
---------------------------------

It is not clear to me how the use of multiple announcing VLANs achieves
the stated goal of one and only one DRB in the presence of inconsistent
connectivity / configuration. Consider the following simple example where
VLANs(1,2,3) are in the enabled set on all RBs:

RB Name/     DVLAN   Announcing VLANs   VLAN Connectivity
Priority
--------------------------------------------------------
RB1/50         1       1,2              1,2,3
RB2/60         1       1                1
RB3/70         3       2                2,3

Given the above the following would ensue:

RB Name     Neighbors       DRB/
             Detected       DVLAN
--------------------------------------------------------
RB1            2,3          3/2
RB2            1            2/1
RB3            2,3          3/2

Now, given the above, both RB3 and RB2 will think they are DRB and potentia=
lly
assign multiple AFs for each of the VLANs. Keeping in mind [TRILL]
Section 4.4.3

"Great care should be taken in configuring an RBridge
   to not send TRILL Hellos on any VLAN where that RBridge is appointed
   forwarder as, under some circumstances, this can lead to loops."

it becomes apparent that at a minimum at least one RB MUST send IIHs on each
enabled VLAN in order to implement loop prevention. But this does not scale
well.

VM> Les it is stated that:

 Designated VLAN: the VLAN being used on the link for all TRILL frames
except some TRILL Hellos.  This is RBn's Desired Designated VLAN if
RBn believes it is the DRB or the Designated VLAN in the DRB's Hellos
if RBn is not the DRB.

This means is that there is atleast one VLAN which is common to all
devices on the link. The example you have given above would be a
configuration issue. The protocol does not deal with configuration
issues.

Section 3.3
-------------

Text says that for hellos received on a VLAN Other than the D-VLAN

"any TRILL Neighbor TLV in such a Hello is ignored..."

I assume this means that it is an implementation choice as to whether to
include the neighbor TLV in such hellos? A clear statement of this would
be helpful.
VM> Neighbor TLV is ignored on receipt and not sent. It is in the
spirit of being liberal while accepting, and being strict while
sending.

Section 4
----------

There needs to be a description of the DRB election process -
equivalent to what is in [IS-IS] Section 8.4.5. For example, the set of
DRB candidates includes all RBs to which the local system has an adjacency
in Detect, 2-way, or Report State ...correct?

You also need to specify in what DRB election states a DRB reports neighbors
in pseudo-node LSPs. It would seem that if neighbors are advertised in
pre-DRB state that we could attract traffic which we are not yet able to
forward.
VM> I think it is well specified. Like clearly mentioned DRB election
happens independent of the neighbor state.

Section 4.2
-----------

When a DRB change causes a change in D-VLAN, the draft says:

      o  The non-Designated VLAN Hello Holding timer is set to the
         maximum of its time to expiration and the time to expiration of
         the Designated VLAN Hello Holding timer.

The "Designated VLAN Hello Holding timer" referred to is the OLD Designated
VLAN Hello Holding timer, correct? If so adding that clarification would he=
lp.
VM> That is correct.

Also, if we are NOT DRB and the new D-VLAN is NOT in the set of announcing
VLANs then the non-DRBs have to include the new D-VLAN in the set of VLANS =
for
which they send hellos, correct? This should be specified.
VM> OK.

It is also apparent that DRB changes are very disruptive - even more so than
at Layer 3. In Layer 3 on a DIS change optimal behavior is to do a "make
before break" to minimize disruption. However, that is not possible here as
all adjacencies will go into "Detect" state following a DRB change.
Should it be recommended then to avoid DRB changes whenever possible
(e.g.
by setting LAN priority)?

VM> I think it is stated in multiple places that DRB change is
diruptive and that is why the algorithm is designed the way it is.

Section 5
---------

[TRILL] 4.3.2 states:

"The MTU-probe MAY be multicast to All-RBridges, or unicast to a specific
RBridge. The MTU-ack is  normally unicast to the source of the MTU-probe
to which it responds  but MAY be multicast to All-RBridges."

How does the sender of the Probe/ACK determine whether to use unicast or
multicast destination address?

VM> By default MTU-Probe and ACK will be unicast. It could be
configured to do it a different way. A reason MTU-probe could be
multicast is when a new device first joins a link, which already has
Rbridges attached.

If an MTU-ACK is sent to multicast address what should the receivers who
did not initiate the probe do with the ACK? Ignore? Process?
VM> It is processed.

On a LAN should MTU probes only be sent to/from the DRB when pseudo-node
bypass is NOT set? It seems useless to do otherwise - but this is not
discussed.

Also, don't you need PORT ID in the Probe Source/ACK Source in the MTU PDU
to fully identify the source/responder?

It would have been better in terms of use of the limited PDU type space to
define only one new PDU type and encode the probe/ack inside of the PDU.

Also, this particular area exemplifies how difficult it is to come to a
full understanding of proper behavior. [TRILL] must be consulted to find
a description of how to send the PDUs, [RFCtisis] must be consulted to find
the PDU code points and formats, and the TRILL-adj document must be consult=
ed
to find a description of how to incorporate MTU test results into the
hello process.

Section 6
-----------

I find the discussion of what RBs should do when the bypass bit is set/not
set unclear. The intent is for RBs to advertise neighbors in Report state
in their non-pseudo-node LSPs when the Bypass bit is set - and to advertise
the neighbor to the pseudo-node when Bypass bit is NOT set - but the
wording used

"directly report their adjacencies"

isn't as clear as it could be.

Also, I assume that when advertising the neighbor to the pseudo-node, the s=
tate
 (2-way or Report) is inherited from the state of the adjacency to the DRB?=
 A
clear satement of this would be helpful.
VM> Clarity could be added.

Section 7.2
------------
Is IIH padding ignored on receipt?? Or is a padded IIH discarded?

In regards to what TLVs should be in an IIH, the text says:

   If there are no adjacencies with a non-zero Designated VLAN Hello
   Holding timer, an empty TRILL Neighbor TLV MUST be included in each
   Hello.  If there are such adjacencies, then the Hello MAY contain a
   TRILL Neighbor TLV as described in Section 4.4.2.1 of [RFCtrill].

The Neighbor TLV is ONLY used to report neighbors I have
seen in IIHs received on the D-VLAN and if I have NO such neighbors I MUST
send an empty neighbor TLV - but if I do have one or more such neighbors
then sending a neighbor TLV is optional??? What is the motivation for this?
VM> The idea is we should not pad, because packets may not get through
due to difference in MTU. However if it is received I think there is
no reason to do anything different for it.

Thanks,
Vishwas

On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
> (resending w corrected TRILL WG address)
>
> Attached please find my comments on draft-ietf-trill-adj-01.
>
> The file draft-ietf-trill-adj-01_comments.txt contains substantive
> comments identified by Section # - except in a couple of cases where the
> remarks are more generic.
>
> The file draft-ietf-trill-adj-01_editorial.txt is portions of the draft
> annotated with editorial comments. Search for "LES:" in the file.
>
> As context, the requirements of [TRILL] introduce the need to send a
> great deal more circuit scoped information on a LAN as compared to Layer
> 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
> [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
> information and to provide robust loop prevention in the forwarding of
> data. But I believe the extensions as currently defined have significant
> scalability issues in the presence of a large number of neighbors on a
> LAN and/or a large number of enabled VLANs. In my comments I have
> confined myself to pointing out where I believe such issues arise. If
> there is consensus that these are issues which should be addressed, then
> additional discussions can be started as to how to do so.
>
> Finally, I would like to thank the authors of draft-ietf-trill-adj-01
> for the effort and diligence they obviously applied to the writing of
> this draft.
>
> =A0 Les
>
>
> _______________________________________________
> rbridge mailing list
> rbridge@postel.org
> http://mailman.postel.org/mailman/listinfo/rbridge
>
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 14 09:12:15 2011
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 BF92828C0E9 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 09:12:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.014
X-Spam-Level: 
X-Spam-Status: No, score=-5.014 tagged_above=-999 required=5 tests=[AWL=-3.615, BAYES_00=-2.599, J_CHICKENPOX_15=0.6, J_CHICKENPOX_19=0.6]
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 ShL+3Q6YIpgv for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 09:12:14 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 1B4F628C10F for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 14 Jan 2011 09:12:14 -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 p0EH2u89027282; Fri, 14 Jan 2011 09:02:59 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0EH2HaE027224 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Fri, 14 Jan 2011 09:02:26 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAM8QME2rRN+J/2dsb2JhbACkVnOiKphmgneCWASEa4lTgnA
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-2.cisco.com with ESMTP; 14 Jan 2011 17:02:12 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p0EH2C1h012643; Fri, 14 Jan 2011 17:02:12 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Jan 2011 09:02:12 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 14 Jan 2011 09:02:09 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Thread-Index: AcuzoeaM2vFz035hTA+jAC+ExMT9oAAaCcjw
References: <4D221B2B.2020207@acm.org><AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com> <AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 14 Jan 2011 17:02:12.0017 (UTC) FILETIME=[C94E9A10:01CBB40C]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0EH2HaE027224
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Vishwas -

Thanx for the reply.
Inline.

> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> Sent: Thursday, January 13, 2011 8:17 PM
> To: Les Ginsberg (ginsberg)
> Cc: isis-wg@ietf.org; rbridge@postel.org
> Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
> =

> Hi Les,
> =

> My comments attached on the technical comments:
> =

> Reliable Circuit Scope Flooding
> --------------------------------
> =

> [RFCTrill] defines a requirement for reliable circuit scoped flooding
> of
> Appointed Forwarder Information (Section 4.4.2) but it is not specified
> how this is to be achieved. I had hoped this document would provide
> that
> specification.
> =

> The lack of reliable flooding means that either:
> =

> a)Appointed forwarder information MUST be included by the DRB always -
> which does not scale well
> =

> OR
> =

> b)Loops and/or loss of traffic for a given VLAN MAY occur
> =

> VM> One way to do it will be to send it Hello Multiplier + 1 times in
> the Hello. If a neighbor misses all the Hellos it will anyway bring
> down its adjacency and it will be noticed, otherwise the information
> will be reliably exchanged.

This only works (with some caveats) in the case where the complete set of A=
ppointed Forwarder information is contained within a single hello. But in l=
arge scale deployments it is likely that each hello will only contain a sub=
set of the appointed forwarder information, in which case the strategy you =
suggest only guarantees that at least one of the subsets has been seen by t=
he neighbor.


> =

> Preventing Multiple DRBs on a LAN
> ---------------------------------
> =

> It is not clear to me how the use of multiple announcing VLANs achieves
> the stated goal of one and only one DRB in the presence of inconsistent
> connectivity / configuration. Consider the following simple example
> where
> VLANs(1,2,3) are in the enabled set on all RBs:
> =

> RB Name/     DVLAN   Announcing VLANs   VLAN Connectivity
> Priority
> --------------------------------------------------------
> RB1/50         1       1,2              1,2,3
> RB2/60         1       1                1
> RB3/70         3       2                2,3
> =

> Given the above the following would ensue:
> =

> RB Name     Neighbors       DRB/
>              Detected       DVLAN
> --------------------------------------------------------
> RB1            2,3          3/2
> RB2            1            2/1
> RB3            2,3          3/2
> =

> Now, given the above, both RB3 and RB2 will think they are DRB and
> potentially
> assign multiple AFs for each of the VLANs. Keeping in mind [TRILL]
> Section 4.4.3
> =

> "Great care should be taken in configuring an RBridge
>    to not send TRILL Hellos on any VLAN where that RBridge is appointed
>    forwarder as, under some circumstances, this can lead to loops."
> =

> it becomes apparent that at a minimum at least one RB MUST send IIHs on
> each
> enabled VLAN in order to implement loop prevention. But this does not
> scale
> well.
> =

> VM> Les it is stated that:
> =

>  Designated VLAN: the VLAN being used on the link for all TRILL frames
> except some TRILL Hellos.  This is RBn's Desired Designated VLAN if
> RBn believes it is the DRB or the Designated VLAN in the DRB's Hellos
> if RBn is not the DRB.
> =

> This means is that there is atleast one VLAN which is common to all
> devices on the link. The example you have given above would be a
> configuration issue. The protocol does not deal with configuration
> issues.

Misconfiguration is not what the example is trying to show. All VLANs are e=
nabled on all RBs in the example above, but there is a connectivity issue o=
n VLANS 2,3 for RB2. This is obviously a pathological case, but as [TRILL] =
emphasizes the importance of being able to handle such cases I am simply de=
monstrating that the extensions are not able to deal with all cases.

If we can assume that there are never any connectivity issues and - as you =
say - the protocol "does not deal with configuration issues", then sending =
hellos on one VLAN would be sufficient - but the concern throughout all of =
the TRILL documents is that such an assumption is not safe.

> =

> Section 3.3
> -------------
> =

> Text says that for hellos received on a VLAN Other than the D-VLAN
> =

> "any TRILL Neighbor TLV in such a Hello is ignored..."
> =

> I assume this means that it is an implementation choice as to whether
> to
> include the neighbor TLV in such hellos? A clear statement of this
> would
> be helpful.
> VM> Neighbor TLV is ignored on receipt and not sent. It is in the
> spirit of being liberal while accepting, and being strict while
> sending.

Agreed - but it would be better to state that explicitly.

> =

> Section 4
> ----------
> =

> There needs to be a description of the DRB election process -
> equivalent to what is in [IS-IS] Section 8.4.5. For example, the set of
> DRB candidates includes all RBs to which the local system has an
> adjacency
> in Detect, 2-way, or Report State ...correct?
> =

> You also need to specify in what DRB election states a DRB reports
> neighbors
> in pseudo-node LSPs. It would seem that if neighbors are advertised in
> pre-DRB state that we could attract traffic which we are not yet able
> to
> forward.
> VM> I think it is well specified. Like clearly mentioned DRB election
> happens independent of the neighbor state.

I do think more clarity would be desirable.
Can you comment on the second point regarding in what "DRB election state" =
(NOT neighbor state) neighbors are advertised?

> =

> Section 4.2
> -----------
> =

> When a DRB change causes a change in D-VLAN, the draft says:
> =

>       o  The non-Designated VLAN Hello Holding timer is set to the
>          maximum of its time to expiration and the time to expiration
> of
>          the Designated VLAN Hello Holding timer.
> =

> The "Designated VLAN Hello Holding timer" referred to is the OLD
> Designated
> VLAN Hello Holding timer, correct? If so adding that clarification
> would help.
> VM> That is correct.
> =

> Also, if we are NOT DRB and the new D-VLAN is NOT in the set of
> announcing
> VLANs then the non-DRBs have to include the new D-VLAN in the set of
> VLANS for
> which they send hellos, correct? This should be specified.
> VM> OK.
> =

> It is also apparent that DRB changes are very disruptive - even more so
> than
> at Layer 3. In Layer 3 on a DIS change optimal behavior is to do a
> "make
> before break" to minimize disruption. However, that is not possible
> here as
> all adjacencies will go into "Detect" state following a DRB change.
> Should it be recommended then to avoid DRB changes whenever possible
> (e.g.
> by setting LAN priority)?
> =

> VM> I think it is stated in multiple places that DRB change is
> diruptive and that is why the algorithm is designed the way it is.
> =


Agreed. I am suggesting that because of the highly disruptive nature of DRB=
 changes that it would be prudent to recommend taking steps to minimize the=
 occurrence of such changes.


> Section 5
> ---------
> =

> [TRILL] 4.3.2 states:
> =

> "The MTU-probe MAY be multicast to All-RBridges, or unicast to a
> specific
> RBridge. The MTU-ack is  normally unicast to the source of the MTU-
> probe
> to which it responds  but MAY be multicast to All-RBridges."
> =

> How does the sender of the Probe/ACK determine whether to use unicast
> or
> multicast destination address?
> =

> VM> By default MTU-Probe and ACK will be unicast. It could be
> configured to do it a different way. A reason MTU-probe could be
> multicast is when a new device first joins a link, which already has
> Rbridges attached.

I have not found any statement in any of the relevant TRILL documents that =
states "unicast is the default". Apologies if I missed it.

That said, on a LAN it would be more efficient for the DRB to multicast the=
 probes, non-DRB to unicast probes to the DRB only, and all ACKS be multica=
st.

> =

> If an MTU-ACK is sent to multicast address what should the receivers
> who
> did not initiate the probe do with the ACK? Ignore? Process?
> VM> It is processed.
> =

> On a LAN should MTU probes only be sent to/from the DRB when pseudo-
> node
> bypass is NOT set? It seems useless to do otherwise - but this is not
> discussed.
> =

> Also, don't you need PORT ID in the Probe Source/ACK Source in the MTU
> PDU
> to fully identify the source/responder?
> =

> It would have been better in terms of use of the limited PDU type space
> to
> define only one new PDU type and encode the probe/ack inside of the
> PDU.
> =

> Also, this particular area exemplifies how difficult it is to come to a
> full understanding of proper behavior. [TRILL] must be consulted to
> find
> a description of how to send the PDUs, [RFCtisis] must be consulted to
> find
> the PDU code points and formats, and the TRILL-adj document must be
> consulted
> to find a description of how to incorporate MTU test results into the
> hello process.
> =

> Section 6
> -----------
> =

> I find the discussion of what RBs should do when the bypass bit is
> set/not
> set unclear. The intent is for RBs to advertise neighbors in Report
> state
> in their non-pseudo-node LSPs when the Bypass bit is set - and to
> advertise
> the neighbor to the pseudo-node when Bypass bit is NOT set - but the
> wording used
> =

> "directly report their adjacencies"
> =

> isn't as clear as it could be.
> =

> Also, I assume that when advertising the neighbor to the pseudo-node,
> the state
>  (2-way or Report) is inherited from the state of the adjacency to the
> DRB? A
> clear satement of this would be helpful.
> VM> Clarity could be added.
> =

> Section 7.2
> ------------
> Is IIH padding ignored on receipt?? Or is a padded IIH discarded?
> =

> In regards to what TLVs should be in an IIH, the text says:
> =

>    If there are no adjacencies with a non-zero Designated VLAN Hello
>    Holding timer, an empty TRILL Neighbor TLV MUST be included in each
>    Hello.  If there are such adjacencies, then the Hello MAY contain a
>    TRILL Neighbor TLV as described in Section 4.4.2.1 of [RFCtrill].
> =

> The Neighbor TLV is ONLY used to report neighbors I have
> seen in IIHs received on the D-VLAN and if I have NO such neighbors I
> MUST
> send an empty neighbor TLV - but if I do have one or more such
> neighbors
> then sending a neighbor TLV is optional??? What is the motivation for
> this?
> VM> The idea is we should not pad, because packets may not get through
> due to difference in MTU. However if it is received I think there is
> no reason to do anything different for it.

In regards to padding, I agree - but would like to see an explicit statemen=
t.

You have not commented on the motivation for omitting a neighbor TLV from a=
 hello when adjacencies are present.

   Les


> =

> Thanks,
> Vishwas
> =

> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
> <ginsberg@cisco.com> wrote:
> > (resending w corrected TRILL WG address)
> >
> > Attached please find my comments on draft-ietf-trill-adj-01.
> >
> > The file draft-ietf-trill-adj-01_comments.txt contains substantive
> > comments identified by Section # - except in a couple of cases where
> the
> > remarks are more generic.
> >
> > The file draft-ietf-trill-adj-01_editorial.txt is portions of the
> draft
> > annotated with editorial comments. Search for "LES:" in the file.
> >
> > As context, the requirements of [TRILL] introduce the need to send a
> > great deal more circuit scoped information on a LAN as compared to
> Layer
> > 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
> > [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
> > information and to provide robust loop prevention in the forwarding
> of
> > data. But I believe the extensions as currently defined have
> significant
> > scalability issues in the presence of a large number of neighbors on
> a
> > LAN and/or a large number of enabled VLANs. In my comments I have
> > confined myself to pointing out where I believe such issues arise. If
> > there is consensus that these are issues which should be addressed,
> then
> > additional discussions can be started as to how to do so.
> >
> > Finally, I would like to thank the authors of draft-ietf-trill-adj-01
> > for the effort and diligence they obviously applied to the writing of
> > this draft.
> >
> > =A0 Les
> >
> >
> > _______________________________________________
> > rbridge mailing list
> > rbridge@postel.org
> > http://mailman.postel.org/mailman/listinfo/rbridge
> >
> >

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 14 10:19:59 2011
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 BAB8F3A6C7C for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 10:19:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.97
X-Spam-Level: 
X-Spam-Status: No, score=-2.97 tagged_above=-999 required=5 tests=[AWL=-0.371, 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 vw13q2ZzbcYq for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 10:19:58 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 7BC8E3A6C7B for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 14 Jan 2011 10:19:58 -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 p0EII3qH011354; Fri, 14 Jan 2011 10:18:07 -0800 (PST)
Received: from mail-wy0-f180.google.com (mail-wy0-f180.google.com [74.125.82.180]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0EIHLNu011226 for <rbridge@postel.org>; Fri, 14 Jan 2011 10:17:31 -0800 (PST)
Received: by wyb28 with SMTP id 28so2997400wyb.39 for <rbridge@postel.org>; Fri, 14 Jan 2011 10:17:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EurL9b6lTAe+LTT1Fm1VyTBHm+HIdXQ82p71OZsEdVE=; b=Oht+9tHGbWUHx24M8wWR7IAJH2Jsu+48FT0sRfcF+beoGWIvWYA5zby1Iev066+IqF 1TSikG+CTihD+nhhL00wUV7qvdGV/zxSyGgNnsW1uv6mroXG5IZh1HtJUBagGV7Fn2dA 5dujBgvQrwIpO2DCSQgrRhwJhFWQb7aCiEiWo=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=T+DStIJW4uf5F5dtjurjlXhSPkaMAilpoIAITUMrxDTmBkA0EK9wGWtOVZ+wvfq889 2zVJn0P9XKOhDuTxMVjFOZKQ4ofFmP6Qs+2sCmVVTBXFAeb9HgrBy5UpgLK4dNeHYc/z j2u4V47KSrvGhzoZDZWOXkEQu6Emce4a79zJM=
MIME-Version: 1.0
Received: by 10.216.155.205 with SMTP id j55mr1885726wek.90.1295029034520; Fri, 14 Jan 2011 10:17:14 -0800 (PST)
Received: by 10.216.139.219 with HTTP; Fri, 14 Jan 2011 10:17:14 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com>
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com> <AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com>
Date: Fri, 14 Jan 2011 10:17:14 -0800
Message-ID: <AANLkTim2Zyx_NTHxm35K6b5gseMkO4RR-9um4b-YL=Wt@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: vishwas.ietf@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0EIHLNu011226
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

Good we are nearly on the same page regarding most of it.

>> VM> One way to do it will be to send it Hello Multiplier + 1 times in
>> the Hello. If a neighbor misses all the Hellos it will anyway bring
>> down its adjacency and it will be noticed, otherwise the information
>> will be reliably exchanged.
>
> This only works (with some caveats) in the case where the complete set of=
 Appointed Forwarder information is contained within a single hello. But in=
 large scale deployments it is likely that each hello will only contain a s=
ubset of the appointed forwarder information, in which case the strategy yo=
u suggest only guarantees that at least one of the subsets has been seen by=
 the neighbor.

VM> I agree, with the information in more then one Hello (which should
not be a very common case) we may have to send the information more
times. That said in most Layer-2 protocols, just sending an
information like 3 times is treated as reliable sending.

>> Preventing Multiple DRBs on a LAN
>> ---------------------------------
>>
>> It is not clear to me how the use of multiple announcing VLANs achieves
>> the stated goal of one and only one DRB in the presence of inconsistent
>> connectivity / configuration.
>> VM> Les it is stated that:
>>
>> =A0Designated VLAN: the VLAN being used on the link for all TRILL frames
>> except some TRILL Hellos. =A0This is RBn's Desired Designated VLAN if
>> RBn believes it is the DRB or the Designated VLAN in the DRB's Hellos
>> if RBn is not the DRB.
>>
>> This means is that there is atleast one VLAN which is common to all
>> devices on the link. The example you have given above would be a
>> configuration issue. The protocol does not deal with configuration
>> issues.
> Misconfiguration is not what the example is trying to show. All VLANs are=
 enabled on all RBs in the example above, but there is a connectivity issue=
 on VLANS 2,3 for RB2. This is obviously a pathological case, but as [TRILL=
] emphasizes the importance of being able to handle such cases I am simply =
demonstrating that the extensions are not able to deal with all cases.
>
> If we can assume that there are never any connectivity issues and - as yo=
u say - the protocol "does not deal with configuration issues", then sendin=
g hellos on one VLAN would be sufficient - but the concern throughout all o=
f the TRILL documents is that such an assumption is not safe.

VM> I think the idea is that we need to do things for most of the
cases. However there might be a very minor percentage(.0001%) of the
cases where things may not work. That however does not mean we leave
it as best effort.


> I do think more clarity would be desirable.
> Can you comment on the second point regarding in what "DRB election state=
" (NOT neighbor state) neighbors are advertised?
VM> Neighbors are still advertized after the 2-way state. BTW, IS-Is
does not itself deal with corner cases. So unlike OSPF where the
entire data base needs to be acknowledged before a neighbor is
advertized in the LS information, in IS-Is we advertize it before,
which could always lead to the case you mention. On Broadcast links
CSNP's are periodically advertized, if I remember it right.

>> VM> By default MTU-Probe and ACK will be unicast. It could be
>> configured to do it a different way. A reason MTU-probe could be
>> multicast is when a new device first joins a link, which already has
>> Rbridges attached.
>
> I have not found any statement in any of the relevant TRILL documents tha=
t states "unicast is the default". Apologies if I missed it.
>
> That said, on a LAN it would be more efficient for the DRB to multicast t=
he probes, non-DRB to unicast probes to the DRB only, and all ACKS be multi=
cast.

VM> I agree with you. It is left to an implementation to decide how to do i=
t.

>> VM> The idea is we should not pad, because packets may not get through
>> due to difference in MTU. However if it is received I think there is
>> no reason to do anything different for it.
>
> In regards to padding, I agree - but would like to see an explicit statem=
ent.

VM> Ok.

> You have not commented on the motivation for omitting a neighbor TLV from=
 a hello when adjacencies are present.
VM> I think the intent is the reverse.  If we have Neighbors and after
adjacency down we do not have any adjacencies, the aim is to still
send the Hello to the neighbor stating that there are no other
neighbors remaining.

Thanks,
Vishwas

>>
>> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
>> <ginsberg@cisco.com> wrote:
>> > (resending w corrected TRILL WG address)
>> >
>> > Attached please find my comments on draft-ietf-trill-adj-01.
>> >
>> > The file draft-ietf-trill-adj-01_comments.txt contains substantive
>> > comments identified by Section # - except in a couple of cases where
>> the
>> > remarks are more generic.
>> >
>> > The file draft-ietf-trill-adj-01_editorial.txt is portions of the
>> draft
>> > annotated with editorial comments. Search for "LES:" in the file.
>> >
>> > As context, the requirements of [TRILL] introduce the need to send a
>> > great deal more circuit scoped information on a LAN as compared to
>> Layer
>> > 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
>> > [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
>> > information and to provide robust loop prevention in the forwarding
>> of
>> > data. But I believe the extensions as currently defined have
>> significant
>> > scalability issues in the presence of a large number of neighbors on
>> a
>> > LAN and/or a large number of enabled VLANs. In my comments I have
>> > confined myself to pointing out where I believe such issues arise. If
>> > there is consensus that these are issues which should be addressed,
>> then
>> > additional discussions can be started as to how to do so.
>> >
>> > Finally, I would like to thank the authors of draft-ietf-trill-adj-01
>> > for the effort and diligence they obviously applied to the writing of
>> > this draft.
>> >
>> > =A0 Les
>> >
>> >
>> > _______________________________________________
>> > rbridge mailing list
>> > rbridge@postel.org
>> > http://mailman.postel.org/mailman/listinfo/rbridge
>> >
>> >
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 14 12:49:52 2011
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 C67E33A6C6B for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 12:49:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.962
X-Spam-Level: 
X-Spam-Status: No, score=-2.962 tagged_above=-999 required=5 tests=[AWL=-0.363, 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 dVdIVOLKAokL for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 12:49:51 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 74F0C3A6A85 for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 14 Jan 2011 12:49:51 -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 p0EKkHOF010537; Fri, 14 Jan 2011 12:46:18 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0EKjKK7010360 for <rbridge@postel.org>; Fri, 14 Jan 2011 12:45:29 -0800 (PST)
Received: by wwd20 with SMTP id 20so3524917wwd.21 for <rbridge@postel.org>; Fri, 14 Jan 2011 12:45:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=RGMCzlN+KKNt3g4xlZNBllGp51g5hOW3WB8BY0ORLDg=; b=nJKBKk4pYnRu3EPBKEl7oV2f9VS6pXJBT7+x1IuNZRz6QhlDfSZVMDw47ImKwQxaA8 snjl/LNc5TE0n5E28JqeX6eREHUw4HBwQj801cbGKX+pXRiJ8neDTLmQMqmrbtv85nA4 Q4a0IV+R0VW89kRf3a2pkMj0lBjC4ZUH4EThU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=xAgj5gXXC3lAaHoaJDbPX2Duv26q/dnIK+90y5ATZ84okZNo17cmQ/3ZpA19S3IIAG prgdb0be/meLt61XbdkNjYEMHtup4qhR4vae6pTIPMNry80nEWIdz9Rb8ajHHkEMl35k nL2fWu7exmal/a4FSdO/HhkceaTbQ0P7phOBw=
MIME-Version: 1.0
Received: by 10.216.205.213 with SMTP id j63mr2044636weo.60.1295037827110; Fri, 14 Jan 2011 12:43:47 -0800 (PST)
Received: by 10.216.139.219 with HTTP; Fri, 14 Jan 2011 12:43:46 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D0DF816@xmb-sjc-222.amer.cisco.com>
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com> <AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com> <AANLkTim2Zyx_NTHxm35K6b5gseMkO4RR-9um4b-YL=Wt@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF816@xmb-sjc-222.amer.cisco.com>
Date: Fri, 14 Jan 2011 12:43:46 -0800
Message-ID: <AANLkTi=h-+9evvY7z0w1eV2xXNpwTvkDLqNFoGb_EVhA@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: vishwas.ietf@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0EKjKK7010360
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

VM> One way to do it will be to send it Hello Multiplier + 1 times
>> in
>> >> the Hello. If a neighbor misses all the Hellos it will anyway bring
>> >> down its adjacency and it will be noticed, otherwise the information
>> >> will be reliably exchanged.
>> >
>> > This only works (with some caveats) in the case where the complete
>> set of Appointed Forwarder information is contained within a single
>> hello. But in large scale deployments it is likely that each hello will
>> only contain a subset of the appointed forwarder information, in which
>> case the strategy you suggest only guarantees that at least one of the
>> subsets has been seen by the neighbor.
>>
>> VM> I agree, with the information in more then one Hello (which should
>> not be a very common case) we may have to send the information more
>> times. That said in most Layer-2 protocols, just sending an
>> information like 3 times is treated as reliable sending.
>
> So you agree there is an issue that needs to be addressed? I hope so - be=
cause otherwise we have a specification that is not guaranteed to work all =
the time.
VM> I think things can be done better and needs to be looked at, but
it should not block the work of the current draft.

>> VM> I think the idea is that we need to do things for most of the
>> cases. However there might be a very minor percentage(.0001%) of the
>> cases where things may not work. That however does not mean we leave
>> it as best effort.
> OK - so we agree this is an issue which needs to be addressed it seems.
VM> Again same as above.

>> > I do think more clarity would be desirable.
>> > Can you comment on the second point regarding in what "DRB election
>> state" (NOT neighbor state) neighbors are advertised?
>> VM> Neighbors are still advertized after the 2-way state. BTW, IS-Is
>> does not itself deal with corner cases. So unlike OSPF where the
>> entire data base needs to be acknowledged before a neighbor is
>> advertized in the LS information, in IS-Is we advertize it before,
>> which could always lead to the case you mention. On Broadcast links
>> CSNP's are periodically advertized, if I remember it right.
>
> TRILL makes no changes to the Update Process - which has been proven reli=
able - so LSP flooding/CSNP usage is not relevant. My question is regarding=
 in what "DRB election state" a neighbor should be advertised in LSPs. The =
draft specifies that when in "pre-DRB" state there is a pre-forwarding time=
r running and we are inhibited from ingressing/egressing native frames. If =
we were to advertise neighbors in LSPs while in pre-DRB state we would ther=
efore be attracting traffic that we cannot deliver for some significant num=
ber of seconds. I am asking for more explicit definition of when neighbor a=
dvertisements should be added to LSPs. Clearly an adjacency must be in Repo=
rt State for that to happen - but I think the DRB election state is also re=
levant and I don't think that is clearly specified.
VM> Like I mentioned the neighbor advertizement should not change from IS-I=
S.

>> VM> I agree with you. It is left to an implementation to decide how to
>> do it.
>
> OK. I do think some guidance would be good as the use of MTU PDUs is an e=
ntirely new functionality.
VM> A clarification could be added.

> To requote the draft:
>
> " If there are no adjacencies with a non-zero Designated VLAN Hello
> =A0 Holding timer, an empty TRILL Neighbor TLV MUST be included in each
> =A0 Hello. =A0If there are such adjacencies, then the Hello MAY contain a
> =A0 TRILL Neighbor TLV..."
>
> I understand the motivation for an explicit "no neighbors" advertisement =
- but I am asking why you want to make inclusion of TRILL Neighbor TLV opti=
onal when you do have adjacencies?
VM> This can again be treated in the context of the fact that if the
data does not fit in one Hello, we could send the other data in the
other Hello, and include empty TRILL Neighbor TLV. It could also be
treated in the context of the fact that we should allow receiving the
empty TLV.

I know this could be removed by itself, as there is no harm or benefit
of the same, based on how the spec stands, however it could help to
state that for some future use like mentioned above.

Thanks,
Vishwas

>> >>
>> >> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
>> >> <ginsberg@cisco.com> wrote:
>> >> > (resending w corrected TRILL WG address)
>> >> >
>> >> > Attached please find my comments on draft-ietf-trill-adj-01.
>> >> >
>> >> > The file draft-ietf-trill-adj-01_comments.txt contains substantive
>> >> > comments identified by Section # - except in a couple of cases
>> where
>> >> the
>> >> > remarks are more generic.
>> >> >
>> >> > The file draft-ietf-trill-adj-01_editorial.txt is portions of the
>> >> draft
>> >> > annotated with editorial comments. Search for "LES:" in the file.
>> >> >
>> >> > As context, the requirements of [TRILL] introduce the need to send
>> a
>> >> > great deal more circuit scoped information on a LAN as compared to
>> >> Layer
>> >> > 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
>> >> > [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
>> >> > information and to provide robust loop prevention in the
>> forwarding
>> >> of
>> >> > data. But I believe the extensions as currently defined have
>> >> significant
>> >> > scalability issues in the presence of a large number of neighbors
>> on
>> >> a
>> >> > LAN and/or a large number of enabled VLANs. In my comments I have
>> >> > confined myself to pointing out where I believe such issues arise.
>> If
>> >> > there is consensus that these are issues which should be
>> addressed,
>> >> then
>> >> > additional discussions can be started as to how to do so.
>> >> >
>> >> > Finally, I would like to thank the authors of draft-ietf-trill-
>> adj-01
>> >> > for the effort and diligence they obviously applied to the writing
>> of
>> >> > this draft.
>> >> >
>> >> > =A0 Les
>> >> >
>> >> >
>> >> > _______________________________________________
>> >> > rbridge mailing list
>> >> > rbridge@postel.org
>> >> > http://mailman.postel.org/mailman/listinfo/rbridge
>> >> >
>> >> >
>> >
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 14 12:55:38 2011
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 A301E3A6C6B for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 12:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.499
X-Spam-Level: 
X-Spam-Status: No, score=-5.499 tagged_above=-999 required=5 tests=[AWL=-2.900, 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 5JHSSNfmd3iy for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 12:55:37 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 2B1703A6C4E for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 14 Jan 2011 12:55: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 p0EKXDVl008193; Fri, 14 Jan 2011 12:33:14 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0EKWlrT008135 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Fri, 14 Jan 2011 12:32:56 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAAdCME2rR7Ht/2dsb2JhbACkWXOhc5kEhU8EhGuJU4Jw
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-6.cisco.com with ESMTP; 14 Jan 2011 20:32:47 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0EKWlTU011649; Fri, 14 Jan 2011 20:32:47 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Jan 2011 12:32:47 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 14 Jan 2011 12:32:45 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D0DF816@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTim2Zyx_NTHxm35K6b5gseMkO4RR-9um4b-YL=Wt@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Thread-Index: Acu0F1qCFy7bRt6DRcShqJyS/5KUHAADnTcw
References: <4D221B2B.2020207@acm.org><AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com><AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com><AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com> <AANLkTim2Zyx_NTHxm35K6b5gseMkO4RR-9um4b-YL=Wt@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 14 Jan 2011 20:32:47.0252 (UTC) FILETIME=[347E7540:01CBB42A]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0EKWlrT008135
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Vishwas -

> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> Sent: Friday, January 14, 2011 10:17 AM
> To: Les Ginsberg (ginsberg)
> Cc: isis-wg@ietf.org; rbridge@postel.org
> Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
> =

> Hi Les,
> =

> Good we are nearly on the same page regarding most of it.

That is good. :-)

> =

> >> VM> One way to do it will be to send it Hello Multiplier + 1 times
> in
> >> the Hello. If a neighbor misses all the Hellos it will anyway bring
> >> down its adjacency and it will be noticed, otherwise the information
> >> will be reliably exchanged.
> >
> > This only works (with some caveats) in the case where the complete
> set of Appointed Forwarder information is contained within a single
> hello. But in large scale deployments it is likely that each hello will
> only contain a subset of the appointed forwarder information, in which
> case the strategy you suggest only guarantees that at least one of the
> subsets has been seen by the neighbor.
> =

> VM> I agree, with the information in more then one Hello (which should
> not be a very common case) we may have to send the information more
> times. That said in most Layer-2 protocols, just sending an
> information like 3 times is treated as reliable sending.

So you agree there is an issue that needs to be addressed? I hope so - beca=
use otherwise we have a specification that is not guaranteed to work all th=
e time.

> =

> >> Preventing Multiple DRBs on a LAN
> >> ---------------------------------
> >>
> >> It is not clear to me how the use of multiple announcing VLANs
> achieves
> >> the stated goal of one and only one DRB in the presence of
> inconsistent
> >> connectivity / configuration.
> >> VM> Les it is stated that:
> >>
> >> =A0Designated VLAN: the VLAN being used on the link for all TRILL
> frames
> >> except some TRILL Hellos. =A0This is RBn's Desired Designated VLAN if
> >> RBn believes it is the DRB or the Designated VLAN in the DRB's
> Hellos
> >> if RBn is not the DRB.
> >>
> >> This means is that there is atleast one VLAN which is common to all
> >> devices on the link. The example you have given above would be a
> >> configuration issue. The protocol does not deal with configuration
> >> issues.
> > Misconfiguration is not what the example is trying to show. All VLANs
> are enabled on all RBs in the example above, but there is a
> connectivity issue on VLANS 2,3 for RB2. This is obviously a
> pathological case, but as [TRILL] emphasizes the importance of being
> able to handle such cases I am simply demonstrating that the extensions
> are not able to deal with all cases.
> >
> > If we can assume that there are never any connectivity issues and -
> as you say - the protocol "does not deal with configuration issues",
> then sending hellos on one VLAN would be sufficient - but the concern
> throughout all of the TRILL documents is that such an assumption is not
> safe.
> =

> VM> I think the idea is that we need to do things for most of the
> cases. However there might be a very minor percentage(.0001%) of the
> cases where things may not work. That however does not mean we leave
> it as best effort.
> =


OK - so we agree this is an issue which needs to be addressed it seems.

> =

> > I do think more clarity would be desirable.
> > Can you comment on the second point regarding in what "DRB election
> state" (NOT neighbor state) neighbors are advertised?
> VM> Neighbors are still advertized after the 2-way state. BTW, IS-Is
> does not itself deal with corner cases. So unlike OSPF where the
> entire data base needs to be acknowledged before a neighbor is
> advertized in the LS information, in IS-Is we advertize it before,
> which could always lead to the case you mention. On Broadcast links
> CSNP's are periodically advertized, if I remember it right.

TRILL makes no changes to the Update Process - which has been proven reliab=
le - so LSP flooding/CSNP usage is not relevant. My question is regarding i=
n what "DRB election state" a neighbor should be advertised in LSPs. The dr=
aft specifies that when in "pre-DRB" state there is a pre-forwarding timer =
running and we are inhibited from ingressing/egressing native frames. If we=
 were to advertise neighbors in LSPs while in pre-DRB state we would theref=
ore be attracting traffic that we cannot deliver for some significant numbe=
r of seconds. I am asking for more explicit definition of when neighbor adv=
ertisements should be added to LSPs. Clearly an adjacency must be in Report=
 State for that to happen - but I think the DRB election state is also rele=
vant and I don't think that is clearly specified.

> =

> >> VM> By default MTU-Probe and ACK will be unicast. It could be
> >> configured to do it a different way. A reason MTU-probe could be
> >> multicast is when a new device first joins a link, which already has
> >> Rbridges attached.
> >
> > I have not found any statement in any of the relevant TRILL documents
> that states "unicast is the default". Apologies if I missed it.
> >
> > That said, on a LAN it would be more efficient for the DRB to
> multicast the probes, non-DRB to unicast probes to the DRB only, and
> all ACKS be multicast.
> =

> VM> I agree with you. It is left to an implementation to decide how to
> do it.

OK. I do think some guidance would be good as the use of MTU PDUs is an ent=
irely new functionality.

> =

> >> VM> The idea is we should not pad, because packets may not get
> through
> >> due to difference in MTU. However if it is received I think there is
> >> no reason to do anything different for it.
> >
> > In regards to padding, I agree - but would like to see an explicit
> statement.
> =

> VM> Ok.
> =

> > You have not commented on the motivation for omitting a neighbor TLV
> from a hello when adjacencies are present.
> VM> I think the intent is the reverse.  If we have Neighbors and after
> adjacency down we do not have any adjacencies, the aim is to still
> send the Hello to the neighbor stating that there are no other
> neighbors remaining.
> =


To requote the draft:

" If there are no adjacencies with a non-zero Designated VLAN Hello
   Holding timer, an empty TRILL Neighbor TLV MUST be included in each
   Hello.  If there are such adjacencies, then the Hello MAY contain a
   TRILL Neighbor TLV..."

I understand the motivation for an explicit "no neighbors" advertisement - =
but I am asking why you want to make inclusion of TRILL Neighbor TLV option=
al when you do have adjacencies?

   Les

> Thanks,
> Vishwas
> =

> >>
> >> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
> >> <ginsberg@cisco.com> wrote:
> >> > (resending w corrected TRILL WG address)
> >> >
> >> > Attached please find my comments on draft-ietf-trill-adj-01.
> >> >
> >> > The file draft-ietf-trill-adj-01_comments.txt contains substantive
> >> > comments identified by Section # - except in a couple of cases
> where
> >> the
> >> > remarks are more generic.
> >> >
> >> > The file draft-ietf-trill-adj-01_editorial.txt is portions of the
> >> draft
> >> > annotated with editorial comments. Search for "LES:" in the file.
> >> >
> >> > As context, the requirements of [TRILL] introduce the need to send
> a
> >> > great deal more circuit scoped information on a LAN as compared to
> >> Layer
> >> > 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
> >> > [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
> >> > information and to provide robust loop prevention in the
> forwarding
> >> of
> >> > data. But I believe the extensions as currently defined have
> >> significant
> >> > scalability issues in the presence of a large number of neighbors
> on
> >> a
> >> > LAN and/or a large number of enabled VLANs. In my comments I have
> >> > confined myself to pointing out where I believe such issues arise.
> If
> >> > there is consensus that these are issues which should be
> addressed,
> >> then
> >> > additional discussions can be started as to how to do so.
> >> >
> >> > Finally, I would like to thank the authors of draft-ietf-trill-
> adj-01
> >> > for the effort and diligence they obviously applied to the writing
> of
> >> > this draft.
> >> >
> >> > =A0 Les
> >> >
> >> >
> >> > _______________________________________________
> >> > rbridge mailing list
> >> > rbridge@postel.org
> >> > http://mailman.postel.org/mailman/listinfo/rbridge
> >> >
> >> >
> >

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 14 14:06:46 2011
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 61A6F3A6BD0 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 14:06:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.427
X-Spam-Level: 
X-Spam-Status: No, score=-5.427 tagged_above=-999 required=5 tests=[AWL=-2.828, 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 oUukPfKUfY2M for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 14:06:44 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id B4DD23A6853 for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 14 Jan 2011 14:06:44 -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 p0ELq7dL022211; Fri, 14 Jan 2011 13:52:08 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0ELpigO022152 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Fri, 14 Jan 2011 13:51:53 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEANFUME2rRN+J/2dsb2JhbACkWXOiBZh5hU8EhGuJU4Jw
Received: from sj-core-3.cisco.com ([171.68.223.137]) by sj-iport-6.cisco.com with ESMTP; 14 Jan 2011 21:51:33 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-3.cisco.com (8.13.8/8.14.3) with ESMTP id p0ELpXjc012993; Fri, 14 Jan 2011 21:51:33 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Jan 2011 13:51:33 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 14 Jan 2011 13:51:32 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D0DF884@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTi=h-+9evvY7z0w1eV2xXNpwTvkDLqNFoGb_EVhA@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Thread-Index: Acu0K/aBDtWrYZz0Q5m/1LS5I0mqAQAAZjGA
References: <4D221B2B.2020207@acm.org><AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com><AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com><AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com><AANLkTim2Zyx_NTHxm35K6b5gseMkO4RR-9um4b-YL=Wt@mail.gmail.com><AE36820147909644AD2A7CA014B1FB520D0DF816@xmb-sjc-222.amer.cisco.com> <AANLkTi=h-+9evvY7z0w1eV2xXNpwTvkDLqNFoGb_EVhA@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 14 Jan 2011 21:51:33.0868 (UTC) FILETIME=[35C6D2C0:01CBB435]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0ELpigO022152
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Vishwas -

> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> Sent: Friday, January 14, 2011 12:44 PM
> To: Les Ginsberg (ginsberg)
> Cc: isis-wg@ietf.org; rbridge@postel.org
> Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
> =

> Hi Les,
> =

> VM> One way to do it will be to send it Hello Multiplier + 1 times
> >> in
> >> >> the Hello. If a neighbor misses all the Hellos it will anyway
> bring
> >> >> down its adjacency and it will be noticed, otherwise the
> information
> >> >> will be reliably exchanged.
> >> >
> >> > This only works (with some caveats) in the case where the complete
> >> set of Appointed Forwarder information is contained within a single
> >> hello. But in large scale deployments it is likely that each hello
> will
> >> only contain a subset of the appointed forwarder information, in
> which
> >> case the strategy you suggest only guarantees that at least one of
> the
> >> subsets has been seen by the neighbor.
> >>
> >> VM> I agree, with the information in more then one Hello (which
> should
> >> not be a very common case) we may have to send the information more
> >> times. That said in most Layer-2 protocols, just sending an
> >> information like 3 times is treated as reliable sending.
> >
> > So you agree there is an issue that needs to be addressed? I hope so
> - because otherwise we have a specification that is not guaranteed to
> work all the time.
> VM> I think things can be done better and needs to be looked at, but
> it should not block the work of the current draft.

This seems very basic to correct operation i.e having introduced the suppor=
t for sending subsets of the information in a given hello it seems that it =
is necessary to solve the problem of how to guarantee delivery of the full =
set of information. =


The only way to provide reliability under the current specification is to s=
end the information all the time. This guarantees that the information will=
 be received "eventually" - but also means convergence time is lengthy and =
indeterminate - and it places a burden on both sender and receiver to conti=
nually process information which changes rarely. And this burden becomes wo=
rse as the number of VLANs/neighbors increases. =


Potential solutions will likely not be backwards compatible. So to suggest =
that we defer this issue means that at some later date (perhaps) a new vers=
ion of the specification will come out which addresses the issues but it wi=
ll not interoperate with existing versions. And since the issues here are r=
elated to scale - and currently there is no defined solution - I would expe=
ct that folks who intend to deploy TRILL would be quite correctly very conc=
erned about this.

> =

> >> VM> I think the idea is that we need to do things for most of the
> >> cases. However there might be a very minor percentage(.0001%) of the
> >> cases where things may not work. That however does not mean we leave
> >> it as best effort.
> > OK - so we agree this is an issue which needs to be addressed it
> seems.
> VM> Again same as above.

And my response is again the same as above. :-)
You have snipped out the context for this, so let me remind that this issue=
 concerns correct operation in the event of pathological connectivity issue=
s. The more relevant point is one that I made earlier:

<snip>
If we can assume that there are never any connectivity issues and - as you =
say - the protocol "does not deal with configuration issues", then sending =
hellos on one VLAN would be sufficient - but the concern throughout all of =
the TRILL documents is that such an assumption is not safe.
<end snip>

The justification for the extensions that have been defined becomes very we=
ak if they do not actually reliably solve the problem they were designed to=
 address. =


> =

> >> > I do think more clarity would be desirable.
> >> > Can you comment on the second point regarding in what "DRB
> election
> >> state" (NOT neighbor state) neighbors are advertised?
> >> VM> Neighbors are still advertized after the 2-way state. BTW, IS-Is
> >> does not itself deal with corner cases. So unlike OSPF where the
> >> entire data base needs to be acknowledged before a neighbor is
> >> advertized in the LS information, in IS-Is we advertize it before,
> >> which could always lead to the case you mention. On Broadcast links
> >> CSNP's are periodically advertized, if I remember it right.
> >
> > TRILL makes no changes to the Update Process - which has been proven
> reliable - so LSP flooding/CSNP usage is not relevant. My question is
> regarding in what "DRB election state" a neighbor should be advertised
> in LSPs. The draft specifies that when in "pre-DRB" state there is a
> pre-forwarding timer running and we are inhibited from
> ingressing/egressing native frames. If we were to advertise neighbors
> in LSPs while in pre-DRB state we would therefore be attracting traffic
> that we cannot deliver for some significant number of seconds. I am
> asking for more explicit definition of when neighbor advertisements
> should be added to LSPs. Clearly an adjacency must be in Report State
> for that to happen - but I think the DRB election state is also
> relevant and I don't think that is clearly specified.
> VM> Like I mentioned the neighbor advertizement should not change from
> IS-IS.

This does not answer my question. :-(

   Les

> =

> >> VM> I agree with you. It is left to an implementation to decide how
> to
> >> do it.
> >
> > OK. I do think some guidance would be good as the use of MTU PDUs is
> an entirely new functionality.
> VM> A clarification could be added.
> =

> > To requote the draft:
> >
> > " If there are no adjacencies with a non-zero Designated VLAN Hello
> > =A0 Holding timer, an empty TRILL Neighbor TLV MUST be included in each
> > =A0 Hello. =A0If there are such adjacencies, then the Hello MAY contain=
 a
> > =A0 TRILL Neighbor TLV..."
> >
> > I understand the motivation for an explicit "no neighbors"
> advertisement - but I am asking why you want to make inclusion of TRILL
> Neighbor TLV optional when you do have adjacencies?
> VM> This can again be treated in the context of the fact that if the
> data does not fit in one Hello, we could send the other data in the
> other Hello, and include empty TRILL Neighbor TLV. It could also be
> treated in the context of the fact that we should allow receiving the
> empty TLV.
> =

> I know this could be removed by itself, as there is no harm or benefit
> of the same, based on how the spec stands, however it could help to
> state that for some future use like mentioned above.
> =

> Thanks,
> Vishwas
> =

> >> >>
> >> >> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
> >> >> <ginsberg@cisco.com> wrote:
> >> >> > (resending w corrected TRILL WG address)
> >> >> >
> >> >> > Attached please find my comments on draft-ietf-trill-adj-01.
> >> >> >
> >> >> > The file draft-ietf-trill-adj-01_comments.txt contains
> substantive
> >> >> > comments identified by Section # - except in a couple of cases
> >> where
> >> >> the
> >> >> > remarks are more generic.
> >> >> >
> >> >> > The file draft-ietf-trill-adj-01_editorial.txt is portions of
> the
> >> >> draft
> >> >> > annotated with editorial comments. Search for "LES:" in the
> file.
> >> >> >
> >> >> > As context, the requirements of [TRILL] introduce the need to
> send
> >> a
> >> >> > great deal more circuit scoped information on a LAN as compared
> to
> >> >> Layer
> >> >> > 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
> >> >> > [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
> >> >> > information and to provide robust loop prevention in the
> >> forwarding
> >> >> of
> >> >> > data. But I believe the extensions as currently defined have
> >> >> significant
> >> >> > scalability issues in the presence of a large number of
> neighbors
> >> on
> >> >> a
> >> >> > LAN and/or a large number of enabled VLANs. In my comments I
> have
> >> >> > confined myself to pointing out where I believe such issues
> arise.
> >> If
> >> >> > there is consensus that these are issues which should be
> >> addressed,
> >> >> then
> >> >> > additional discussions can be started as to how to do so.
> >> >> >
> >> >> > Finally, I would like to thank the authors of draft-ietf-trill-
> >> adj-01
> >> >> > for the effort and diligence they obviously applied to the
> writing
> >> of
> >> >> > this draft.
> >> >> >
> >> >> > =A0 Les
> >> >> >
> >> >> >
> >> >> > _______________________________________________
> >> >> > rbridge mailing list
> >> >> > rbridge@postel.org
> >> >> > http://mailman.postel.org/mailman/listinfo/rbridge
> >> >> >
> >> >> >
> >> >
> >

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 14 14:30:04 2011
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 6EAFB3A6813 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 14:30:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.955
X-Spam-Level: 
X-Spam-Status: No, score=-2.955 tagged_above=-999 required=5 tests=[AWL=-0.356, 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 1QLUAwM-EHFQ for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 14:30:02 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 50BCE3A67D9 for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 14 Jan 2011 14:30:02 -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 p0EMRgUG028098; Fri, 14 Jan 2011 14:27:43 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0EMRDV1028049 for <rbridge@postel.org>; Fri, 14 Jan 2011 14:27:22 -0800 (PST)
Received: by wwd20 with SMTP id 20so3618158wwd.21 for <rbridge@postel.org>; Fri, 14 Jan 2011 14:27:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UQ7IhzEHkplgYMF+8dvng+WRiD3WvkihltRDHCQlAfY=; b=ORrbtnHsn3AEqgEPRuuSqbP/ViO3SHskgRJ2lleNjnfBfmnbhCBwgjd+3XsMFRYbJ4 LgoAmeJ53MHMoyz0TKANWGZmMlIXsURLK1JtWyHjvIgA1eowoZ4Ve4cwYu3cUaCCtnDg hZXqnM6D4X4kRMzHzpKUKE5o9+gtCHF6FzEN8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=OY3fiyHC7Ijd6Oenbz2gxKkbUGRWiZCZ5tWs7NySxQ1B91K95h9+zNeBOJVpaZ8Jqh X/6ojMMghl65QPLKIoybCA+GVwpf6cceVq1K5PJUyoaFXjYccU1U1G5BrECVguyJlcns BB8dSgcoYA8PeDXnmDTwhlzMcsXA0I5sMB/v0=
MIME-Version: 1.0
Received: by 10.216.27.202 with SMTP id e52mr998884wea.75.1295043954183; Fri, 14 Jan 2011 14:25:54 -0800 (PST)
Received: by 10.216.139.219 with HTTP; Fri, 14 Jan 2011 14:25:24 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D0DF884@xmb-sjc-222.amer.cisco.com>
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com> <AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com> <AANLkTim2Zyx_NTHxm35K6b5gseMkO4RR-9um4b-YL=Wt@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF816@xmb-sjc-222.amer.cisco.com> <AANLkTi=h-+9evvY7z0w1eV2xXNpwTvkDLqNFoGb_EVhA@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF884@xmb-sjc-222.amer.cisco.com>
Date: Fri, 14 Jan 2011 14:25:24 -0800
Message-ID: <AANLkTi=c9ZLQa53CzV1yZnW0J2ncfFdgbeZZ2mzFduRh@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: vishwas.ietf@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0EMRDV1028049
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

You have good comments.

Like I said we could send the same information multiple times to
assume the information has reached its neighbor. If the information is
in one Hello we already have the solution.

I agree this can be improved, however I feel we do not need to do
every optimization at this point.

Thanks,
Vishwas

>>
>> >> VM> I agree with you. It is left to an implementation to decide how
>> to
>> >> do it.
>> >
>> > OK. I do think some guidance would be good as the use of MTU PDUs is
>> an entirely new functionality.
>> VM> A clarification could be added.
>>
>> > To requote the draft:
>> >
>> > " If there are no adjacencies with a non-zero Designated VLAN Hello
>> > =A0 Holding timer, an empty TRILL Neighbor TLV MUST be included in each
>> > =A0 Hello. =A0If there are such adjacencies, then the Hello MAY contai=
n a
>> > =A0 TRILL Neighbor TLV..."
>> >
>> > I understand the motivation for an explicit "no neighbors"
>> advertisement - but I am asking why you want to make inclusion of TRILL
>> Neighbor TLV optional when you do have adjacencies?
>> VM> This can again be treated in the context of the fact that if the
>> data does not fit in one Hello, we could send the other data in the
>> other Hello, and include empty TRILL Neighbor TLV. It could also be
>> treated in the context of the fact that we should allow receiving the
>> empty TLV.
>>
>> I know this could be removed by itself, as there is no harm or benefit
>> of the same, based on how the spec stands, however it could help to
>> state that for some future use like mentioned above.
>>
>> Thanks,
>> Vishwas
>>
>> >> >>
>> >> >> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
>> >> >> <ginsberg@cisco.com> wrote:
>> >> >> > (resending w corrected TRILL WG address)
>> >> >> >
>> >> >> > Attached please find my comments on draft-ietf-trill-adj-01.
>> >> >> >
>> >> >> > The file draft-ietf-trill-adj-01_comments.txt contains
>> substantive
>> >> >> > comments identified by Section # - except in a couple of cases
>> >> where
>> >> >> the
>> >> >> > remarks are more generic.
>> >> >> >
>> >> >> > The file draft-ietf-trill-adj-01_editorial.txt is portions of
>> the
>> >> >> draft
>> >> >> > annotated with editorial comments. Search for "LES:" in the
>> file.
>> >> >> >
>> >> >> > As context, the requirements of [TRILL] introduce the need to
>> send
>> >> a
>> >> >> > great deal more circuit scoped information on a LAN as compared
>> to
>> >> >> Layer
>> >> >> > 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
>> >> >> > [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
>> >> >> > information and to provide robust loop prevention in the
>> >> forwarding
>> >> >> of
>> >> >> > data. But I believe the extensions as currently defined have
>> >> >> significant
>> >> >> > scalability issues in the presence of a large number of
>> neighbors
>> >> on
>> >> >> a
>> >> >> > LAN and/or a large number of enabled VLANs. In my comments I
>> have
>> >> >> > confined myself to pointing out where I believe such issues
>> arise.
>> >> If
>> >> >> > there is consensus that these are issues which should be
>> >> addressed,
>> >> >> then
>> >> >> > additional discussions can be started as to how to do so.
>> >> >> >
>> >> >> > Finally, I would like to thank the authors of draft-ietf-trill-
>> >> adj-01
>> >> >> > for the effort and diligence they obviously applied to the
>> writing
>> >> of
>> >> >> > this draft.
>> >> >> >
>> >> >> > =A0 Les
>> >> >> >
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > rbridge mailing list
>> >> >> > rbridge@postel.org
>> >> >> > http://mailman.postel.org/mailman/listinfo/rbridge
>> >> >> >
>> >> >> >
>> >> >
>> >
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 14 14:44:54 2011
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 DEA533A6C0B for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 14:44:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.944
X-Spam-Level: 
X-Spam-Status: No, score=-2.944 tagged_above=-999 required=5 tests=[AWL=-0.345, 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 nNOBhMsTolsL for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 14:44:53 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id A99EA3A6BF0 for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 14 Jan 2011 14:44:53 -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 p0EMRrIv028101; Fri, 14 Jan 2011 14:27:54 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0EMRDV2028049 for <rbridge@postel.org>; Fri, 14 Jan 2011 14:27:25 -0800 (PST)
Received: by mail-ww0-f52.google.com with SMTP id 20so3618158wwd.21 for <rbridge@postel.org>; Fri, 14 Jan 2011 14:27:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=UQ7IhzEHkplgYMF+8dvng+WRiD3WvkihltRDHCQlAfY=; b=ORrbtnHsn3AEqgEPRuuSqbP/ViO3SHskgRJ2lleNjnfBfmnbhCBwgjd+3XsMFRYbJ4 LgoAmeJ53MHMoyz0TKANWGZmMlIXsURLK1JtWyHjvIgA1eowoZ4Ve4cwYu3cUaCCtnDg hZXqnM6D4X4kRMzHzpKUKE5o9+gtCHF6FzEN8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=OY3fiyHC7Ijd6Oenbz2gxKkbUGRWiZCZ5tWs7NySxQ1B91K95h9+zNeBOJVpaZ8Jqh X/6ojMMghl65QPLKIoybCA+GVwpf6cceVq1K5PJUyoaFXjYccU1U1G5BrECVguyJlcns BB8dSgcoYA8PeDXnmDTwhlzMcsXA0I5sMB/v0=
MIME-Version: 1.0
Received: by 10.216.172.212 with SMTP id t62mr996154wel.60.1295044029590; Fri, 14 Jan 2011 14:27:09 -0800 (PST)
Received: by 10.216.139.219 with HTTP; Fri, 14 Jan 2011 14:25:24 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D0DF884@xmb-sjc-222.amer.cisco.com>
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com> <AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com> <AANLkTim2Zyx_NTHxm35K6b5gseMkO4RR-9um4b-YL=Wt@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF816@xmb-sjc-222.amer.cisco.com> <AANLkTi=h-+9evvY7z0w1eV2xXNpwTvkDLqNFoGb_EVhA@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DF884@xmb-sjc-222.amer.cisco.com>
Date: Fri, 14 Jan 2011 14:25:24 -0800
Message-ID: <AANLkTi=c9ZLQa53CzV1yZnW0J2ncfFdgbeZZ2mzFduRh@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: vishwas.ietf@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0EMRDV2028049
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

You have good comments.

Like I said we could send the same information multiple times to
assume the information has reached its neighbor. If the information is
in one Hello we already have the solution.

I agree this can be improved, however I feel we do not need to do
every optimization at this point.

Thanks,
Vishwas

>>
>> >> VM> I agree with you. It is left to an implementation to decide how
>> to
>> >> do it.
>> >
>> > OK. I do think some guidance would be good as the use of MTU PDUs is
>> an entirely new functionality.
>> VM> A clarification could be added.
>>
>> > To requote the draft:
>> >
>> > " If there are no adjacencies with a non-zero Designated VLAN Hello
>> > =A0 Holding timer, an empty TRILL Neighbor TLV MUST be included in each
>> > =A0 Hello. =A0If there are such adjacencies, then the Hello MAY contai=
n a
>> > =A0 TRILL Neighbor TLV..."
>> >
>> > I understand the motivation for an explicit "no neighbors"
>> advertisement - but I am asking why you want to make inclusion of TRILL
>> Neighbor TLV optional when you do have adjacencies?
>> VM> This can again be treated in the context of the fact that if the
>> data does not fit in one Hello, we could send the other data in the
>> other Hello, and include empty TRILL Neighbor TLV. It could also be
>> treated in the context of the fact that we should allow receiving the
>> empty TLV.
>>
>> I know this could be removed by itself, as there is no harm or benefit
>> of the same, based on how the spec stands, however it could help to
>> state that for some future use like mentioned above.
>>
>> Thanks,
>> Vishwas
>>
>> >> >>
>> >> >> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
>> >> >> <ginsberg@cisco.com> wrote:
>> >> >> > (resending w corrected TRILL WG address)
>> >> >> >
>> >> >> > Attached please find my comments on draft-ietf-trill-adj-01.
>> >> >> >
>> >> >> > The file draft-ietf-trill-adj-01_comments.txt contains
>> substantive
>> >> >> > comments identified by Section # - except in a couple of cases
>> >> where
>> >> >> the
>> >> >> > remarks are more generic.
>> >> >> >
>> >> >> > The file draft-ietf-trill-adj-01_editorial.txt is portions of
>> the
>> >> >> draft
>> >> >> > annotated with editorial comments. Search for "LES:" in the
>> file.
>> >> >> >
>> >> >> > As context, the requirements of [TRILL] introduce the need to
>> send
>> >> a
>> >> >> > great deal more circuit scoped information on a LAN as compared
>> to
>> >> >> Layer
>> >> >> > 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
>> >> >> > [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
>> >> >> > information and to provide robust loop prevention in the
>> >> forwarding
>> >> >> of
>> >> >> > data. But I believe the extensions as currently defined have
>> >> >> significant
>> >> >> > scalability issues in the presence of a large number of
>> neighbors
>> >> on
>> >> >> a
>> >> >> > LAN and/or a large number of enabled VLANs. In my comments I
>> have
>> >> >> > confined myself to pointing out where I believe such issues
>> arise.
>> >> If
>> >> >> > there is consensus that these are issues which should be
>> >> addressed,
>> >> >> then
>> >> >> > additional discussions can be started as to how to do so.
>> >> >> >
>> >> >> > Finally, I would like to thank the authors of draft-ietf-trill-
>> >> adj-01
>> >> >> > for the effort and diligence they obviously applied to the
>> writing
>> >> of
>> >> >> > this draft.
>> >> >> >
>> >> >> > =A0 Les
>> >> >> >
>> >> >> >
>> >> >> > _______________________________________________
>> >> >> > rbridge mailing list
>> >> >> > rbridge@postel.org
>> >> >> > http://mailman.postel.org/mailman/listinfo/rbridge
>> >> >> >
>> >> >> >
>> >> >
>> >
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 14 15:00:00 2011
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 A44E63A6BE6 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 15:00:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.366
X-Spam-Level: 
X-Spam-Status: No, score=-5.366 tagged_above=-999 required=5 tests=[AWL=-2.767, 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 eVg45te3Rccg for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 14 Jan 2011 14:59:59 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 346893A6BCC for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 14 Jan 2011 14:59:59 -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 p0EMXHo0028931; Fri, 14 Jan 2011 14:33:18 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0EMWbre028858 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Fri, 14 Jan 2011 14:32:46 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHNdME2rR7Hu/2dsb2JhbACkWXOiAZh6hU8EhGuJU4Jw
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-4.cisco.com with ESMTP; 14 Jan 2011 22:32:37 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0EMWbwb009021; Fri, 14 Jan 2011 22:32:37 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Fri, 14 Jan 2011 14:32:37 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 14 Jan 2011 14:32:35 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D0DF8B6@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTi=c9ZLQa53CzV1yZnW0J2ncfFdgbeZZ2mzFduRh@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Thread-Index: Acu0OjXW8nMWCl0GRsivW/DpK5sR0QAAFB9Q
References: <4D221B2B.2020207@acm.org><AE36820147909644AD2A7CA014B1FB520D0DF50D@xmb-sjc-222.amer.cisco.com><AANLkTikKAD86kLWo7w9ExcsNWAtu9y4Zv0cmCg=qz+uM@mail.gmail.com><AE36820147909644AD2A7CA014B1FB520D0DF658@xmb-sjc-222.amer.cisco.com><AANLkTim2Zyx_NTHxm35K6b5gseMkO4RR-9um4b-YL=Wt@mail.gmail.com><AE36820147909644AD2A7CA014B1FB520D0DF816@xmb-sjc-222.amer.cisco.com><AANLkTi=h-+9evvY7z0w1eV2xXNpwTvkDLqNFoGb_EVhA@mail.gmail.com><AE36820147909644AD2A7CA014B1FB520D0DF884@xmb-sjc-222.amer.cisco.com> <AANLkTi=c9ZLQa53CzV1yZnW0J2ncfFdgbeZZ2mzFduRh@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Vishwas Manral" <vishwas.ietf@gmail.com>
X-OriginalArrivalTime: 14 Jan 2011 22:32:37.0124 (UTC) FILETIME=[F1FDDC40:01CBB43A]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0EMWbre028858
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Vishwas -

This isn't an optimization in my view. While things work "most of the time"=
 - when they don't work you run the risk of loops, blackholes, or indetermi=
nate convergence times - as well as very poor scaling behavior - which make=
s the likelihood of failure greater.

If you think these are all issues which "can be addressed later" then we wi=
ll simply have to agree to disagree.

   Les

> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> Sent: Friday, January 14, 2011 2:25 PM
> To: Les Ginsberg (ginsberg)
> Cc: isis-wg@ietf.org; rbridge@postel.org
> Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
> =

> Hi Les,
> =

> You have good comments.
> =

> Like I said we could send the same information multiple times to
> assume the information has reached its neighbor. If the information is
> in one Hello we already have the solution.
> =

> I agree this can be improved, however I feel we do not need to do
> every optimization at this point.
> =

> Thanks,
> Vishwas
> =

> >>
> >> >> VM> I agree with you. It is left to an implementation to decide
> how
> >> to
> >> >> do it.
> >> >
> >> > OK. I do think some guidance would be good as the use of MTU PDUs
> is
> >> an entirely new functionality.
> >> VM> A clarification could be added.
> >>
> >> > To requote the draft:
> >> >
> >> > " If there are no adjacencies with a non-zero Designated VLAN
> Hello
> >> > =A0 Holding timer, an empty TRILL Neighbor TLV MUST be included in
> each
> >> > =A0 Hello. =A0If there are such adjacencies, then the Hello MAY
> contain a
> >> > =A0 TRILL Neighbor TLV..."
> >> >
> >> > I understand the motivation for an explicit "no neighbors"
> >> advertisement - but I am asking why you want to make inclusion of
> TRILL
> >> Neighbor TLV optional when you do have adjacencies?
> >> VM> This can again be treated in the context of the fact that if the
> >> data does not fit in one Hello, we could send the other data in the
> >> other Hello, and include empty TRILL Neighbor TLV. It could also be
> >> treated in the context of the fact that we should allow receiving
> the
> >> empty TLV.
> >>
> >> I know this could be removed by itself, as there is no harm or
> benefit
> >> of the same, based on how the spec stands, however it could help to
> >> state that for some future use like mentioned above.
> >>
> >> Thanks,
> >> Vishwas
> >>
> >> >> >>
> >> >> >> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
> >> >> >> <ginsberg@cisco.com> wrote:
> >> >> >> > (resending w corrected TRILL WG address)
> >> >> >> >
> >> >> >> > Attached please find my comments on draft-ietf-trill-adj-01.
> >> >> >> >
> >> >> >> > The file draft-ietf-trill-adj-01_comments.txt contains
> >> substantive
> >> >> >> > comments identified by Section # - except in a couple of
> cases
> >> >> where
> >> >> >> the
> >> >> >> > remarks are more generic.
> >> >> >> >
> >> >> >> > The file draft-ietf-trill-adj-01_editorial.txt is portions
> of
> >> the
> >> >> >> draft
> >> >> >> > annotated with editorial comments. Search for "LES:" in the
> >> file.
> >> >> >> >
> >> >> >> > As context, the requirements of [TRILL] introduce the need
> to
> >> send
> >> >> a
> >> >> >> > great deal more circuit scoped information on a LAN as
> compared
> >> to
> >> >> >> Layer
> >> >> >> > 3 IS-IS. Extensions to the IS-IS protocol defined in
> [TRILL],
> >> >> >> > [TRILL-ISIS], and [TRILL-ADJ] are designed to support this
> new
> >> >> >> > information and to provide robust loop prevention in the
> >> >> forwarding
> >> >> >> of
> >> >> >> > data. But I believe the extensions as currently defined have
> >> >> >> significant
> >> >> >> > scalability issues in the presence of a large number of
> >> neighbors
> >> >> on
> >> >> >> a
> >> >> >> > LAN and/or a large number of enabled VLANs. In my comments I
> >> have
> >> >> >> > confined myself to pointing out where I believe such issues
> >> arise.
> >> >> If
> >> >> >> > there is consensus that these are issues which should be
> >> >> addressed,
> >> >> >> then
> >> >> >> > additional discussions can be started as to how to do so.
> >> >> >> >
> >> >> >> > Finally, I would like to thank the authors of draft-ietf-
> trill-
> >> >> adj-01
> >> >> >> > for the effort and diligence they obviously applied to the
> >> writing
> >> >> of
> >> >> >> > this draft.
> >> >> >> >
> >> >> >> > =A0 Les
> >> >> >> >
> >> >> >> >
> >> >> >> > _______________________________________________
> >> >> >> > rbridge mailing list
> >> >> >> > rbridge@postel.org
> >> >> >> > http://mailman.postel.org/mailman/listinfo/rbridge
> >> >> >> >
> >> >> >> >
> >> >> >
> >> >
> >

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Sat Jan 15 13:47:10 2011
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 53A8F3A6D6E for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sat, 15 Jan 2011 13:47:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.909
X-Spam-Level: 
X-Spam-Status: No, score=-102.909 tagged_above=-999 required=5 tests=[AWL=-0.310, 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 Z7tpIs3W8Z8J for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sat, 15 Jan 2011 13:47:09 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 24EBE3A6D63 for <trill-archive-Osh9cae4@lists.ietf.org>; Sat, 15 Jan 2011 13:47:08 -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 p0FLWnpc012851; Sat, 15 Jan 2011 13:32:50 -0800 (PST)
Received: from mail-wy0-f180.google.com (mail-wy0-f180.google.com [74.125.82.180]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0FLW3Hu012759 for <rbridge@postel.org>; Sat, 15 Jan 2011 13:32:13 -0800 (PST)
Received: by wyb28 with SMTP id 28so3845917wyb.39 for <rbridge@postel.org>; Sat, 15 Jan 2011 13:31:49 -0800 (PST)
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=/LwfzUvF+e+qc5D3YFb00vgyUisMcecmb7cTRFMvANk=; b=ImAKhf1e1HHd8idT13okbYpV3Pib48rNBniZskQfeFMZma595cEGTCux/UwF+yR46d raLnU2qZ1ORm/3fthxs2LieEnCpOPq916//Ybj71udcARcNq5EEDatGFd65dEUIwPffY 2dIzfnSkjKPxMlrCfGewsCJ9qbPmuqa9Up74g=
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=GvCpltRcYyX6uCpsoEfrLM2KDp8h9pYw4vqaWI/vSABg0qkFDXVO9XIgMjI3KCKQYA U1v1jKNuNUbJnBNOjwCtqkO5GOzZ+SbcglCzFNY8BE2TYzYRUgoFufP3ef4yBGPzXXxm /ITFHJ567pyjXkGE9QolQm6H6rN+qcl7lEOPY=
Received: by 10.227.201.5 with SMTP id ey5mr2241062wbb.182.1295126979249; Sat, 15 Jan 2011 13:29:39 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Sat, 15 Jan 2011 13:29:19 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D0DF509@xmb-sjc-222.amer.cisco.com>
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF509@xmb-sjc-222.amer.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 15 Jan 2011 16:29:19 -0500
Message-ID: <AANLkTimETdWyO-_9=rzJtmv9M_MzrQb+7zZ=6V+e9OGh@mail.gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0FLW3Hu012759
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] [Isis-wg] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

On Thu, Jan 13, 2011 at 8:32 PM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
> Attached please find my comments on draft-ietf-trill-adj-01.
>
> The file draft-ietf-trill-adj-01_comments.txt contains substantive
> comments identified by Section # - except in a couple of cases where the
> remarks are more generic.
>
> The file draft-ietf-trill-adj-01_editorial.txt is portions of the draft
> annotated with editorial comments. Search for "LES:" in the file.
>
> ...
>
> Finally, I would like to thank the authors of draft-ietf-trill-adj-01
> for the effort and diligence they obviously applied to the writing of
> this draft.

Thanks. Sounds like the adj draft has achieved its purpose "to improve
the quality of the
description of the TRILL LAN Hello protocol". Below is a response to
your editorial comments. My comments are at <DEE3>. I will reply to
your technical comments separately.

> =A0 Les

2. The TRILL Hello Environment and Purposes

   [IS-IS] has subnet independent functions and subnet dependent

LES: I believe all occurences of "subnet" should really be "subnetwork".

<DEE3> OK.

   functions. Currently Layer 3 use of IS-IS supports two types of
   subnets: point-to-point link subnets between routers and general
   broadcast (LAN) subnets. Because of the differences between the
   environment of Layer 3 routers and the environment of TRILL RBridges,
   the TRILL protocol uses a different type of LAN subnet from the
   broadcast (LAN) subnet type encountered at Layer 3. The environmental
   differences are described below followed by a summation, in Section
   2.5, of the purposes of the TRILL LAN Hello protocol.

LES: Suggested rewrite
  "the TRILL protocol uses a different type of LAN subnet from the
   broadcast (LAN) subnet type encountered at Layer 3" to be

to become

  "The TRILL protocol uses different subnetwork dependent functions
  from those specified in [IS-IS] Section 8.4."

<DEE3> It seems to me that the current wording int he draft is more
specific. I don't see that advantage of changing to more vague
wording... How about "instead of the broadcast (LAN) subnetwork
functions encountered at Layer 3, which are specified in [IS-IS]
Section 8.4, the TRILL protocol uses different functions for a LAN
subnetwork."

...

2.5 Purposes of the TRILL Hello Protocol

...

   In Layer 3 IS-IS all three of these functions are combined. Hellos
   are padded to the maximum length so that a router neighbor is not
   even discovered if it is impossible to communicate with it using
   maximum sized packets. Also, even if Hellos from a neighbor R2 are
   received by R1, if connectivity to R2 is not 2-way (i.e., R2 does not


LES: Padding in [IS-IS] is optional. See RFC 3719 Section 6 for a discussio=
n.

<DEE3> OK, I'll replace "area padded" with "are usually padded".

...

4.2 DRB Election Events

   Determination of events 3 and 4 occurs by comparing priorities (with
   neighbor MAC address (SNPA) as a tie breaker and Port ID as a
   secondary tie breaker) across all entries in the port's adjacency
   table including those in the Detect and 2-Way states as well as those
   in the Report state.

LES: The highest Port ID is preferred??? Need an explicit statement.

<DEE3> Yes, highest, considered as an unsigned integer. I can add that.

...

5. MTU Matching

...

   An RBridge, RB1, determines the desired campus link MTU by
   calculating the minimum of its originatingL1LSPBufferSize and the
   originatingLSPBufferSize advertised in the link state database by

LES: These should all be "originatingL1LSPBufferSize".
(you have omitted "L1" in some cases)

<DEE3> I believe the variable in the LSP is just
originatingLSPBufferSize and is L1 or L2 depending on whether the LSP
is L1 or L2.

6. Pseudonodes

   The Designated RBridge (DRB), determined as described above, controls
   whether a pseudonode will be used on a link.

   It is anticipated that many links between RBridges will actually be
   point-to-point, in which case using a pseudonode merely adds to the
   complexity. If the DRB sets the bypass pseudonode bit in its TRILL
   LAN Hellos, the RBridges on the link just directly report their
   adjacencies that are in the Report state. If the DRB does not set the
   bypass pseudonode bit in its TRILL Hellos, then it specifies a
   pseudonode for the link and sends LSPs on behalf of the pseudonode as
   usual. Setting the bypass pseudonode bit has no effect on how LSPs
   are flooded on a link. It only affects what LSPs are generated.

LES: The phrase "specifies a pseudo-node for the link" suggests that
the LANID sent by the DRB may be different depending on whether the
bypass pseudo-node bit is set or not. Do you really mean that?

<DEE3> No, it is not meant to imply that. How about, "..., then the LAN
ID in the DRB's Hellos specifies the pseudonode for the link and the
DRB sends ..."

he DRB does not set the
   bypass pseudonode bit in its TRILL Hellos, then it specifies a
   pseudonode for the link and sends LSPs on behalf of the pseudonode as
   usual. Setting the bypass pseudonode bit has no effect on how LSPs
   are flooded on a link. It only affects what LSPs are generated.

LES

<DEE3> Thanks, Donald

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Sat Jan 15 14:53:42 2011
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 0CA383A6BA8 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sat, 15 Jan 2011 14:53:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.313
X-Spam-Level: 
X-Spam-Status: No, score=-5.313 tagged_above=-999 required=5 tests=[AWL=-2.714, 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 cRe5NqBgeU-Q for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sat, 15 Jan 2011 14:53:40 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 3F0563A6BA7 for <trill-archive-Osh9cae4@lists.ietf.org>; Sat, 15 Jan 2011 14:53:40 -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 p0FMjhw1022363; Sat, 15 Jan 2011 14:45:44 -0800 (PST)
Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0FMj6LV022312 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Sat, 15 Jan 2011 14:45:15 -0800 (PST)
Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAHayMU2rR7H+/2dsb2JhbACkaXOkKJgehVAEhHCJWQ
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-4.cisco.com with ESMTP; 15 Jan 2011 22:45:04 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0FMj4c0024597; Sat, 15 Jan 2011 22:45:04 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Sat, 15 Jan 2011 14:45:04 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Sat, 15 Jan 2011 14:45:01 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D0DFA2C@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTimETdWyO-_9=rzJtmv9M_MzrQb+7zZ=6V+e9OGh@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Thread-Index: Acu0+6a2kYXxM+90RWiZygweP3pbYwABpGxQ
References: <4D221B2B.2020207@acm.org><AE36820147909644AD2A7CA014B1FB520D0DF509@xmb-sjc-222.amer.cisco.com> <AANLkTimETdWyO-_9=rzJtmv9M_MzrQb+7zZ=6V+e9OGh@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>
X-OriginalArrivalTime: 15 Jan 2011 22:45:04.0865 (UTC) FILETIME=[DA17D510:01CBB505]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0FMj6LV022312
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] [Isis-wg] WG last call on draft-ietf-trill-adj-01.txt
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 -

Thanx for the prompt reply.
Comments on open issues inline.

> 
> 2. The TRILL Hello Environment and Purposes
> 
>    functions. Currently Layer 3 use of IS-IS supports two types of
>    subnets: point-to-point link subnets between routers and general
>    broadcast (LAN) subnets. Because of the differences between the
>    environment of Layer 3 routers and the environment of TRILL
> RBridges,
>    the TRILL protocol uses a different type of LAN subnet from the
>    broadcast (LAN) subnet type encountered at Layer 3. The
> environmental
>    differences are described below followed by a summation, in Section
>    2.5, of the purposes of the TRILL LAN Hello protocol.
> 
> LES: Suggested rewrite
>   "the TRILL protocol uses a different type of LAN subnet from the
>    broadcast (LAN) subnet type encountered at Layer 3" to be
> 
> to become
> 
>   "The TRILL protocol uses different subnetwork dependent functions
>   from those specified in [IS-IS] Section 8.4."
> 
> <DEE3> It seems to me that the current wording int he draft is more
> specific. I don't see that advantage of changing to more vague
> wording... How about "instead of the broadcast (LAN) subnetwork
> functions encountered at Layer 3, which are specified in [IS-IS]
> Section 8.4, the TRILL protocol uses different functions for a LAN
> subnetwork."

I did not realize what I suggested was less specific. The intent of my
suggested change is to correctly state that the nature of the subnetwork
(LAN) has not changed at all, but the subnetwork dependent functions are
different for TRILL. Your suggested wording indicates that about as well
as mine - but the "standard terminology" used in "ISO speak" is
"subnetwork dependent functions" or "subnetwork dependent convergence
functions(SNDCF)". A bit obfuscatory in an IP centric world, but I would
like something that conforms to "ISO speak". 

Sorry for the nit picking...

> 
> ...
> 
> 2.5 Purposes of the TRILL Hello Protocol
> 
> ...
> 
>    In Layer 3 IS-IS all three of these functions are combined. Hellos
>    are padded to the maximum length so that a router neighbor is not
>    even discovered if it is impossible to communicate with it using
>    maximum sized packets. Also, even if Hellos from a neighbor R2 are
>    received by R1, if connectivity to R2 is not 2-way (i.e., R2 does
> not
> 
> 
> LES: Padding in [IS-IS] is optional. See RFC 3719 Section 6 for a
> discussion.
> 
> <DEE3> OK, I'll replace "area padded" with "are usually padded".

I think "may be padded" is better. There are some strong opinions on
both sides of the aisle in regards to the benefits/drawbacks of padding.
I don't want to suggest unaninimity where it does not exist.
(For the record, I am in favor of padding)


> 
> 5. MTU Matching
> 
> ...
> 
>    An RBridge, RB1, determines the desired campus link MTU by
>    calculating the minimum of its originatingL1LSPBufferSize and the
>    originatingLSPBufferSize advertised in the link state database by
> 
> LES: These should all be "originatingL1LSPBufferSize".
> (you have omitted "L1" in some cases)
> 
> <DEE3> I believe the variable in the LSP is just
> originatingLSPBufferSize and is L1 or L2 depending on whether the LSP
> is L1 or L2.

The TLV name is originatingLSPBufferSize(or LSPBufferSize in IANA). Per
ISO 10589 there are two variables which an implementation maintains:

originatingL1LSPBufferSize
originatingL2LSPBufferSize
(they are often the same - but do not have to be as the set of circuits
in use at the two levels may be different)

Whether L1 or L2 is in the TLV is determined by the type of PDU it is in
(Level1LSP or Level2LSP).

There is no variable named originatingLSPBufferSize.
Since TRILL is limited to L1 only at present, you should be using
originatingL1LSPBufferSize everywhere.

In cases where I have written text which is layer independent I have
used the term "originatingLxLSPBufferSize" - but this has no official
support. :-)

> 
> 6. Pseudonodes
> 
>    The Designated RBridge (DRB), determined as described above,
> controls
>    whether a pseudonode will be used on a link.
> 
>    It is anticipated that many links between RBridges will actually be
>    point-to-point, in which case using a pseudonode merely adds to the
>    complexity. If the DRB sets the bypass pseudonode bit in its TRILL
>    LAN Hellos, the RBridges on the link just directly report their
>    adjacencies that are in the Report state. If the DRB does not set
> the
>    bypass pseudonode bit in its TRILL Hellos, then it specifies a
>    pseudonode for the link and sends LSPs on behalf of the pseudonode
> as
>    usual. Setting the bypass pseudonode bit has no effect on how LSPs
>    are flooded on a link. It only affects what LSPs are generated.
> 
> LES: The phrase "specifies a pseudo-node for the link" suggests that
> the LANID sent by the DRB may be different depending on whether the
> bypass pseudo-node bit is set or not. Do you really mean that?
> 
> <DEE3> No, it is not meant to imply that. How about, "..., then the
LAN
> ID in the DRB's Hellos specifies the pseudonode for the link and the
> DRB sends ..."
> 
> he DRB does not set the
>    bypass pseudonode bit in its TRILL Hellos, then it specifies a
>    pseudonode for the link and sends LSPs on behalf of the pseudonode
> as
>    usual. Setting the bypass pseudonode bit has no effect on how LSPs
>    are flooded on a link. It only affects what LSPs are generated.
> 

If we agree that the contents of the LANID field are not affected by the
state of the bypass bit - which I think we do - then I think removing
the phrase is the best thing to do. 

   Les


_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Sun Jan 16 11:43:39 2011
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 EB5FB3A6E15 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun, 16 Jan 2011 11:43:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level: 
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=0.300, 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 ApgVARAVI8iw for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun, 16 Jan 2011 11:43:38 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id CB4563A6E11 for <trill-archive-Osh9cae4@lists.ietf.org>; Sun, 16 Jan 2011 11:43:38 -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 p0GJQjIn021779; Sun, 16 Jan 2011 11:26:46 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0GJQNOr021416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Sun, 16 Jan 2011 11:26:34 -0800 (PST)
Received: from [192.168.254.211] (dhcp-211 [192.168.254.211]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id p0GJN89B025282 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Sun, 16 Jan 2011 14:23:08 -0500 (EST)
Message-ID: <4D334595.3030507@workingcode.com>
Date: Sun, 16 Jan 2011 14:23:01 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: pppext@ietf.org
References: <20110106154501.15655.20204.idtracker@localhost>
In-Reply-To: <20110106154501.15655.20204.idtracker@localhost>
X-DCC-SIHOPE-DCC-3-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: "rbridge@postel.org" <rbridge@postel.org>
Subject: [rbridge] working group last call for PPP TRILL protocol control protocol [was Re: [Pppext] I-D Action:draft-ietf-pppext-trill-protocol-02.txt]
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

On 1/6/2011 10:45 AM, Internet-Drafts@ietf.org wrote:
> 	Title           : PPP TRILL Protocol Control Protocol
> 	Author(s)       : J. Carlson
> 	Filename        : draft-ietf-pppext-trill-protocol-02.txt
> 	Pages           : 6
> 	Date            : 2011-01-06
> 
> The Point-to-Point Protocol (PPP) [1] defines a Link Control Protocol
> (LCP) and a method for negotiating the use of multi-protocol traffic
> over point-to-point links.  This document describes support for
> Transparent Interconnection of Lots of Links (TRILL) Protocol,
> allowing direct communication between Routing Bridges (RBridges) via
> PPP links.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-pppext-trill-protocol-02.txt

I'm starting a working group last-call comment period for this draft.
The new version incorporates changes for all of the comments received up
to this point.

Last call will run for two weeks.  Please submit any comments,
questions, or concerns you might have to me or to the pppext@ietf.org
mailing list (or both) on or before Sunday, January 30th, 2011.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Jan 17 10:32:52 2011
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 593DD28C209 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 17 Jan 2011 10:32:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.682
X-Spam-Level: 
X-Spam-Status: No, score=-2.682 tagged_above=-999 required=5 tests=[AWL=-0.083, 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 kjcaiEbI7mLB for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 17 Jan 2011 10:32:51 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 4BA5628C212 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 17 Jan 2011 10:32:51 -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 p0HIHjiw012047; Mon, 17 Jan 2011 10:17:46 -0800 (PST)
Received: from mail-ew0-f52.google.com (mail-ew0-f52.google.com [209.85.215.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0HIHJhc012008 for <rbridge@postel.org>; Mon, 17 Jan 2011 10:17:28 -0800 (PST)
Received: by ewy23 with SMTP id 23so2558977ewy.39 for <rbridge@postel.org>; Mon, 17 Jan 2011 10:17:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=TrpWrYRvfbBPQShTTzh3ebpqrfdZH10+rhO7P05muco=; b=QnJMFO3ZF4viqsTo5MQWpV2voJELKJKDgwwe7mjU28eFUQtJ/Al0IYkCRTOT1wBarr RzkIUwzyuFm0NA1mJne4RNu5Sc0UczzJHiU476hEz9XxnZPubXfyOQjVsw1aPe8X4GI2 2qZs5ov4B3jWNn6qTThjaBLd90fJK8g0rzLhI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=mjLZ35V7vtmHjJu24rFOTCwcmAJpSIfcSbp3bdWc5bgGHjf7Cu0sz7wS0l7ETB5333 GM9RqwA4+pS1QHM5fEAqMz9e7hjY29AZsTDaCdJb9klc5qrh365OVOj67KLXZYpTF9Qh FwkI3kwSTBu8D+kQPAfqkh8/rhKeHVOdmhHU4=
MIME-Version: 1.0
Received: by 10.227.142.17 with SMTP id o17mr4516330wbu.111.1295288238507; Mon, 17 Jan 2011 10:17:18 -0800 (PST)
Received: by 10.216.139.219 with HTTP; Mon, 17 Jan 2011 10:17:18 -0800 (PST)
Date: Mon, 17 Jan 2011 10:17:18 -0800
Message-ID: <AANLkTi=Rd=w_nU2QMYH4Qh2-FqqU-Z3LH-KiEK-SLYm9@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: rbridge@postel.org
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: vishwas.ietf@gmail.com
Cc: anil_rijhsinghani@3com.com, kate.zebrose@alum.mit.edu
Subject: [rbridge] draft-ietf-trill-rbridge-mib
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

Hi Anil/ Kate,

I briefly looked at the TRILL MIB and had the following top level comments:

1. I think we should have a seperate tree for the Rbridge. I notice
some of the tables are the same as IS-IS. It will be very confusing to
code a MBI which is half IS-IS and half TRILL IS-IS.
2. There is no information for MultiTopology.
3. Another thing that needs to be kept is the MTU table. Which has MTU
information received from all the devices in the network. I know we
have MTU objects at a link and neighbor basis.
4. We probably need tohave Multicast Address listner  table too.
5. We will need a table for the the information in the system for
distribution trees, and information advertized by each system, or
atleast a way to change the values to be configured for a system.

Thanks,
Vishwas
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 18 07:57:13 2011
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 887AB28C151 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 07:57:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.911
X-Spam-Level: 
X-Spam-Status: No, score=-102.911 tagged_above=-999 required=5 tests=[AWL=-0.312, 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 iNt9nJDrBRLU for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 07:57:12 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 8FD1D3A7027 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 18 Jan 2011 07:57:12 -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 p0IFWJkw001077; Tue, 18 Jan 2011 07:32:20 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0IFVnUc000965 for <rbridge@postel.org>; Tue, 18 Jan 2011 07:31:59 -0800 (PST)
Received: by wwd20 with SMTP id 20so6921281wwd.21 for <rbridge@postel.org>; Tue, 18 Jan 2011 07:31:42 -0800 (PST)
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=OznyirfaQeWRWfeItTGPDUgNmKrHDQ3x9ODqNn3CTOo=; b=ICvJqpoQtwo9pEnpBnN55k4LcXetSKCs1X3UCxNSAzbTqiyxICHflomen24LGM2qLh 5D2MCBpXV0nyO9nfTlguFAfKl188ssh+nZQg2xSBqyR1tQkzmqA4MsLEGQQpei6pJeh4 30n7H0jr2HrE5cYOmGq9eAX0GU1uyH2JdYNvw=
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=H6wfEa6FTdc9bmX9F8bdiE0u5ndueQUAi65IAt7CyV9Gbo+W13Z9JbY4YNy8TonS41 2mJUYYQs8aIMHSQRznRT8Duf9ZS/yzTRontS7j2cj6xyZd6gyjlT7CXvk84i2FyMR9Tq wFMZ5G5p2CRntPO8byS2tlfZvfPkTaPV74xwk=
Received: by 10.227.141.138 with SMTP id m10mr5748106wbu.66.1295364702149; Tue, 18 Jan 2011 07:31:42 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Tue, 18 Jan 2011 07:31:19 -0800 (PST)
In-Reply-To: <4D2226FA.3040001@acm.org>
References: <4D221B2B.2020207@acm.org> <4D2226FA.3040001@acm.org>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 18 Jan 2011 10:31:19 -0500
Message-ID: <AANLkTikNsMAk3p_h66zo+9=wVHS2APXVToLkDceHLcRj@mail.gmail.com>
To: Erik Nordmark <nordmark@acm.org>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0IFVnUc000965
Cc: rbridge@postel.org
Subject: Re: [rbridge] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Erik,

On Mon, Jan 3, 2011 at 2:43 PM, Erik Nordmark <nordmark@acm.org> wrote:
> On 01/ 3/11 10:53 AM, Erik Nordmark wrote:
>>
>> ...
>
> I have a small editorial suggestion for the draft.
>
> Currently the events are numbered 1-8 and 1-5. Thus "event 5" isn't
> sufficient to specify the name of an event. It would be more clear if
> they were numbered A1-A8 and D1-D5 (or P1-P5).

I'm fine with that change. Unless there are some arguments the other
way, I'll make the change.

Thanks,
Donald

> That means we don't need text like e.g., "an adjacency event 5 occurs
> for the adjacency", but can instead say "an event A5 occurs for the
> adjacency".
>
> =A0 =A0Erik

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 18 10:16:37 2011
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 6ADE03A705E for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 10:16:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 wH73+eH+2d1D for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 10:16:36 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 432673A6FE2 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 18 Jan 2011 10:16:36 -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 p0IHiMZj028078; Tue, 18 Jan 2011 09:44:23 -0800 (PST)
Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0IHhr2t028008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Tue, 18 Jan 2011 09:44:02 -0800 (PST)
Received: from [128.107.114.233] ([128.107.114.233]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id p0IHhp8r032066 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2011 09:43:51 -0800
Message-ID: <4D35D160.9020602@acm.org>
Date: Tue, 18 Jan 2011 09:44:00 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: rbridge@postel.org
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: nordmark@acm.org
Subject: [rbridge] Fwd: Re: [Isis-wg] WG last call on draft-ietf-trill-adj-01.txt
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

Forwarded from the isis list so all the trill discussion is visible on 
the rbridge list.

    Erik

-------- Original Message --------
Subject: Re: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Date: Tue, 18 Jan 2011 12:44:53 +0000
From: mike shand <mshand@cisco.com>
To: isis-wg@ietf.org

  To be absolutely clear on this, perhaps the text should also describe
what the non DRBs do. I appreciate that the example includes this,
but it is somewhat anomalous that the normative text describes the
changed actions of the DRB, but not (explicitly) those of the non-DRBs.

So how about:-


"If the DRB sets the bypass pseudonode bit in its TRILL
    LAN Hellos, the RBridges on the link (including the DRB) just
directly report all their
    adjacencies on the LAN that are in the Report state. If the DRB does
not set the
    bypass pseudonode bit in its TRILL Hellos, then (as in ISO/IEC
10589) it sends LSPs on behalf of the pseudonode, and all RBridges
report only their adjacency to the pseudonode. Setting the bypass
pseudonode bit has no effect on how LSPs
    are flooded on a link. It only affects what LSPs are generated."


     Mike


On 15/01/2011 22:45, Les Ginsberg (ginsberg) wrote:
>> 6. Pseudonodes
>> >
>> >      The Designated RBridge (DRB), determined as described above,
>> >  controls
>> >      whether a pseudonode will be used on a link.
>> >
>> >      It is anticipated that many links between RBridges will actually be
>> >      point-to-point, in which case using a pseudonode merely adds to the
>> >      complexity. If the DRB sets the bypass pseudonode bit in its TRILL
>> >      LAN Hellos, the RBridges on the link just directly report their
>> >      adjacencies that are in the Report state. If the DRB does not set
>> >  the
>> >      bypass pseudonode bit in its TRILL Hellos, then it specifies a
>> >      pseudonode for the link and sends LSPs on behalf of the pseudonode
>> >  as
>> >      usual. Setting the bypass pseudonode bit has no effect on how LSPs
>> >      are flooded on a link. It only affects what LSPs are generated.
>> >
>> >  LES: The phrase "specifies a pseudo-node for the link" suggests that
>> >  the LANID sent by the DRB may be different depending on whether the
>> >  bypass pseudo-node bit is set or not. Do you really mean that?
>> >
>> >  <DEE3>  No, it is not meant to imply that. How about, "..., then the
> LAN
>> >  ID in the DRB's Hellos specifies the pseudonode for the link and the
>> >  DRB sends ..."
>> >
>> >  he DRB does not set the
>> >      bypass pseudonode bit in its TRILL Hellos, then it specifies a
>> >      pseudonode for the link and sends LSPs on behalf of the pseudonode
>> >  as
>> >      usual. Setting the bypass pseudonode bit has no effect on how LSPs
>> >      are flooded on a link. It only affects what LSPs are generated.
>> >
> If we agree that the contents of the LANID field are not affected by the
> state of the bypass bit - which I think we do - then I think removing
> the phrase is the best thing to do.
>
>     Les
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 18 10:25:37 2011
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 7E3F03A7059 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 10:25:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 MlrMa5izKzgR for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 10:25:36 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 29F773A6F42 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 18 Jan 2011 10:25:36 -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 p0IHhxpu028028; Tue, 18 Jan 2011 09:44:00 -0800 (PST)
Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0IHhWdF027972 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Tue, 18 Jan 2011 09:43:40 -0800 (PST)
Received: from [128.107.114.233] ([128.107.114.233]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id p0IHhUm9031788 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Tue, 18 Jan 2011 09:43:30 -0800
Message-ID: <4D35D14B.6000604@acm.org>
Date: Tue, 18 Jan 2011 09:43:39 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: rbridge@postel.org
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: nordmark@acm.org
Subject: [rbridge] Fwd: Re: [Isis-wg] WG last call on draft-ietf-trill-adj-01.txt
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

Forwarded from the isis list so all the trill discussion is visible on 
the rbridge list.

    Erik

-------- Original Message --------
Subject: Re: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Date: Tue, 18 Jan 2011 13:36:48 +0000
From: mike shand <mshand@cisco.com>
To: isis-wg@ietf.org

  Vishwas,
     If the consequences of failure for this information to be correctly
exchanged, as a result of loss a single message, are that "bad things
happen", then I don't think it can be considered an optimization to
provide a mechanism which guarantees correct delivery.

     An optimization, in my view, is something like the sending of CSNPs
on pt-pt circuit start up. If they are correctly received the
synchronization process is speeded up, but if they are not, correct
synchronization is still guaranteed to occur, albeit at the expense of
further message exchanges.

     What am I failing to understand? How likely is a failure scenario,
and what is the extent of the damage caused? It is a truism that if
something CAN go wrong it WILL go wrong just at the point where it will
cause maximum disruption. The Boston Hospital meltdown is but one of the
oft cited examples of this phenomenon.

     Mike




On 14/01/2011 22:25, Vishwas Manral wrote:
> Hi Les,
>
> You have good comments.
>
> Like I said we could send the same information multiple times to
> assume the information has reached its neighbor. If the information is
> in one Hello we already have the solution.
>
> I agree this can be improved, however I feel we do not need to do
> every optimization at this point.
>
> Thanks,
> Vishwas
>
>>>>> VM>  I agree with you. It is left to an implementation to decide how
>>> to
>>>>> do it.
>>>> OK. I do think some guidance would be good as the use of MTU PDUs is
>>> an entirely new functionality.
>>> VM>  A clarification could be added.
>>>
>>>> To requote the draft:
>>>>
>>>> " If there are no adjacencies with a non-zero Designated VLAN Hello
>>>>    Holding timer, an empty TRILL Neighbor TLV MUST be included in each
>>>>    Hello.  If there are such adjacencies, then the Hello MAY contain a
>>>>    TRILL Neighbor TLV..."
>>>>
>>>> I understand the motivation for an explicit "no neighbors"
>>> advertisement - but I am asking why you want to make inclusion of TRILL
>>> Neighbor TLV optional when you do have adjacencies?
>>> VM>  This can again be treated in the context of the fact that if the
>>> data does not fit in one Hello, we could send the other data in the
>>> other Hello, and include empty TRILL Neighbor TLV. It could also be
>>> treated in the context of the fact that we should allow receiving the
>>> empty TLV.
>>>
>>> I know this could be removed by itself, as there is no harm or benefit
>>> of the same, based on how the spec stands, however it could help to
>>> state that for some future use like mentioned above.
>>>
>>> Thanks,
>>> Vishwas
>>>
>>>>>>> On Thu, Jan 13, 2011 at 5:36 PM, Les Ginsberg (ginsberg)
>>>>>>> <ginsberg@cisco.com>  wrote:
>>>>>>>> (resending w corrected TRILL WG address)
>>>>>>>>
>>>>>>>> Attached please find my comments on draft-ietf-trill-adj-01.
>>>>>>>>
>>>>>>>> The file draft-ietf-trill-adj-01_comments.txt contains
>>> substantive
>>>>>>>> comments identified by Section # - except in a couple of cases
>>>>> where
>>>>>>> the
>>>>>>>> remarks are more generic.
>>>>>>>>
>>>>>>>> The file draft-ietf-trill-adj-01_editorial.txt is portions of
>>> the
>>>>>>> draft
>>>>>>>> annotated with editorial comments. Search for "LES:" in the
>>> file.
>>>>>>>> As context, the requirements of [TRILL] introduce the need to
>>> send
>>>>> a
>>>>>>>> great deal more circuit scoped information on a LAN as compared
>>> to
>>>>>>> Layer
>>>>>>>> 3 IS-IS. Extensions to the IS-IS protocol defined in [TRILL],
>>>>>>>> [TRILL-ISIS], and [TRILL-ADJ] are designed to support this new
>>>>>>>> information and to provide robust loop prevention in the
>>>>> forwarding
>>>>>>> of
>>>>>>>> data. But I believe the extensions as currently defined have
>>>>>>> significant
>>>>>>>> scalability issues in the presence of a large number of
>>> neighbors
>>>>> on
>>>>>>> a
>>>>>>>> LAN and/or a large number of enabled VLANs. In my comments I
>>> have
>>>>>>>> confined myself to pointing out where I believe such issues
>>> arise.
>>>>> If
>>>>>>>> there is consensus that these are issues which should be
>>>>> addressed,
>>>>>>> then
>>>>>>>> additional discussions can be started as to how to do so.
>>>>>>>>
>>>>>>>> Finally, I would like to thank the authors of draft-ietf-trill-
>>>>> adj-01
>>>>>>>> for the effort and diligence they obviously applied to the
>>> writing
>>>>> of
>>>>>>>> this draft.
>>>>>>>>
>>>>>>>>    Les
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> rbridge mailing list
>>>>>>>> rbridge@postel.org
>>>>>>>> http://mailman.postel.org/mailman/listinfo/rbridge
>>>>>>>>
>>>>>>>>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
>
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 18 14:22:52 2011
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 9C7993A6D82 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 14:22:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.912
X-Spam-Level: 
X-Spam-Status: No, score=-102.912 tagged_above=-999 required=5 tests=[AWL=-0.313, 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 PobioUpAaBx8 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 14:22:51 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 5D9063A6DCE for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 18 Jan 2011 14:22:51 -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 p0IMC0tp028433; Tue, 18 Jan 2011 14:12:02 -0800 (PST)
Received: from mail-wy0-f180.google.com (mail-wy0-f180.google.com [74.125.82.180]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0IMBa1w028382 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Tue, 18 Jan 2011 14:11:46 -0800 (PST)
Received: by wyb28 with SMTP id 28so136184wyb.39 for <rbridge@postel.org>; Tue, 18 Jan 2011 14:11:36 -0800 (PST)
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=MBNGP+pSBLH99Xe+bwMaHhwUIr1vkPY3JQNJx/1/rO4=; b=vdHJWDKB1sXq/QQq0cvNVwbo2dfvOpuo6TnEjAx1ay2/poyrlguUTbF3OonaTW/tPj UJCoeoL+uSsh4R58k8GHWaSSwNprucVW9Nt2DIAh+Dx9d10DLAX46kyqW2wFJ92SHIqF bBVFZmTJcoGDiWlGX4AJXKIhQqhsqx1Uug1ww=
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=L/cpsl7jWeZDggHOhXoVgP/p5FaPhmyLkwPthhMTjKGvMhcBAmG0lGbhMpNar0XTKb 416g5dnXk7IUAwHJky63gmfcuADqOf22uItnEbz85qRHRdgu1pYEiGBOKoAAgloEhxos vY6cjsEDRdrLYWKandp/zmUU1VwfgWZHl5yRs=
Received: by 10.227.141.138 with SMTP id m10mr6301983wbu.66.1295388695662; Tue, 18 Jan 2011 14:11:35 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Tue, 18 Jan 2011 14:11:15 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D0DFA2C@xmb-sjc-222.amer.cisco.com>
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF509@xmb-sjc-222.amer.cisco.com> <AANLkTimETdWyO-_9=rzJtmv9M_MzrQb+7zZ=6V+e9OGh@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DFA2C@xmb-sjc-222.amer.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 18 Jan 2011 17:11:15 -0500
Message-ID: <AANLkTimus5DuV+LvoBN83vd97g6TzNUTkFD_gFvj2rOn@mail.gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0IMBa1w028382
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] [Isis-wg] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

On Sat, Jan 15, 2011 at 5:45 PM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
> Donald -
>
> Thanx for the prompt reply.
> Comments on open issues inline.
>
>> 2. The TRILL Hello Environment and Purposes
>>
>> =A0 =A0functions. Currently Layer 3 use of IS-IS supports two types of
>> =A0 =A0subnets: point-to-point link subnets between routers and general
>> =A0 =A0broadcast (LAN) subnets. Because of the differences between the
>> =A0 =A0environment of Layer 3 routers and the environment of TRILL
>> RBridges,
>> =A0 =A0the TRILL protocol uses a different type of LAN subnet from the
>> =A0 =A0broadcast (LAN) subnet type encountered at Layer 3. The
>> environmental
>> =A0 =A0differences are described below followed by a summation, in Secti=
on
>> =A0 =A02.5, of the purposes of the TRILL LAN Hello protocol.
>>
>> LES: Suggested rewrite
>> =A0 "the TRILL protocol uses a different type of LAN subnet from the
>> =A0 =A0broadcast (LAN) subnet type encountered at Layer 3" to be
>>
>> to become
>>
>> =A0 "The TRILL protocol uses different subnetwork dependent functions
>> =A0 from those specified in [IS-IS] Section 8.4."
>>
>> <DEE3> It seems to me that the current wording int he draft is more
>> specific. I don't see that advantage of changing to more vague
>> wording... How about "instead of the broadcast (LAN) subnetwork
>> functions encountered at Layer 3, which are specified in [IS-IS]
>> Section 8.4, the TRILL protocol uses different functions for a LAN
>> subnetwork."
>
> I did not realize what I suggested was less specific. The intent of my
> suggested change is to correctly state that the nature of the subnetwork
> (LAN) has not changed at all, but the subnetwork dependent functions are
> different for TRILL. Your suggested wording indicates that about as well
> as mine - but the "standard terminology" used in "ISO speak" is
> "subnetwork dependent functions" or "subnetwork dependent convergence
> functions(SNDCF)". A bit obfuscatory in an IP centric world, but I would
> like something that conforms to "ISO speak".
>
> Sorry for the nit picking...

OK, "instead of the broadcast (LAN) subnetwork dependent functions
encountered at Layer 3, which are specified in [IS-IS] Section 8.4,
the TRILL protocol uses different subnetwork dependent functions for a
LAN subnetwork."

>> ...
>>
>> 2.5 Purposes of the TRILL Hello Protocol
>>
>> ...
>>
>> =A0 =A0In Layer 3 IS-IS all three of these functions are combined. Hellos
>> =A0 =A0are padded to the maximum length so that a router neighbor is not
>> =A0 =A0even discovered if it is impossible to communicate with it using
>> =A0 =A0maximum sized packets. Also, even if Hellos from a neighbor R2 are
>> =A0 =A0received by R1, if connectivity to R2 is not 2-way (i.e., R2 does
>> not
>>
>>
>> LES: Padding in [IS-IS] is optional. See RFC 3719 Section 6 for a
>> discussion.
>>
>> <DEE3> OK, I'll replace "are padded" with "are usually padded".
>
> I think "may be padded" is better. There are some strong opinions on
> both sides of the aisle in regards to the benefits/drawbacks of padding.
> I don't want to suggest unaninimity where it does not exist.
> (For the record, I am in favor of padding)

OK, in context "may be padded" is all right. I think I'll also add an
informational reference to RFC 3719.

>> 5. MTU Matching
>>
>> ...
>>
>> =A0 =A0An RBridge, RB1, determines the desired campus link MTU by
>> =A0 =A0calculating the minimum of its originatingL1LSPBufferSize and the
>> =A0 =A0originatingLSPBufferSize advertised in the link state database by
>>
>> LES: These should all be "originatingL1LSPBufferSize".
>> (you have omitted "L1" in some cases)
>>
>> <DEE3> I believe the variable in the LSP is just
>> originatingLSPBufferSize and is L1 or L2 depending on whether the LSP
>> is L1 or L2.
>
> The TLV name is originatingLSPBufferSize(or LSPBufferSize in IANA). Per
> ISO 10589 there are two variables which an implementation maintains:
>
> originatingL1LSPBufferSize
> originatingL2LSPBufferSize
> (they are often the same - but do not have to be as the set of circuits
> in use at the two levels may be different)
>
> Whether L1 or L2 is in the TLV is determined by the type of PDU it is in
> (Level1LSP or Level2LSP).
>
> There is no variable named originatingLSPBufferSize.
> Since TRILL is limited to L1 only at present, you should be using
> originatingL1LSPBufferSize everywhere.

I note that RFC 3719, to which you referred me above, uses
originatingL1LSPBufferSize in some contexts and
originatingLSPBufferSize in others. Whether there is a "variable"
named originatingLSPBufferSize depends on what you think a variable
is. We seem to agree that there is a TLV field called
originatingLSPBufferSize and the reference from the draft above to "in
the link state database" was meant to refer to that field by its
proper name.

> ...
>
>> 6. Pseudonodes
>>
>> =A0 =A0The Designated RBridge (DRB), determined as described above,
>> controls
>> =A0 =A0whether a pseudonode will be used on a link.
>>
>> =A0 =A0It is anticipated that many links between RBridges will actually =
be
>> =A0 =A0point-to-point, in which case using a pseudonode merely adds to t=
he
>> =A0 =A0complexity. If the DRB sets the bypass pseudonode bit in its TRILL
>> =A0 =A0LAN Hellos, the RBridges on the link just directly report their
>> =A0 =A0adjacencies that are in the Report state. If the DRB does not set
>> the
>> =A0 =A0bypass pseudonode bit in its TRILL Hellos, then it specifies a
>> =A0 =A0pseudonode for the link and sends LSPs on behalf of the pseudonode
>> as
>> =A0 =A0usual. Setting the bypass pseudonode bit has no effect on how LSPs
>> =A0 =A0are flooded on a link. It only affects what LSPs are generated.
>>
>> LES: The phrase "specifies a pseudo-node for the link" suggests that
>> the LANID sent by the DRB may be different depending on whether the
>> bypass pseudo-node bit is set or not. Do you really mean that?
>>
>> <DEE3> No, it is not meant to imply that. How about, "..., then the
> LAN
>> ID in the DRB's Hellos specifies the pseudonode for the link and the
>> DRB sends ..."
>>
>> he DRB does not set the
>> =A0 =A0bypass pseudonode bit in its TRILL Hellos, then it specifies a
>> =A0 =A0pseudonode for the link and sends LSPs on behalf of the pseudonode
>> as
>> =A0 =A0usual. Setting the bypass pseudonode bit has no effect on how LSPs
>> =A0 =A0are flooded on a link. It only affects what LSPs are generated.
>>
>
> If we agree that the contents of the LANID field are not affected by the
> state of the bypass bit - which I think we do - then I think removing
> the phrase is the best thing to do.

Yes, I agree on that. Deleting "specifies a pseudonode for the link
and" seems OK.

> =A0 Les

Thanks,
Donald

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 18 17:03:18 2011
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 06EC828C0F7 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 17:03:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.267
X-Spam-Level: 
X-Spam-Status: No, score=-5.267 tagged_above=-999 required=5 tests=[AWL=-2.668, 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 ceT+HRJA37VP for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 18 Jan 2011 17:03:16 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 2844E28C0E1 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 18 Jan 2011 17:03:16 -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 p0J0nZZm025332; Tue, 18 Jan 2011 16:49:37 -0800 (PST)
Received: from sj-iport-2.cisco.com (sj-iport-2.cisco.com [171.71.176.71]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0J0n7Kj025307 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Tue, 18 Jan 2011 16:49:16 -0800 (PST)
Authentication-Results: sj-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAEnENU2rR7Hu/2dsb2JhbACkQnOnbpophVAEhG+JWYJy
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-2.cisco.com with ESMTP; 19 Jan 2011 00:49:07 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p0J0n705026048; Wed, 19 Jan 2011 00:49:07 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 18 Jan 2011 16:49:07 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 18 Jan 2011 16:49:06 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D17770B@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTimus5DuV+LvoBN83vd97g6TzNUTkFD_gFvj2rOn@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Thread-Index: Acu3XLUBkTRv2KlcRUuXZGTUu3JwEwAFQoQA
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF509@xmb-sjc-222.amer.cisco.com> <AANLkTimETdWyO-_9=rzJtmv9M_MzrQb+7zZ=6V+e9OGh@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DFA2C@xmb-sjc-222.amer.cisco.com> <AANLkTimus5DuV+LvoBN83vd97g6TzNUTkFD_gFvj2rOn@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>
X-OriginalArrivalTime: 19 Jan 2011 00:49:07.0135 (UTC) FILETIME=[AD455CF0:01CBB772]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0J0n7Kj025307
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] [Isis-wg] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Donald -

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Tuesday, January 18, 2011 2:11 PM
> To: Les Ginsberg (ginsberg)
> Cc: rbridge@postel.org; isis-wg@ietf.org
> Subject: Re: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-adj-
> 01.txt
> =

> Hi Les,
> =

> On Sat, Jan 15, 2011 at 5:45 PM, Les Ginsberg (ginsberg)
> <ginsberg@cisco.com> wrote:
> > Donald -
> >
> > Thanx for the prompt reply.
> > Comments on open issues inline.
> >
> >> 2. The TRILL Hello Environment and Purposes
> >>
> >> =A0 =A0functions. Currently Layer 3 use of IS-IS supports two types of
> >> =A0 =A0subnets: point-to-point link subnets between routers and general
> >> =A0 =A0broadcast (LAN) subnets. Because of the differences between the
> >> =A0 =A0environment of Layer 3 routers and the environment of TRILL
> >> RBridges,
> >> =A0 =A0the TRILL protocol uses a different type of LAN subnet from the
> >> =A0 =A0broadcast (LAN) subnet type encountered at Layer 3. The
> >> environmental
> >> =A0 =A0differences are described below followed by a summation, in
> Section
> >> =A0 =A02.5, of the purposes of the TRILL LAN Hello protocol.
> >>
> >> LES: Suggested rewrite
> >> =A0 "the TRILL protocol uses a different type of LAN subnet from the
> >> =A0 =A0broadcast (LAN) subnet type encountered at Layer 3" to be
> >>
> >> to become
> >>
> >> =A0 "The TRILL protocol uses different subnetwork dependent functions
> >> =A0 from those specified in [IS-IS] Section 8.4."
> >>
> >> <DEE3> It seems to me that the current wording int he draft is more
> >> specific. I don't see that advantage of changing to more vague
> >> wording... How about "instead of the broadcast (LAN) subnetwork
> >> functions encountered at Layer 3, which are specified in [IS-IS]
> >> Section 8.4, the TRILL protocol uses different functions for a LAN
> >> subnetwork."
> >
> > I did not realize what I suggested was less specific. The intent of
> my
> > suggested change is to correctly state that the nature of the
> subnetwork
> > (LAN) has not changed at all, but the subnetwork dependent functions
> are
> > different for TRILL. Your suggested wording indicates that about as
> well
> > as mine - but the "standard terminology" used in "ISO speak" is
> > "subnetwork dependent functions" or "subnetwork dependent convergence
> > functions(SNDCF)". A bit obfuscatory in an IP centric world, but I
> would
> > like something that conforms to "ISO speak".
> >
> > Sorry for the nit picking...
> =

> OK, "instead of the broadcast (LAN) subnetwork dependent functions
> encountered at Layer 3, which are specified in [IS-IS] Section 8.4,
> the TRILL protocol uses different subnetwork dependent functions for a
> LAN subnetwork."

ACK

> =

> >> ...
> >>
> >> 2.5 Purposes of the TRILL Hello Protocol
> >>
> >> ...
> >>
> >> =A0 =A0In Layer 3 IS-IS all three of these functions are combined.
> Hellos
> >> =A0 =A0are padded to the maximum length so that a router neighbor is n=
ot
> >> =A0 =A0even discovered if it is impossible to communicate with it using
> >> =A0 =A0maximum sized packets. Also, even if Hellos from a neighbor R2
> are
> >> =A0 =A0received by R1, if connectivity to R2 is not 2-way (i.e., R2 do=
es
> >> not
> >>
> >>
> >> LES: Padding in [IS-IS] is optional. See RFC 3719 Section 6 for a
> >> discussion.
> >>
> >> <DEE3> OK, I'll replace "are padded" with "are usually padded".
> >
> > I think "may be padded" is better. There are some strong opinions on
> > both sides of the aisle in regards to the benefits/drawbacks of
> padding.
> > I don't want to suggest unaninimity where it does not exist.
> > (For the record, I am in favor of padding)
> =

> OK, in context "may be padded" is all right. I think I'll also add an
> informational reference to RFC 3719.

ACK

> =

> >> 5. MTU Matching
> >>
> >> ...
> >>
> >> =A0 =A0An RBridge, RB1, determines the desired campus link MTU by
> >> =A0 =A0calculating the minimum of its originatingL1LSPBufferSize and t=
he
> >> =A0 =A0originatingLSPBufferSize advertised in the link state database =
by
> >>
> >> LES: These should all be "originatingL1LSPBufferSize".
> >> (you have omitted "L1" in some cases)
> >>
> >> <DEE3> I believe the variable in the LSP is just
> >> originatingLSPBufferSize and is L1 or L2 depending on whether the
> LSP
> >> is L1 or L2.
> >
> > The TLV name is originatingLSPBufferSize(or LSPBufferSize in IANA).
> Per
> > ISO 10589 there are two variables which an implementation maintains:
> >
> > originatingL1LSPBufferSize
> > originatingL2LSPBufferSize
> > (they are often the same - but do not have to be as the set of
> circuits
> > in use at the two levels may be different)
> >
> > Whether L1 or L2 is in the TLV is determined by the type of PDU it is
> in
> > (Level1LSP or Level2LSP).
> >
> > There is no variable named originatingLSPBufferSize.
> > Since TRILL is limited to L1 only at present, you should be using
> > originatingL1LSPBufferSize everywhere.
> =

> I note that RFC 3719, to which you referred me above, uses
> originatingL1LSPBufferSize in some contexts and
> originatingLSPBufferSize in others. Whether there is a "variable"
> named originatingLSPBufferSize depends on what you think a variable
> is. We seem to agree that there is a TLV field called
> originatingLSPBufferSize and the reference from the draft above to "in
> the link state database" was meant to refer to that field by its
> proper name.


We agree that if referring to the type name of the TLV the correct name is =
originatingLSPBufferSize.
I think we also agree that what is advertised in the TLV (the value) is eit=
her originatingL1LSPBufferSize or originatingL2LSPBufferSize. In reviewing =
the draft I think all uses are actually referring to the value advertised -=
 not the type name of the TLV - so that is why I suggest that all uses in t=
he draft should be originatingL1LSPBufferSize.


> =

> > ...
> >
> >> 6. Pseudonodes
> >>
> >> =A0 =A0The Designated RBridge (DRB), determined as described above,
> >> controls
> >> =A0 =A0whether a pseudonode will be used on a link.
> >>
> >> =A0 =A0It is anticipated that many links between RBridges will actually
> be
> >> =A0 =A0point-to-point, in which case using a pseudonode merely adds to
> the
> >> =A0 =A0complexity. If the DRB sets the bypass pseudonode bit in its
> TRILL
> >> =A0 =A0LAN Hellos, the RBridges on the link just directly report their
> >> =A0 =A0adjacencies that are in the Report state. If the DRB does not s=
et
> >> the
> >> =A0 =A0bypass pseudonode bit in its TRILL Hellos, then it specifies a
> >> =A0 =A0pseudonode for the link and sends LSPs on behalf of the
> pseudonode
> >> as
> >> =A0 =A0usual. Setting the bypass pseudonode bit has no effect on how
> LSPs
> >> =A0 =A0are flooded on a link. It only affects what LSPs are generated.
> >>
> >> LES: The phrase "specifies a pseudo-node for the link" suggests that
> >> the LANID sent by the DRB may be different depending on whether the
> >> bypass pseudo-node bit is set or not. Do you really mean that?
> >>
> >> <DEE3> No, it is not meant to imply that. How about, "..., then the
> > LAN
> >> ID in the DRB's Hellos specifies the pseudonode for the link and the
> >> DRB sends ..."
> >>
> >> he DRB does not set the
> >> =A0 =A0bypass pseudonode bit in its TRILL Hellos, then it specifies a
> >> =A0 =A0pseudonode for the link and sends LSPs on behalf of the
> pseudonode
> >> as
> >> =A0 =A0usual. Setting the bypass pseudonode bit has no effect on how
> LSPs
> >> =A0 =A0are flooded on a link. It only affects what LSPs are generated.
> >>
> >
> > If we agree that the contents of the LANID field are not affected by
> the
> > state of the bypass bit - which I think we do - then I think removing
> > the phrase is the best thing to do.
> =

> Yes, I agree on that. Deleting "specifies a pseudonode for the link
> and" seems OK.

ACK.

   Les

> =

> > =A0 Les
> =

> Thanks,
> Donald

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Thu Jan 20 17:55:37 2011
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 17D303A6894 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 20 Jan 2011 17:55:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.909
X-Spam-Level: 
X-Spam-Status: No, score=-102.909 tagged_above=-999 required=5 tests=[AWL=-0.310, 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 HKkeSLjGvvBL for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 20 Jan 2011 17:55:36 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id EBF143A680E for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 20 Jan 2011 17:55:35 -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 p0L1b5Xr024401; Thu, 20 Jan 2011 17:37:06 -0800 (PST)
Received: from mail-wy0-f180.google.com (mail-wy0-f180.google.com [74.125.82.180]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0L1aCnK023995 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 20 Jan 2011 17:36:22 -0800 (PST)
Received: by wyb28 with SMTP id 28so1313009wyb.39 for <rbridge@postel.org>; Thu, 20 Jan 2011 17:36:11 -0800 (PST)
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=Erpt5wWIfPwF7viLMfMj5HNxMmEwhsccKudGak5bjsQ=; b=S1TwqXBwyAKh6z9ZEC1jQUVrouq9WPe8wVBlF85nAXBWhRHnmTtAH/G2SgD4pEMC1J 7jMhlEw5VUfc/Ilt7xGmEi4+JuMaRf/GcRIIjQTjrA83A5uQJlQTlAmQwr/NxZFweqZ1 KNrCSEN0NfhAjLn/U3qnscZD4cMBXSW73XEm4=
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=F7FbnHIiap+vUidrdqKxAlaOp6SIO1dTboS+kJyUNgikqGgKcpgliq8TfGv/RM/15c uIySOrOJZ8SpgVavuS0X97aCcrA4cDf7vWq5JzsGhnkmo5cPSL1VWAP02xyjirr5n1c4 6ju3tRLvllgOcZNpFowwxL/T8LRs1GNMBS3Fc=
Received: by 10.227.145.139 with SMTP id d11mr39667wbv.8.1295573771500; Thu, 20 Jan 2011 17:36:11 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Thu, 20 Jan 2011 17:35:51 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D17770B@xmb-sjc-222.amer.cisco.com>
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF509@xmb-sjc-222.amer.cisco.com> <AANLkTimETdWyO-_9=rzJtmv9M_MzrQb+7zZ=6V+e9OGh@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DFA2C@xmb-sjc-222.amer.cisco.com> <AANLkTimus5DuV+LvoBN83vd97g6TzNUTkFD_gFvj2rOn@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D17770B@xmb-sjc-222.amer.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 20 Jan 2011 20:35:51 -0500
Message-ID: <AANLkTikydKQiU6mYWeV88WQoBf0NNFE2sspk=+kn32po@mail.gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0L1aCnK023995
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] [Isis-wg] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

On Tue, Jan 18, 2011 at 7:49 PM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
> Donald -
>
>> -----Original Message-----
>> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
>> Sent: Tuesday, January 18, 2011 2:11 PM
>> To: Les Ginsberg (ginsberg)
>> Cc: rbridge@postel.org; isis-wg@ietf.org
>> Subject: Re: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-adj-
>> 01.txt
>>
>> Hi Les,
>>
>> On Sat, Jan 15, 2011 at 5:45 PM, Les Ginsberg (ginsberg)
>> <ginsberg@cisco.com> wrote:
>> > Donald -
...
>> >> 5. MTU Matching
>> >>
>> >> ...
>> >>
>> >> =A0 =A0An RBridge, RB1, determines the desired campus link MTU by
>> >> =A0 =A0calculating the minimum of its originatingL1LSPBufferSize and =
the
>> >> =A0 =A0originatingLSPBufferSize advertised in the link state database=
 by
>> >>
>> >> LES: These should all be "originatingL1LSPBufferSize".
>> >> (you have omitted "L1" in some cases)
>> >>
>> >> <DEE3> I believe the variable in the LSP is just
>> >> originatingLSPBufferSize and is L1 or L2 depending on whether the
>> LSP
>> >> is L1 or L2.
>> >
>> > The TLV name is originatingLSPBufferSize(or LSPBufferSize in IANA).
>> Per
>> > ISO 10589 there are two variables which an implementation maintains:
>> >
>> > originatingL1LSPBufferSize
>> > originatingL2LSPBufferSize
>> > (they are often the same - but do not have to be as the set of
>> circuits
>> > in use at the two levels may be different)
>> >
>> > Whether L1 or L2 is in the TLV is determined by the type of PDU it is
>> in
>> > (Level1LSP or Level2LSP).
>> >
>> > There is no variable named originatingLSPBufferSize.
>> > Since TRILL is limited to L1 only at present, you should be using
>> > originatingL1LSPBufferSize everywhere.
>>
>> I note that RFC 3719, to which you referred me above, uses
>> originatingL1LSPBufferSize in some contexts and
>> originatingLSPBufferSize in others. Whether there is a "variable"
>> named originatingLSPBufferSize depends on what you think a variable
>> is. We seem to agree that there is a TLV field called
>> originatingLSPBufferSize and the reference from the draft above to "in
>> the link state database" was meant to refer to that field by its
>> proper name.
>
> We agree that if referring to the type name of the TLV the correct name i=
s originatingLSPBufferSize.
> I think we also agree that what is advertised in the TLV (the value) is e=
ither originatingL1LSPBufferSize or originatingL2LSPBufferSize. In reviewin=
g the draft I think all uses are actually referring to the value advertised=
 - not the type name of the TLV - so that is why I suggest that all uses in=
 the draft should be originatingL1LSPBufferSize.

I still think it is the field in the link state database that is being
referred to and it should be called originatingLSPBufferSize. But I'm
willing to change it to originatingL1LSPBufferSize with other changes
that make if refer to the originating RBridge's variable. How about:

"An RBridge, RB1, determines the desired campus link MTU by
calculating the minimum of its originatingL1LSPBufferSize and the
originatingL1LSPBufferSize of other RBridges in the campus, as
advertised in the link state database, but not less than 1,470 bytes."

>>
>> > ...
...

>
> =A0 Les

I glanced at your other comments and think they are best handled via
separate mail threads.

Thanks,
Donald

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Thu Jan 20 22:43:12 2011
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 528DC3A68D4 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 20 Jan 2011 22:43:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.226
X-Spam-Level: 
X-Spam-Status: No, score=-5.226 tagged_above=-999 required=5 tests=[AWL=-2.627, 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 5W9TqvbE1nhH for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 20 Jan 2011 22:43:09 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 2AC3B3A68E0 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 20 Jan 2011 22:43:09 -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 p0L6O0Gk006839; Thu, 20 Jan 2011 22:24:02 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0L6Ngcq006826 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 20 Jan 2011 22:23:51 -0800 (PST)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAIq1OE2rR7Ht/2dsb2JhbACkY3OjFJsLhVAEhG+JW4Jz
Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-1.cisco.com with ESMTP; 21 Jan 2011 06:23:42 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id p0L6Ngka021948; Fri, 21 Jan 2011 06:23:42 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Thu, 20 Jan 2011 22:23:42 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 20 Jan 2011 22:23:41 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D20FC3E@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTikydKQiU6mYWeV88WQoBf0NNFE2sspk=+kn32po@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-adj-01.txt
Thread-Index: Acu5C5lF6G2slQJUTOG7IWJ59rVxfgAKBORg
References: <4D221B2B.2020207@acm.org> <AE36820147909644AD2A7CA014B1FB520D0DF509@xmb-sjc-222.amer.cisco.com> <AANLkTimETdWyO-_9=rzJtmv9M_MzrQb+7zZ=6V+e9OGh@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D0DFA2C@xmb-sjc-222.amer.cisco.com> <AANLkTimus5DuV+LvoBN83vd97g6TzNUTkFD_gFvj2rOn@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D17770B@xmb-sjc-222.amer.cisco.com> <AANLkTikydKQiU6mYWeV88WQoBf0NNFE2sspk=+kn32po@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>
X-OriginalArrivalTime: 21 Jan 2011 06:23:42.0455 (UTC) FILETIME=[BFEB9870:01CBB933]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0L6Ngcq006826
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] [Isis-wg] WG last call on draft-ietf-trill-adj-01.txt
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Donald -

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Thursday, January 20, 2011 5:36 PM
> To: Les Ginsberg (ginsberg)
> Cc: rbridge@postel.org; isis-wg@ietf.org
> Subject: Re: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-adj-
> 01.txt
> =

> Hi Les,
> =

> On Tue, Jan 18, 2011 at 7:49 PM, Les Ginsberg (ginsberg)
> <ginsberg@cisco.com> wrote:
> > Donald -
> >
> >> -----Original Message-----
> >> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> >> Sent: Tuesday, January 18, 2011 2:11 PM
> >> To: Les Ginsberg (ginsberg)
> >> Cc: rbridge@postel.org; isis-wg@ietf.org
> >> Subject: Re: [Isis-wg] [rbridge] WG last call on draft-ietf-trill-
> adj-
> >> 01.txt
> >>
> >> Hi Les,
> >>
> >> On Sat, Jan 15, 2011 at 5:45 PM, Les Ginsberg (ginsberg)
> >> <ginsberg@cisco.com> wrote:
> >> > Donald -
> ...
> >> >> 5. MTU Matching
> >> >>
> >> >> ...
> >> >>
> >> >> =A0 =A0An RBridge, RB1, determines the desired campus link MTU by
> >> >> =A0 =A0calculating the minimum of its originatingL1LSPBufferSize and
> the
> >> >> =A0 =A0originatingLSPBufferSize advertised in the link state databa=
se
> by
> >> >>
> >> >> LES: These should all be "originatingL1LSPBufferSize".
> >> >> (you have omitted "L1" in some cases)
> >> >>
> >> >> <DEE3> I believe the variable in the LSP is just
> >> >> originatingLSPBufferSize and is L1 or L2 depending on whether the
> >> LSP
> >> >> is L1 or L2.
> >> >
> >> > The TLV name is originatingLSPBufferSize(or LSPBufferSize in
> IANA).
> >> Per
> >> > ISO 10589 there are two variables which an implementation
> maintains:
> >> >
> >> > originatingL1LSPBufferSize
> >> > originatingL2LSPBufferSize
> >> > (they are often the same - but do not have to be as the set of
> >> circuits
> >> > in use at the two levels may be different)
> >> >
> >> > Whether L1 or L2 is in the TLV is determined by the type of PDU it
> is
> >> in
> >> > (Level1LSP or Level2LSP).
> >> >
> >> > There is no variable named originatingLSPBufferSize.
> >> > Since TRILL is limited to L1 only at present, you should be using
> >> > originatingL1LSPBufferSize everywhere.
> >>
> >> I note that RFC 3719, to which you referred me above, uses
> >> originatingL1LSPBufferSize in some contexts and
> >> originatingLSPBufferSize in others. Whether there is a "variable"
> >> named originatingLSPBufferSize depends on what you think a variable
> >> is. We seem to agree that there is a TLV field called
> >> originatingLSPBufferSize and the reference from the draft above to
> "in
> >> the link state database" was meant to refer to that field by its
> >> proper name.
> >
> > We agree that if referring to the type name of the TLV the correct
> name is originatingLSPBufferSize.
> > I think we also agree that what is advertised in the TLV (the value)
> is either originatingL1LSPBufferSize or originatingL2LSPBufferSize. In
> reviewing the draft I think all uses are actually referring to the
> value advertised - not the type name of the TLV - so that is why I
> suggest that all uses in the draft should be
> originatingL1LSPBufferSize.
> =

> I still think it is the field in the link state database that is being
> referred to and it should be called originatingLSPBufferSize. But I'm
> willing to change it to originatingL1LSPBufferSize with other changes
> that make if refer to the originating RBridge's variable. How about:
> =

> "An RBridge, RB1, determines the desired campus link MTU by
> calculating the minimum of its originatingL1LSPBufferSize and the
> originatingL1LSPBufferSize of other RBridges in the campus, as
> advertised in the link state database, but not less than 1,470 bytes."
> =


Works for me.
Thanx.

   Les

> >>
> >> > ...
> ...
> =

> >
> > =A0 Les
> =

> I glanced at your other comments and think they are best handled via
> separate mail threads.
> =

> Thanks,
> Donald

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Jan 24 09:21:20 2011
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 31F3A3A6906 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 24 Jan 2011 09:21:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.291
X-Spam-Level: 
X-Spam-Status: No, score=-102.291 tagged_above=-999 required=5 tests=[AWL=0.308, 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 aGFc-J76ftWB for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 24 Jan 2011 09:21:18 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 4B7623A687C for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 24 Jan 2011 09:21:18 -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 p0OH9iUe023111; Mon, 24 Jan 2011 09:09:45 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0OH982u023018 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Mon, 24 Jan 2011 09:09:19 -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>
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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

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>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Jan 24 12:57:46 2011
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 2CD5C3A696B for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 24 Jan 2011 12:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.36
X-Spam-Level: 
X-Spam-Status: No, score=-102.36 tagged_above=-999 required=5 tests=[AWL=0.239, 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 wX3bzbvUKkIg for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 24 Jan 2011 12:57:45 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 320633A693C for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 24 Jan 2011 12:57:45 -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 p0OKjrpN008419; Mon, 24 Jan 2011 12:45:54 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0OKjDeg008295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Mon, 24 Jan 2011 12:45:23 -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 p0OKftqF009445 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Jan 2011 15:41:55 -0500 (EST)
Message-ID: <4D3DE413.80908@workingcode.com>
Date: Mon, 24 Jan 2011 15:41:55 -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>
In-Reply-To: <4D3DCD97.7040005@gmail.com>
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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

William Allen Simpson wrote:
> I'm staring at the TRILL draft, and cannot find anything in the protocol
> to detect, eliminate, or resolve duplicate System ID numbers.  Obviously,
> I'm missing something.  Please advise.

I don't believe that anything can or will do that.  It's assumed into
existence, as far as I understand.

The System ID is used (among other things) for pseudonode generation and
TRILL nickname resolution.  If those aren't unique, then my
understanding is that the network will fly to bits.

I'm not the IS-IS expert here.  If someone else (preferably on the
RBridge mailing list) has an opinion about running a TRILL IS-IS network
where some of the nodes using only point-to-point links have System IDs
that are possibly non-unique, then now is the time to speak up.

But I certainly don't feel comfortable endorsing this sort of usage in
the PPP TRILL draft without review by at least the TRILL group, and
probably the IS-IS group as well.

> Thus, I got the routing religion....  Never use a bridge where a router
> could be used instead.

Indeed.  I agree completely, though I don't think it's really the
problem at hand.  If the user has PPP TRILL links, he's already decided
(for whatever reason) that he wants to bridge.

> Of course, this assumes that the PPP Magic Number has been implemented
> correctly, and it checks the number against all its interfaces to avoid
> loops.  It also assumes you haven't deployed Junipers with the fairly evil
> "ppp magic-number ignore-mismatch".

I see nothing in RFC 1661 section 6.4 requiring or even suggesting a
check across all of the node's interfaces.  Off hand, I don't know of
any that do that, and I do know of a few implementations where such a
test would be architecturally impractical (if not outright impossible).

In any event, I think this is a detour: the real issue is that the IS-IS
System ID must be unique across the IS-IS campus, and PPP's Magic-Number
option doesn't have that quality, even if it has the checks you're
suggesting.

With Ethernet, the assumption is that MAC addresses among systems that
speak IS-IS are unique per the standards.  Whether any vendor is able to
achieve that and/or whether relying on MAC uniqueness is a smart thing
to do is possibly an interesting topic, but I think is certainly one for
a different mailing list.  It doesn't involve PPP.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Jan 24 17:35:28 2011
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 8401D3A6B49 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 24 Jan 2011 17:35:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level: 
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, 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 MRtAer8ckxRX for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 24 Jan 2011 17:35:27 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 0193D3A699F for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 24 Jan 2011 17:35:26 -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 p0P1KRGG029047; Mon, 24 Jan 2011 17:20:28 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0P1K1hm029004 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Mon, 24 Jan 2011 17:20:11 -0800 (PST)
Received: from dhcp-226.workingcode.com (dhcp-226 [192.168.254.226]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id p0P1Gj8Y013388 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 24 Jan 2011 20:16:45 -0500 (EST)
Message-ID: <4D3E247D.9090201@workingcode.com>
Date: Mon, 24 Jan 2011 20:16:45 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
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>
In-Reply-To: <4D3E00B9.7050509@gmail.com>
X-Enigmail-Version: 1.1.1
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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

On 1/24/11 5:44 PM, William Allen Simpson wrote:
> On 1/24/11 3:41 PM, James Carlson wrote:
>> William Allen Simpson wrote:
>>> I'm staring at the TRILL draft, and cannot find anything in the protocol
>>> to detect, eliminate, or resolve duplicate System ID numbers. 
>>> Obviously,
>>> I'm missing something.  Please advise.
>>
>> I don't believe that anything can or will do that.  It's assumed into
>> existence, as far as I understand.
>>
>> The System ID is used (among other things) for pseudonode generation and
>> TRILL nickname resolution.  If those aren't unique, then my
>> understanding is that the network will fly to bits.
>>
> There is some text about resolving nicknames that aren't unique.  Nicknames
> aren't deterministic on the System ID, though.  They're small, so they have
> a 2*8 average chance of collision.  (Section 3.7)
> 
> I cannot find a description of pseudonode generation.  (Or even a
> definition for "pseudonode".)

It's part of RFC 1142.  I'm no IS-IS expert; it could possibly be just a
LAN-type feature.

The bottom line, though, is that I'm not willing to define a new mode of
operation for IS-IS on my own.  If there's some documentation of how
existing IS-IS systems with only point-to-point links operate without a
System ID, I'll be happy to provide a pointer to it along with an
appropriate synopsis to make it as clear as possible.

I am unable to locate any documentation of that sort.  If you have
pointers, please supply them, and I'll incorporate.

I wrote this draft as a favor to the RBridges chair to describe how the
protocol would work on some medium other than Ethernet.  The TRILL
protocol is designed so that it should be medium-agnostic (at least on
the transport side), but without an existence proof, it's hard to know,
and that's what this draft helps accomplish.

But I don't intend this draft as an extension or modification of IS-IS
in any way.  If extensions are required, then I think it would be best
to withdraw the draft and call it a day.  Someone else will have to
design whatever extensions you and the other reviewers feel are
necessary.  (I don't believe any such extensions are required, but if
that's the case, then I'm out.  I can't do that work.)

> OK, let's wait a bit.
> 
> The questions are:
> 
>  - How does TRILL handle System IDs that are not unique?

I do not know.  But I do know that RFC 1142 goes out of its way to say
that MAC addresses are unique, and that System IDs must also be unique.
 As far as I can tell, it's just assumed.

But this is *not* the IS-IS working group.  I think any questions about
how IS-IS does or does not work really ought to be directed to that
group.  I can't answer them in any reasonable way, and I'm pretty sure
that questions like that are just plain out of scope for this draft.

For that matter, this draft also doesn't address TRILL itself.  It only
addresses the operation of TRILL over PPP links.  If there are design
problems in TRILL itself -- if there needs to be some magic in TRILL
that checks for the "impossible" duplicate System IDs -- then I believe
that this is a generic issue with TRILL, and it should be addressed
outside the scope of the last call for this draft.

If there's a fix to the problem you're describing, then surely it's not
dependent on PPP for operation.  Right?

>  - Are System IDs ever used in the ethernet source or destination fields?

Not that I'm aware of.  They are used in the generation of LSPs as part
of IS-IS, though.

>> I see nothing in RFC 1661 section 6.4 requiring or even suggesting a
>> check across all of the node's interfaces.  Off hand, I don't know of
>> any that do that, and I do know of a few implementations where such a
>> test would be architecturally impractical (if not outright impossible).
>>
> The whole point is to avoid loops.  It is "a unique number".  You cannot
> avoid a loop with your *own* interfaces without checking against any
> existing interfaces to see whether your chosen number is unique....

It's to avoid looped-back interfaces.  That's exactly what the RFC says.
 Not "avoid loops."  The RFC goes to great length to describe when and
why an implementation must generate a new Magic Number value due to
conflict, and at no point does it describe comparisons against any value
except the two values used by the two peers on the link.

I agree that it'd be nice to have it do more, and that what you're
suggesting sounds reasonable.  However, it's certainly not what the RFC
says.

And worse still, even if the RFC were to describe the mechanism you're
suggesting, IT WOULD NOT HELP!  The requirement in IS-IS is for
network-wide uniqueness, and merely checking all of your own links --
but not those of all of the nodes in the network -- is insufficient to
meet that goal.  Nothing PPP does can help with that.

Thus, I believe this entire discussion about the operation of the LCP
Magic-Number option is without a point.

> Certainly, I'd never expect connecting serial port 1 to serial port 2
> on the same machine would ever pass the magic number test.
> 
> (Sometimes I wonder, how many more details must we write in specifications,
> when something this obvious is missed by some implementers?)

If you'd like to publish an update to RFC 1661 with this sort of
restriction, that sounds fine to me.  For what it's worth, though, I
can't say I know of any implementations that will pass this new stricter
test.

In particular, the common CMU/ANU/samba.org pppd implementation would
not pass.  It has no means of comparing Magic-Number option values
across links.  The control portion of each link runs in a completely
different address space -- different processes.  It'd require a database
similar to the one currently used for RFC 1990 E-Ds and MP in order to
implement it, and given the sorts of problems seen with that, it's not
what I'd call an improvement.

>> With Ethernet, the assumption is that MAC addresses among systems that
>> speak IS-IS are unique per the standards.  Whether any vendor is able to
>> achieve that and/or whether relying on MAC uniqueness is a smart thing
>> to do is possibly an interesting topic, but I think is certainly one for
>> a different mailing list.  It doesn't involve PPP.
>>
> I don't like assumptions.  That's a tautology.
> 
> If the proven existing MAC uniqueness in the field is already *less* than
> known mathematical uniqueness of the PPP Magic Number, then there's no
> PPP-specific issue to be solved.  In either case of conflict, then manual
> configuration is required.
> 
> The chance of PPP collision is *much* rarer.  Automatic PPP configuration
> should be part of this specification.

I still don't understand why this draft has to define this new special
usage.  We're talking about a corner case out of a corner case -- a
special TRILL-speaking system with PPP links but that has zero Ethernet
interfaces.  Who is going to build such a beast?  And why?

In the unlikely case that someone does build that thing, I'd be happy to
let that person define exactly how the required IS-IS System ID is
computed, formed, configured, guessed, or drawn carefully out of the
ether.  For the simple case of allowing a TRILL-speaking system that
already has its own means of deriving a System ID (whatever that may be)
to use PPP links between other cooperating systems, I believe the
existing text is sufficient.

To be clear: TRILL over PPP allows the packets to be exchanged in a
reasonable manner.  Unlike Ethernet, it does not come with a burned-in
"guaranteed globally unique" MAC address, and thus any existing text in
TRILL and/or IS-IS documents that assume the existence of such an
address on at least one link in the system -- such as section B.2.1.3 of
RFC 1142 -- will have to look elsewhere for that value.  PPP can't
supply it.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Jan 24 23:55:57 2011
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 C0CD13A6B19 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 24 Jan 2011 23:55:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.915
X-Spam-Level: 
X-Spam-Status: No, score=-102.915 tagged_above=-999 required=5 tests=[AWL=-0.316, 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 30tlyWOSgMu2 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 24 Jan 2011 23:55:56 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 96D2B3A6A84 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 24 Jan 2011 23:55:56 -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 p0P7aVbK027731; Mon, 24 Jan 2011 23:36:33 -0800 (PST)
Received: from mail-wy0-f180.google.com (mail-wy0-f180.google.com [74.125.82.180]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0P7ZpKu027369 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 24 Jan 2011 23:36:01 -0800 (PST)
Received: by wyb28 with SMTP id 28so5165224wyb.39 for <rbridge@postel.org>; Mon, 24 Jan 2011 23:35:51 -0800 (PST)
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=K9gWYrHFxZhkdGhcZDV0s2bRgSIgtWgIPZX0a2JjVm8=; b=byr6PBdGvtmaY5hXxA08sjRlH8tv+4DYWsMkNkgxB0Hv7g99ct30bPeZBSGXZDTQ2m i+mI1gbs4iQFA3qTmkCMD96hx8/s7Q3lL1SvJa6oeoZUth3LyFXt9H43y3ouv3Jk43E9 pQ+9H5eKVQ5A+wR0bsVX3ulJ1bDNpC4zcn0aY=
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=SUNc0e/djrrbmpGykI9C8apBgxyHhVPrMjv9S0QBeG4ORDFlqGLET8qtJUk02TL+t2 SPC1+g2RoGR5ukLwHHni+49Cp9EzEVZSrp36+VcnLg0qTUIgVNBfXOZx9EfmNOk2JEr5 UvKjBIkVPC3qBHbDfMyZGCLB8a3YmNeP3JUFM=
Received: by 10.227.155.140 with SMTP id s12mr5429907wbw.153.1295940950949; Mon, 24 Jan 2011 23:35:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Mon, 24 Jan 2011 23:35:30 -0800 (PST)
In-Reply-To: <4D3DCD97.7040005@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>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 25 Jan 2011 02:35:30 -0500
Message-ID: <AANLkTinH-EjsxxO5DkKWRnuKXP+iA9X=hKO79L03WGRz@mail.gmail.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0P7ZpKu027369
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi,

On Mon, Jan 24, 2011 at 2:05 PM, William Allen Simpson
<william.allen.simpson@gmail.com> wrote:
> On 1/24/11 1:29 PM, William Allen Simpson wrote:
>>
>> On 1/24/11 12:05 PM, James Carlson wrote:
>>>
>>> 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.
>>>
>> It must be nice to live in a world with unique MAC addresses! In my
>> experience, I've run into rather a lot of them that are not -- and it
>> will be much worse in this cross-linked multi-media environment. Many
>> vendors think that it's OK to reuse the MAC address for different link
>> speeds and types.
>>
> I'm staring at the TRILL draft, and cannot find anything in the protocol
> to detect, eliminate, or resolve duplicate System ID numbers. =A0Obviousl=
y,
> I'm missing something. =A0Please advise.

You are looking in the wrong place. The unique System ID requirement
is an IS-IS requirement.

It is my impression that manufacturers of ISIS routers either allocate
a MAC address under their OUI to use as System ID or use the MAC
address of one of their interfaces. Maybe, in this instance, they are
more careful to not duplicate from some other box they built. But it
doesn't matter what they do. It's an IS-IS requirement and their
problem.

Maybe the draft should just say less about this.

Donald

PS: Current traveling so I'm a bit out of phase...

>> The only way that the Magic Number has any significant chance to ever be
>> non-unique would be a very large number of PPP-only bridges in the
>> network,
>> on the order of 2**16. Probably best to stick an IP router in there....
>>
> To elaborate, I've an old story to tell. =A0Once upon a time, Michigan St=
ate
> University supposedly had the world's largest bridged ethernet, covering
> many square miles. =A0Performance was abysmal. =A0But once I stuck a 286 =
box
> with KA9Q net (this was circa 1985) between the computing center and
> engineering, performance miraculously improved!
>
> (The problem turned out to be fragments inserted by the IBM in the
> administration building next door to the computing center.)
>
> Thus, I got the routing religion.... =A0Never use a bridge where a router
> could be used instead.
>
> I really doubt we'll ever see more than one or two PPP-only Rbridges in a
> single installation. =A0The point being that PPP is vastly more robust th=
an
> ethernet -- and you shouldn't let the good enough (ethernet) be the enemy
> of the better (PPP).
>
>> If the PPP-only bridges are talking to each other, there will *never* be
>> any non-unique numbers. That's the more likely case of centrally
>> located PPP-only bridges.
>>
> Of course, this assumes that the PPP Magic Number has been implemented
> correctly, and it checks the number against all its interfaces to avoid
> loops. =A0It also assumes you haven't deployed Junipers with the fairly e=
vil
> "ppp magic-number ignore-mismatch".

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 25 00:13:26 2011
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 395043A6B7B for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 00:13:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.911
X-Spam-Level: 
X-Spam-Status: No, score=-102.911 tagged_above=-999 required=5 tests=[AWL=-0.312, 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 P2eJC2H4IOA7 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 00:13:24 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id BF7B63A6964 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 25 Jan 2011 00:13:24 -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 p0P7x5ht001182; Mon, 24 Jan 2011 23:59:07 -0800 (PST)
Received: from mail-wy0-f180.google.com (mail-wy0-f180.google.com [74.125.82.180]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0P7wLJG001088 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 24 Jan 2011 23:58:31 -0800 (PST)
Received: by wyb28 with SMTP id 28so5188024wyb.39 for <rbridge@postel.org>; Mon, 24 Jan 2011 23:58:20 -0800 (PST)
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=5ZuqLnJuQh0rCHBlVfV+GoLYTrYlRHKIfcDB5tJn1RI=; b=GxDqHPNNra3FaU2thM2SWKxGVuQL4ekXalnoXHmt60vMw3UU6oKJfXSkJdWuYwpmyE dgBoJZ4ll6Azv6it/7zaHtUwDFO+AsZOXe70AnNIf0QVdGdzxiZYpw1rO5ytz4Oh29+t UQYxtOya9BvnKTRu7pWqmQMU/85HCDddVQU6I=
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=JonNUI39ycaDJZbYfwRlSCeA3FZ6wCYQ5GHXm+/XfpJ9jOEhvC9rRfNNbo9fKbhsnR J69Bn37bOB0+PDCnb3UpyoYyp0BeqLUpkuorDyVkWiLCR2tOouOV7tPaVns/EpCgKzZu F6PPFiDuzsCKsiDiNVEyz1Zk06ASvoTx7VUik=
Received: by 10.227.147.133 with SMTP id l5mr5605688wbv.37.1295942300569; Mon, 24 Jan 2011 23:58:20 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Mon, 24 Jan 2011 23:58:00 -0800 (PST)
In-Reply-To: <4D3E00B9.7050509@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>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 25 Jan 2011 02:58:00 -0500
Message-ID: <AANLkTinqbPiGKRYsy4YwQA65-1eszKd4Xv5QPEGAUeRs@mail.gmail.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0P7wLJG001088
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi,

On Mon, Jan 24, 2011 at 5:44 PM, William Allen Simpson
<william.allen.simpson@gmail.com> wrote:
> On 1/24/11 3:41 PM, James Carlson wrote:
>>
>> William Allen Simpson wrote:
>>>
>>> I'm staring at the TRILL draft, and cannot find anything in the protocol
>>> to detect, eliminate, or resolve duplicate System ID numbers. =A0Obviou=
sly,
>>> I'm missing something. =A0Please advise.
>>
>> I don't believe that anything can or will do that. =A0It's assumed into
>> existence, as far as I understand.
>>
>> The System ID is used (among other things) for pseudonode generation and
>> TRILL nickname resolution. =A0If those aren't unique, then my
>> understanding is that the network will fly to bits.
>>
> There is some text about resolving nicknames that aren't unique. =A0Nickn=
ames
> aren't deterministic on the System ID, though. =A0They're small, so they =
have
> a 2*8 average chance of collision. =A0(Section 3.7)

Nickname resolution is dynamic so collisions get resolved.

> I cannot find a description of pseudonode generation. =A0(Or even a
> definition for "pseudonode".)

That's because all of that is part of IS-IS. You need to start with
ISO 10589, the 2002 edition.

>> I'm not the IS-IS expert here. =A0If someone else (preferably on the
>> RBridge mailing list) has an opinion about running a TRILL IS-IS network
>> where some of the nodes using only point-to-point links have System IDs
>> that are possibly non-unique, then now is the time to speak up.
>>
>> But I certainly don't feel comfortable endorsing this sort of usage in
>> the PPP TRILL draft without review by at least the TRILL group, and
>> probably the IS-IS group as well.
>>
> OK, let's wait a bit.
>
> The questions are:
>
> =A0- How does TRILL handle System IDs that are not unique?

System IDs are used to uniquely identify IS-IS router in the link
state database. There is no TRILL specific stuff related to non-unique
System IDs. It's all IS-IS.

> =A0- Are System IDs ever used in the ethernet source or destination field=
s?

There is no requirement to ever to that. Since they are the same size
you can. As far as I know (which isn't that much), most manufacturers
of IS-IS switches either allocate an MAC address they control to use
as the System ID for a box or, a bit more commonly, use the MAC
address of one of the boxes interface, such as the numerically lowest
interface MAC address.

There is no requirement for the MAC interfaces of RBridges in a campus
to all have unique addresses as long as all the RBridges connected to
a particular link have unique MAC addresses over that link. But the
System IDs must be unique across the campus as per IS-IS subnet
independent functions requirement.

>> I see nothing in RFC 1661 section 6.4 requiring or even suggesting a
>> check across all of the node's interfaces. =A0Off hand, I don't know of
>> any that do that, and I do know of a few implementations where such a
>> test would be architecturally impractical (if not outright impossible).
>>
> The whole point is to avoid loops. =A0It is "a unique number". =A0You can=
not
> avoid a loop with your *own* interfaces without checking against any
> existing interfaces to see whether your chosen number is unique....
>
> Certainly, I'd never expect connecting serial port 1 to serial port 2
> on the same machine would ever pass the magic number test.
>
> (Sometimes I wonder, how many more details must we write in specification=
s,
> when something this obvious is missed by some implementers?)
>
>
>> With Ethernet, the assumption is that MAC addresses among systems that
>> speak IS-IS are unique per the standards. =A0Whether any vendor is able =
to
>> achieve that and/or whether relying on MAC uniqueness is a smart thing
>> to do is possibly an interesting topic, but I think is certainly one for
>> a different mailing list. =A0It doesn't involve PPP.
>>
> I don't like assumptions. =A0That's a tautology.
>
> If the proven existing MAC uniqueness in the field is already *less* than
> known mathematical uniqueness of the PPP Magic Number, then there's no
> PPP-specific issue to be solved. =A0In either case of conflict, then manu=
al
> configuration is required.

See above. MAC address uniqueness isn't the same as System ID
uniqueness although in practice they might be conflated sometimes.

Donald

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 25 10:24:05 2011
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 7C7B03A6816 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 10:24:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.877
X-Spam-Level: 
X-Spam-Status: No, score=-102.877 tagged_above=-999 required=5 tests=[AWL=-0.278, 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 5F4jJWPjdtmJ for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 10:24:04 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 0DF473A6811 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 25 Jan 2011 10:24:03 -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 p0PI9qV8021769; Tue, 25 Jan 2011 10:09:55 -0800 (PST)
Received: from mail-qw0-f52.google.com (mail-qw0-f52.google.com [209.85.216.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0PI9BTk021569 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Tue, 25 Jan 2011 10:09:20 -0800 (PST)
Received: by qwi4 with SMTP id 4so38764qwi.39 for <rbridge@postel.org>; Tue, 25 Jan 2011 10:09:11 -0800 (PST)
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=8N2YLVxCZVIjUsj4FFExYIg2CdkYUEhFHx9Kw/hkjz0=; b=a+XVick+Wp5qmi29JJRNN5YE6juzmoEqcNG+Uru0Fx5dCSLAfNZqVkijNeV661FK5d hFXKI+HMyszn/dOKSfQORqCLF4felEV7yNeEbkt4UqbFu1XpNYZFEplhEkl1ogyeH+HH xsOyuhHa/jZfLHqHYB0fpoI5teeZzSSYlxP2c=
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=JSpDAi17WKgYxfepWJFWO4395u/TfFlmvBgGDw8LthyCSllhEaR6+QR7tg+ebzNpE1 5nzizuTFNAMDNrlz+8opELE6vHn9e7rzjGhqzTuK4mh6LiZj5xYvJBh3hSlrNGIGeWSz Hn9mZE2cXr7MiE7FL0IlRKgbRECuLGHhaqLgI=
Received: by 10.224.19.146 with SMTP id a18mr5568219qab.224.1295978950889; Tue, 25 Jan 2011 10:09:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.220.64.169 with HTTP; Tue, 25 Jan 2011 10:08:50 -0800 (PST)
In-Reply-To: <4D3E247D.9090201@workingcode.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>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 25 Jan 2011 13:08:50 -0500
Message-ID: <AANLkTi=+K-Kzsc+kahrmBoj1oC0WBzj7DYquS5ySCpP6@mail.gmail.com>
To: James Carlson <carlsonj@workingcode.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0PI9BTk021569
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi James,

I think your position below is reasonable. The System ID of an IS-IS
router is certainly not required to be any sort of MAC address, it
just has to be a 48-bit quantity unique among the IS-IS routers whose
link state entries need to be distinguished.

Perhaps Section 3, point 3, should be reworded to something like: "In
the case of an RBridge with only PPP links, the practice of using the
MAC address of an interface for the IS-IS System ID will not be
available. The implementor will have to use other means, such as
deriving a System ID from a MAC address allocated to the device as a
whole, to assure that it has a campus-wide unique System ID."

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

On Mon, Jan 24, 2011 at 8:16 PM, James Carlson <carlsonj@workingcode.com> w=
rote:
> On 1/24/11 5:44 PM, William Allen Simpson wrote:
>> On 1/24/11 3:41 PM, James Carlson wrote:
>>> William Allen Simpson wrote:
>>>> I'm staring at the TRILL draft, and cannot find anything in the protoc=
ol
>>>> to detect, eliminate, or resolve duplicate System ID numbers.
>>>> Obviously,
>>>> I'm missing something. =A0Please advise.
>>>
>>> I don't believe that anything can or will do that. =A0It's assumed into
>>> existence, as far as I understand.
>>>
>>> The System ID is used (among other things) for pseudonode generation and
>>> TRILL nickname resolution. =A0If those aren't unique, then my
>>> understanding is that the network will fly to bits.
>>>
>> There is some text about resolving nicknames that aren't unique. =A0Nick=
names
>> aren't deterministic on the System ID, though. =A0They're small, so they=
 have
>> a 2*8 average chance of collision. =A0(Section 3.7)
>>
>> I cannot find a description of pseudonode generation. =A0(Or even a
>> definition for "pseudonode".)
>
> It's part of RFC 1142. =A0I'm no IS-IS expert; it could possibly be just a
> LAN-type feature.
>
> The bottom line, though, is that I'm not willing to define a new mode of
> operation for IS-IS on my own. =A0If there's some documentation of how
> existing IS-IS systems with only point-to-point links operate without a
> System ID, I'll be happy to provide a pointer to it along with an
> appropriate synopsis to make it as clear as possible.
>
> I am unable to locate any documentation of that sort. =A0If you have
> pointers, please supply them, and I'll incorporate.
>
> I wrote this draft as a favor to the RBridges chair to describe how the
> protocol would work on some medium other than Ethernet. =A0The TRILL
> protocol is designed so that it should be medium-agnostic (at least on
> the transport side), but without an existence proof, it's hard to know,
> and that's what this draft helps accomplish.
>
> But I don't intend this draft as an extension or modification of IS-IS
> in any way. =A0If extensions are required, then I think it would be best
> to withdraw the draft and call it a day. =A0Someone else will have to
> design whatever extensions you and the other reviewers feel are
> necessary. =A0(I don't believe any such extensions are required, but if
> that's the case, then I'm out. =A0I can't do that work.)
>
>> OK, let's wait a bit.
>>
>> The questions are:
>>
>> =A0- How does TRILL handle System IDs that are not unique?
>
> I do not know. =A0But I do know that RFC 1142 goes out of its way to say
> that MAC addresses are unique, and that System IDs must also be unique.
> =A0As far as I can tell, it's just assumed.
>
> But this is *not* the IS-IS working group. =A0I think any questions about
> how IS-IS does or does not work really ought to be directed to that
> group. =A0I can't answer them in any reasonable way, and I'm pretty sure
> that questions like that are just plain out of scope for this draft.
>
> For that matter, this draft also doesn't address TRILL itself. =A0It only
> addresses the operation of TRILL over PPP links. =A0If there are design
> problems in TRILL itself -- if there needs to be some magic in TRILL
> that checks for the "impossible" duplicate System IDs -- then I believe
> that this is a generic issue with TRILL, and it should be addressed
> outside the scope of the last call for this draft.
>
> If there's a fix to the problem you're describing, then surely it's not
> dependent on PPP for operation. =A0Right?
>
>> =A0- Are System IDs ever used in the ethernet source or destination fiel=
ds?
>
> Not that I'm aware of. =A0They are used in the generation of LSPs as part
> of IS-IS, though.
>
>>> I see nothing in RFC 1661 section 6.4 requiring or even suggesting a
>>> check across all of the node's interfaces. =A0Off hand, I don't know of
>>> any that do that, and I do know of a few implementations where such a
>>> test would be architecturally impractical (if not outright impossible).
>>>
>> The whole point is to avoid loops. =A0It is "a unique number". =A0You ca=
nnot
>> avoid a loop with your *own* interfaces without checking against any
>> existing interfaces to see whether your chosen number is unique....
>
> It's to avoid looped-back interfaces. =A0That's exactly what the RFC says.
> =A0Not "avoid loops." =A0The RFC goes to great length to describe when and
> why an implementation must generate a new Magic Number value due to
> conflict, and at no point does it describe comparisons against any value
> except the two values used by the two peers on the link.
>
> I agree that it'd be nice to have it do more, and that what you're
> suggesting sounds reasonable. =A0However, it's certainly not what the RFC
> says.
>
> And worse still, even if the RFC were to describe the mechanism you're
> suggesting, IT WOULD NOT HELP! =A0The requirement in IS-IS is for
> network-wide uniqueness, and merely checking all of your own links --
> but not those of all of the nodes in the network -- is insufficient to
> meet that goal. =A0Nothing PPP does can help with that.
>
> Thus, I believe this entire discussion about the operation of the LCP
> Magic-Number option is without a point.
>
>> Certainly, I'd never expect connecting serial port 1 to serial port 2
>> on the same machine would ever pass the magic number test.
>>
>> (Sometimes I wonder, how many more details must we write in specificatio=
ns,
>> when something this obvious is missed by some implementers?)
>
> If you'd like to publish an update to RFC 1661 with this sort of
> restriction, that sounds fine to me. =A0For what it's worth, though, I
> can't say I know of any implementations that will pass this new stricter
> test.
>
> In particular, the common CMU/ANU/samba.org pppd implementation would
> not pass. =A0It has no means of comparing Magic-Number option values
> across links. =A0The control portion of each link runs in a completely
> different address space -- different processes. =A0It'd require a database
> similar to the one currently used for RFC 1990 E-Ds and MP in order to
> implement it, and given the sorts of problems seen with that, it's not
> what I'd call an improvement.
>
>>> With Ethernet, the assumption is that MAC addresses among systems that
>>> speak IS-IS are unique per the standards. =A0Whether any vendor is able=
 to
>>> achieve that and/or whether relying on MAC uniqueness is a smart thing
>>> to do is possibly an interesting topic, but I think is certainly one for
>>> a different mailing list. =A0It doesn't involve PPP.
>>>
>> I don't like assumptions. =A0That's a tautology.
>>
>> If the proven existing MAC uniqueness in the field is already *less* than
>> known mathematical uniqueness of the PPP Magic Number, then there's no
>> PPP-specific issue to be solved. =A0In either case of conflict, then man=
ual
>> configuration is required.
>>
>> The chance of PPP collision is *much* rarer. =A0Automatic PPP configurat=
ion
>> should be part of this specification.
>
> I still don't understand why this draft has to define this new special
> usage. =A0We're talking about a corner case out of a corner case -- a
> special TRILL-speaking system with PPP links but that has zero Ethernet
> interfaces. =A0Who is going to build such a beast? =A0And why?
>
> In the unlikely case that someone does build that thing, I'd be happy to
> let that person define exactly how the required IS-IS System ID is
> computed, formed, configured, guessed, or drawn carefully out of the
> ether. =A0For the simple case of allowing a TRILL-speaking system that
> already has its own means of deriving a System ID (whatever that may be)
> to use PPP links between other cooperating systems, I believe the
> existing text is sufficient.
>
> To be clear: TRILL over PPP allows the packets to be exchanged in a
> reasonable manner. =A0Unlike Ethernet, it does not come with a burned-in
> "guaranteed globally unique" MAC address, and thus any existing text in
> TRILL and/or IS-IS documents that assume the existence of such an
> address on at least one link in the system -- such as section B.2.1.3 of
> RFC 1142 -- will have to look elsewhere for that value. =A0PPP can't
> supply it.
>
> --
> James Carlson =A0 =A0 =A0 =A0 42.703N 71.076W =A0 =A0 =A0 =A0 <carlsonj@w=
orkingcode.com>
> _______________________________________________
> Pppext mailing list
> Pppext@ietf.org
> https://www.ietf.org/mailman/listinfo/pppext
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 25 10:26:34 2011
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 E3CCB3A685B for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 10:26:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.403
X-Spam-Level: 
X-Spam-Status: No, score=-102.403 tagged_above=-999 required=5 tests=[AWL=0.196, 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 uJs+KZjxG+xR for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 10:26:34 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 2E63F3A6853 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 25 Jan 2011 10:26:34 -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 p0PILILl024305; Tue, 25 Jan 2011 10:21:19 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0PIKeNe023892 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Tue, 25 Jan 2011 10:20:51 -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 p0PIHNLZ028022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Jan 2011 13:17:23 -0500 (EST)
Message-ID: <4D3F13B3.9070706@workingcode.com>
Date: Tue, 25 Jan 2011 13:17:23 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@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>
In-Reply-To: <AANLkTi=+K-Kzsc+kahrmBoj1oC0WBzj7DYquS5ySCpP6@mail.gmail.com>
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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 wrote:
> Hi James,
> 
> I think your position below is reasonable. The System ID of an IS-IS
> router is certainly not required to be any sort of MAC address, it
> just has to be a 48-bit quantity unique among the IS-IS routers whose
> link state entries need to be distinguished.
> 
> Perhaps Section 3, point 3, should be reworded to something like: "In
> the case of an RBridge with only PPP links, the practice of using the
> MAC address of an interface for the IS-IS System ID will not be
> available. The implementor will have to use other means, such as
> deriving a System ID from a MAC address allocated to the device as a
> whole, to assure that it has a campus-wide unique System ID."

That seems quite reasonable to me.  I just want to steer clear of
writing too much of the IS-IS requirements into this draft, as I think
the overall system design implications are out of scope.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 25 10:44:45 2011
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 7EBB53A6825 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 10:44:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.718
X-Spam-Level: 
X-Spam-Status: No, score=-2.718 tagged_above=-999 required=5 tests=[AWL=-0.119, 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 f5chO3aPLT8V for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 10:44:44 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 7C6E33A681D for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 25 Jan 2011 10:44:44 -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 p0PIWUSl026627; Tue, 25 Jan 2011 10:32:32 -0800 (PST)
Received: from mail-ey0-f180.google.com (mail-ey0-f180.google.com [209.85.215.180]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0PIVuG5026526 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Tue, 25 Jan 2011 10:32:06 -0800 (PST)
Received: by eyf18 with SMTP id 18so67071eyf.39 for <rbridge@postel.org>; Tue, 25 Jan 2011 10:31:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=uVem6QhsraVcmvGWmQxQ6HEqmXymVIGiAsqdxjd106w=; b=IEmBlVTbCbak5JnOQ1S8bZWe/1qYOlx0dnlFH1fbZ0138qRg3Ux4yoRrcEQMdHcc9g 8Qqkvma5hkLX8+vudQ9R1VFRm9D3AgQb/lLIKXeb+VFLIIKjk3nA2LNOV1hcd1ESlV5G PR8+NUDqUPbpP3lR0a5GSR8KNLg7fkadTu2SI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=pEiOojrj0KtDpxSiekKq2zwOkGYs5BiPpN7Fug8t5VDbH8+7s8EeLTxCyckLYnPXXY mq8gm7JMU3mn/R/Wo6Y57XZDqT1/KCs3+lRhVTm/QwEITfBBjFm1IMCBxF2i2wdNjS3P 9y8wVgnzCjFdoUC6dWkOMdogk9qTm1n9g/kq0=
MIME-Version: 1.0
Received: by 10.216.182.212 with SMTP id o62mr4050418wem.52.1295980316014; Tue, 25 Jan 2011 10:31:56 -0800 (PST)
Received: by 10.216.21.65 with HTTP; Tue, 25 Jan 2011 10:31:55 -0800 (PST)
In-Reply-To: <4D3F13B3.9070706@workingcode.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>
Date: Tue, 25 Jan 2011 10:31:55 -0800
Message-ID: <AANLkTikJjMcc1es7qyabddcXBFS93sRwcRO7XvPQzbe2@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: James Carlson <carlsonj@workingcode.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: vishwas.ietf@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0PIVuG5026526
Cc: Donald Eastlake <d3e3e3@gmail.com>, pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi James,

IMHO there should be no mention of IS-IS in the PPP draft. As IS-IS is
a control plane protocol (we could as well use static Rbridge route
entries - a requirement we have heard from 2 of our customers) and PPP
is the data plane.

Thanks,
Vishwas

On Tue, Jan 25, 2011 at 10:17 AM, James Carlson
<carlsonj@workingcode.com> wrote:
> Donald Eastlake wrote:
>> Hi James,
>>
>> I think your position below is reasonable. The System ID of an IS-IS
>> router is certainly not required to be any sort of MAC address, it
>> just has to be a 48-bit quantity unique among the IS-IS routers whose
>> link state entries need to be distinguished.
>>
>> Perhaps Section 3, point 3, should be reworded to something like: "In
>> the case of an RBridge with only PPP links, the practice of using the
>> MAC address of an interface for the IS-IS System ID will not be
>> available. The implementor will have to use other means, such as
>> deriving a System ID from a MAC address allocated to the device as a
>> whole, to assure that it has a campus-wide unique System ID."
>
> That seems quite reasonable to me. =A0I just want to steer clear of
> writing too much of the IS-IS requirements into this draft, as I think
> the overall system design implications are out of scope.
>
> --
> James Carlson =A0 =A0 =A0 =A0 42.703N 71.076W =A0 =A0 =A0 =A0 <carlsonj@w=
orkingcode.com>
> _______________________________________________
> rbridge mailing list
> rbridge@postel.org
> http://mailman.postel.org/mailman/listinfo/rbridge
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Tue Jan 25 11:24:10 2011
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 72E6A3A6852 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 11:24:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.433
X-Spam-Level: 
X-Spam-Status: No, score=-102.433 tagged_above=-999 required=5 tests=[AWL=0.166, 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 VgAc1isIW81U for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 25 Jan 2011 11:24:09 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 6998E3A6838 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 25 Jan 2011 11:24:09 -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 p0PJ86rt004485; Tue, 25 Jan 2011 11:08:07 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0PJ7YwP004351 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Tue, 25 Jan 2011 11:07:44 -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 p0PJ4Dqp028765 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Jan 2011 14:04:13 -0500 (EST)
Message-ID: <4D3F1EAD.5040901@workingcode.com>
Date: Tue, 25 Jan 2011 14:04:13 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: Vishwas Manral <vishwas.ietf@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>
In-Reply-To: <AANLkTikJjMcc1es7qyabddcXBFS93sRwcRO7XvPQzbe2@mail.gmail.com>
X-DCC-SIHOPE-DCC-3-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: Donald Eastlake <d3e3e3@gmail.com>, pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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

Vishwas Manral wrote:
> Hi James,
> 
> IMHO there should be no mention of IS-IS in the PPP draft. As IS-IS is
> a control plane protocol (we could as well use static Rbridge route
> entries - a requirement we have heard from 2 of our customers) and PPP
> is the data plane.

I assume you're talking about the discussion of the System ID issue, and
not the TLSP Packet Format described in section 2.3 for carrying IS-IS
packets.  (If you *do* mean TLSP, then I'll probably need some
additional clarification.)

I certainly agree with the sentiment (I don't like duplicating
documentation at all, particularly for this issue), but the existing
notation about MAC addresses (and the lack of them on PPP) was added at
the behest of other reviewers who found that it was confusing to match
up the PPP TRILL draft with the primary TRILL documentation without some
indication that there are differences here.

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.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Wed Jan 26 08:33:22 2011
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 437213A67AD for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 08:33:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 DWG1B4RlwnrD for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 08:33:21 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 3D92B3A67A4 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 08:33:21 -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 p0QGONfo004648; Wed, 26 Jan 2011 08:24:23 -0800 (PST)
Received: from mta41.charter.net (mta41.charter.net [216.33.127.83]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QGNgbS004502 for <rbridge@postel.org>; Wed, 26 Jan 2011 08:23:51 -0800 (PST)
Received: from imp11 ([10.20.200.11]) by mta41.charter.net (InterMail vM.7.09.02.04 201-2219-117-106-20090629) with ESMTP id <20110126162341.UFCZ2629.mta41.charter.net@imp11>; Wed, 26 Jan 2011 11:23:41 -0500
Received: from mp08 ([209.225.8.238]) by imp11 with smtp.charter.net id 0GPh1g00C588i5505GPh1w; Wed, 26 Jan 2011 11:23:41 -0500
X-Authority-Analysis: v=1.0 c=1 a=Ft6M8Dj6ea0A:10 a=IkcTkHD0fZMA:10 a=pGLkceISAAAA:8 a=0Qg8RWfqAAAA:8 a=ghOt4u8qtLLk1_9QLkMA:9 a=g47ehZuccRhdsbC51X1VmQ4pDaoA:4 a=QEXdDO2ut3YA:10 a=MSl-tDqOz04A:10 a=NeaMLyczsAwA:10
Message-ID: <20110126112341.AA6XN.11297223.root@mp08>
Date: Wed, 26 Jan 2011 11:23:41 -0500
From: Anil Rijhsinghani <anil@charter.net>
To: Donald Eastlake <d3e3e3@gmail.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
Sensitivity: Normal
X-Originating-IP: from 151.104.126.59 by ssomail.charter.net; Wed, 26 Jan 2011 11:23:41 -0500
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: anil@charter.net
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0QGNgbS004502
Cc: rbridge@postel.org
Subject: Re: [rbridge] Request for review of draft-ietf-trill-rbridge-mib-01.txt
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="utf-8"
Content-Transfer-Encoding: base64
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

SGkgRG9uYWxkLAoKPiBJIHRoaW5rIHRoYXQgU3osIHRoZSBjYW1wdXMgd2lkZSBtaW5pbXVtIE1U
VSB0aGF0IGFuIFJCcmlkZ2UgaGFzCj4gY2FsY3VsYXRlZCwgc2hvdWxkIGJlIGEgcmVhZC1vbmx5
IHBlci1SQnJpZGdlIE1JQiBvYmplY3QgYW5kIHRoYXQgaXQKPiBzaG91bGQgYmUgcG9zc2libGUg
Zm9yIGEgY2hhbmdlIGluIFN6IHRvIGNhdXNlIGEgbm90aWZpY2F0aW9uLgoKSeKAmWxsIGFkZCBT
eiBhcyBhIHJlYWQtb25seSBvYmplY3QgdG8gdGhlIFRSSUxMIGdyb3VwLCBuZXh0IHRvIE1pbk10
dURlc2lyZWQgd2hpY2gKaXMgYSByZWFkLXdyaXRlIG9iamVjdC4KCkkgd291bGQgc3VnZ2VzdCB3
ZSBub3QgbWFrZSBhIGNoYW5naW5nIHZhbHVlIG9mIHRoaXMgYSBub3RpZmljYXRpb24sIGFzIGl0
IGNvdWxkCmxlYWQgdG8gdGhlIHRyYXAgc2luayBiZWluZyBmbG9vZGVkIHNpbXVsdGFuZW91c2x5
IHdpdGggYSBsYXJnZSBudW1iZXIgb2YKbm90aWZpY2F0aW9ucy4gVGhpcyBpcyBhbiBvYmplY3Qg
dGhhdCBhbiBOTVMgd2lsbCB3YW50IHRvIG1vbml0b3Igb3IgcG9sbCB3aGVuCm5lY2Vzc2FyeS4K
ClJlZ2FyZHMsCkFuaWwKCkZyb206IERvbmFsZCBFYXN0bGFrZSA8ZDNlM2UzQGdtYWlsLmNvbT4K
RGF0ZTogRGVjZW1iZXIgMjcsIDIwMTAgMTA6MjY6MTIgUE0gRVNUClRvOiAiRGV2ZWxvcGluZyBh
IGh5YnJpZCByb3V0ZXIvYnJpZGdlLiIgPHJicmlkZ2VAcG9zdGVsLm9yZz4KU3ViamVjdDogUmU6
IFtyYnJpZGdlXSBSZXF1ZXN0IGZvciByZXZpZXcgb2YgZHJhZnQtaWV0Zi10cmlsbC1yYnJpZGdl
LW1pYi0wMS50eHQKCkhpLAoKSXQgd291bGQgYmUgaGVscGZ1bCBpZiBwZW9wbGUgd291bGQgcmV2
aWV3IHRoZSBNSUIgZG9jdW1lbnQuIEhlcmUgaXMgYQpjb21tZW50IG9mIG1pbmU6CgpJIHRoaW5r
IHRoYXQgU3osIHRoZSBjYW1wdXMgd2lkZSBtaW5pbXVtIE1UVSB0aGF0IGFuIFJCcmlkZ2UgaGFz
CmNhbGN1bGF0ZWQsIHNob3VsZCBiZSBhIHJlYWQtb25seSBwZXItUkJyaWRnZSBNSUIgb2JqZWN0
IGFuZCB0aGF0IGl0CnNob3VsZCBiZSBwb3NzaWJsZSBmb3IgYSBjaGFuZ2UgaW4gU3ogdG8gY2F1
c2UgYSBub3RpZmljYXRpb24uCgpUaGFua3MsCkRvbmFsZAoKCl9fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fCnJicmlkZ2UgbWFpbGluZyBsaXN0CnJicmlkZ2VA
cG9zdGVsLm9yZwpodHRwOi8vbWFpbG1hbi5wb3N0ZWwub3JnL21haWxtYW4vbGlzdGluZm8vcmJy
aWRnZQo=

From rbridge-bounces@postel.org  Wed Jan 26 09:05:54 2011
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 C93953A6804 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 09:05:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 WLgk7ZoGMeHd for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 09:05:53 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 995763A67DF for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 09:05:53 -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 p0QGhSNk008518; Wed, 26 Jan 2011 08:43:30 -0800 (PST)
Received: from mta41.charter.net (mta41.charter.net [216.33.127.83]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QGgqRQ008452 for <rbridge@postel.org>; Wed, 26 Jan 2011 08:43:01 -0800 (PST)
Received: from imp11 ([10.20.200.11]) by mta41.charter.net (InterMail vM.7.09.02.04 201-2219-117-106-20090629) with ESMTP id <20110126164252.UTSW2629.mta41.charter.net@imp11>; Wed, 26 Jan 2011 11:42:52 -0500
Received: from mp08 ([209.225.8.238]) by imp11 with smtp.charter.net id 0Gis1g00H588i5505GisBF; Wed, 26 Jan 2011 11:42:52 -0500
X-Authority-Analysis: v=1.0 c=1 a=sEZnAFdKAG4A:10 a=IkcTkHD0fZMA:10 a=gEsRDbIwAAAA:8 a=pGLkceISAAAA:8 a=0Qg8RWfqAAAA:8 a=z6-SGSSWrNClYuCOb40A:9 a=q_l6Veph5bCpBBFf5fFeAmBuLH0A:4 a=QEXdDO2ut3YA:10 a=4dyfk4FV-b8A:10 a=MSl-tDqOz04A:10 a=NeaMLyczsAwA:10 a=BdN0azpYFKSc08pT:21 a=jZh3-7zSP4Hu0dHw:21
Message-ID: <20110126114252.N5ZK9.11297420.root@mp08>
Date: Wed, 26 Jan 2011 11:42:52 -0500
From: Anil Rijhsinghani <anil@charter.net>
To: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
Sensitivity: Normal
X-Originating-IP: from 151.104.126.59 by ssomail.charter.net; Wed, 26 Jan 2011 11:42:51 -0500
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: anil@charter.net
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0QGgqRQ008452
Cc: rbridge@postel.org
Subject: Re: [rbridge] Request for review ofdraft-ietf-trill-rbridge-mib-01.txt
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="utf-8"
Content-Transfer-Encoding: base64
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

SGkgRGFuLAoKPiAxLiBUaGUgcmVsYXRpb25zaGlwIHdpdGggb3RoZXIgTUlCIG1vZHVsZSBzZWN0
aW9ucyByZWZlciB0byB0aGUgSUVURiBSRkNzLgo+IEhvd2V2ZXIsIHNpbmNlIDIwMDYgdGhlIGRl
dmVsb3BtZW50IG9mIHRoZSBCcmlkZ2UgTUlCIG1vZHVsZXMgYW5kIHRoZWlyCj4gc3VjY2Vzc29y
cyB3ZXJlIHRyYW5zZmVycmVkIHRvIElFRUUgODAyLjEuIEkgc3VnZ2VzdCB0byBkZWZpbmUgdGhl
Cj4gcmVsYXRpb25zaGlwIHNlY3Rpb25zIGluIHJlbGF0aW9uIHRvIHRoZSBJRUVFIE1JQiBtb2R1
bGVzIGRlZmluZWQgaW4KPiBJRUVFIDgwMi4xYXAKCldpbGwgZG8uCgo+IDIuIFNvbWUgb2YgdGhl
IG9iamVjdHMgd2l0aCByZWFkLWNyZWF0ZSBNQVgtQUNDRVNTIG5lZWQgREVGQVVMVCBjbGF1c2Vz
Lgo+IEluIHNvbWUgY2FzZXMgdGhlIGRlZmF1bHQgaXMgbWVudGlvbiBpbiB0aGUgREVTQ1JJUFRJ
T04gY2xhdXNlIC0gdGhpcyBpcyBub3QKPiBzdWZmaWNpZW50CgpPSywgSSdsbCBhZGQgdGhlc2Ug
Y2xhdXNlcy4KCj4gMy4gTUlCIHN0cnVjdHVyZSAtIGJldHRlciBncm91cCBhbGwgTUlCIGdyb3Vw
cyB0aGF0IGRlZmluZSBvYmplY3RzIHVuZGVyIG9uZQo+IHN1Yi10cmVlCj4gcmJyaWRnZU9iamVj
dHMgICAgICAgICAgIE9CSkVDVCBJREVOVElGSUVSIDo6PSB7IHJicmlkZ2VNSUIgMSB9CgpJbiBv
dGhlciB3b3JkcywgZGVmaW5lIGEgc2luZ2xlIHN1Yi10cmVlIGZvciBvYmplY3RzLCBvbmUgZm9y
Cm5vdGlmaWNhdGlvbnMgJiBvbmUgZm9yIGNvbmZvcm1hbmNlPyBJdCBhZGRzIGFub3RoZXIgbGV2
ZWwsIGJ1dCBjYW4gY2VydGFpbmx5CmJlIGRvbmUuIEnigJl2ZSBzdHJ1Y3R1cmVkIGl0IGluIGEg
bWFubmVyIHBhcmFsbGVsIHRvIGVhcmxpZXIgdmVyc2lvbnMgb2YgdGhlCkJyaWRnZSBNSUIuCgo+
IDQuIFRoZSBjdXJyZW50IGxldmVsIG9mIGRldGFpbCBpbiB0aGUgU2VjdXJpdHkgQ29uc2lkZXJh
dGlvbnMgc2VjdGlvbiBpcyBub3QKPiBzdWZmaWNpZW50LgoKWWVzLCB3aWxsIGV4cGFuZCB0aGlz
IHNlY3Rpb24uCgo+IDUuIHJ1bm5pbmcgbGlic21pIGNvbXBpbGF0aW9uIGxlYWRzIHRvIGEgbnVt
YmVyIG9mIGVycm9ycyBhbmQgd2FybmluZ3MgdGhhdCBuZWVkCj4gdG8gYmUgZml4ZWQuIAoKSSBj
b21waWxlZCB3aXRoIGEgY29tbWVyY2lhbCBtYW5hZ2VyIHByaW9yIHRvIHB1YmxpY2F0aW9uOyB3
aWxsIHRyeSBsaWJzbWkuIEl0IHdvdWxkCmJlIG5pY2UgdG8gaGF2ZSBhIE1JQiBjb21waWxlciBv
biB0aGUgSUVURiB0b29scyBkaXJlY3RvcnkgdG8gY2hlY2sgY29tcGxpYW5jZSwKaWYgYXQgYWxs
IHBvc3NpYmxlLgoKUmVnYXJkcywKQW5pbAoKRnJvbTogIlJvbWFzY2FudSwgRGFuIChEYW4pIiA8
ZHJvbWFzY2FAYXZheWEuY29tPgpEYXRlOiBKYW51YXJ5IDMsIDIwMTEgMTE6MDk6NTUgQU0gRVNU
ClRvOiAiRG9uYWxkIEVhc3RsYWtlIiA8ZDNlM2UzQGdtYWlsLmNvbT4sICJEZXZlbG9waW5nIGEg
aHlicmlkIHJvdXRlci9icmlkZ2UuIiA8cmJyaWRnZUBwb3N0ZWwub3JnPgpTdWJqZWN0OiBSZTog
W3JicmlkZ2VdIFJlcXVlc3QgZm9yIHJldmlldyBvZmRyYWZ0LWlldGYtdHJpbGwtcmJyaWRnZS1t
aWItMDEudHh0CgpJIGRpZCBub3QgaGF2ZSB0aW1lIGZvciBhIGZ1bGwgcmV2aWV3LCBidXQgaGVy
ZSBhcmUgbXkgY29tbWVudHMgZnJvbSBhIGZpcnN0IHF1aWNrIGV4YW1pbmF0aW9uIG9mIHRoZSBk
b2N1bWVudAoKMS4gVGhlIHJlbGF0aW9uc2hpcCB3aXRoIG90aGVyIE1JQiBtb2R1bGUgc2VjdGlv
bnMgcmVmZXIgdG8gdGhlIElFVEYgUkZDcy4gSG93ZXZlciwgc2luY2UgMjAwNiB0aGUgZGV2ZWxv
cG1lbnQgb2YgdGhlIEJyaWRnZSBNSUIgbW9kdWxlcyBhbmQgdGhlaXIgc3VjY2Vzc29ycyB3ZXJl
IHRyYW5zZmVycmVkIHRvIElFRUUgODAyLjEuIEkgc3VnZ2VzdCB0byBkZWZpbmUgdGhlIHJlbGF0
aW9uc2hpcCBzZWN0aW9ucyBpbiByZWxhdGlvbiB0byB0aGUgSUVFRSBNSUIgbW9kdWxlcyBkZWZp
bmVkIGluIElFRUUgODAyLjFhcAoKMi4gU29tZSBvZiB0aGUgb2JqZWN0cyB3aXRoIHJlYWQtY3Jl
YXRlIE1BWC1BQ0NFU1MgbmVlZCBERUZBVUxUIGNsYXVzZXMuIEluIHNvbWUgY2FzZXMgdGhlIGRl
ZmF1bHQgaXMgbWVudGlvbiBpbiB0aGUgREVTQ1JJUFRJT04gY2xhdXNlIC0gdGhpcyBpcyBub3Qg
c3VmZmljaWVudAoKMy4gTUlCIHN0cnVjdHVyZSAtIGJldHRlciBncm91cCBhbGwgTUlCIGdyb3Vw
cyB0aGF0IGRlZmluZSBvYmplY3RzIHVuZGVyIG9uZSBzdWItdHJlZSAKCnJicmlkZ2VPYmplY3Rz
ICAgICAgICAgICBPQkpFQ1QgSURFTlRJRklFUiA6Oj0geyByYnJpZGdlTUlCIDEgfSAKCjQuIFRo
ZSBjdXJyZW50IGxldmVsIG9mIGRldGFpbCBpbiB0aGUgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMg
c2VjdGlvbiBpcyBub3Qgc3VmZmljaWVudC4gCgo1LiBydW5uaW5nIGxpYnNtaSBjb21waWxhdGlv
biBsZWFkcyB0byBhIG51bWJlciBvZiBlcnJvcnMgYW5kIHdhcm5pbmdzIHRoYXQgbmVlZCB0byBi
ZSBmaXhlZC4gCgpSZWdhcmRzLAoKRGFuCgoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18KcmJyaWRnZSBtYWlsaW5nIGxpc3QKcmJyaWRnZUBwb3N0ZWwub3Jn
Cmh0dHA6Ly9tYWlsbWFuLnBvc3RlbC5vcmcvbWFpbG1hbi9saXN0aW5mby9yYnJpZGdlCg==

From rbridge-bounces@postel.org  Wed Jan 26 09:09:16 2011
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 342E63A6845 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 09:09:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 uaDooSxjeBG8 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 09:09:15 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 14FE23A681F for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 09:09:15 -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 p0QGxsRR012147; Wed, 26 Jan 2011 08:59:55 -0800 (PST)
Received: from mta41.charter.net (mta41.charter.net [216.33.127.83]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QGxTWv012105 for <rbridge@postel.org>; Wed, 26 Jan 2011 08:59:38 -0800 (PST)
Received: from imp10 ([10.20.200.15]) by mta41.charter.net (InterMail vM.7.09.02.04 201-2219-117-106-20090629) with ESMTP id <20110126165929.VFJN2629.mta41.charter.net@imp10>; Wed, 26 Jan 2011 11:59:29 -0500
Received: from mp08 ([209.225.8.238]) by imp10 with smtp.charter.net id 0GzU1g00Z588i5505GzUkw; Wed, 26 Jan 2011 11:59:28 -0500
X-Authority-Analysis: v=1.0 c=1 a=OczIKRAeacIA:10 a=IkcTkHD0fZMA:10 a=pGLkceISAAAA:8 a=0Qg8RWfqAAAA:8 a=n7ah38dEI_tpkJBXK-wA:9 a=cjk3kIK-nk5LRDBM4bAA:7 a=_nnsoUOO7R2EOCxGvFr1xfKthgMA:4 a=QEXdDO2ut3YA:10 a=MSl-tDqOz04A:10 a=NeaMLyczsAwA:10 a=ckSnMuS-9GEj_o4X:21 a=fSEJPcNpRuu-5T-F:21
Message-ID: <20110126115928.NLY9L.11297578.root@mp08>
Date: Wed, 26 Jan 2011 11:59:28 -0500
From: Anil Rijhsinghani <anil@charter.net>
To: Vishwas Manral <vishwas.ietf@gmail.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
Sensitivity: Normal
X-Originating-IP: from 151.104.126.59 by ssomail.charter.net; Wed, 26 Jan 2011 11:59:28 -0500
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: anil@charter.net
Cc: rbridge@postel.org
Subject: Re: [rbridge] draft-ietf-trill-rbridge-mib
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

Hi Vishwas,

> 1. I think we should have a seperate tree for the Rbridge. I notice 
> some of the tables are the same as IS-IS. It will be very confusing to 
> code a MBI which is half IS-IS and half TRILL IS-IS.

IETF convention is to leverage pre-existing MIBs for pre-defined protocols.
Otherwise, we would end up with bloated MIBs and duplicated work.
In this MIB we have re-used management work done for IS-IS as well as Bridges,
and added new objects defined by the TRILL protocol.

> 2. There is no information for MultiTopology.

We do not yet have multi-topology in TRILL.

> 3. Another thing that needs to be kept is the MTU table. Which has MTU 
> information received from all the devices in the network. I know we 
> have MTU objects at a link and neighbor basis.

What would be the management benefit of adding such a (potentially
huge) table? It seems to me that it would suffice for a manager to know
the configurable Desired MTU per Rbridge, its neighbors, and the agreed MTU for
the campus. For information regarding other Rbridges, it can visit those Rbridges.

> 4. We probably need tohave Multicast Address listner  table too.

The group rbridgeSnooping contains a minimal level of multicast listener and snooping information necessary to support TRILL. Adding all objects necessary for
IPv4 and IPv6 snooping is a non-goal and belongs in an independent Snooping/Listener MIB, as this is not functionality defined by TRILL. If there
are additional objects you believe are necessary specifically to support TRILL,
please list.

> 5. We will need a table for the the information in the system for 
> distribution trees, and information advertized by each system, or 
> atleast a way to change the values to be configured for a system.

There is a group and table for distribution trees, rbridgeDtree and rbridgeDtreeTable. If you believe there are useful configurable objects
missing, could you please list them?

Regards,
Anil

-----Original Message-----
From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
Sent: Monday, January 17, 2011 1:17 PM
To: rbridge@postel.org
Cc: Rijhsinghani, Anil; kate.zebrose@alum.mit.edu
Subject: draft-ietf-trill-rbridge-mib

Hi Anil/ Kate,

I briefly looked at the TRILL MIB and had the following top level comments:

1. I think we should have a seperate tree for the Rbridge. I notice some of the tables are the same as IS-IS. It will be very confusing to code a MBI which is half IS-IS and half TRILL IS-IS.
2. There is no information for MultiTopology.
3. Another thing that needs to be kept is the MTU table. Which has MTU information received from all the devices in the network. I know we have MTU objects at a link and neighbor basis.
4. We probably need tohave Multicast Address listner  table too.
5. We will need a table for the the information in the system for distribution trees, and information advertized by each system, or atleast a way to change the values to be configured for a system.

Thanks,
Vishwas

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Wed Jan 26 09:57:18 2011
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 944353A67FD for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 09:57:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level: 
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, 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 sQj32HX6JcSG for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 09:57:17 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 66CA03A67B3 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 09:57:17 -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 p0QHmxBH022527; Wed, 26 Jan 2011 09:49:00 -0800 (PST)
Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QHmcxu022473 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Wed, 26 Jan 2011 09:48:49 -0800 (PST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEAKbsP03GmAcF/2dsb2JhbACkeHOjYgKZNIVPBJAKgnw
X-IronPort-AV: E=Sophos;i="4.60,381,1291611600"; d="scan'208";a="229433079"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 26 Jan 2011 12:48:36 -0500
X-IronPort-AV: E=Sophos;i="4.60,381,1291611600"; d="scan'208";a="575012192"
Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 26 Jan 2011 12:48:32 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 26 Jan 2011 18:48:12 +0100
Message-ID: <EDC652A26FB23C4EB6384A4584434A0402B3190F@307622ANEX5.global.avaya.com>
In-Reply-To: <20110126114252.N5ZK9.11297420.root@mp08>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [rbridge] Request for review ofdraft-ietf-trill-rbridge-mib-01.txt
Thread-Index: Acu9eBZLjMdRW51ZRKq8/TqKzquR/QACBktQ
References: <20110126114252.N5ZK9.11297420.root@mp08>
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "Anil Rijhsinghani" <anil@charter.net>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: dromasca@avaya.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0QHmcxu022473
Cc: rbridge@postel.org
Subject: Re: [rbridge] Request for review ofdraft-ietf-trill-rbridge-mib-01.txt
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

Hi Anil,

Thank you for your response and for addressing my comments. 

To your last point - libsmi
http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/ is not maintained by
the IETF tools team but by volunteers from a German university. It is
however referenced from the OPS Area wiki page - see
https://svn.tools.ietf.org/area/ops/trac/wiki/mib-review-tools

Regards,

Dan


> -----Original Message-----
> From: Anil Rijhsinghani [mailto:anil@charter.net] 
> Sent: Wednesday, January 26, 2011 6:43 PM
> To: Romascanu, Dan (Dan)
> Cc: rbridge@postel.org
> Subject: Re: [rbridge] Request for review 
> ofdraft-ietf-trill-rbridge-mib-01.txt
> 
> Hi Dan,
> 
> > 1. The relationship with other MIB module sections refer to 
> the IETF RFCs.
> > However, since 2006 the development of the Bridge MIB modules and 
> > their successors were transferred to IEEE 802.1. I suggest 
> to define 
> > the relationship sections in relation to the IEEE MIB 
> modules defined 
> > in IEEE 802.1ap
> 
> Will do.
> 
> > 2. Some of the objects with read-create MAX-ACCESS need 
> DEFAULT clauses.
> > In some cases the default is mention in the DESCRIPTION 
> clause - this 
> > is not sufficient
> 
> OK, I'll add these clauses.
> 
> > 3. MIB structure - better group all MIB groups that define objects 
> > under one sub-tree
> > rbridgeObjects           OBJECT IDENTIFIER ::= { rbridgeMIB 1 }
> 
> In other words, define a single sub-tree for objects, one for 
> notifications & one for conformance? It adds another level, 
> but can certainly be done. I've structured it in a manner 
> parallel to earlier versions of the Bridge MIB.
> 
> > 4. The current level of detail in the Security 
> Considerations section 
> > is not sufficient.
> 
> Yes, will expand this section.
> 
> > 5. running libsmi compilation leads to a number of errors 
> and warnings 
> > that need to be fixed.
> 
> I compiled with a commercial manager prior to publication; 
> will try libsmi. It would be nice to have a MIB compiler on 
> the IETF tools directory to check compliance, if at all possible.
> 
> Regards,
> Anil
> 
> From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
> Date: January 3, 2011 11:09:55 AM EST
> To: "Donald Eastlake" <d3e3e3@gmail.com>, "Developing a 
> hybrid router/bridge." <rbridge@postel.org>
> Subject: Re: [rbridge] Request for review 
> ofdraft-ietf-trill-rbridge-mib-01.txt
> 
> I did not have time for a full review, but here are my 
> comments from a first quick examination of the document
> 
> 1. The relationship with other MIB module sections refer to 
> the IETF RFCs. However, since 2006 the development of the 
> Bridge MIB modules and their successors were transferred to 
> IEEE 802.1. I suggest to define the relationship sections in 
> relation to the IEEE MIB modules defined in IEEE 802.1ap
> 
> 2. Some of the objects with read-create MAX-ACCESS need 
> DEFAULT clauses. In some cases the default is mention in the 
> DESCRIPTION clause - this is not sufficient
> 
> 3. MIB structure - better group all MIB groups that define 
> objects under one sub-tree 
> 
> rbridgeObjects           OBJECT IDENTIFIER ::= { rbridgeMIB 1 } 
> 
> 4. The current level of detail in the Security Considerations 
> section is not sufficient. 
> 
> 5. running libsmi compilation leads to a number of errors and 
> warnings that need to be fixed. 
> 
> Regards,
> 
> Dan
> 
> 

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Wed Jan 26 10:19:03 2011
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 1BD883A6818 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 10:19:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.906
X-Spam-Level: 
X-Spam-Status: No, score=-102.906 tagged_above=-999 required=5 tests=[AWL=-0.307, 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 fGGBNh-pqtLs for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 10:19:02 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id EC8B23A67D8 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 10:19:01 -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 p0QI8TCf026328; Wed, 26 Jan 2011 10:08:31 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QI7lW3026217 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Wed, 26 Jan 2011 10:07:57 -0800 (PST)
Received: by wwd20 with SMTP id 20so1332412wwd.21 for <rbridge@postel.org>; Wed, 26 Jan 2011 10:07:47 -0800 (PST)
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=AQhgl79d1zb+l9kATFnP0+XJn6ZhWVXAKmdWfvo2sB8=; b=w7Vk64scXPMwovSipJscqYJXLy6W6C+GnllmNNksUzX02JCzCqyDs9fKgIn8PwxMRI 0fvWlwGBTE5jyPWHkKdtdvXUJsxVQ3Qw5r28Y8pnKQ6rDYFwz4BEHcMrkTy98lvv+fqI r+uuVfuaY9Kyr21ReTDSAAKwpyXu7Mp3U3P6M=
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=M8RAVl73g+E2iGLc46WzFX3Ky/M8tRqVeCcSKperRkmUw4olPvDFzGp0Sm53uYVxiV TGBbyEJBePk1Nn4KTk7F+9K36Yzi0v1Y3oJQktnoE2F5YtUNmJNsDn1ajUXVwBkLWMzN ZiE2lLY/Tng7NQ2tT1CsUoJC3R29EUSICHKCw=
Received: by 10.227.143.198 with SMTP id w6mr1717946wbu.37.1296065266831; Wed, 26 Jan 2011 10:07:46 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Wed, 26 Jan 2011 10:07:26 -0800 (PST)
In-Reply-To: <20110126112341.AA6XN.11297223.root@mp08>
References: <20110126112341.AA6XN.11297223.root@mp08>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 26 Jan 2011 13:07:26 -0500
Message-ID: <AANLkTimmfYsGSei0-Chhy_Er82s2ExoajgL3SuitxfyR@mail.gmail.com>
To: Anil Rijhsinghani <anil@charter.net>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0QI7lW3026217
Cc: rbridge@postel.org
Subject: Re: [rbridge] Request for review of draft-ietf-trill-rbridge-mib-01.txt
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="windows-1252"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Anil,

On Wed, Jan 26, 2011 at 11:23 AM, Anil Rijhsinghani <anil@charter.net> wrot=
e:
> Hi Donald,
>
>> I think that Sz, the campus wide minimum MTU that an RBridge has
>> calculated, should be a read-only per-RBridge MIB object and that it
>> should be possible for a change in Sz to cause a notification.
>
> I=92ll add Sz as a read-only object to the TRILL group, next to MinMtuDes=
ired which
> is a read-write object.
>
> I would suggest we not make a changing value of this a notification, as i=
t could
> lead to the trap sink being flooded simultaneously with a large number of
> notifications. This is an object that an NMS will want to monitor or poll=
 when
> necessary.

On further thought, I agree. It should very rarely change but when it
does it will likely change for many RBridges at once.

> Regards,
> Anil

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA=A0=A0 +1-508-634-2066 (home)
=A0d3e3e3@gmail.com

> From: Donald Eastlake <d3e3e3@gmail.com>
> Date: December 27, 2010 10:26:12 PM EST
> To: "Developing a hybrid router/bridge." <rbridge@postel.org>
> Subject: Re: [rbridge] Request for review of draft-ietf-trill-rbridge-mib=
-01.txt
>
> Hi,
>
> It would be helpful if people would review the MIB document. Here is a
> comment of mine:
>
> I think that Sz, the campus wide minimum MTU that an RBridge has
> calculated, should be a read-only per-RBridge MIB object and that it
> should be possible for a change in Sz to cause a notification.
>
> Thanks,
> Donald
>
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Wed Jan 26 11:53:48 2011
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 519AA3A68E6 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 11:53:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.455
X-Spam-Level: 
X-Spam-Status: No, score=-102.455 tagged_above=-999 required=5 tests=[AWL=0.144, 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 Sax86FqwxLE5 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 11:53:47 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 465913A689F for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 11:53:47 -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 p0QJp7ZZ018251; Wed, 26 Jan 2011 11:51:08 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QJoROq018069 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Wed, 26 Jan 2011 11:50:37 -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>
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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

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>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Wed Jan 26 12:24:03 2011
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 EBE7C3A6930 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 12:24:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.905
X-Spam-Level: 
X-Spam-Status: No, score=-102.905 tagged_above=-999 required=5 tests=[AWL=-0.306, 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 lJKTU2tgq5vU for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 12:24:02 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id CA87E3A6860 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 12:24:02 -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 p0QK9aNh022794; Wed, 26 Jan 2011 12:09:38 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QK9DkJ022731 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Wed, 26 Jan 2011 12:09:23 -0800 (PST)
Received: by wwd20 with SMTP id 20so1467395wwd.21 for <rbridge@postel.org>; Wed, 26 Jan 2011 12:09:13 -0800 (PST)
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=uONw3fXNCRrp61SLj8LxTxiuIBXU+vH/dTO49cgV8bE=; b=TFL2g70Nphn5xghRog8DMQ/Z62cUgieWaWHm+To2WdtyARhmP5J0yuGpPafPDZWEE6 Nf76MCEUfXnAuLUVD1He96t7SU/pO4bH+3mySxIRX6hBG0XQqpeLtfqWjYZakjanw3zs xZTjLqefWp9wmiZc5GhSao0B7xKZyqzneZito=
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=s+Gssll74gf9wcn6vvec1jzmrA3+CjCt6pSKqgl3tGJ2v05QpSK+uAuaU+2kmHKh/n 75oo5KB3/DvYiw+W1gfAsvOEMQ9ZnCt8p/FmyvI2mzOIKlL+8JiD32RLY0IljpY595YB GLRrrOoViO3NUQ5Hlqwk6uImFA9Qb9Vg+rJpE=
Received: by 10.227.143.206 with SMTP id w14mr39949wbu.66.1296072553054; Wed, 26 Jan 2011 12:09:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Wed, 26 Jan 2011 12:08:52 -0800 (PST)
In-Reply-To: <4D4065F2.3080305@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>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 26 Jan 2011 15:08:52 -0500
Message-ID: <AANLkTimi5vsYbGb0QXhyg_jdE2aCPKkUL9Y_Qj=g0Jpo@mail.gmail.com>
To: William Allen Simpson <william.allen.simpson@gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0QK9DkJ022731
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi,

On Wed, Jan 26, 2011 at 1:20 PM, William Allen Simpson
<william.allen.simpson@gmail.com> wrote:
> On 1/25/11 2:04 PM, James Carlson wrote:
>>
>> I certainly agree with the sentiment (I don't like duplicating
>> documentation at all, particularly for this issue), but the existing
>> notation about MAC addresses (and the lack of them on PPP) was added at
>> the behest of other reviewers who found that it was confusing to match
>> up the PPP TRILL draft with the primary TRILL documentation without some
>> indication that there are differences here.
>>
> I agree with the other reviewers. =A0Pretty hard to understand TRILL over
> PPP without mentioning System IDs and the lack of MAC addresses.

I don't understand why you say that. Seem to me that TRILL over PPP
just involves the formats, code points, and PPP procedures. Anyway, it
isn't clear to me that anyone will build a practical RBridge that
doesn't have a MAC address Ethernet interface even if it is just a
virtual internal interface for a virtual internal end station. If that
doesn't exist, you can't really address the RBridge for management or
maintenance.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA=A0=A0 +1-508-634-2066 (home)
=A0d3e3e3@gmail.com

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Wed Jan 26 12:53:53 2011
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 414753A6897 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 12:53:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.962
X-Spam-Level: 
X-Spam-Status: No, score=-2.962 tagged_above=-999 required=5 tests=[AWL=-0.363, 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 p5xQ3oNHyZoD for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 12:53:52 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 06A683A6895 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 12:53:51 -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 p0QKd0r3028281; Wed, 26 Jan 2011 12:39:01 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QKcNva028235 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Wed, 26 Jan 2011 12:38:33 -0800 (PST)
Received: by wwd20 with SMTP id 20so1499006wwd.21 for <rbridge@postel.org>; Wed, 26 Jan 2011 12:38:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=La2RvZL8YDziu+AkwKQsWg2tbXuGq+/uXzIZG4XqAfQ=; b=m4ZgFROV/JbwGtmI3HRQwhIVuLKgCrxQvGI5gzn4fCa+nQCzG2ytiYnQyDhCuBemiR 0RmepSXZQBNBSVkdVz7fXCi0di3TT+8hufLsGv9xz4A8xVU4YlMH6YDZXnRs3Hc+Ljyu lq1/tNOtP0rlOkn65/qCyeiorat/sMXGUq308=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=uhS0l+gGIN4yGeLmArtGolkFZLvws3+OyOpFLq1aaMTOZKPYStasQWpv9pVLYeCKQh VJDyllrS7DXRfC8fDQOTBSvpDAllsU90OANzySfkCIyd2eGu8nQHmsIDI0HqOTHyJVPO zQpC0wYVdbFr2IHCa3jg6rdrdIQ1H1FvYmqfU=
MIME-Version: 1.0
Received: by 10.216.156.149 with SMTP id m21mr5592692wek.22.1296074302901; Wed, 26 Jan 2011 12:38:22 -0800 (PST)
Received: by 10.216.21.65 with HTTP; Wed, 26 Jan 2011 12:38:22 -0800 (PST)
In-Reply-To: <20110126115928.NLY9L.11297578.root@mp08>
References: <20110126115928.NLY9L.11297578.root@mp08>
Date: Wed, 26 Jan 2011 12:38:22 -0800
Message-ID: <AANLkTi=JgvnR+TUo=wSANnObVtD0QGYPmrMU=5zBSMJm@mail.gmail.com>
From: Vishwas Manral <vishwas.ietf@gmail.com>
To: Anil Rijhsinghani <anil@charter.net>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: vishwas.ietf@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0QKcNva028235
Cc: rbridge@postel.org
Subject: Re: [rbridge] draft-ietf-trill-rbridge-mib
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Anil,

> IETF convention is to leverage pre-existing MIBs for pre-defined protocol=
s.
> Otherwise, we would end up with bloated MIBs and duplicated work.
> In this MIB we have re-used management work done for IS-IS as well as Bri=
dges,
> and added new objects defined by the TRILL protocol.
No the MIB's will not be bloated.

By having control protocols for 2 different layers use the same MIB,
you are forcing to have the entire functionality in one address space,
or having to have an unnecessary middle layer which will have to probe
two different protocol modules.

Note using the same protocol machine does not mean we reuse the same
MIB. A similar example is OSPFv2 and OSPFv3. They share protocol
mechansims and not all OSPFv2 mechanisms are duplicated in OSPFv3,
however the MIB's have to be different.

>> 2. There is no information for MultiTopology.
>
> We do not yet have multi-topology in TRILL.
May be you want to see the Layer-2 IS-IS and TRILL IS-IS draft.

>> 3. Another thing that needs to be kept is the MTU table. Which has MTU
>> information received from all the devices in the network. I know we
>> have MTU objects at a link and neighbor basis.
>
> What would be the management benefit of adding such a (potentially
> huge) table? It seems to me that it would suffice for a manager to know
> the configurable Desired MTU per Rbridge, its neighbors, and the agreed M=
TU for
> the campus. For information regarding other Rbridges, it can visit those =
Rbridges.

Note a MIB is a logical way of manipulating data. You do not need to
have special tables for them. The data I am talking about is already
present in IS-IS. The idea here is to let management access to it.

We can discuss the other smaller points later.

Thanks,
Vishwas

>> 4. We probably need tohave Multicast Address listner =A0table too.
>
> The group rbridgeSnooping contains a minimal level of multicast listener =
and snooping information necessary to support TRILL. Adding all objects nec=
essary for
> IPv4 and IPv6 snooping is a non-goal and belongs in an independent Snoopi=
ng/Listener MIB, as this is not functionality defined by TRILL. If there
> are additional objects you believe are necessary specifically to support =
TRILL,
> please list.

>> 5. We will need a table for the the information in the system for
>> distribution trees, and information advertized by each system, or
>> atleast a way to change the values to be configured for a system.
>
> There is a group and table for distribution trees, rbridgeDtree and rbrid=
geDtreeTable. If you believe there are useful configurable objects
> missing, could you please list them?
>
> Regards,
> Anil
>
> -----Original Message-----
> From: Vishwas Manral [mailto:vishwas.ietf@gmail.com]
> Sent: Monday, January 17, 2011 1:17 PM
> To: rbridge@postel.org
> Cc: Rijhsinghani, Anil; kate.zebrose@alum.mit.edu
> Subject: draft-ietf-trill-rbridge-mib
>
> Hi Anil/ Kate,
>
> I briefly looked at the TRILL MIB and had the following top level comment=
s:
>
> 1. I think we should have a seperate tree for the Rbridge. I notice some =
of the tables are the same as IS-IS. It will be very confusing to code a MB=
I which is half IS-IS and half TRILL IS-IS.
> 2. There is no information for MultiTopology.
> 3. Another thing that needs to be kept is the MTU table. Which has MTU in=
formation received from all the devices in the network. I know we have MTU =
objects at a link and neighbor basis.
> 4. We probably need tohave Multicast Address listner =A0table too.
> 5. We will need a table for the the information in the system for distrib=
ution trees, and information advertized by each system, or atleast a way to=
 change the values to be configured for a system.
>
> Thanks,
> Vishwas
>
>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Wed Jan 26 14:01:53 2011
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 D383D3A68BB for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 14:01:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.472
X-Spam-Level: 
X-Spam-Status: No, score=-102.472 tagged_above=-999 required=5 tests=[AWL=0.127, 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 q5wx8nNq-Y1J for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 26 Jan 2011 14:01:52 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id CA32B3A6893 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 26 Jan 2011 14:01:52 -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 p0QLgbsF011329; Wed, 26 Jan 2011 13:42:38 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0QLfwEi011230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Wed, 26 Jan 2011 13:42:08 -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 p0QLca5L021550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Jan 2011 16:38:36 -0500 (EST)
Message-ID: <4D40945C.1070906@workingcode.com>
Date: Wed, 26 Jan 2011 16:38:36 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Thunderbird 2.0.0.22 (X11/20090605)
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@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> <AANLkTimi5vsYbGb0QXhyg_jdE2aCPKkUL9Y_Qj=g0Jpo@mail.gmail.com>
In-Reply-To: <AANLkTimi5vsYbGb0QXhyg_jdE2aCPKkUL9Y_Qj=g0Jpo@mail.gmail.com>
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org, William Allen Simpson <william.allen.simpson@gmail.com>
Subject: Re: [rbridge] [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: 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 wrote:
> I don't understand why you say that. Seem to me that TRILL over PPP
> just involves the formats, code points, and PPP procedures. Anyway, it
> isn't clear to me that anyone will build a practical RBridge that
> doesn't have a MAC address Ethernet interface even if it is just a
> virtual internal interface for a virtual internal end station. If that
> doesn't exist, you can't really address the RBridge for management or
> maintenance.

Sure, you could.  It would just have to be addressed via IP (e.g., via
SNMP, ssh, or even TELNET) rather than by something locked into Ethernet.

One could imagine a large TRILL bridge designed for telecom applications
exclusively on the interior of the cloud, where the only possible links
are point-to-point; no Ethernet need apply.

Whether anyone ever builds that beast -- and, if so, whether it lacks
any built-in mechanism for automatic System ID assignment -- is a
different question.

What we're really discussing is whether failing to cover this case with
some sort of automatic resolution is a hole in the specification (as I
think Mr. Simpson is contending), or whether it's just an unlikely
corner that implementors should be warned away from (as I believe).

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Thu Jan 27 06:46:52 2011
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 C76A83A688C for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 06:46:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.903
X-Spam-Level: 
X-Spam-Status: No, score=-102.903 tagged_above=-999 required=5 tests=[AWL=-0.304, 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 qZw68tYQH+bB for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 06:46:50 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 282CE3A68A6 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 27 Jan 2011 06:46:49 -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 p0REYSa2016815; Thu, 27 Jan 2011 06:34:29 -0800 (PST)
Received: from mail-wy0-f180.google.com (mail-wy0-f180.google.com [74.125.82.180]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0REXxjx016731 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 27 Jan 2011 06:34:09 -0800 (PST)
Received: by wyb28 with SMTP id 28so2100954wyb.39 for <rbridge@postel.org>; Thu, 27 Jan 2011 06:33:58 -0800 (PST)
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=Ut2LDRXrky8PsLrdx34e+Ba9JPhDrS18rp69C2yifiI=; b=mfIT9HjStQyvN2be6eWgDNvGby8I9XaVQVm2Bf+b+jWzYNrI9nHLcADAr9DXSF0UxN RbmxlVmvBy1m1oHcxHDsNHuxq3Yza49sTkFfdHpFkQge4zLWyzq9BwgP5sANQM5s3nPH QNvTBVVjdmoDAVQhvw0acaYYclNsT79S1IeQM=
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=vdEXwSDyAL2GZNpg9NU0ATLIrSVSsJ3egtSAv/qjqH85U4hIlkaoHvn4WHaPXI5b9P tc3XUG5Ew0sjCnq1kypZS+WauSiBjsJ6qj8VUL0LVChuMC0ptj1E0uLkQAXYc3/K8eU4 SRqjAvc8YfYpAUlvm8DIzIPAS6BsBKybZ+UV0=
Received: by 10.227.145.139 with SMTP id d11mr1160163wbv.8.1296138838512; Thu, 27 Jan 2011 06:33:58 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Thu, 27 Jan 2011 06:33:34 -0800 (PST)
In-Reply-To: <4D40945C.1070906@workingcode.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> <AANLkTimi5vsYbGb0QXhyg_jdE2aCPKkUL9Y_Qj=g0Jpo@mail.gmail.com> <4D40945C.1070906@workingcode.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 27 Jan 2011 09:33:34 -0500
Message-ID: <AANLkTi=RTh8YWh4Ck8P97Qv7YugbtoVOncko=mhA5ahN@mail.gmail.com>
To: James Carlson <carlsonj@workingcode.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0REXxjx016731
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi James,

On Wed, Jan 26, 2011 at 4:38 PM, James Carlson <carlsonj@workingcode.com> w=
rote:
> Donald Eastlake wrote:
>> I don't understand why you say that. Seem to me that TRILL over PPP
>> just involves the formats, code points, and PPP procedures. Anyway, it
>> isn't clear to me that anyone will build a practical RBridge that
>> doesn't have a MAC address Ethernet interface even if it is just a
>> virtual internal interface for a virtual internal end station. If that
>> doesn't exist, you can't really address the RBridge for management or
>> maintenance.
>
> Sure, you could. =A0It would just have to be addressed via IP (e.g., via
> SNMP, ssh, or even TELNET) rather than by something locked into Ethernet.

Really? RBridge don't route on IP addresses. They route based on
nickname and, on ingress, they convert to nickname from MAC/VLAN. How
are you going to get an RBridge to route on an IP address?

Thanks,
Donald

> One could imagine a large TRILL bridge designed for telecom applications
> exclusively on the interior of the cloud, where the only possible links
> are point-to-point; no Ethernet need apply.
>
> Whether anyone ever builds that beast -- and, if so, whether it lacks
> any built-in mechanism for automatic System ID assignment -- is a
> different question.
>
> What we're really discussing is whether failing to cover this case with
> some sort of automatic resolution is a hole in the specification (as I
> think Mr. Simpson is contending), or whether it's just an unlikely
> corner that implementors should be warned away from (as I believe).
>
> --
> James Carlson =A0 =A0 =A0 =A0 42.703N 71.076W =A0 =A0 =A0 =A0 <carlsonj@w=
orkingcode.com>

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Thu Jan 27 07:14:44 2011
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 108E33A68B0 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 07:14:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level: 
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, 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 rSAKbaebMttg for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 07:14:43 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 07ED93A6882 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 27 Jan 2011 07:14:42 -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 p0REsSIG020697; Thu, 27 Jan 2011 06:54:29 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0RErlMD020528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Thu, 27 Jan 2011 06:53:58 -0800 (PST)
Received: from [75.150.68.97] (carlson [75.150.68.97]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id p0REoVqM006368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2011 09:50:31 -0500 (EST)
Message-ID: <4D418637.10007@workingcode.com>
Date: Thu, 27 Jan 2011 09:50:31 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.7) Gecko/20100214 Lightning/1.0b1 Thunderbird/3.0.1
MIME-Version: 1.0
To: Donald Eastlake <d3e3e3@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> <AANLkTimi5vsYbGb0QXhyg_jdE2aCPKkUL9Y_Qj=g0Jpo@mail.gmail.com> <4D40945C.1070906@workingcode.com> <AANLkTi=RTh8YWh4Ck8P97Qv7YugbtoVOncko=mhA5ahN@mail.gmail.com>
In-Reply-To: <AANLkTi=RTh8YWh4Ck8P97Qv7YugbtoVOncko=mhA5ahN@mail.gmail.com>
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [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: 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

On 01/27/11 09:33, Donald Eastlake wrote:
> Hi James,
> 
> On Wed, Jan 26, 2011 at 4:38 PM, James Carlson <carlsonj@workingcode.com> wrote:
>> Donald Eastlake wrote:
>>> I don't understand why you say that. Seem to me that TRILL over PPP
>>> just involves the formats, code points, and PPP procedures. Anyway, it
>>> isn't clear to me that anyone will build a practical RBridge that
>>> doesn't have a MAC address Ethernet interface even if it is just a
>>> virtual internal interface for a virtual internal end station. If that
>>> doesn't exist, you can't really address the RBridge for management or
>>> maintenance.
>>
>> Sure, you could.  It would just have to be addressed via IP (e.g., via
>> SNMP, ssh, or even TELNET) rather than by something locked into Ethernet.
> 
> Really? RBridge don't route on IP addresses. They route based on
> nickname and, on ingress, they convert to nickname from MAC/VLAN. How
> are you going to get an RBridge to route on an IP address?

You provide it with access to a management network, perhaps also through
PPP.  This could be done via separate interfaces or, if desired, by
running IPCP in parallel with TRILL on the existing PPP links.

Who said all management must be in-band with the data network?

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Thu Jan 27 11:44:47 2011
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 0985D3A69FB for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 11:44:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.899
X-Spam-Level: 
X-Spam-Status: No, score=-102.899 tagged_above=-999 required=5 tests=[AWL=-0.300, 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 wezLGFjOx8qw for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 11:44:45 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 914BE3A6810 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 27 Jan 2011 11:44:45 -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 p0RJPAua020832; Thu, 27 Jan 2011 11:25:11 -0800 (PST)
Received: from mail-ww0-f42.google.com (mail-ww0-f42.google.com [74.125.82.42]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0RJOSpF020651 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 27 Jan 2011 11:24:38 -0800 (PST)
Received: by wwi17 with SMTP id 17so126648wwi.3 for <rbridge@postel.org>; Thu, 27 Jan 2011 11:24:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=3C03vRFvZhxxj7CLXwXz/sEO/Y9oGq2VubZNTQfguBE=; b=LRKxygLvaBLtAQmCyUDIsfG/s++PWfzbI+5G7XpDjwSNsVYpcx7rGDRJMnl2F6dMkx 9dlCyRqgLqHCTbktpQRqmHuHCjK8EQ5XQOQTzyCiGH6o01uaXnpVvOkIF5D1eis5smRC xGtiuOg57FLUyClBzLZzui1S7DB3RkSP7gO2g=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=hpsb0fJuXCxWGJ2v8UGPFwUVI8i8pGXl8JbAzsLwbIL9qXgw/KXh+M9/QElfntJVXi ZV5rTxNSvtXXro75Y/cw5YMFbZDR84Y+t37YZbEiUaGP4JfN+MYZtL0BidN9YQ8T3i8j BaRU2BgBD5z5L/FAf+6uzGzjF2eccINNYL1X4=
Received: by 10.227.201.5 with SMTP id ey5mr1532217wbb.182.1296156267716; Thu, 27 Jan 2011 11:24:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Thu, 27 Jan 2011 11:24:07 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 27 Jan 2011 14:24:07 -0500
Message-ID: <AANLkTikWNuQJQU9fFuGVNVPy1AicMSp37+rqffsMW9Xm@mail.gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, rbridge@postel.org
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0RJOSpF020651
Subject: [rbridge] trill-adj Section 4 comments
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Response to some comments by Les Ginsberg:

> Section 4
> ----------

> There needs to be a description of the DRB election process -
> equivalent to what is in [IS-IS] Section 8.4.5. For example, the set
> of DRB candidates includes all RBs to which the local system has an
> adjacency in Detect, 2-way, or Report State ...correct?

I'm certainly willing to re-word it, but it seems to me that the
following existing paragraph says what is needed:

   Determination of events 3 and 4 occurs by comparing priorities (with
   neighbor MAC address (SNPA) as a tie breaker and Port ID as a
   secondary tie breaker) across all entries in the port's adjacency
   table including those in the Detect and 2-Way states as well as those
   in the Report state.

I could make this into a separate sub-section, add references to it,
and perhaps re-word as follows:

   Events 3 and 4 consistute losing and winning the DRB election at
   the port, respectivly.

   The candidates are the local RBridge and all RBridges with which
   there is an adjacency on the port in a state other than Down. The
   winner is the RBridge with highest priority to be DRB, as
   determined from the 7-bit priority field in the Hellos received and
   the local port's priority to be DRB field, with MAC address (SNPA)
   as a tie breaker and Port ID as a secondary tie breaker. These
   fields are compared as unsigned inteered with the larger magnitude
   being considered higher priority.

> You also need to specify in what DRB election states a DRB reports
> neighbors in pseudo-node LSPs. It would seem that if neighbors are
> advertised in pre-DRB state that we could attract traffic which we
> are not yet able to forward.

An RBridge in DRB or Pre-DRB state (unless it is asserting bypass
pseudonode) report all adjacencies in the Report state in pseudo-node
LSPs. Perhaps "Pre-DRB" should be renamed "Inh-DRB" for inhibited
DRB. An RBridge in either Pre-DRB or DRB states is the Designated
RBridge for the link. It is just that in "Pre-DRB" it can't ingress or
egress native frames. In any state other than Down, it can handle
TRILL Data frames just fine.

Note the existing description of "Pre-DRB":

         The port has become DRB but is in a pre-forwarding state with
         regard to native frames and is inhibited from ingressing or
         egressing them.

> Section 4.2
> -----------

> When a DRB change causes a change in D-VLAN, the draft says:

      o  The non-Designated VLAN Hello Holding timer is set to the
         maximum of its time to expiration and the time to expiration of
         the Designated VLAN Hello Holding timer.

> The "Designated VLAN Hello Holding timer" referred to is the OLD
> Designated VLAN Hello Holding timer, correct? If so adding that
> clarification would help.

I don't like "old". How about if I change "the Designated VLAN Hello
Holding timer" to "the pre-existing Designated VLAN Hello Holding
timer".

> Also, if we are NOT DRB and the new D-VLAN is NOT in the set of
> announcing VLANs then the non-DRBs have to include the new D-VLAN in
> the set of VLANS for which they send hellos, correct? This should be
> specified.

The specification of what VLANs you send Hellos on is seems quite
clear in the TRILL base protocol standard Section 4.4.3. An RBridge
port not configured as point-to-point always sends TRILL Hellos on the
Designated VLAN, except where that VLAN is actually disabled at the
port, and the Announcing VLANs set has no effect on that.

> It is alpso apparent that DRB changes are very disruptive - even more
> so than at Layer 3. In Layer 3 on a DIS change optimal behavior is
> to do a "make before break" to minimize disruption. However, that is
> not possible here as all adjacencies will go into "Detect" state
> following a DRB change. Should it be recommended then to avoid DRB
> changes whenever possible (e.g.  by setting LAN priority)?

I don't see how a DRB change is any more disruptive to TRILL Data than
a Layer 3 DIS change is to Layer 3 data forwarding. As above, perhaps
it needs to be clarified that the purpose of the Pre-DRB state is just
to temporarily inhibit ingress and egress of native frames.

A change in Designated VLAN is somewhat disruptive. Could add at the
end of Section 4.2 "Because of the temporary disruption caused by a
change in the Designated VLAN on a link that has multiple RBridges
attached, it is RECOMMENDED that all RBridges attached to a link have
the same desired Designated VLAN for their ports on that link."

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Thu Jan 27 12:53:28 2011
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 E64C53A6A51 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 12:53:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, 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 izExrgfGdSVg for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 12:53:27 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id ADF2E3A695D for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 27 Jan 2011 12:53:27 -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 p0RKcMG3006124; Thu, 27 Jan 2011 12:38:23 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0RKboto006030 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Thu, 27 Jan 2011 12:38:01 -0800 (PST)
Received: from [75.150.68.97] (carlson [75.150.68.97]) (authenticated bits=0) by carlson.workingcode.com (8.14.2+Sun/8.14.4) with ESMTP id p0RKYalG011575 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jan 2011 15:34:36 -0500 (EST)
Message-ID: <4D41D6DC.2040406@workingcode.com>
Date: Thu, 27 Jan 2011 15:34:36 -0500
From: James Carlson <carlsonj@workingcode.com>
User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:1.9.1.7) Gecko/20100214 Lightning/1.0b1 Thunderbird/3.0.1
MIME-Version: 1.0
To: William Allen Simpson <william.allen.simpson@gmail.com>
References: <4D415111.4010009@gmail.com> <4D41ABED.5070308@gmail.com>
In-Reply-To: <4D41ABED.5070308@gmail.com>
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [Pppext] proposed TRILL IS-IS System ID text
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

On 01/27/11 12:31, William Allen Simpson wrote:
> On 1/27/11 6:03 AM, William Allen Simpson wrote:
>> 3. An implementation that has only PPP links might have no previously
>> configured Media Access Control (MAC) that can function as an
>> IS-IS System ID. In this case, the System ID is formed by adding
>> a randomly generated 14-bit leading number (in place of an OUI) to
>> the link's unique LCP Magic Number. The Magic Number MUST be
>> unique for all links and all known link peers. This pseudo-MAC
>> MUST have both the "locally-assigned" and "broadcast/multicast"
>> (group) bits set to 1; that is, the least significant two bits of
>> the most significant octet are both set to 1.
>>
> Looking at this again, and remembering how fanatic the new RFC Editors (TM)
> are about abbreviations, probably needs to expand OUI, too:
> 
>                .... In this case, the System ID is formed by appending
>   the link's unique 32-bit LCP Magic Number after a randomly generated
>   14-bit number in place of an Organizationally Unique Identifier (OUI).
> 
> [Also makes the number of bits explicit: N/2**23 birthday attack;
> considerably less than having 2 identical MACs from the same vendor, or
> being killed by lightning.  Could put that in the Security Considerations?]

[Sorry for the duplicate on the PPP list; Thunderbird hurt me with the
CC-list again.]

Yes, I see where you're going with this.  I don't think it's a
"Security" issue.  It's actually a correctness issue -- if there are
duplicates, then IS-IS falls down.

That aside, what you're suggesting is still a bit uncomfortable to me.
You're essentially saying that this draft can forge up a new way of
creating IS-IS System IDs on its own just to be helpful.  I'm not so
sure that it can or should.  I think it's out of scope.

While I certainly agree that, if implemented properly (and if existing
system architectures allow implementation), what you're describing
should work nicely, I don't want to run afoul of the IS-IS folks by
tromping so squarely on their turf.

In particular, IS-IS simply mandates that System IDs must be unique
across the domain in which they're used.  Not that they're "extremely
unlikely to be duplicated" -- but that they're _never_ duplicated.  The
existing protocol clearly puts the responsibility for that in the hands
of system implementers, not the link layer designers.

Now, you're certainly within your rights to claim that MAC addresses are
a feeble mechanism, and you may well be right that there are systems
that duplicate them (though I can't say *I* have ever seen this), but
the ISO people behind IS-IS appear (to me at least) to think
differently.  It's not a matter of statistics, or of field experience,
but of specification.

Instead, I think the issue you're talking about is really a fundamental
issue in IS-IS itself, and is not one that is created by or altered by
or in any way related to PPP or TRILL.  IS-IS already supports
point-to-point links without PPP or TRILL.  And if you were to build an
IS-IS router with only point-to-point links and without some source of a
System ID, you would run into exactly this problem.  But as the links on
this hypothetical router are just plain old point-to-point links, you
would not have the benefit of the mechanism you're proposing to have to
this draft.

And the same problem occurs if you run an IS-IS router with only PPP
links using OSINLCP.  So, it's not specifically a TRILL issue.

It's the same problem, and it's not something that I think we ought to
be addressing.  We can certainly call it out, though.

I think that if this is to be addressed -- it's probably the least
important issue I can imagine in TRILL, and likely needs no fixing at
all, as I strongly suspect that real systems won't have the problem --
it should be addressed in the TRILL IS-IS document, or perhaps in the
base IS-IS documents themselves.  It's IS-IS itself that demands a
single unique System ID (PPP frankly doesn't care), and it's TRILL that
demands zero configuration.

At a minimum, I want to hear from IS-IS and TRILL experts before I go
ahead with proposing any new random-number-based System ID mechanism.
If they sign on, then I'll go ahead with it.

But my off-the-cuff guess is that they'll have objections, and more
objections probably aren't helpful in getting to consensus.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Thu Jan 27 19:10:35 2011
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 54B963A6B87 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 19:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.895
X-Spam-Level: 
X-Spam-Status: No, score=-102.895 tagged_above=-999 required=5 tests=[AWL=-0.296, 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 SSzw6LzcsMu5 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 27 Jan 2011 19:10:34 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 53DEE3A6B86 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 27 Jan 2011 19:10:31 -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 p0S2qn7D015732; Thu, 27 Jan 2011 18:52:50 -0800 (PST)
Received: from mail-ww0-f52.google.com (mail-ww0-f52.google.com [74.125.82.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0S2qWwO015709 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 27 Jan 2011 18:52:42 -0800 (PST)
Received: by wwd20 with SMTP id 20so3157165wwd.21 for <rbridge@postel.org>; Thu, 27 Jan 2011 18:52:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=M3q/lpzE/EuQ36652LT4QyKQyfg1vY6SXP6LXE+T+n4=; b=MXoO5Q6svuksJYrIsING8YogTiLoQB5kHM5YWor39pj+JjtHPlYGl+y3ITaQmuwVIg 4WyYkTCKZvoKFbSsp3tjnaALt6UGNbZ+bdL1P6MMCtpuUpp3+uADnJ0HOV16NN7qHBUj yxsjK0Od3vLtwMfTkY1/z3yiLGiC9gQaS6bU4=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type :content-transfer-encoding; b=aO+9dgkUfu9crEthvGflTJfPRGrLMORMTpbkHRdSgIFIuX2UaECRag3s3vv4IlJWj9 lpVaYG/pFFRbFgYdWcB1mkPMuY0XBZiF96hkA09t+fz+9vn+fphLe3VaLUnZ3UNUs76T 5IbMIGWk8emxMrhPAOXHQDX7tppq3rN8VGJ9E=
Received: by 10.227.145.139 with SMTP id d11mr2042190wbv.8.1296183151688; Thu, 27 Jan 2011 18:52:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Thu, 27 Jan 2011 18:52:11 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 27 Jan 2011 21:52:11 -0500
Message-ID: <AANLkTini2Q1rwYFjETFkqLs1710n1BzfRmndGqMsT=UQ@mail.gmail.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, rbridge@postel.org
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: d3e3e3@gmail.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0S2qWwO015709
Subject: [rbridge] trill-adj Section 3.3 comments
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Response to some comments by Les Ginsberg:

> Section 3.3
> -------------

> Text says that for hellos received on a VLAN Other than the D-VLAN

> "any TRILL Neighbor TLV in such a Hello is ignored..."

> I assume this means that it is an implementation choice as to
> whether to include the neighbor TLV in such hellos? A clear
> statement of this would be helpful.

To avoid the posibility of temporary confusion if there is a change in
the Designated VLAN, the TRILL Neighbor TLV sent on a VLAN should
reflect the neighbors seen on that VLAN. Since an implementation
conformant to this draft is only assured of having per VLAN neighbor
information for the Deisgnated VLAN, I think something like the
following should be added in Section 7.2:

"The TRILL Neighbor TLV sent on a VLAN MUST show the neighbor
information, as sensed by the transmitting RBridge, on that
VLAN. Since implementations conformant to this document maintain such
information on a per VLAN basis only for the Designated VLAN, such
implementations only send the TRILL Neighbor TLV in TRILL Hellos on
the Deisgnated VLAN."

You could imagine an implementation that kept more state and had
neighbor information for multiple VLANs but it doesn't seem worth going
into that.

Thanks,
Donald
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
=A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
=A0155 Beaver Street
=A0Milford, MA 01757 USA
=A0d3e3e3@gmail.com

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Fri Jan 28 11:33:54 2011
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 564A23A6969 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 28 Jan 2011 11:33:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.486
X-Spam-Level: 
X-Spam-Status: No, score=-102.486 tagged_above=-999 required=5 tests=[AWL=0.113, 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 VK8MGyceUaUr for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 28 Jan 2011 11:33:53 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 02C443A696A for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 28 Jan 2011 11:33:52 -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 p0SJELG0000145; Fri, 28 Jan 2011 11:14:22 -0800 (PST)
Received: from carlson.workingcode.com (carlson.workingcode.com [75.150.68.97]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0SJDawQ000022 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <rbridge@postel.org>; Fri, 28 Jan 2011 11:13:46 -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 p0SJAD2d001235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Jan 2011 14:10:14 -0500 (EST)
Message-ID: <4D431494.6090906@workingcode.com>
Date: Fri, 28 Jan 2011 14:10:12 -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: <4D415111.4010009@gmail.com> <4D41ABED.5070308@gmail.com> <4D41D6DC.2040406@workingcode.com> <4D430123.8010101@gmail.com>
In-Reply-To: <4D430123.8010101@gmail.com>
X-DCC-x.dcc-servers-Metrics: carlson; whitelist
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: carlsonj@workingcode.com
Cc: pppext@ietf.org, rbridge@postel.org
Subject: Re: [rbridge] [Pppext] proposed TRILL IS-IS System ID text
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

William Allen Simpson wrote:
> On 1/27/11 3:34 PM, James Carlson wrote:
>> That aside, what you're suggesting is still a bit uncomfortable to me.
>> You're essentially saying that this draft can forge up a new way of
>> creating IS-IS System IDs on its own just to be helpful.  I'm not so
>> sure that it can or should.  I think it's out of scope.
>>
> It's a point-to-point link specific issue.  In the IETF, it belongs in a
> PPP document.  In the past, we had enough on our plates to ensure our
> *own* protocols worked.  We didn't fuss about some other organization.

The leap I think your argument might be making is that PPP is the only
possible point-to-point protocol over which IS-IS would run, and that
this is thus the right place to write this specification.

I strongly disagree.

The existing OSINLCP in PPP allows you to run IS-IS over PPP *TODAY*,
and the problem you're citing isn't solved.  Moreover, it isn't solved
even if I put this special text into the draft under consideration,
because this draft addresses only TRILL usage of PPP.  And it's not
fixed when IS-IS is run over _other_ point-to-point media.

In other words, it's an IS-IS issue, not a PPP issue.

>> While I certainly agree that, if implemented properly (and if existing
>> system architectures allow implementation), what you're describing
>> should work nicely, I don't want to run afoul of the IS-IS folks by
>> tromping so squarely on their turf.
>>
> It's a sad comment on the IETF that it's become so fussy about "turf"!
> 
> Remember the fights with ANSI T1 about defining a link layer over "their"
> bits?  Or defining PPP over SONET/SDH (with two competing bodies)?
> 
> Let's just get the job done.

If you don't like the word, then I can certainly use another.

IS-IS operation is simply outside the purview of the IETF PPP Extensions
working group.  It's got nothing to do with us.  We don't define IS-IS
any more than we define SONET/SDH.  We just live with it.

I believe the best we can reasonably do here is say, gee, IS-IS people,
it looks like you have a possibly ugly hole in your specification.  If
you care about it, please fix it, because we can't fix it for you.  As a
bonus, we can offer you these bits from our neck of the woods, if
they'll help.

>> In particular, IS-IS simply mandates that System IDs must be unique
>> across the domain in which they're used.  Not that they're "extremely
>> unlikely to be duplicated" -- but that they're _never_ duplicated.  The
>> existing protocol clearly puts the responsibility for that in the hands
>> of system implementers, not the link layer designers.
>>
> I cannot "clearly" find that "responsibility" anywhere in RFC-1142.  Please
> cite references.

How about 7.1.1, where it's defined?

  ID, a 6 octet system identification. Correct operation of the routeing
  protocol requires that this field be unique within an area for End
  Systems and Level 1 Intermediate systems, and unique within the
  routeing domain for Level 2 Intermediate systems.

It's unique; end of story.  It doesn't say "you must demand this from
your link layer interfaces."  It doesn't say "you can optionally create
one out of thin air by generating random numbers if you want."  It
doesn't even say whether administrative intervention is needed or desired.

That puts it in the hands of the implementer.

> It is the responsibility of protocol designers to completely specify the
> protocol, including error recovery!  Only after changing to a prescriptive
> specification, PPP achieved wide-spread interoperability in '91.

I agree, and I believe I've done that here.

I think the only way I can comply with your demand is to put text like
this into the draft:

	If the TRILL implementation using PPP links also uses IS-IS,
	then the IS-IS implementation MUST have a network-wide unique
	System ID.  Commonly, this is derived from a link layer MAC
	address (which is not available on PPP) or from a system-wide
	MAC address (which may be available on certain systems).
	Acceptable means of determining a System ID for this use are
	covered in the IS-IS and TRILL IS-IS documentation.

In other words, call out the issue, and effectively outlaw (via "MUST")
the degenerate mode of operation where a system has only PPP links and
_also_ has no means of getting a system-wide identifier.

> Apparently, you've never operated an ISP, nor read the NANOG list.

I refuse to respond to ad hominem attacks.  Stick to the topic, please.

>> It's the same problem, and it's not something that I think we ought to
>> be addressing.  We can certainly call it out, though.
>>
> If you insist on waiting for ISO to issue a specification, then arguably
> you MUST wait to publish this document, as that would be a Normative
> Reference....

I don't understand what you're saying.  How is it Normative?

What part of this specification changes in any way depending on what the
IS-IS folks decide to do about this decades-old hole in their document?

Do any of the PPP bits on the wire change as a result?  Are there any
configuration option changes?  Or new packet formats?  Or state machine
variations?

I see no dependency here at all, so no way the reference you're
requiring could be Normative.  It does not define the protocol.

>> At a minimum, I want to hear from IS-IS and TRILL experts before I go
>> ahead with proposing any new random-number-based System ID mechanism.
>> If they sign on, then I'll go ahead with it.
>>
>> But my off-the-cuff guess is that they'll have objections, and more
>> objections probably aren't helpful in getting to consensus.
>>
> We don't have consensus now.

In observing the TRILL discussions with the IS-IS group, it seemed clear
to me that making changes to IS-IS (beyond adding a few new data types)
was not a substantial area of interest.

I still don't see why any sort of System ID fabrication mechanism needs
to be part of this specification.  It's not a requirement that any given
TRILL implementation uses IS-IS.  And even if a given TRILL/IS-IS system
doesn't have PPP links, the implementor already has substantial issues
to resolve in getting the System ID right.  (E.g., dealing with hot-swap
hardware is a very interesting problem.)

I do not believe it's PPP's fault if a given IS-IS implementation can't
get the System ID it needs to run.  It wouldn't be Ethernet's fault,
either, if the implementor doesn't know how to deal with hot-swap, and
uses a "bad" MAC address as a result.

I think the fix you're proposing just polishes the tip of an iceberg.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Jan 31 02:03:07 2011
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 4BBFC3A68EF for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 31 Jan 2011 02:03:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.191
X-Spam-Level: 
X-Spam-Status: No, score=-5.191 tagged_above=-999 required=5 tests=[AWL=-2.592, 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 lEqG7EyDRGhG for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 31 Jan 2011 02:03:05 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id DAB6C3A68D8 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 31 Jan 2011 02:03:05 -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 p0V9l2p6023035; Mon, 31 Jan 2011 01:47:03 -0800 (PST)
Received: from sj-iport-5.cisco.com (sj-iport-5.cisco.com [171.68.10.87]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0V9k5p4022641 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 31 Jan 2011 01:46:14 -0800 (PST)
Authentication-Results: sj-iport-5.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As4DAOITRk2rR7H+/2dsb2JhbACWFo5gc6BUmlKDEYI9BIUTilmDEQ
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-5.cisco.com with ESMTP; 31 Jan 2011 09:44:50 +0000
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0V9ior0004889; Mon, 31 Jan 2011 09:44:50 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 31 Jan 2011 01:44:50 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 31 Jan 2011 01:44:44 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D323EC9@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTikWNuQJQU9fFuGVNVPy1AicMSp37+rqffsMW9Xm@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: trill-adj Section 4 comments
Thread-Index: Acu+V9VxFFAOQorUQf2hEZGf8b9EywCzOgpQ
References: <AANLkTikWNuQJQU9fFuGVNVPy1AicMSp37+rqffsMW9Xm@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>, <rbridge@postel.org>, <isis-wg@ietf.org>
X-OriginalArrivalTime: 31 Jan 2011 09:44:50.0273 (UTC) FILETIME=[8107FD10:01CBC12B]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0V9k5p4022641
Subject: Re: [rbridge] trill-adj Section 4 comments
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Donald -

Thanx for the response.
Please include the IS-IS WG on all emails associated with trill-adj review =
comments.

Inline.

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Thursday, January 27, 2011 11:24 AM
> To: Les Ginsberg (ginsberg); rbridge@postel.org
> Subject: trill-adj Section 4 comments
> =

> Response to some comments by Les Ginsberg:
> =

> > Section 4
> > ----------
> =

> > There needs to be a description of the DRB election process -
> > equivalent to what is in [IS-IS] Section 8.4.5. For example, the set
> > of DRB candidates includes all RBs to which the local system has an
> > adjacency in Detect, 2-way, or Report State ...correct?
> =

> I'm certainly willing to re-word it, but it seems to me that the
> following existing paragraph says what is needed:
> =

>    Determination of events 3 and 4 occurs by comparing priorities (with
>    neighbor MAC address (SNPA) as a tie breaker and Port ID as a
>    secondary tie breaker) across all entries in the port's adjacency
>    table including those in the Detect and 2-Way states as well as
> those
>    in the Report state.

Given that you have introduced new adjacency states, it would help if you h=
ad more explicit language. See ISO 10589 Section 8.4.5d.

> =

> I could make this into a separate sub-section, add references to it,
> and perhaps re-word as follows:
> =

>    Events 3 and 4 consistute losing and winning the DRB election at
>    the port, respectivly.
> =

>    The candidates are the local RBridge and all RBridges with which
>    there is an adjacency on the port in a state other than Down. The
>    winner is the RBridge with highest priority to be DRB, as
>    determined from the 7-bit priority field in the Hellos received and
>    the local port's priority to be DRB field, with MAC address (SNPA)
>    as a tie breaker and Port ID as a secondary tie breaker. These
>    fields are compared as unsigned inteered with the larger magnitude
>    being considered higher priority.

Yes - something like this would be good.

> =

> > You also need to specify in what DRB election states a DRB reports
> > neighbors in pseudo-node LSPs. It would seem that if neighbors are
> > advertised in pre-DRB state that we could attract traffic which we
> > are not yet able to forward.
> =

> An RBridge in DRB or Pre-DRB state (unless it is asserting bypass
> pseudonode) report all adjacencies in the Report state in pseudo-node
> LSPs. Perhaps "Pre-DRB" should be renamed "Inh-DRB" for inhibited
> DRB. An RBridge in either Pre-DRB or DRB states is the Designated
> RBridge for the link. It is just that in "Pre-DRB" it can't ingress or
> egress native frames. In any state other than Down, it can handle
> TRILL Data frames just fine.
> =

> Note the existing description of "Pre-DRB":
> =

>          The port has become DRB but is in a pre-forwarding state with
>          regard to native frames and is inhibited from ingressing or
>          egressing them.

This is exactly my point. If there is two way connectivity and the reachabl=
e VLAN/MAC addresses have been advertised by the respective appointed forwa=
rders, then traffic will be attracted even though it cannot be delivered. I=
s this desirable? If the pseudo-node LSP did NOT advertise neighbors in pse=
udo-node LSPs then such packets could be dropped closer to the source until=
 the pre-forwarding state had expired.

> =

> > Section 4.2
> > -----------
> =

> > When a DRB change causes a change in D-VLAN, the draft says:
> =

>       o  The non-Designated VLAN Hello Holding timer is set to the
>          maximum of its time to expiration and the time to expiration
> of
>          the Designated VLAN Hello Holding timer.
> =

> > The "Designated VLAN Hello Holding timer" referred to is the OLD
> > Designated VLAN Hello Holding timer, correct? If so adding that
> > clarification would help.
> =

> I don't like "old". How about if I change "the Designated VLAN Hello
> Holding timer" to "the pre-existing Designated VLAN Hello Holding
> timer".

What I want clarified is that the Designated VLAN Holding timer mentioned h=
ere is associated with the D-VLAN specified by the "old DRB" - not the new =
DRB. How about:

"the Designated VLAN Hello Holding Timer associated with the D-VLAN specifi=
ed by the previous DRB"

??


> =

> > Also, if we are NOT DRB and the new D-VLAN is NOT in the set of
> > announcing VLANs then the non-DRBs have to include the new D-VLAN in
> > the set of VLANS for which they send hellos, correct? This should be
> > specified.
> =

> The specification of what VLANs you send Hellos on is seems quite
> clear in the TRILL base protocol standard Section 4.4.3. An RBridge
> port not configured as point-to-point always sends TRILL Hellos on the
> Designated VLAN, except where that VLAN is actually disabled at the
> port, and the Announcing VLANs set has no effect on that.

Yes - but as this specification is attempting to fully describe the operati=
on of the adjacency machinery it seems worth including explicit language he=
re - rather than requiring people to go to another document. It may be comm=
onplace for all Rbridges to be configured with the same D-VLAN, but for cas=
es where that is NOT the case (which is of course necessary for a D-VLAN ch=
ange to be possible at all) it is a requirement for all Rbridges on the LAN=
 to send hellos on whatever D-VLAN is specified by the DRB - which means Rb=
ridges have to take this action on a DRB change which involves a D-VLAN cha=
nge. Discussing this seems very relevant to the scope of this document.



> =

> > It is alpso apparent that DRB changes are very disruptive - even more
> > so than at Layer 3. In Layer 3 on a DIS change optimal behavior is
> > to do a "make before break" to minimize disruption. However, that is
> > not possible here as all adjacencies will go into "Detect" state
> > following a DRB change. Should it be recommended then to avoid DRB
> > changes whenever possible (e.g.  by setting LAN priority)?
> =

> I don't see how a DRB change is any more disruptive to TRILL Data than
> a Layer 3 DIS change is to Layer 3 data forwarding.

A DRB change will cause a pre-forwarding timer to be started - which means =
that native frames will not be deliverable for some period of time. This de=
lay/black-holing period does not occur at Layer 3 - which is why I say a DR=
B change in TRILL is more disruptive as you have deliberately designed in a=
 black-holing period as a safety mechanism. This argues that we should avoi=
d unnecessary DRB changes.

   Les


> As above, perhaps
> it needs to be clarified that the purpose of the Pre-DRB state is just
> to temporarily inhibit ingress and egress of native frames.
> =

> A change in Designated VLAN is somewhat disruptive. Could add at the
> end of Section 4.2 "Because of the temporary disruption caused by a
> change in the Designated VLAN on a link that has multiple RBridges
> attached, it is RECOMMENDED that all RBridges attached to a link have
> the same desired Designated VLAN for their ports on that link."
> =

> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> =A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
> =A0155 Beaver Street
> =A0Milford, MA 01757 USA
> =A0d3e3e3@gmail.com

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Jan 31 02:34:21 2011
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 81D513A68F5 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 31 Jan 2011 02:34:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.159
X-Spam-Level: 
X-Spam-Status: No, score=-5.159 tagged_above=-999 required=5 tests=[AWL=-2.560, 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 b1ISxWwZWEXh for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 31 Jan 2011 02:34:19 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 91A4A3A68ED for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 31 Jan 2011 02:34:19 -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 p0VAKbD3029103; Mon, 31 Jan 2011 02:20:38 -0800 (PST)
Received: from sj-iport-6.cisco.com (sj-iport-6.cisco.com [171.71.176.117]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p0VAJwa5029032 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 31 Jan 2011 02:20:07 -0800 (PST)
Authentication-Results: sj-iport-6.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: As4DABYcRk2rR7H+/2dsb2JhbACWFo5gc6B1ml2DEYI9BIUTilmDEQ
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-6.cisco.com with ESMTP; 31 Jan 2011 10:19:58 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p0VAJw0f028801; Mon, 31 Jan 2011 10:19:58 GMT
Received: from xmb-sjc-222.amer.cisco.com ([128.107.191.106]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675);  Mon, 31 Jan 2011 02:19:58 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 31 Jan 2011 02:19:51 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D323ECB@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTini2Q1rwYFjETFkqLs1710n1BzfRmndGqMsT=UQ@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: trill-adj Section 3.3 comments
Thread-Index: Acu+ln57gRAhYZWuQKy5t7TTDghVoQCmAdPQ
References: <AANLkTini2Q1rwYFjETFkqLs1710n1BzfRmndGqMsT=UQ@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>, <rbridge@postel.org>, <isis-wg@ietf.org>
X-OriginalArrivalTime: 31 Jan 2011 10:19:58.0332 (UTC) FILETIME=[698843C0:01CBC130]
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ginsberg@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p0VAJwa5029032
Subject: Re: [rbridge] trill-adj Section 3.3 comments
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Donald -

Thanx for the response.
Please include the IS-IS WG on all emails associated with trill-adj review =
comments.

Inline.


> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Thursday, January 27, 2011 6:52 PM
> To: Les Ginsberg (ginsberg); rbridge@postel.org
> Subject: trill-adj Section 3.3 comments
> =

> Response to some comments by Les Ginsberg:
> =

> > Section 3.3
> > -------------
> =

> > Text says that for hellos received on a VLAN Other than the D-VLAN
> =

> > "any TRILL Neighbor TLV in such a Hello is ignored..."
> =

> > I assume this means that it is an implementation choice as to
> > whether to include the neighbor TLV in such hellos? A clear
> > statement of this would be helpful.
> =

> To avoid the posibility of temporary confusion if there is a change in
> the Designated VLAN, the TRILL Neighbor TLV sent on a VLAN should
> reflect the neighbors seen on that VLAN. Since an implementation
> conformant to this draft is only assured of having per VLAN neighbor
> information for the Deisgnated VLAN, I think something like the
> following should be added in Section 7.2:
> =

> "The TRILL Neighbor TLV sent on a VLAN MUST show the neighbor
> information, as sensed by the transmitting RBridge, on that
> VLAN. Since implementations conformant to this document maintain such
> information on a per VLAN basis only for the Designated VLAN, such
> implementations only send the TRILL Neighbor TLV in TRILL Hellos on
> the Deisgnated VLAN."
> =

> You could imagine an implementation that kept more state and had
> neighbor information for multiple VLANs but it doesn't seem worth going
> into that.

Yes - I agree.

Section 3.2 states:

      o  Two Hello holding timers, each consisting of an 16-bit unsigned
         integer number of seconds: a Designated VLAN holding timer and
         a non-Designated VLAN holding timer.

This text indicates that adjacencies are NOT per VLAN - but that a timer is=
 kept indicating the reception of hellos on a VLAN other than the D-VLAN. W=
hich raises the question as to whether this timer simply tracks reception o=
f a hello on all VLANs other than the D-VLAN (which is what I thought) or i=
s meant to be a separate timer for each VLAN other than the D-VLAN.

Your response indicates that if an implementation were to send neighbor inf=
ormation in a hello sent on a VLAN other than the D-VLAN that it MUST refle=
ct only those neighbors seen on that VLAN - which makes sense to me - but w=
ould require that the implementation have a VLAN specific timer. =


I think your suggested text helps a lot and is definitely needed.

   Les

> =

> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
> =A0Donald E. Eastlake 3rd=A0=A0 +1-508-333-2270 (cell)
> =A0155 Beaver Street
> =A0Milford, MA 01757 USA
> =A0d3e3e3@gmail.com

_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge
