
From rbridge-bounces@postel.org  Wed Feb  2 11:27: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 119FA3A6D35 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed,  2 Feb 2011 11:27:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.897
X-Spam-Level: 
X-Spam-Status: No, score=-104.897 tagged_above=-999 required=5 tests=[AWL=1.702, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 bF9iwWnvP7fL for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed,  2 Feb 2011 11:27:21 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id E80BD3A6BEE for <trill-archive-Osh9cae4@lists.ietf.org>; Wed,  2 Feb 2011 11:27:20 -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 p12J75qu021991; Wed, 2 Feb 2011 11:07:06 -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 p12J6jnc021938 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Wed, 2 Feb 2011 11:06:55 -0800 (PST)
Received: by wwd20 with SMTP id 20so313548wwd.21 for <rbridge@postel.org>; Wed, 02 Feb 2011 11:06:44 -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:content-type:content-transfer-encoding; bh=6CCjPBtyUXRoxxPnXEUDZdyM96omOub0d2/LHfWGYos=; b=oBpBexROEwDGPHOtdBbMPCTQYUaBbMj1yNDDnV9XFCeJvodQXq3dv00/T8mvcLtBj7 Ub7V7F8Vc6jv14ruWbCm3Vbxh48wxVf6sHRKFBYXbsJTV6o8aNSETtyzMZboV8ux4SFx oenrwv9euip3r0xn2g6HQMGt2mGTF9tlhUE4o=
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=VFm53mMkWXOIAMVZWlfzhCs/7dny2Efx8zUzDM6ssIjHchKcIwkhxRVQWTtmvKaVGx UwTkvQuyXk257szIqg5f86aYn0GYhAqrUuLUu64OCFPjpqKihVqLrJVP4tTIJqY4/0of sEIFMjDSs8pUs/ptzAF36qi2NsnB0Mt7Zc2yg=
Received: by 10.227.143.198 with SMTP id w6mr9592590wbu.37.1296673604869; Wed, 02 Feb 2011 11:06:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Wed, 2 Feb 2011 11:06:24 -0800 (PST)
In-Reply-To: <20110202190003.2525.47.idtracker@localhost>
References: <20110202190003.2525.47.idtracker@localhost>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 2 Feb 2011 14:06:24 -0500
Message-ID: <AANLkTi=sNMax7D_+u+hF248sVP4WO8rhxRgY7P1dmPao@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 p12J6jnc021938
Subject: [rbridge] Fwd: [Isis-wg] I-D Action:draft-ietf-isis-trill-05.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

From:  <Internet-Drafts@ietf.org>
Date: Wed, Feb 2, 2011 at 2:00 PM
Subject: [Isis-wg] I-D Action:draft-ietf-isis-trill-05.txt
To: i-d-announce@ietf.org
Cc: isis-wg@ietf.org

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
This draft is a work item of the IS-IS for IP Internets Working Group
of the IETF.

=A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : TRILL Use of IS-IS
=A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : D. Eastlake 3rd, et al.
=A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-isis-trill-05.txt
=A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 30
=A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-02-02

The IETF has standardized the TRILL protocol, which provides
transparent Layer 2 forwarding using encapsulation with a hop count
and IS-IS link state routing. This document specifies the data
formats and code points for the IS-IS extensions to support TRILL.

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

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

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

From rbridge-bounces@postel.org  Fri Feb  4 17:02: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 499F73A6405 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri,  4 Feb 2011 17:02:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.477
X-Spam-Level: 
X-Spam-Status: No, score=-4.477 tagged_above=-999 required=5 tests=[AWL=1.500, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
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 mZjYec7UcP+g for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri,  4 Feb 2011 17:02:21 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id EDF773A65A5 for <trill-archive-Osh9cae4@lists.ietf.org>; Fri,  4 Feb 2011 17:02: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 p1511twp023426; Fri, 4 Feb 2011 17:01:56 -0800 (PST)
Received: from mail-yi0-f52.google.com (mail-yi0-f52.google.com [209.85.218.52]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p1511arC023405 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Fri, 4 Feb 2011 17:01:45 -0800 (PST)
Received: by yic1 with SMTP id 1so1144216yic.39 for <rbridge@postel.org>; Fri, 04 Feb 2011 17:01:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=4lX+DodPWi3qohRuOpyfq9mmzwJTMQ+wTiLNJ4ZJCRc=; b=PmbZ0eKcxdxXhD49HtgX1vHBMSVaBTGW89djBLGepP0pTCGIz9vtwdkfUvDwUKmtE+ 9YRf7yGCdQWkz1g7+nyhq2fl5YVKA4a45OfPCBhpycENkS4n0EdfEKeb/G5Q7zPjdVBv LHnwhhBhYxArKoNcYbM46Vg3/qs+6Nrmdujgg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=IBBSUS9wmQhl8l+6+fh1T+tmF6UBsJguxTs79HU/fHs1ghvgigeSOdoHvl3tCjxGoj C2djNAiZ70Jl/upzZmFtKyfKovQmo8ZFTv/PvZU0MYh9pZ4E7BxKgdttcFRkB662vTVc ydiu61iCbd3JM4JcEr2U9/di0dNjpSbDa6vJc=
MIME-Version: 1.0
Received: by 10.147.170.19 with SMTP id x19mr764633yao.3.1296867695403; Fri, 04 Feb 2011 17:01:35 -0800 (PST)
Received: by 10.147.167.20 with HTTP; Fri, 4 Feb 2011 17:01:35 -0800 (PST)
In-Reply-To: <4D41D6DC.2040406@workingcode.com>
References: <4D415111.4010009@gmail.com> <4D41ABED.5070308@gmail.com> <4D41D6DC.2040406@workingcode.com>
Date: Fri, 4 Feb 2011 17:01:35 -0800
X-Google-Sender-Auth: 9D-GR1pbi0MGR-lA8-irvf6MF6E
Message-ID: <AANLkTi=njqz66Ep-Kfn9m=cvHXPpyeH1+W3PznU3f78s@mail.gmail.com>
From: Anoop Ghanwani <anoop@alumni.duke.edu>
To: James Carlson <carlsonj@workingcode.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: ghanwani@gmail.com
Cc: pppext@ietf.org, rbridge@postel.org, William Allen Simpson <william.allen.simpson@gmail.com>
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 Thu, Jan 27, 2011 at 12:34 PM, James Carlson
<carlsonj@workingcode.com> wrote:

> 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.

Coming from the TRILL part of the world, I don't think this is a problem
that needs to be addressed in this draft.  Generating a unique System ID
for IS-IS is an IS-IS problem, and as such should be addressed in the IS-IS
working group.

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

From rbridge-bounces@postel.org  Fri Feb  4 17:53:11 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 49F133A68FD for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri,  4 Feb 2011 17:53:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.92
X-Spam-Level: 
X-Spam-Status: No, score=-104.92 tagged_above=-999 required=5 tests=[AWL=1.679, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 8IxyGv3bLfPk for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri,  4 Feb 2011 17:53:10 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 4DA2D3A687A for <trill-archive-Osh9cae4@lists.ietf.org>; Fri,  4 Feb 2011 17:53:10 -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 p151bRK0029138; Fri, 4 Feb 2011 17:37:28 -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 p151b5ZB029117 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Fri, 4 Feb 2011 17:37:15 -0800 (PST)
Received: by wwd20 with SMTP id 20so3165686wwd.21 for <rbridge@postel.org>; Fri, 04 Feb 2011 17:37:04 -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=C3UQMJTViLw4xLjKEXKpiT7X4aKlCiK9wGCKonGqlVw=; b=eh6VdA1mLcLnDwyU0eNYrY/+tIRYTTbd1mqmANzqFvB9yz4ClxAKPwkkLrgPSxG6ow ud/j5ZhV91sOwPYJGh7fLdW3XcRRSobTH8f0lc6kSW70H8TIYVUDWoRdfiX5tRunTK+R zdBsuM34d9GgMrAHW1gklRIjTjlp15ShcQHF0=
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=vSvRA8Y8mWqsx7R1VudjPF/wHbqVKl/1fethao4+5rfgjHlEf0tdptpvAgAns13rPl FLZ9ncHh8ahZa//gd7+mkoUwZn7R2pFazsQNoJB3JfEGqGkBISrubSxGsFKOSNV6kkYT /1yCAX50u+taYVaE6xKb0WU6JnTkri8XeI5wQ=
Received: by 10.227.201.5 with SMTP id ey5mr4656946wbb.182.1296869824581; Fri, 04 Feb 2011 17:37:04 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Fri, 4 Feb 2011 17:36:44 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D323ECB@xmb-sjc-222.amer.cisco.com>
References: <AANLkTini2Q1rwYFjETFkqLs1710n1BzfRmndGqMsT=UQ@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D323ECB@xmb-sjc-222.amer.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 4 Feb 2011 20:36:44 -0500
Message-ID: <AANLkTikuUAKNUNYz6Pv8wkKEQJsT1zv_rZL4s4g1tovU@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 p151b5ZB029117
Cc: rbridge@postel.org, isis-wg@ietf.org
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

Hi,

On Mon, Jan 31, 2011 at 5:19 AM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
>...
>
>> -----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.

OK.

> Section 3.2 states:
>
> =A0 =A0 =A0o =A0Two Hello holding timers, each consisting of an 16-bit un=
signed
> =A0 =A0 =A0 =A0 integer number of seconds: a Designated VLAN holding time=
r and
> =A0 =A0 =A0 =A0 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. Which raises the question as to whether this timer
> simply tracks reception of a hello on all VLANs other than the
> D-VLAN (which is what I thought) or is meant to be a separate timer
> for each VLAN other than the D-VLAN.

? Adjacencies have to do with the DRB election and the IS-IS topology
for route calculation and the forwarding of TRILL Data. TRILL Data is
only ever forwarded on the Designated VLAN. The text in the current
trill-adj draft is consistent and correct and there is only one timer
per neighbor for all non-Designated VLANs.

> Your response indicates that if an implementation were to send
> neighbor information in a hello sent on a VLAN other than the D-VLAN
> that it MUST reflect only those neighbors seen on that VLAN - which
> makes sense to me - but would require that the implementation have a
> VLAN specific timer.

Right.

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

OK.

> =A0 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

From rbridge-bounces@postel.org  Sun Feb  6 19:16:06 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 5EE4A3A6C8A for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun,  6 Feb 2011 19:16:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.892
X-Spam-Level: 
X-Spam-Status: No, score=-103.892 tagged_above=-999 required=5 tests=[AWL=2.707, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 F4uVuuFLwDIv for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun,  6 Feb 2011 19:16:05 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 6F6EB3A6C70 for <trill-archive-Osh9cae4@lists.ietf.org>; Sun,  6 Feb 2011 19:16: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 p172vMLx005137; Sun, 6 Feb 2011 18:57:23 -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 p172v1Jp005095 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Sun, 6 Feb 2011 18:57:11 -0800 (PST)
Received: by wyb28 with SMTP id 28so4067985wyb.39 for <rbridge@postel.org>; Sun, 06 Feb 2011 18:57:01 -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:cc :content-type:content-transfer-encoding; bh=Eg8YC+aWOjOha7UfpfaidRYDg4Dx4TvLtTGtvxvR9u0=; b=Ud+zPQskqLZjzuXKiE7uZrkVENj7qnTJJcOSfXSYrUQcAc8xa0EJ2P5Llc+Xj3b+13 GMDbK6jV8bJOEJBlL0oTFpYv2fe0/JvmVkppoXP3v6I/DFlOry5J4d6gVAr3Otzmz4p2 /Lgqb7xThZ2jCf2Cbx0VjiSwj78sa8Rp7b4Pc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; b=ojE9ZBJDrkk65cdMmFjFzKxUzuTXAB+u0bQ6O3cXxh0WUADJZh/CI+LLW3rQTu0rSG DP6xI4BXHHfYjq4MmVO1SxZDqRfrzwy1OQoo1tfh7aLKuuWlKy8cVJ8znxw3+nEznAH0 3nD11+dvVlJY1l81kges4+XvIdBOPCXJ9xzRI=
Received: by 10.227.41.204 with SMTP id p12mr8888620wbe.153.1297047420848; Sun, 06 Feb 2011 18:57:00 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Sun, 6 Feb 2011 18:56:40 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 6 Feb 2011 21:56:40 -0500
Message-ID: <AANLkTin=fTG3WA6Uv8o+cwe7gpWE6HB0-OAgkYFL2-bz@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 p172v1Jp005095
Cc: isis mailing list <isis-wg@ietf.org>
Subject: [rbridge] trill-adj
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:

> 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.

Sending Hellos on multiple VLANs doesn't guarantee one DRB on a link
in the presence of arbitrary port and bridge configuration, which is
why there are two additional loop safety mechanisms in TRILL. But it
does a lot better than sending Hellos on only one VLAN.

> 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

Configuring Announcing VLANs to be anything less than the default of
all enabled VLANs is to deliberately accept an increased risk of loops
in return for fewer Hellos. If you leave Announcing VLANs at its
default value, there is no problem in this case.

In the TRILL working group, the two main opinions were that RBridges
should always send Hellos on all VLANs and that they should send
Hellos only on the Designated VLAN. The TRILL base protocol standard
defaults for sending Hellos are a compromise that provides reasonable
safety for plausible configurations. The ability to configure the
Announcing VLANs set is a facility primarily for those who insist that
their networks are fully configured with nothing funny in between
RBridges so that it is safe to reduce the number of Hellos.

Configuring the RBridges on a link with inconsistent desired
Designated VLANs and a reduced number of Hellos via a non-default
Announcing VLANs set is risky, as you demonstrate.

> 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."

I think the "this" towards the end of that sentence should probably be
replaced by "failure to send such Hellos", for clarity. I'll make a
note of this as an editorial clarification.

> 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.

The DRB does send such Hellos unless you configure things so that it
doesn't.

If you are willing to bet that all your RBridges on a link have
connectivity to each other over the Designated VLAN for that link,
then Hellos just on that VLAN are adequate and you can get that by
configuring the Announcing VLANs set on all the ports to be the null
set. This would lead to N Hellos being sent if there are N RBridges on
the link.

If you are not willing to bet on that, then the TRILL default for N
RBridges where k VLANs are enabled would be N+k-1 Hellos. If the DRB
assigns lots of VLANs to other RBridges, this would likely tend toward
2*k Hellos. But all this scales much better than the N*k Hellos some
people were insisting on.

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 Feb  7 08:14: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 194573A6E0F for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  7 Feb 2011 08:14:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
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 zg4w6iriTHCQ for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  7 Feb 2011 08:14:21 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 184C63A6D03 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon,  7 Feb 2011 08:14: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 p17Fw7qM016358; Mon, 7 Feb 2011 07:58:08 -0800 (PST)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p17FvI3P016156 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 7 Feb 2011 07:57:28 -0800 (PST)
Authentication-Results: ams-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Aj0GAJOlT02Q/khMgWdsb2JhbACXE44fFQEBFiIknxyadoVaBItngy4
Received: from ams-core-3.cisco.com ([144.254.72.76]) by ams-iport-2.cisco.com with ESMTP; 07 Feb 2011 15:57:17 +0000
Received: from [10.61.100.130] (dhcp-10-61-100-130.cisco.com [10.61.100.130]) by ams-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id p17FvH5Y017293 for <rbridge@postel.org>; Mon, 7 Feb 2011 15:57:17 GMT
Message-ID: <4D50165D.2090106@cisco.com>
Date: Mon, 07 Feb 2011 15:57:17 +0000
From: mike shand <mshand@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.9) Gecko/20100915 Lightning/1.0b2 Thunderbird/3.1.4
MIME-Version: 1.0
To: rbridge@postel.org
References: <4D415111.4010009@gmail.com> <4D41ABED.5070308@gmail.com>	<4D41D6DC.2040406@workingcode.com> <AANLkTi=njqz66Ep-Kfn9m=cvHXPpyeH1+W3PznU3f78s@mail.gmail.com>
In-Reply-To: <AANLkTi=njqz66Ep-Kfn9m=cvHXPpyeH1+W3PznU3f78s@mail.gmail.com>
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: mshand@cisco.com
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

  As far as IS-IS is concerned, the requirement is that the system ID 
must be unique within the routing domain (level 1 or level 2). IS-IS 
does not mandate HOW this unique system ID is obtained. Certainly, using 
a MAC address can be a good source of such unique IDs if you have 
confidence that they truly are unique. In a certain implementation from 
the early days, the system board contained a "MAC address" chip which 
was guaranteed to be unique (wrt to other such chips from the same 
manufacturer) and was used to generate the system ID even when there 
were no Ethernet cards installed.

But as has been pointed out, this is really left to the 
implementation/operator to ensure.

The consequence of having duplicate addresses is that LSP sequence 
numbers begin counting up, and generating network management events each 
time they do so. Most implementations have a means of flashing in big 
red letters that something is misconfigured.

     Mike


On 05/02/2011 01:01, Anoop Ghanwani wrote:
> On Thu, Jan 27, 2011 at 12:34 PM, James Carlson
> <carlsonj@workingcode.com>  wrote:
>
>> 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.
> Coming from the TRILL part of the world, I don't think this is a problem
> that needs to be addressed in this draft.  Generating a unique System ID
> for IS-IS is an IS-IS problem, and as such should be addressed in the IS-IS
> working group.
>
> Anoop
> _______________________________________________
> 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  Mon Feb  7 15:57: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 F057E3A6E77 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  7 Feb 2011 15:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.197
X-Spam-Level: 
X-Spam-Status: No, score=-105.197 tagged_above=-999 required=5 tests=[AWL=1.402, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 HQiYM4VzuVnq for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  7 Feb 2011 15:57:35 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id F1E783A6C8B for <trill-archive-Osh9cae4@lists.ietf.org>; Mon,  7 Feb 2011 15:57: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 p17NbMhk022629; Mon, 7 Feb 2011 15:37:24 -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 p17NaUZa022525 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 7 Feb 2011 15:36:39 -0800 (PST)
Received: by wwd20 with SMTP id 20so5762300wwd.21 for <rbridge@postel.org>; Mon, 07 Feb 2011 15:36:29 -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=RAPqlMa4pZy3MqSvENO2iIh4xFjy4H4EvB24pWjzYig=; b=ot40STMeSeQ36Re5isFJOaULLYex70pDxaHCTR/VA2B5V+mq5tJNwU7S0r6R3K/P/r GDO7ME4uVhXkJW2qZDSRVWoWZQsi/2KBrMSoF/ZxG/eZ0ORPMdMD/bvY9soDElSoMy+y q/3L2glXi79tBiRCP/qHU23LzgyXfPauIkmos=
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=ns5SARuE268azPeADgFP1BDwfP6DZjOmSlsIbSdkzXYhXM9JTDU/9p1BJtkMTcs9sz eUEXNEIpZooFjaSEqX4tDPtzxNgbvCbeFFHbI4++vi86pj2/iTw/SpCUKrrQMMQJ5/3R 76yZk314TRdI+/HHS1s/FbuVVUOy42+mBgYBM=
Received: by 10.227.151.211 with SMTP id d19mr9734006wbw.124.1297121777184; Mon, 07 Feb 2011 15:36:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Mon, 7 Feb 2011 15:35:57 -0800 (PST)
In-Reply-To: <4D358B45.7030606@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> <4D358B45.7030606@cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 7 Feb 2011 18:35:57 -0500
Message-ID: <AANLkTi=g4GAQ7EbrxYKHN310O99JxxYZv+zi-5mmhwu3@mail.gmail.com>
To: mike shand <mshand@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 p17NaUZa022525
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 Mike,

I think I failed to respond to your message below. Sorry. You wording
looks fine to me.

Thanks,
Donald

On Tue, Jan 18, 2011 at 7:44 AM, mike shand <mshand@cisco.com> wrote:
> =A0To 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
> =A0 LAN Hellos, the RBridges on the link (including the DRB) just directly
> report all their
> =A0 adjacencies on the LAN that are in the Report state. If the DRB does =
not
> set the
> =A0 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 eff=
ect
> on how LSPs
> =A0 are flooded on a link. It only affects what LSPs are generated."
>
>
> =A0 =A0Mike
>
>
> On 15/01/2011 22:45, Les Ginsberg (ginsberg) wrote:
>>>
>>> 6. Pseudonodes
>>> > =A0> =A0 =A0 =A0The Designated RBridge (DRB), determined as described=
 above,
>>> > =A0controls
>>> > =A0 =A0 =A0whether a pseudonode will be used on a link.
>>> > =A0> =A0 =A0 =A0It is anticipated that many links between RBridges wi=
ll
>>> > actually be
>>> > =A0 =A0 =A0point-to-point, in which case using a pseudonode merely ad=
ds to
>>> > the
>>> > =A0 =A0 =A0complexity. If the DRB sets the bypass pseudonode bit in i=
ts TRILL
>>> > =A0 =A0 =A0LAN Hellos, the RBridges on the link just directly report =
their
>>> > =A0 =A0 =A0adjacencies that are in the Report state. If the DRB does =
not set
>>> > =A0the
>>> > =A0 =A0 =A0bypass pseudonode bit in its TRILL Hellos, then it specifi=
es a
>>> > =A0 =A0 =A0pseudonode for the link and sends LSPs on behalf of the ps=
eudonode
>>> > =A0as
>>> > =A0 =A0 =A0usual. Setting the bypass pseudonode bit has no effect on =
how LSPs
>>> > =A0 =A0 =A0are flooded on a link. It only affects what LSPs are gener=
ated.
>>> > =A0> =A0LES: The phrase "specifies a pseudo-node for the link" sugges=
ts
>>> > that
>>> > =A0the LANID sent by the DRB may be different depending on whether the
>>> > =A0bypass pseudo-node bit is set or not. Do you really mean that?
>>> > =A0> =A0<DEE3> =A0No, it is not meant to imply that. How about, "...,=
 then
>>> > the
>>
>> LAN
>>>
>>> > =A0ID in the DRB's Hellos specifies the pseudonode for the link and t=
he
>>> > =A0DRB sends ..."
>>> > =A0> =A0he DRB does not set the
>>> > =A0 =A0 =A0bypass pseudonode bit in its TRILL Hellos, then it specifi=
es a
>>> > =A0 =A0 =A0pseudonode for the link and sends LSPs on behalf of the ps=
eudonode
>>> > =A0as
>>> > =A0 =A0 =A0usual. Setting the bypass pseudonode bit has no effect on =
how LSPs
>>> > =A0 =A0 =A0are flooded on a link. It only affects what LSPs are gener=
ated.
>>> >
>>
>> 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.
>>
>> =A0 =A0Les
>
> _______________________________________________
> 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  Mon Feb  7 20: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 E9E563A6C9B for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  7 Feb 2011 20:44:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.446
X-Spam-Level: 
X-Spam-Status: No, score=-104.446 tagged_above=-999 required=5 tests=[AWL=2.153, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 bBPW4TZHggLG for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  7 Feb 2011 20:44:46 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 5BC573A6C86 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon,  7 Feb 2011 20:44:46 -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 p184VQM4007475; Mon, 7 Feb 2011 20:31:27 -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 p184Ud9v007083 for <rbridge@postel.org>; Mon, 7 Feb 2011 20:30:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 737223A6C95 for <rbridge@postel.org>; Mon,  7 Feb 2011 20:30:03 -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 bDyMwX383wOS; Mon,  7 Feb 2011 20:30:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ACF13A6BDF; Mon,  7 Feb 2011 20:30: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.12
Message-ID: <20110208043002.10691.91557.idtracker@localhost>
Date: Mon, 07 Feb 2011 20:30: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-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>
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-02.txt
	Pages           : 27
	Date            : 2011-02-07

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-02.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-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-02-07202828.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 Feb  7 21:02:01 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 6D0883A6CA3 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  7 Feb 2011 21:02:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.398
X-Spam-Level: 
X-Spam-Status: No, score=-105.398 tagged_above=-999 required=5 tests=[AWL=1.201, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 qt+Yhu2o1J6b for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon,  7 Feb 2011 21:02:00 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 4F9863A6C95 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon,  7 Feb 2011 21:02:00 -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 p184k5Px009691; Mon, 7 Feb 2011 20:46: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 p184jOxv009562 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 7 Feb 2011 20:45:34 -0800 (PST)
Received: by wyb28 with SMTP id 28so5275912wyb.39 for <rbridge@postel.org>; Mon, 07 Feb 2011 20:45: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:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=uO/efEZ/wJsauKf+KFfmnSYHsPDxavPhN8O0dxCOghk=; b=F19LK06c3GQYb5k2IC0zmlDyn+8xYuEmr7gRytIaRqOrFJiNPQca0t789PpzSENymz qahGVFJ+BsgsMKWRXgnNtBblK6awzwPlGbjXJ2tVzNPzYwxBvKmizb9KxXC3j1lPg66n eIo3ZeFDk8n4G8i4gADS1Gg3VWbioeRjq+scM=
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=ioZ7gfD6ZLG3Xb689KOLGqz13YcwpAcmxt1gcKYtqAg5oGKVkRMeh1ri/K+l3OoSiB t7y2xgKJqhrG57S5WSNYcsJ1Kfd586sXPie4/WUWK0L4GGjOfK/e5cDeM2kYqVBEghi5 tWBijf6gMOQzN/Bv/279gButMfC6bX8JSg3G0=
Received: by 10.227.41.204 with SMTP id p12mr10599673wbe.153.1297140323074; Mon, 07 Feb 2011 20:45:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Mon, 7 Feb 2011 20:45:02 -0800 (PST)
In-Reply-To: <20110208043002.10691.91557.idtracker@localhost>
References: <20110208043002.10691.91557.idtracker@localhost>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 7 Feb 2011 23:45:02 -0500
Message-ID: <AANLkTin80Zdi7RKcL8_Y-Eh6H6tiGkgPqwABfz6bESwz@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 p184jOxv009562
Cc: isis mailing list <isis-wg@ietf.org>
Subject: Re: [rbridge] I-D Action:draft-ietf-trill-adj-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

This version has changes from earlier resolved comments incorporated.
Donald

On Mon, Feb 7, 2011 at 11:30 PM,  <Internet-Drafts@ietf.org> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Transparent Interconnection of Lots of L=
inks Working Group of the IETF.
>
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : RBridges: Adjacency
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : D. Eastlake 3rd, et al.
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-trill-adj-02.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 27
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-02-07
>
> 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-02.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/

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

From rbridge-bounces@postel.org  Tue Feb  8 13:24:23 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 9AD9E3A687D for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue,  8 Feb 2011 13:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.511
X-Spam-Level: 
X-Spam-Status: No, score=-105.511 tagged_above=-999 required=5 tests=[AWL=1.088, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 e+g3t8TddIHC for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue,  8 Feb 2011 13:24:22 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 2FC8A3A6857 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue,  8 Feb 2011 13:24: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 p18L8Osq001360; Tue, 8 Feb 2011 13:08:26 -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 p18L7wPN001287 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Tue, 8 Feb 2011 13:08:08 -0800 (PST)
Received: by wyb28 with SMTP id 28so6084973wyb.39 for <rbridge@postel.org>; Tue, 08 Feb 2011 13:07:57 -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:content-type:content-transfer-encoding; bh=2BEK971M09+cJOzQn1DKDej+VaTD7y2S80n/CkbFjCA=; b=DROE1yGJ+knPPvsZCJ9Tr05rU2eg9/iNJursozbq+9wpMDudcDe+AF/ouA3ZzUeGap 3gP/jICckvTI43NaKr41e9jm2YyySStt6bkbXkw/aUoBXwQyHRVi8XJ8veNhI3Mjdpn0 0RF7fcCh3J09MyUu0cny+1QacV3KY6YCnstqA=
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=vtwvyDtWkLk33qNd9HumRd7nwAXEQ/xijxaCt3MuO79l6EyW9I8V6KGEcYnd2oD+FN NKH9SRptXdXY75FMuxLFoDqlEsnp6e4o2TcQTS/UUCFv+9dfjvQk2wfQ7HbjL0c4eSY3 G56llO+95lFpIBDgIgV5qsepUmDymISyr6ga4=
Received: by 10.227.135.4 with SMTP id l4mr2043640wbt.95.1297199277515; Tue, 08 Feb 2011 13:07:57 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Tue, 8 Feb 2011 13:07:37 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D323EC9@xmb-sjc-222.amer.cisco.com>
References: <AANLkTikWNuQJQU9fFuGVNVPy1AicMSp37+rqffsMW9Xm@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D323EC9@xmb-sjc-222.amer.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 8 Feb 2011 16:07:37 -0500
Message-ID: <AANLkTi=_Kc+mG_YSx_HChqY8o5t7jzn4a4TSypLY6Y2E@mail.gmail.com>
To: isis mailing list <isis-wg@ietf.org>, 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 p18L7wPN001287
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

Hi Les,

On Mon, Jan 31, 2011 at 4:44 AM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
> Donald -
>...
>
>> -----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
...

>> 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.

OK.

>> > 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":
>>
>> =A0 =A0 =A0 =A0 =A0The port has become DRB but is in a pre-forwarding st=
ate with
>> =A0 =A0 =A0 =A0 =A0regard to native frames and is inhibited from ingress=
ing or
>> =A0 =A0 =A0 =A0 =A0egressing them.
>
> This is exactly my point. If there is two way connectivity and the
> reachable VLAN/MAC addresses have been advertised by the respective
> appointed forwarders, then traffic will be attracted even though it
> cannot be delivered. Is this desirable? If the pseudo-node LSP did
> NOT advertise neighbors in pseudo-node LSPs then such packets could
> be dropped closer to the source until the pre-forwarding state had
> expired.

There may or may not be a psuedo-node, which I think has nothing to do
with it. Adjacencies in the Report state are reported. They appear in
the topology so that TRILL Data through traffic, and traffic being
ingressed or egressed on other ports, can use the link.

Advertisement of end station MAC and VLAN connectivity is beyond the
scope of this document. However, I would note that single destination
TRILL Data traffic can only be "attracted" to an RBridge by frames
that RBridge itself has sent. As for multi-destination TRILL Data, it
is sent on one or more distribution trees that can be pruned on VLAN
but native frame VLAN connectivity is only reported at the RBridge
level, not the port level, and there is no pruning effect if there is
any downstream connectivity to that VLAN.

>> > Section 4.2
>> > -----------
>>
>> > When a DRB change causes a change in D-VLAN, the draft says:
>>
>> =A0 =A0 =A0 o =A0The non-Designated VLAN Hello Holding timer is set to t=
he
>> =A0 =A0 =A0 =A0 =A0maximum of its time to expiration and the time to exp=
iration
>> of
>> =A0 =A0 =A0 =A0 =A0the 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 here 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
> specified by the previous DRB"
>
> ??

There is only one Designated VLAN Hello Holding timer for each
adjacency. The wording you suggest gives the impression that there
might be more than one Designated VLAN Hello Holding timer for the
adjacency associated with different VLANs, which is not what is
specified.

How about adding some text and rewording the two points on what to do
to each adjacency when the Designated VLAN changes to something like
this:

"o  If the Designated VLAN Hello Holding timer is expired, no special
    action need be taken.

o  If the Designated VLAN Hello Holding timer has time left to
   exiration, then: 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 time to expiration
   of the Designated VLAN Hello Holding timer will reflect the most
   recent Hello received on the old Designated VLAN.) Then the
   Designated VLAN Hello Holding timer is then set to the expired
   state and an event A5 occurs for the adjacency (see Section
   3.3). Afterwards the Designated VLAN Hello Holding timer will be
   updated based on Hellos received in the new Designated VLAN."

>> > 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
> operation of the adjacency machinery it seems worth including
> explicit language here - rather than requiring people to go to
> another document. It may be commonplace for all Rbridges to be
> configured with the same D-VLAN, but for cases where that is NOT the
> case (which is of course necessary for a D-VLAN change 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
> Rbridges have to take this action on a DRB change which involves a
> D-VLAN change. Discussing this seems very relevant to the scope of
> this document.

I really can't see duplicating over a page of detailed specifications
from the TRILL base protocol standard into this document. Those
specifications are already incorporated by reference. But I suppose a
reminder could be added such as "If the Designated VLAN for a link
changes or an RBridge changes in either direction between being the
Designated RBridge and not being the Designated RBridge at a port,
this will generally change the VLANs on which Hellos are sent by that
RBridge on that port as specified in Section 4.4.3 of [RFCtrill]."

>> > 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. =A0by setting LAN priority)?

They go into Detect state only if the Designated VLAN changes, not if
the DRB changes but the Designated VLAN stays the same.

>> 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 delay/black-holing period does not occur at Layer 3 -
> which is why I say a DRB 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 avoid unnecessary DRB changes.

You're talking about native frames, not TRILL Data.

How about adding text something like:

   "Unnecessary DRB changes should be avoided, especially on links
   offering native frame service, as a DRB change will generally cause
   a transient interruption to native frame service. When practical,
   all RBridge ports on a link should be configured with the same
   designed Designated VLAN because a change in the Designated VLAN on
   the link can cause a transient interruption to TRILL Data
   forwarding on the link."

An omission in the current draft is the case where the DRB remains
unchanged but the Designated VLAN changes, perhaps because the DRB
configuration is changed to dictate a different Deisgnated VLAN. This
is fairly easy to fix and, unless there is some objection, I plan to
do so.

> =A0 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

From rbridge-bounces@postel.org  Wed Feb  9 11:48: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 C108F3A69C2 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed,  9 Feb 2011 11:48:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.632
X-Spam-Level: 
X-Spam-Status: No, score=-105.632 tagged_above=-999 required=5 tests=[AWL=0.967, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 ju1-kRbcvhP9 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed,  9 Feb 2011 11:48:12 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 9B2B43A69BC for <trill-archive-Osh9cae4@lists.ietf.org>; Wed,  9 Feb 2011 11:48: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 p19JRViZ026093; Wed, 9 Feb 2011 11:27:32 -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 p19JR6W4026025 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Wed, 9 Feb 2011 11:27:15 -0800 (PST)
Received: by wyb28 with SMTP id 28so522008wyb.39 for <rbridge@postel.org>; Wed, 09 Feb 2011 11:27:05 -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:content-type:content-transfer-encoding; bh=Z3QGLOYQ9cxB8cA8l7vtDTx+VwUmldBACUVQjnsVBoY=; b=uM4icBSTol75N9AWujLs4jjrrU/1+JMgbTsHHj/d3WSTE9Yjng6XCQz/OIOwIyV+OF rTtDL0zfBmf9HESSQuetfn1W48psk8GucdeFXN9KgfxQeNfvpeEmIDrLgJ9JAbcEKKQ7 Kyrkh0brr6jRNrZ91hc3g17fm1bMHvsFSYCNY=
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=qyhcmgNyPe0OJAviJx7R8DmiUP/W62woRbyuUrVxQ8S8jU/xX07SUr4djOIqP05pj6 b3d8jkSwVgJBCh1bwBv+8gdBw5TZ8jfTRkygG0hQrUt+ys3I0aVCQhVwDDPYJ2aYRL7R o/H2IQ87Fwv/GPQ1gYrlb/9TRKGBl+Cx1qRhE=
Received: by 10.227.143.198 with SMTP id w6mr19539220wbu.37.1297279625201; Wed, 09 Feb 2011 11:27:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Wed, 9 Feb 2011 11:26:44 -0800 (PST)
In-Reply-To: <20110209170822.9717.21251.idtracker@localhost>
References: <20110209170822.9717.21251.idtracker@localhost>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 9 Feb 2011 14:26:44 -0500
Message-ID: <AANLkTi=sJhMzMmjPfm_tAVOaABsie1WyeQKyhpkmaXLB@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 p19JR6W4026025
Subject: [rbridge] Fwd: Protocol Action: 'Extensions to IS-IS for Layer-2 Systems' to Proposed Standard (draft-ietf-isis-layer2-10.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: The IESG <iesg-secretary@ietf.org>
Date: Wed, Feb 9, 2011 at 12:08 PM
Subject: Protocol Action: 'Extensions to IS-IS for Layer-2 Systems' to
Proposed Standard (draft-ietf-isis-layer2-10.txt)
To: IETF-Announce <ietf-announce@ietf.org>
Cc: isis chair <isis-chairs@tools.ietf.org>, Internet Architecture
Board <iab@iab.org>, isis mailing list <isis-wg@ietf.org>, RFC Editor
<rfc-editor@rfc-editor.org>


The IESG has approved the following document:
- 'Extensions to IS-IS for Layer-2 Systems'
=A0(draft-ietf-isis-layer2-10.txt) as a Proposed Standard

This document is the product of the IS-IS for IP Internets Working Group.

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-isis-layer2/




Technical Summary

This document specifies the IS-IS extensions necessary to support
link state routing to any protocols running directly over layer 2.
While supporting this concept involves several pieces, this document
only describes extensions to IS-IS. Furthermore, the TLVs described
in this document are generic layer 2 additions and specific ones as
needed are defined in the IS-IS technology specific extensions.

Working Group Summary

Issues arose as this document, draft-ietf-isis-trill and draft-ietf-isis-ie=
ee-aq
were originally one document. It was felt during review that
draft-ietf-isis-trill and draft-ietf-isis-ieee-aq were sufficiently
different that there needed to be a "base" document (this one)
and two separate technology documents. The opinion of the ISIS
WG it is unfortunate that there could not be one solution for
layer2 routing in ISIS but, this decision was not within the remit
of the ISIS WG.

Document Quality

There are multiple, interoperable implementations.

Personnel

David Ward is the Document Shepherd for this document.
Stewart Bryant is the =A0Responsible Area Director.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

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

From rbridge-bounces@postel.org  Wed Feb  9 12:00:17 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 54F9F3A6A3B for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed,  9 Feb 2011 12:00:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.728
X-Spam-Level: 
X-Spam-Status: No, score=-105.728 tagged_above=-999 required=5 tests=[AWL=0.871, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 xlqpFlm1qmdb for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed,  9 Feb 2011 12:00:15 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 468C03A6A33 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed,  9 Feb 2011 12:00:13 -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 p19JTPxu026294; Wed, 9 Feb 2011 11:29:26 -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 p19JSsKZ026268 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Wed, 9 Feb 2011 11:29:04 -0800 (PST)
Received: by wwd20 with SMTP id 20so598007wwd.21 for <rbridge@postel.org>; Wed, 09 Feb 2011 11:28:53 -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:content-type:content-transfer-encoding; bh=h96LL+TuW3k6UGINf/Zs8jppK+O6je5J5zXx68GrJxA=; b=B3HN1PXzQlEx3VGgRPkQqa1Wk2fvJxp9ChxQ4VK1clRV8JuccCRy8XioMvUi/71xhh NM5ZFsHo6vReLYsHNymP5XnlZ6t3gBDr0KYD9o/154mTHw/Lu6Mm2XgKzLVeE2L6GIJh GIXTejokXvUIunES2ReyoY6c/B3TQW+DfTJCI=
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=Fyk9F/EyIK1mZ0wOsu+bESdHnzUlcY2NhQbGLP8Tcys2YnhAhDWjM4HcfBDl2sxJ5w MilEvuEGxTDISsaPP6sFGlau0vKFpfxnxyzvyo5uxbdnlsOPO1jfXz6BgYKfIc19wQ3m wjdIk4oY3arfxb11FSzBH3ZCZg6HZGM7y1E2w=
Received: by 10.227.135.4 with SMTP id l4mr3653187wbt.95.1297279733281; Wed, 09 Feb 2011 11:28:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Wed, 9 Feb 2011 11:28:33 -0800 (PST)
In-Reply-To: <20110209171002.7636.71670.idtracker@localhost>
References: <20110209171002.7636.71670.idtracker@localhost>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 9 Feb 2011 14:28:33 -0500
Message-ID: <AANLkTinQtSrg++x8ddxW6vZ4KED=8HRqapZekrsRew5a@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 p19JSsKZ026268
Subject: [rbridge] Fwd: Protocol Action: 'TRILL Use of IS-IS' to Proposed Standard (draft-ietf-isis-trill-05.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: The IESG <iesg-secretary@ietf.org>
Date: Wed, Feb 9, 2011 at 12:10 PM
Subject: Protocol Action: 'TRILL Use of IS-IS' to Proposed Standard
(draft-ietf-isis-trill-05.txt)
To: IETF-Announce <ietf-announce@ietf.org>
Cc: isis chair <isis-chairs@tools.ietf.org>, Internet Architecture
Board <iab@iab.org>, isis mailing list <isis-wg@ietf.org>, RFC Editor
<rfc-editor@rfc-editor.org>


The IESG has approved the following document:
- 'TRILL Use of IS-IS'
=A0(draft-ietf-isis-trill-05.txt) as a Proposed Standard

This document is the product of the IS-IS for IP Internets Working Group.

The IESG contact persons are Stewart Bryant and Adrian Farrel.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-isis-trill/




Technical Summary

=A0 The IETF has standardized the TRILL protocol, which provides
=A0 transparent Layer 2 forwarding using encapsulation with a hop count
=A0 and IS-IS link state routing. This document specifies the data
=A0 formats and code points for the IS-IS extensions to support TRILL.


Working Group Summary

=A0 This document, draft-ietf-isis-ieee-aq and draft-ietf-isis-layer2 were
=A0 originally one document.Through the review process it was
=A0 determined that a split into a base document (draft-ietf-isis-layer2)
=A0 and draft-ietf-isis-trill and draft-ietf-isis-ieee-aq into separate
=A0 documents. One solution to pass layer2 information in ISIS or at
=A0 least one specification was desired but, the IEEE and IETF have each
=A0 defined their own mechanism. Given the divergence of solutions, a
=A0 specification split was appropriate.

Document Quality

=A0 There are known interoperable implementations of this technology
=A0 based in earlier versions of the drafts. Earlier versions were based
=A0 on additional PDUs in the ISIS protocol which have been changed
=A0 to TLVs. It is reasonable that implementors can make the change
=A0 and that earlier interoperation demonstrates that the solution
=A0 is viable.

Personnel

=A0 David Ward is the Document Shepherd for this document.
=A0 Stewart Bryant is the Responsible Area Director.

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce

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

From rbridge-bounces@postel.org  Thu Feb 10 12:24: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 CDC023A69BC for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 10 Feb 2011 12:24:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.748
X-Spam-Level: 
X-Spam-Status: No, score=-105.748 tagged_above=-999 required=5 tests=[AWL=0.851, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 3QjXkW52kejz for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 10 Feb 2011 12:24:11 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id D379B3A67D8 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 10 Feb 2011 12:24: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 p1AK4Z9C026136; Thu, 10 Feb 2011 12:04:36 -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 p1AK4DAM026082 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 10 Feb 2011 12:04:23 -0800 (PST)
Received: by wwi17 with SMTP id 17so3432433wwi.3 for <rbridge@postel.org>; Thu, 10 Feb 2011 12:04:13 -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:cc :content-type:content-transfer-encoding; bh=csdhJ8O3Z7d6w47BqGQNV5TA+gFYOk3v99GTl/UtViA=; b=cUCKODh10sbV9yqbPNGlQyxsl7Xvwogcg13CedoIFpiSRkhHRpmFuRUUtesLlO6Sgp 7S0BVF3EstzVPA50vqnLW7TVQycUlsBiqXU8WifyZ9AHolGwUQcBaOldhmfsMIJiZcRh 8G3rC4wnfr3TdDE6Of+PtrVe/7cA9efi6WgN8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; b=Wmc8TbnQd9t5KZzG08hZ3CGkCNZJV55RzSGWnmkDTlMSF17uBtBILF88mFMb/DGnmg BLUR9VaktaPX76Ph3cdNQxABe0tH+vrVzc9Jq5QYRWa6iIt46sRG3I8byNT/AMC4+fec FbRqIz5xAr7wFDEZQv6sXA4rPyEwHBQj7Pz58=
Received: by 10.227.143.198 with SMTP id w6mr21222577wbu.37.1297368252989; Thu, 10 Feb 2011 12:04:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.61.81 with HTTP; Thu, 10 Feb 2011 12:03:50 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 10 Feb 2011 15:03:50 -0500
Message-ID: <AANLkTinyq+mtLEFHpXLH253q6aa_L2Y7aVd3FsK2+rW1@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 p1AK4DAM026082
Cc: isis mailing list <isis-wg@ietf.org>
Subject: [rbridge] trill-adj Section 6 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 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.

I believe the wording suggested by Mike Shand here
http://www.ietf.org/mail-archive/web/isis-wg/current/msg02822.html
which is actually already incorporated in draft-ietf-trill-adj-02.txt
resolves the above.

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 Feb 11 00:01: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 129C73A6BB0 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 11 Feb 2011 00:01:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.599
X-Spam-Level: 
X-Spam-Status: No, score=-8.599 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 xb2XknhHpclu for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 11 Feb 2011 00:01:09 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id E99713A6BAF for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 11 Feb 2011 00:01: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 p1B7no36000985; Thu, 10 Feb 2011 23:49:51 -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 p1B7nKBM000963 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 10 Feb 2011 23:49:28 -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: AigBAMV4VE2rRN+K/2dsb2JhbACXFo5fc6ApmyqDF4JFBIUBijODBg
X-IronPort-AV: E=Sophos;i="4.60,454,1291593600"; d="scan'208";a="328261173"
Received: from sj-core-4.cisco.com ([171.68.223.138]) by sj-iport-5.cisco.com with ESMTP; 11 Feb 2011 07:49:18 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-4.cisco.com (8.13.8/8.14.3) with ESMTP id p1B7nJHO000136; Fri, 11 Feb 2011 07:49:19 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);  Thu, 10 Feb 2011 23:49:19 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 10 Feb 2011 23:49:17 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D4E291D@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTinyq+mtLEFHpXLH253q6aa_L2Y7aVd3FsK2+rW1@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: trill-adj Section 6 comments
Thread-Index: AcvJXbTLM90G5xCpS/y8C1sxlJKJ3QAYm/BA
References: <AANLkTinyq+mtLEFHpXLH253q6aa_L2Y7aVd3FsK2+rW1@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>, <rbridge@postel.org>
X-OriginalArrivalTime: 11 Feb 2011 07:49:19.0419 (UTC) FILETIME=[3076D8B0:01CBC9C0]
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 p1B7nKBM000963
Cc: isis mailing list <isis-wg@ietf.org>
Subject: Re: [rbridge] trill-adj Section 6 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

Looks good.
Thanx.

  Les

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Thursday, February 10, 2011 12:04 PM
> To: Les Ginsberg (ginsberg); rbridge@postel.org
> Cc: isis mailing list
> Subject: trill-adj Section 6 comments
> =

> Response to some comments by Les Ginsberg:
> =

> > 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.
> =

> I believe the wording suggested by Mike Shand here
> http://www.ietf.org/mail-archive/web/isis-wg/current/msg02822.html
> which is actually already incorporated in draft-ietf-trill-adj-02.txt
> resolves the above.
> =

> 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 Feb 11 00:14: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 D952B3A68BB for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 11 Feb 2011 00:14:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.932
X-Spam-Level: 
X-Spam-Status: No, score=-7.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Ys6uSbnt7nie for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Fri, 11 Feb 2011 00:14:24 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 3C78F3A6BCE for <trill-archive-Osh9cae4@lists.ietf.org>; Fri, 11 Feb 2011 00:14: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 p1B7hJcZ000275; Thu, 10 Feb 2011 23:43:22 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p1B7h7kQ000259 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 10 Feb 2011 23:43:16 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AigBAMp3VE2rR7H+/2dsb2JhbACXFo5fc6AsmyqDF4JFBIUBijODBg
X-IronPort-AV: E=Sophos;i="4.60,454,1291593600"; d="scan'208";a="261242117"
Received: from sj-core-2.cisco.com ([171.71.177.254]) by sj-iport-3.cisco.com with ESMTP; 11 Feb 2011 07:43:03 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p1B7h31R021348; Fri, 11 Feb 2011 07:43:03 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);  Thu, 10 Feb 2011 23:43:03 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 10 Feb 2011 23:43:01 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D4E291C@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTi=_Kc+mG_YSx_HChqY8o5t7jzn4a4TSypLY6Y2E@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isis-wg] trill-adj Section 4 comments
Thread-Index: AcvH1EoBRiLciKWySsGnw4cUKtEaAQB5Pv6A
References: <AANLkTikWNuQJQU9fFuGVNVPy1AicMSp37+rqffsMW9Xm@mail.gmail.com><AE36820147909644AD2A7CA014B1FB520D323EC9@xmb-sjc-222.amer.cisco.com> <AANLkTi=_Kc+mG_YSx_HChqY8o5t7jzn4a4TSypLY6Y2E@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>, "isis mailing list" <isis-wg@ietf.org>, <rbridge@postel.org>
X-OriginalArrivalTime: 11 Feb 2011 07:43:03.0484 (UTC) FILETIME=[5063B7C0:01CBC9BF]
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 p1B7h7kQ000259
Subject: Re: [rbridge] [Isis-wg] 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 -

> -----Original Message-----
> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On
> Behalf Of Donald Eastlake
> Sent: Tuesday, February 08, 2011 1:08 PM
> To: isis mailing list; rbridge@postel.org
> Subject: Re: [Isis-wg] trill-adj Section 4 comments
> =

> Hi Les,
> =

> On Mon, Jan 31, 2011 at 4:44 AM, Les Ginsberg (ginsberg)
> <ginsberg@cisco.com> wrote:
> > Donald -
> >...
> >
> >> -----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
> ...
> =

> >> 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.
> =

> OK.
> =

> >> > 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":
> >>
> >> =A0 =A0 =A0 =A0 =A0The port has become DRB but is in a pre-forwarding =
state
> with
> >> =A0 =A0 =A0 =A0 =A0regard to native frames and is inhibited from ingre=
ssing or
> >> =A0 =A0 =A0 =A0 =A0egressing them.
> >
> > This is exactly my point. If there is two way connectivity and the
> > reachable VLAN/MAC addresses have been advertised by the respective
> > appointed forwarders, then traffic will be attracted even though it
> > cannot be delivered. Is this desirable? If the pseudo-node LSP did
> > NOT advertise neighbors in pseudo-node LSPs then such packets could
> > be dropped closer to the source until the pre-forwarding state had
> > expired.
> =

> There may or may not be a psuedo-node, which I think has nothing to do
> with it. Adjacencies in the Report state are reported. They appear in
> the topology so that TRILL Data through traffic, and traffic being
> ingressed or egressed on other ports, can use the link.

OK - it is likely my brain is still too L3 centric and I therefore likely m=
ade more of this issue than it really is. I think my major concern is discu=
ssed under DRB changes below.

> =

> Advertisement of end station MAC and VLAN connectivity is beyond the
> scope of this document. However, I would note that single destination
> TRILL Data traffic can only be "attracted" to an RBridge by frames
> that RBridge itself has sent. As for multi-destination TRILL Data, it
> is sent on one or more distribution trees that can be pruned on VLAN
> but native frame VLAN connectivity is only reported at the RBridge
> level, not the port level, and there is no pruning effect if there is
> any downstream connectivity to that VLAN.
> =

> >> > Section 4.2
> >> > -----------
> >>
> >> > When a DRB change causes a change in D-VLAN, the draft says:
> >>
> >> =A0 =A0 =A0 o =A0The non-Designated VLAN Hello Holding timer is set to=
 the
> >> =A0 =A0 =A0 =A0 =A0maximum of its time to expiration and the time to
> expiration
> >> of
> >> =A0 =A0 =A0 =A0 =A0the 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 here 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
> > specified by the previous DRB"
> >
> > ??
> =

> There is only one Designated VLAN Hello Holding timer for each
> adjacency. The wording you suggest gives the impression that there
> might be more than one Designated VLAN Hello Holding timer for the
> adjacency associated with different VLANs, which is not what is
> specified.
> =

> How about adding some text and rewording the two points on what to do
> to each adjacency when the Designated VLAN changes to something like
> this:
> =

> "o  If the Designated VLAN Hello Holding timer is expired, no special
>     action need be taken.
> =

> o  If the Designated VLAN Hello Holding timer has time left to
>    exiration, then: 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 time to expiration
>    of the Designated VLAN Hello Holding timer will reflect the most
>    recent Hello received on the old Designated VLAN.) Then the
>    Designated VLAN Hello Holding timer is then set to the expired
>    state and an event A5 occurs for the adjacency (see Section
>    3.3). Afterwards the Designated VLAN Hello Holding timer will be
>    updated based on Hellos received in the new Designated VLAN."

After this discussion and rereading your original text I think perhaps smal=
ler changes to the original text would suffice and be less verbose. How abo=
ut:

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

      o  The Designated VLAN Hello Holding timer is then set to expired (if=
 necessary)
         and an adjacency event 5 occurs for the adjacency (see Section 3.3=
).

???


> =

> >> > 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
> > operation of the adjacency machinery it seems worth including
> > explicit language here - rather than requiring people to go to
> > another document. It may be commonplace for all Rbridges to be
> > configured with the same D-VLAN, but for cases where that is NOT the
> > case (which is of course necessary for a D-VLAN change 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
> > Rbridges have to take this action on a DRB change which involves a
> > D-VLAN change. Discussing this seems very relevant to the scope of
> > this document.
> =

> I really can't see duplicating over a page of detailed specifications
> from the TRILL base protocol standard into this document. Those
> specifications are already incorporated by reference. But I suppose a
> reminder could be added such as "If the Designated VLAN for a link
> changes or an RBridge changes in either direction between being the
> Designated RBridge and not being the Designated RBridge at a port,
> this will generally change the VLANs on which Hellos are sent by that
> RBridge on that port as specified in Section 4.4.3 of [RFCtrill]."
> =


I would argue that it would be more useful to the implementor/reader to hav=
e all the relevant information in one document, but I also appreciate your =
reluctance to rework RFCtrill and the dangers of redundant specification - =
so I agree to your suggested reference. Thanx for the accommodation.


> >> > 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. =A0by setting LAN priority)?
> =

> They go into Detect state only if the Designated VLAN changes, not if
> the DRB changes but the Designated VLAN stays the same.
> =

> >> 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 delay/black-holing period does not occur at Layer 3 -
> > which is why I say a DRB 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 avoid unnecessary DRB changes.
> =

> You're talking about native frames, not TRILL Data.
> =

> How about adding text something like:
> =

>    "Unnecessary DRB changes should be avoided, especially on links
>    offering native frame service, as a DRB change will generally cause
>    a transient interruption to native frame service. When practical,
>    all RBridge ports on a link should be configured with the same
>    designed Designated VLAN because a change in the Designated VLAN on
>    the link can cause a transient interruption to TRILL Data
>    forwarding on the link."

Sounds good.

> =

> An omission in the current draft is the case where the DRB remains
> unchanged but the Designated VLAN changes, perhaps because the DRB
> configuration is changed to dictate a different Deisgnated VLAN. This
> is fairly easy to fix and, unless there is some objection, I plan to
> do so.

Good point. I agree it would be desirable to cover this.

   Les

> =

> > =A0 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
> _______________________________________________
> 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  Sat Feb 12 18:11: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 E3D0B3A6A78 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sat, 12 Feb 2011 18:11:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.763
X-Spam-Level: 
X-Spam-Status: No, score=-105.763 tagged_above=-999 required=5 tests=[AWL=0.836, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 ysq7wYN4JiLk for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sat, 12 Feb 2011 18:11:47 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id F2C223A6A57 for <trill-archive-Osh9cae4@lists.ietf.org>; Sat, 12 Feb 2011 18:11:46 -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 p1D1oKdb003102; Sat, 12 Feb 2011 17:50:22 -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 p1D1nmZl003000 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Sat, 12 Feb 2011 17:49:58 -0800 (PST)
Received: by wyb28 with SMTP id 28so3632941wyb.39 for <rbridge@postel.org>; Sat, 12 Feb 2011 17:49:47 -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=ZLni1j5d07xINZbi8hQTEXuLk6lmC1JpbigaMKNNHdM=; b=VWftYkSNfmBWlwZYkb0ngLFp8UmoSdGl1Y+8gxJ0ARvqqxuUMJey9ehBx+qGU7jBT7 Bcqwh9BRt2j7yDQ8C45jfwm0g1d/sibAJaP07uPzhw0sbp5hpfz1+u+WDM0pHwMABvDV KUAKOc3g8AnJAz0FLY4KtYlkJ2aYBjZ9m0PQw=
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=vLQ/hw2aVdg01qcuZTAQEp5vbkwfT0w3+vY5H1giHcJ0+dMQDPzOABeWzavc5+Ettn f3vD0QNNTvGZrsMO8t3bsMbi6tLOdGTB36oSq6AFYXRQGa9MbodFJlR5D3CH9UTphkUP i9Qgxhfla8BmxakzjjuyL1s7RpvnENhJNS5SQ=
Received: by 10.227.41.204 with SMTP id p12mr1288266wbe.153.1297561787625; Sat, 12 Feb 2011 17:49:47 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.182.7 with HTTP; Sat, 12 Feb 2011 17:49:27 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 12 Feb 2011 20:49:27 -0500
Message-ID: <AANLkTikTUAxQ-zPaZwjsVKwAo_mXtJVZu4RAYmW1hyGU@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 p1D1nmZl003000
Subject: [rbridge] trill-adj Section 7.2 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 7.2
> ------------

> Is IIH padding ignored on receipt?? Or is a padded IIH discarded?

I'm not sure why anyone would think that a padded TRILL Hello would be
discarded on reciept because of the padding. But, in any case, to
clear things up in a more general way, how about replacing

   "TRILL Hellos MAY contain an Authentication TLV."

at the end of the section with

   "In addition to the TLVs mentioned in [RFCtisis] or above in this
   document as occuring in TRILL Hellos, a TRILL Hello MAY also
   contain any TLV permitted in a Layer 3 IS-IS Hello. Padding and
   Neighbor TLVs, as well as any unimplemented or unknown TLVs, are
   ignored."

> 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?

It was the consensus of the participants in the TRILL interop at UNH
IOL to add a requirement for sending a TRILL Neighbor TLV with an
empty list when you have no neighbors on the Designated VLAN and the
working group went along with them. I suppose it clears thing out more
quickly in the case of some types of failures and, in any case, a
TRILL Neighbor TLV with an empty list of neighbors is only 3 bytes
long.

> One of the underlying concerns is that the indication of a
> connectivity change in a hello may already be delayed because of
> space limitations. The behavior you suggest here only seems to make
> that issue more significant.

Since, in some cases, this provision requires information to be sent
sooner, I would have thought you would consider it an improvement.

It would be possible to add some general exhortation to implementers
not to dilly-dally around too much in sending TRILL Neighbor TLVs. It
seems like an issue in implementation quality that I can't believe
would be a problem in the real world. There are lots of ways people
can do an implementation with bad performance. For example, you could
implement or schedule the updating of topology and calculation of
shortest paths so that it took, say, an hour to process LSPs that
updated reachability. I believe such an implementation would be
conformant to the existing IS-IS specification but, somehow, I just
don't see people using it (or buying it if it were a product). Just
so, an implementation that, when the neighbor list was non-empty, only
sent a TRILL neighbor TLV once an hour wouldn't get used (or purchased
if it was a product), at least not for any environment that seems
plausible to me.

In any case, "If there are such adjacencies, then the Hello MAY
contain a TRILL Neighbor TLV as described in Section 4.4.2.1 of
[RFCtrill]."  could be replaced with something like the following:

"If there are such adjacencies, it is RECOMMENDED that a TRILL
Neighbor TLV or TLVs, as described in Section 4.4.2.1 of [RFCtrill],
covering the entire range of MAC addresses, be in TRILL Hellos sent on
the Designated VLAN, if there is sufficient room. If this is not
possible, then TRILL Neighbor TLV's covering sub-ranges of MAC
addresses should be sent so that the entire range is covered
reasonably promptly.  Delays in sending TRILL Neighbor TLVs will delay
the advancement of adjacencies to the Report state and the discovery
of some link failures. Rapid, for example sub-second, detection of
link or node failures is best addressed with a protocol designed for
that purpose, such as BFD [RFC5880], use of which with TRILL will be
specified in a separate document."

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 Feb 14 22:54:11 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 A1A823A6E53 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 14 Feb 2011 22:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.799
X-Spam-Level: 
X-Spam-Status: No, score=-7.799 tagged_above=-999 required=5 tests=[AWL=-1.200, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 D-SzWOsAFqNy for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 14 Feb 2011 22:53:39 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 60A873A6E5B for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 14 Feb 2011 22:53: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 p1F6LHPV000546; Mon, 14 Feb 2011 22:21:19 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p1F6KY6v000127 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 14 Feb 2011 22:20:43 -0800 (PST)
Authentication-Results: sj-iport-3.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag4BABuqWU2rR7Hu/2dsb2JhbACXCY5dc6Bvm0qDF4JHBIUFijSDBg
X-IronPort-AV: E=Sophos;i="4.60,472,1291593600"; d="scan'208";a="263606985"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-3.cisco.com with ESMTP; 15 Feb 2011 06:20:33 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p1F6KXFn013430; Tue, 15 Feb 2011 06:20:33 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);  Mon, 14 Feb 2011 22:20:33 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Mon, 14 Feb 2011 22:20:31 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D57BDEB@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTikAFQK5heaqc=hiBt4BeYM2EHQZVAskqLBvOi4z@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isis-wg] Fwd: trill-adj Section 7.2 comments
Thread-Index: AcvLIHCSbQZG2ishTlq0FB6SfpUG+wBs5oSQ
References: <AANLkTikTUAxQ-zPaZwjsVKwAo_mXtJVZu4RAYmW1hyGU@mail.gmail.com> <AANLkTikAFQK5heaqc=hiBt4BeYM2EHQZVAskqLBvOi4z@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>, "isis mailing list" <isis-wg@ietf.org>
X-OriginalArrivalTime: 15 Feb 2011 06:20:33.0008 (UTC) FILETIME=[73540700:01CBCCD8]
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 p1F6KY6v000127
Cc: rbridge@postel.org
Subject: Re: [rbridge] [Isis-wg] Fwd: trill-adj Section 7.2 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

Hi Donald.

> -----Original Message-----
> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On
> Behalf Of Donald Eastlake
> Sent: Saturday, February 12, 2011 5:50 PM
> To: isis mailing list
> Subject: [Isis-wg] Fwd: trill-adj Section 7.2 comments
> =

> Sorry, forgot to cc the isis WG
> ---------- Forwarded message ----------
> From: Donald Eastlake <d3e3e3@gmail.com>
> Date: Sat, Feb 12, 2011 at 8:49 PM
> Subject: trill-adj Section 7.2 comments
> To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, rbridge@postel.org
> =

> =

> Response to some comments by Les Ginsberg:
> =

> > Section 7.2
> > ------------
> =

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

> I'm not sure why anyone would think that a padded TRILL Hello would be
> discarded on reciept because of the padding. But, in any case, to
> clear things up in a more general way, how about replacing
> =

> =A0 "TRILL Hellos MAY contain an Authentication TLV."
> =

> at the end of the section with
> =

> =A0 "In addition to the TLVs mentioned in [RFCtisis] or above in this
> =A0 document as occuring in TRILL Hellos, a TRILL Hello MAY also
> =A0 contain any TLV permitted in a Layer 3 IS-IS Hello. Padding and
> =A0 Neighbor TLVs, as well as any unimplemented or unknown TLVs, are
> =A0 ignored."


I asked about padding because TRILL makes it a point to deviate from the ba=
se IS-IS spec in regards to padding - so I thought it worth being "extra ex=
plicit".

What now seems more important - and which I neglected to ask previously - i=
s what happens to a received IIH which exceeds 1470 bytes? Is it discarded?=
 The draft says "TRILL Hello messages MUST NOT exceed 1,470 octets in lengt=
h..." - which suggests that any IIH larger than this is "illegal". What is =
the intended behavior on receipt of a too large IIH?

As far as your suggested wording above I would propose a modest rewrite:

"A TRILL Hello MAY also contain any TLV permitted in a Layer 3 IS-IS Hello.=
 TLVs which either have no defined functionality for TRILL or are unsupport=
ed/unknown are ignored."

> =

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

> > =A0 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 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?
> =

> It was the consensus of the participants in the TRILL interop at UNH
> IOL to add a requirement for sending a TRILL Neighbor TLV with an
> empty list when you have no neighbors on the Designated VLAN and the
> working group went along with them. I suppose it clears thing out more
> quickly in the case of some types of failures and, in any case, a
> TRILL Neighbor TLV with an empty list of neighbors is only 3 bytes
> long.
> =

> > One of the underlying concerns is that the indication of a
> > connectivity change in a hello may already be delayed because of
> > space limitations. The behavior you suggest here only seems to make
> > that issue more significant.
> =

> Since, in some cases, this provision requires information to be sent
> sooner, I would have thought you would consider it an improvement.
> =


The mandatory requirement to send an empty neighbor TLV is not useful. If I=
 receive an IIH which has no neighbor TLV I am supposed to conclude that th=
e sender actually has some neighbors but they chose (for whatever reason) n=
ot to send any in this particular hello. But I can't draw any useful conclu=
sion from this i.e. if they subsequently send an IIH with an empty neighbor=
 TLV (presumably w both the smallest/largest flags set)  am I to conclude t=
hat they lied in the previous IIH? And if I did, what would I do about it?

The relevant point to make - which you discuss below - is to recommend that=
 the full range of neighbors be advertised as frequently as practical as th=
e consequence of not doing so is to impact convergence. I think the text ab=
out requiring an empty neighbor TLV to be sent when you have no neighbors s=
hould be removed for the sake of clarity.

The convergence issue is one which concerns me as in the presence of a larg=
e # of neighbors and/or a large number of supported VLANs hellos either hav=
e to be sent with higher frequency (=3D> poorer scalability) or a longer co=
nvergence time has to be accepted. But that is a larger issue which I hope =
we can discuss when you respond to my comments on "Reliable Circuit Scoped =
Flooding".

   Les


> It would be possible to add some general exhortation to implementers
> not to dilly-dally around too much in sending TRILL Neighbor TLVs. It
> seems like an issue in implementation quality that I can't believe
> would be a problem in the real world. There are lots of ways people
> can do an implementation with bad performance. For example, you could
> implement or schedule the updating of topology and calculation of
> shortest paths so that it took, say, an hour to process LSPs that
> updated reachability. I believe such an implementation would be
> conformant to the existing IS-IS specification but, somehow, I just
> don't see people using it (or buying it if it were a product). Just
> so, an implementation that, when the neighbor list was non-empty, only
> sent a TRILL neighbor TLV once an hour wouldn't get used (or purchased
> if it was a product), at least not for any environment that seems
> plausible to me.
> =

> In any case, "If there are such adjacencies, then the Hello MAY
> contain a TRILL Neighbor TLV as described in Section 4.4.2.1 of
> [RFCtrill]." =A0could be replaced with something like the following:
> =

> "If there are such adjacencies, it is RECOMMENDED that a TRILL
> Neighbor TLV or TLVs, as described in Section 4.4.2.1 of [RFCtrill],
> covering the entire range of MAC addresses, be in TRILL Hellos sent on
> the Designated VLAN, if there is sufficient room. If this is not
> possible, then TRILL Neighbor TLV's covering sub-ranges of MAC
> addresses should be sent so that the entire range is covered
> reasonably promptly. =A0Delays in sending TRILL Neighbor TLVs will delay
> the advancement of adjacencies to the Report state and the discovery
> of some link failures. Rapid, for example sub-second, detection of
> link or node failures is best addressed with a protocol designed for
> that purpose, such as BFD [RFC5880], use of which with TRILL will be
> specified in a separate document."
> =

> 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
> _______________________________________________
> 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  Thu Feb 17 00:20: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 47D183A6DC6 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 17 Feb 2011 00:20:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.667
X-Spam-Level: 
X-Spam-Status: No, score=-105.667 tagged_above=-999 required=5 tests=[AWL=0.932, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 46U70WjxZ3ha for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 17 Feb 2011 00:20:13 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id F04933A6DB9 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 17 Feb 2011 00:20: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 p1H82tIS010751; Thu, 17 Feb 2011 00:02:56 -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 p1H82PUt010730 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Thu, 17 Feb 2011 00:02:35 -0800 (PST)
Received: by wyb28 with SMTP id 28so2173604wyb.39 for <rbridge@postel.org>; Thu, 17 Feb 2011 00:02: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:from:date :message-id:subject:to:cc:content-type:content-transfer-encoding; bh=bATPO+BjDhTU4G1xQHTmbP2lepmyb3h54IdJg2d689k=; b=in16dmyGGRWrfqSINsJWw9ZtY+Gis6uWSq7LX2UCB6DuNa1tjTwPNmu/9VRWpysmXk 64M2cojRKD85cHh4KNk6AFEsGPqmb4xYEpOHQ2XYpQtGYMWQMPbMruVcFK25Y8jfzH47 piWyEu8/NK8hJ6PomJMkCaB/V3/if6NoMIMJM=
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=J2k6gWb40+CnDlmfBSAFTEGh60usLkw2AUUVcl8neZTbHaSNSoZbcEbDz+vFGxpzgD ppgUvV7Sn9fnJH31fuRq3IhQEB0osFOCnUOVWV95FdQF6cfNeVL7RLgJxOKi29Kc0rPy DUCIRl5dhAjVLmASICrmGUb+plRx6sitKa8UY=
Received: by 10.227.127.65 with SMTP id f1mr1336744wbs.209.1297929744439; Thu, 17 Feb 2011 00:02:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.68.140 with HTTP; Thu, 17 Feb 2011 00:02:04 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D4E291C@xmb-sjc-222.amer.cisco.com>
References: <AANLkTikWNuQJQU9fFuGVNVPy1AicMSp37+rqffsMW9Xm@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D323EC9@xmb-sjc-222.amer.cisco.com> <AANLkTi=_Kc+mG_YSx_HChqY8o5t7jzn4a4TSypLY6Y2E@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D4E291C@xmb-sjc-222.amer.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 17 Feb 2011 00:02:04 -0800
Message-ID: <AANLkTikdncAYsY=cdYPe7Sp=C=7QGs=UugBHsH81R+Rf@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 p1H82PUt010730
Cc: isis mailing list <isis-wg@ietf.org>
Subject: Re: [rbridge] [Isis-wg] 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

Hi Les,

On Thu, Feb 10, 2011 at 11:43 PM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
> Donald -
>
>> -----Original Message-----
>> From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] On
>> Behalf Of Donald Eastlake
>> Sent: Tuesday, February 08, 2011 1:08 PM
>> To: isis mailing list; rbridge@postel.org
>> Subject: Re: [Isis-wg] trill-adj Section 4 comments

...

>> >> -----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.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 here 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
>> > specified by the previous DRB"
>> >
>> > ??
>>
>> There is only one Designated VLAN Hello Holding timer for each
>> adjacency. The wording you suggest gives the impression that there
>> might be more than one Designated VLAN Hello Holding timer for the
>> adjacency associated with different VLANs, which is not what is
>> specified.
>>
>> How about adding some text and rewording the two points on what to do
>> to each adjacency when the Designated VLAN changes to something like
>> this:
>>
>> "o  If the Designated VLAN Hello Holding timer is expired, no special
>>     action need be taken.
>>
>> o  If the Designated VLAN Hello Holding timer has time left to
>>    exiration, then: 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 time to expiration
>>    of the Designated VLAN Hello Holding timer will reflect the most
>>    recent Hello received on the old Designated VLAN.) Then the
>>    Designated VLAN Hello Holding timer is then set to the expired
>>    state and an event A5 occurs for the adjacency (see Section
>>    3.3). Afterwards the Designated VLAN Hello Holding timer will be
>>    updated based on Hellos received in the new Designated VLAN."
>
> After this discussion and rereading your original text I think
> perhaps smaller changes to the original text would suffice and be
> less verbose. How about:
>
>   o  The non-Designated VLAN Hello Holding timer is set to the
>      maximum of its time to expiration and the current time to expiration
>      of the Designated VLAN Hello Holding timer.
>
>   o  The Designated VLAN Hello Holding timer is then set to expired (if
>      necessary) and an adjacency event 5 occurs for the adjacency (see
>      Section 3.3).
>
> ???

OK, except "adjacency event 5" -> "event A5" for the current draft.

>>
>> >> > 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
>> > operation of the adjacency machinery it seems worth including
>> > explicit language here - rather than requiring people to go to
>> > another document. It may be commonplace for all Rbridges to be
>> > configured with the same D-VLAN, but for cases where that is NOT the
>> > case (which is of course necessary for a D-VLAN change 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
>> > Rbridges have to take this action on a DRB change which involves a
>> > D-VLAN change. Discussing this seems very relevant to the scope of
>> > this document.
>>
>> I really can't see duplicating over a page of detailed specifications
>> from the TRILL base protocol standard into this document. Those
>> specifications are already incorporated by reference. But I suppose a
>> reminder could be added such as "If the Designated VLAN for a link
>> changes or an RBridge changes in either direction between being the
>> Designated RBridge and not being the Designated RBridge at a port,
>> this will generally change the VLANs on which Hellos are sent by that
>> RBridge on that port as specified in Section 4.4.3 of [RFCtrill]."
>>
>
> I would argue that it would be more useful to the implementor/reader
> to have all the relevant information in one document, but I also
> appreciate your reluctance to rework RFCtrill and the dangers of
> redundant specification - so I agree to your suggested reference.
> Thanx for the accommodation.

You're welcome.

>> >> > 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. =A0by setting LAN priority)?
>>
>> They go into Detect state only if the Designated VLAN changes, not if
>> the DRB changes but the Designated VLAN stays the same.
>>
>> >> 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 delay/black-holing period does not occur at Layer 3 -
>> > which is why I say a DRB 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 avoid unnecessary DRB changes.
>>
>> You're talking about native frames, not TRILL Data.
>>
>> How about adding text something like:
>>
>>   "Unnecessary DRB changes should be avoided, especially on links
>>   offering native frame service, as a DRB change will generally cause
>>   a transient interruption to native frame service. When practical,
>>   all RBridge ports on a link should be configured with the same
>>   designed Designated VLAN because a change in the Designated VLAN on
>>   the link can cause a transient interruption to TRILL Data
>>   forwarding on the link."
>
> Sounds good.

OK.

>> An omission in the current draft is the case where the DRB remains
>> unchanged but the Designated VLAN changes, perhaps because the DRB
>> configuration is changed to dictate a different Deisgnated VLAN. This
>> is fairly easy to fix and, unless there is some objection, I plan to
>> do so.
>
> Good point. I agree it would be desirable to cover this.

OK.

> =A0 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
 Donald E. Eastlake 3rd +1-508-333-2270 (cell)
 155 Beaver Street
 Milford, MA 01757 USA
 d3e3e3@gmail.com

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

From rbridge-bounces@postel.org  Thu Feb 17 15:40: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 DC83F3A6F67 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 17 Feb 2011 15:40:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.499
X-Spam-Level: 
X-Spam-Status: No, score=-104.499 tagged_above=-999 required=5 tests=[AWL=2.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 7kFjpiKzggrH for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Thu, 17 Feb 2011 15:40:29 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 6B8753A6F65 for <trill-archive-Osh9cae4@lists.ietf.org>; Thu, 17 Feb 2011 15:40: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 p1HNUMbd005157; Thu, 17 Feb 2011 15:30:22 -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 p1HNTuRC005051 for <rbridge@postel.org>; Thu, 17 Feb 2011 15:30:05 -0800 (PST)
Received: by core3.amsl.com (Postfix, from userid 30) id E7AC13A6F54; Thu, 17 Feb 2011 15:28:51 -0800 (PST)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Mime-Version: 1.0
Message-Id: <20110217232851.E7AC13A6F54@core3.amsl.com>
Date: Thu, 17 Feb 2011 15:28:51 -0800 (PST)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: wwwrun@core3.amsl.com
Cc: d3e3e3@gmail.com, rbridge@postel.org, erik.nordmark@oracle.com
Subject: [rbridge] WG Action: RECHARTER: Transparent Interconnection of Lots of Links (trill)
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

The Transparent Interconnection of Lots of Links (trill) working group in
the Internet Area of the IETF has been rechartered.  For additional
information, please contact the Area Directors or the working group
Chairs.

Transparent Interconnection of Lots of Links (trill)
---------------------------------------------------
Current Status: Active Working Group

Chairs:
  Erik Nordmark <erik.nordmark@oracle.com>
  Donald Eastlake 3rd <d3e3e3@gmail.com>

Internet Area Directors:
  Jari Arkko <jari.arkko@piuha.net>
  Ralph Droms <rdroms.ietf@gmail.com>

Internet Area Advisor:
  Ralph Droms <rdroms.ietf@gmail.com>

Mailing Lists:
  Address:        rbridge@postel.org
  To Subscribe:   http://www.postel.org/mailman/listinfo/rbridge
  Archive:        http://www.postel.org/pipermail/rbridge

Description of Working Group:

The TRILL WG has specified a solution for shortest-path frame
routing in multi-hop IEEE 802.1-compliant Ethernet networks with
arbitrary topologies, using an existing link-state routing protocol
technology and encapsulation with a hop count.

The current work of the working group is around operational and
deployment support for the protocol. This includes a MIB module and
other pieces needed for operations, but also additional ways to
extend and optimize TRILL for the properties of the networks on
which it is deployed.

The WG will work on the following items:

(1) A MIB module for TRILL which specifies the unique pieces needed
for the protocol while reusing what is in the IS-IS MIB module and
the IEEE 802.1 MIB modules for pieces that are not unique to TRILL
(draft-ietf-trill-rbridge-mib).

(2) Development, within the TRILL protocol context, of requirements
and specifications for broadcast/multicast (multi-destination) frame
reduction; e.g., ARP/ND (Neighbor Discovery) reduction through
use of the TRILL ESADI protocol.

(3) Refinement of TRILL Header Options, as initially defined in
draft-ietf-trill-rbridge-protocol and specification of an initial
base set of options (draft-ietf-trill-rbridge-options).

(4) Provide documentation for the handling of Operations,
Administration, and Maintenance (OAM) in networks using TRILL. Any
documentation will take into consideration any existing OAM
mechanisms that might apply to TRILL.

(5) Publish an implementation report for TRILL.

(6) Analyze use of IS-IS security in TRILL and determine if any work
is needed to accommodate the specific application of IS-IS security
in TRILL forwarding.

(7) Publish a description of the adjacency state machine in TRILL
(draft-ietf-trill-adj).

The trill WG will continue to work with other IETF working groups
such as the isis WG, and SDO groups such as IEEE 802.1 through
established inter-WG relationships and SDO liaison processes,
including early and WG last call review by the isis WG of documents
modifying the IS-IS protocol. The trill WG will have a Routing Area
Advisor for advice on the IS-IS protocol and liaison with the isis
WG. 

Goals and Milestones:

Done      Initial WG draft on VLAN Mapping 
          (draft-ietf-trill-rbridge-vlan-mapping)
Done      Initial WG draft TRILL Header Options 
          (draft-ietf-trill-rbridge-options)
Done      Initial WG draft on RBridge MIB module 
          (draft-ietf-trill-rbridge-mib)
Done      Initial WG draft on trill adjacency state machine 
          (draft-ietf-trill-adj)
Feb 2011  Submit trill adjacency state machine to IESG for publication 
          as Proposed Standard (draft-ietf-trill-adj)
Feb 2011  Submit RBridge MIB module to IESG for publication as Proposed 
          Standard (draft-ietf-trill-rbridge-mib)
Mar 2011  Submit TRILL Header Options to IESG for publication as 
          Proposed Standard (draft-ietf-trill-rbridge-options)
Mar 2011  Initial WG draft on ARP/ND optimizations
Mar 2011  Initial WG draft on RBridge OAM (draft-bond-trill-rbridge-oam)
May 2011  Submit TRILL ARP/ND optimizations to IESG for publication as 
          Proposed Standard
Jun 2011  Submit RBridge support of Data Center Bridging to IESG for 
          publication as Proposed Standard 
          (draft-eastlake-trill-rbridge-dcb)
Jul 2011  Submit RBridge OAM to IESG for publication as Proposed 
          Standard
Jul 2012  Re-charter or shut down the WG 
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Sun Feb 20 01:26: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 2BA2A3A6EFA for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun, 20 Feb 2011 01:26:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.684
X-Spam-Level: 
X-Spam-Status: No, score=-105.684 tagged_above=-999 required=5 tests=[AWL=0.915, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 d1NaGOWKhF2d for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun, 20 Feb 2011 01:26:12 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 2720C3A6F12 for <trill-archive-Osh9cae4@lists.ietf.org>; Sun, 20 Feb 2011 01:25: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 p1K94jla013263; Sun, 20 Feb 2011 01:04:47 -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 p1K94Qlg013190 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Sun, 20 Feb 2011 01:04:36 -0800 (PST)
Received: by wwd20 with SMTP id 20so5653315wwd.21 for <rbridge@postel.org>; Sun, 20 Feb 2011 01:04:25 -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:cc :content-type:content-transfer-encoding; bh=IGT1fqDmQ9NP7vnQMPa+yPhDaSidU0fBZ738iZg5YRI=; b=PS5dF9OtbcdpNZgTk4qJyflVDJcrbIkzb8a86pwIW+Wm2DGyx+w31ykdc/g1trauN2 ZPz5eTLNxzOx9kUBmeWtoMEgz1stLYxr7b+jEGVhWIuWfSzuAu/9CVTCLnEJm2xb1mbk CYvMEUgMRvuzJ/IKn/+Y30m4O+SjM6/vsWguU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; b=i4YA/KWSLHtFo1zb5l/wI13KHB24OKAZhg7CxhzUGHMmxpwzXPf2vFBJMT6jIjsxO/ D9Js0BMLdFXCBc3f2dy6YUK2EIW3uz9gOyFqeeXyZF4z6MZQIvzFjJhufWoSAOdVQ6Io R8A/44hq+SrBBxn8yBefoS7gsl/AiR66/Ow1Q=
Received: by 10.227.154.132 with SMTP id o4mr119554wbw.93.1298192665139; Sun, 20 Feb 2011 01:04:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.68.140 with HTTP; Sun, 20 Feb 2011 01:04:05 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 20 Feb 2011 01:04:05 -0800
Message-ID: <AANLkTi=G1=6Dkv5R_HBF8gdpUBRba3aKMaidAt3ypNuD@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 p1K94Qlg013190
Cc: isis mailing list <isis-wg@ietf.org>
Subject: [rbridge] trill-adj Section 5 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 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?

It is an implementation choice. Probably multicast is good to use
initially or testing a new MTU value to all your neighbors, basically
whenever there is a large or indefinite number of desired
responders. Unicast would be good to use if a single new station has
appeared on the link and you just want to test MTU to that station
without bothering others. That sort of strategy would seem to minimize
the burden on the link. (See some suggested text further below.)

> 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?

Receipt of such an MTU-ack confirms MTU but only one way from the
sender, not to the sender. Whether that makes any difference is an
implementation choice. If bidirectional MTU had previously been
confirmed, perhaps an implementation would use such uni-directional
confirmation to push out, by a bounded amount, the time until it next
does a bi-directional MTU re-confirmation.

Some text could be added, after the text you quote, such as:

   "Use of multicast or unicast is an implementation choice. However,
   the burden on the link is generally minimized by unicasting MTU-ack
   frames and by multicasting MTU-probes when a response from all
   other RBridges on the link is desired, such as when initializing or
   re-confirming MTU, and unicasting MTU-probes when a response from a
   single RBridge, such as one that has just been detected on the
   link, is desired."

Given that the MTU facility is new, it does not seem wise to be overly
constraining at this point.

> 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.

I don't quite understand your comment. If MTU testing is enabled, then
it is a part of determining if an adjacency is in the Report state. It
seems to me that whether or not the adjacency from a non-DRB RBridge
to the DRB is in Report state is important whether or not the DRB is
asserting bypass pseudonode.

If bypass pseudo-node is set, then the RBridge's adjacency to the DRB
   is not particularly special. It gets reported or not in the
   RBridge's LSP, depending on whether that RBridge sees it as being
   in the Report state, just like any other of the RBridge's
   adjacencies on the link.

If bypass pseudo-node is not set, then the DRB is reporting its
   adjacency to the pseudo-node and reports, in the pseudo-node LSP,
   adjacency to other RBridge on the link only if the DRB sees its
   adjacency to the other RBridge as being in the Report
   state. Similarly, the other RBridge only reports its adjacency to
   the pseudo-node if it sees its adjacency to the DRB as in Report
   state; and it does not report adjacencies to any other RBridges on
   the link regardless of the state of its adjacency to them.

The second case above is not clear from the current wording in Section
6. Perhaps the sentence

   "If the DRB does not set the bypass pseudonode bit in its TRILL
   Hellos, then (as in [IS-IS]) it sends LSPs on behalf of the
   pseudonode, and all RBridges report only their adjacency to the
   pseudonode."

should be replaced with

   "If the DRB does not set the bypass pseudonode bit in its TRILL
   Hellos, then (1) the DRB reports in its LSP its adjacency to the
   pseudonode, (2) the DRB sends LSPs on behalf of the pseudonode in
   which it reports adjacency to all other RBridges on the link where
   it sees that adjacency in the Report state, and (3) all other
   RBridges on the link report their adjacency to the pseudonode if
   they see their adjacency to the DRB as being in the Report state
   and do not report any other adjacencies on the."

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

An RBridge can figure out what port an MTU PDU came from by looking at
the source MAC address but normally I don't think it needs that. The
sender of an MTU-probe gets to encode things however they want into
the Probe ID field in such a way that they can identify the resulting
MTU-ack. The Probe ID field is opaque as far as the responder is
concerned.  draft-ietf-isis-trill-05 says, concerning Probe ID: "For
example, an IS creating an MTU-probe could compose this quantity from
a port identifier and probe sequence number relative to that port."

> ...

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  Sun Feb 20 09:26: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 E04593A6CFE for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun, 20 Feb 2011 09:26:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.699
X-Spam-Level: 
X-Spam-Status: No, score=-105.699 tagged_above=-999 required=5 tests=[AWL=0.900, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 US4jg9EuYKdc for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun, 20 Feb 2011 09:26:02 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 62DE43A6C68 for <trill-archive-Osh9cae4@lists.ietf.org>; Sun, 20 Feb 2011 09:26: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 p1KH6xMS025309; Sun, 20 Feb 2011 09:07:00 -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 p1KH6Ei6025262 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Sun, 20 Feb 2011 09:06:24 -0800 (PST)
Received: by wyg36 with SMTP id 36so404689wyg.39 for <rbridge@postel.org>; Sun, 20 Feb 2011 09:06: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; bh=Eq2JwGov61rGMzfm0SMbipbVCibM0vl5/KU1Tw1dvMc=; b=V8ond3jP+lc6KsgMFNXR159p3snA2nXkzbT2nBHGPtzv3ezBvG0ctp4GVZIafK7Gtx m3xrBxse73UdIywZQIJ9F6OslcdC501A13GEQqA0BmTAASakimXpqA0QoqYWIYz0QMhl zTTmaVArFQ6QEiEDWgBjAM37RTtZuhERyk2/g=
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; b=nooeoSVH6st6/l7dS3dm6R0/oi6gDh95tY9LS0Pd1plNEC1n3lLtHOpWIO9+Ytc7E1 5lCCVtdDe6HloyHO5wL/mElbOxoHcW7EwIe1qBKkvvvuWfod2huJeEvDuzzeUuGWaBZU CtE2g6uarm26qS3k1HHSUroIigYx9iMnlMjvw=
Received: by 10.227.144.145 with SMTP id z17mr386511wbu.151.1298221573214; Sun, 20 Feb 2011 09:06:13 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.68.140 with HTTP; Sun, 20 Feb 2011 09:05:53 -0800 (PST)
In-Reply-To: <AE36820147909644AD2A7CA014B1FB520D57BDEB@xmb-sjc-222.amer.cisco.com>
References: <AANLkTikTUAxQ-zPaZwjsVKwAo_mXtJVZu4RAYmW1hyGU@mail.gmail.com> <AANLkTikAFQK5heaqc=hiBt4BeYM2EHQZVAskqLBvOi4z@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D57BDEB@xmb-sjc-222.amer.cisco.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 20 Feb 2011 09:05:53 -0800
Message-ID: <AANLkTinSWKs4ZFrpLFH4OKX6wMGS3aGJnCQhWr4vWVoA@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
Cc: isis mailing list <isis-wg@ietf.org>
Subject: Re: [rbridge] [Isis-wg] Fwd: trill-adj Section 7.2 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Hi Les,

On Mon, Feb 14, 2011 at 10:20 PM, Les Ginsberg (ginsberg)
<ginsberg@cisco.com> wrote:
> Hi Donald.
...

>> Response to some comments by Les Ginsberg:
>>
>> > Section 7.2
>> > ------------
>>
>> > Is IIH padding ignored on receipt?? Or is a padded IIH discarded?
>>
>> I'm not sure why anyone would think that a padded TRILL Hello would be
>> discarded on reciept because of the padding. But, in any case, to
>> clear things up in a more general way, how about replacing
>>
>>   "TRILL Hellos MAY contain an Authentication TLV."
>>
>> at the end of the section with
>>
>>   "In addition to the TLVs mentioned in [RFCtisis] or above in this
>>   document as occuring in TRILL Hellos, a TRILL Hello MAY also
>>   contain any TLV permitted in a Layer 3 IS-IS Hello. Padding and
>>   Neighbor TLVs, as well as any unimplemented or unknown TLVs, are
>>   ignored."
>
> I asked about padding because TRILL makes it a point to deviate from
> the base IS-IS spec in regards to padding - so I thought it worth
> being "extra explicit".
>
> What now seems more important - and which I neglected to ask
> previously - is what happens to a received IIH which exceeds 1470
> bytes? Is it discarded? The draft says "TRILL Hello messages MUST
> NOT exceed 1,470 octets in length..." - which suggests that any IIH
> larger than this is "illegal". What is the intended behavior on
> receipt of a too large IIH?

Ah, good point. This seems like an instance where the IETF maxim of
being conservative in what you send and liberal in what you accept is
the right thing. Should there be some TRILL implementation that padded
TRILL Hellos to 1,471 bytes, on a link with multiple RBridges if those
Hellos were accepted and processed, things would most likely work fine
whereas if they were rejected, you would likely have a loop. So
perhaps

   "TRILL Hello messages MUST NOT exceed 1,470 octets in length and
   SHOULD NOT be padded."

should be replaced by

   "TRILL Hellos PDUs SHOULD NOT be padded and MUST NOT be sent
   exceeding 1,470 octets; however, a received TRILL Hello longer than
   1,470 octets is processed normally."

> As far as your suggested wording above I would propose a modest rewrite:
>
> "A TRILL Hello MAY also contain any TLV permitted in a Layer 3 IS-IS
> Hello. TLVs which either have no defined functionality for TRILL or
> are unsupported/unknown are ignored."

Humm, well, what I don't like about the re-write is the "either...or"
part. It seems to me that there could be things that are
orthogonal/unrelated to TRILL and should be allowed and processed if
they are both allowed in Layer 3 IS-IS LAN Hellos and are supported by
a particular RBridge implementation. For example, IS-IS Authentication
seems for the most part, logically, to be a facility completely
orthogonal to everything else in IS-IS PDUs. An IS implementing
Authentication can add an Authentication TLV to any IS-IS PDU it
originates, check any Authentication TLV in any IS-IS PDU it receives,
etc. While there is mention of IS-IS Authentication in TRILL documents
and I'm not proposing its removal, one could argue that all those
mentions are logically unnecessary. You could even model IS-IS
Authentication as a separate layer between all the rest of IS-IS
(whether Layer 3 or TRILL) and the network. In any case, what exactly
would be your objeciton to simplifying the second sentence you propose
to just "TLVs which are unsupported/unknown are ignored." which is a
general principal of IS-IS anyway?

>> > 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?
>>
>> It was the consensus of the participants in the TRILL interop at UNH
>> IOL to add a requirement for sending a TRILL Neighbor TLV with an
>> empty list when you have no neighbors on the Designated VLAN and the
>> working group went along with them. I suppose it clears thing out more
>> quickly in the case of some types of failures and, in any case, a
>> TRILL Neighbor TLV with an empty list of neighbors is only 3 bytes
>> long.
>>
>> > One of the underlying concerns is that the indication of a
>> > connectivity change in a hello may already be delayed because of
>> > space limitations. The behavior you suggest here only seems to make
>> > that issue more significant.
>>
>> Since, in some cases, this provision requires information to be sent
>> sooner, I would have thought you would consider it an improvement.
>
> The mandatory requirement to send an empty neighbor TLV is not
> useful. If I receive an IIH which has no neighbor TLV I am supposed
> to conclude that the sender actually has some neighbors but they
> chose (for whatever reason) not to send any in this particular
> hello. But I can't draw any useful conclusion from this i.e. if they
> subsequently send an IIH with an empty neighbor TLV (presumably w
> both the smallest/largest flags set) am I to conclude that they lied
> in the previous IIH? And if I did, what would I do about it?
>
> The relevant point to make - which you discuss below - is to
> recommend that the full range of neighbors be advertised as
> frequently as practical as the consequence of not doing so is to
> impact convergence. I think the text about requiring an empty
> neighbor TLV to be sent when you have no neighbors should be removed
> for the sake of clarity.

I admit that it is a bit odd making the inclusion of a TRILL Neighbor
TLV mandatory if their are no neighbors. Perhaps the existing sentence

   "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 sent on the designated VLAN."

could be combined with the new sentence

   "If there are such adjacencies, it is RECOMMENDED that a TRILL
   Neighbor TLV or TLVs, as described in Section 4.4.2.1 of
   [RFCtrill], covering the entire range of MAC addresses, be in TRILL
   Hellos sent on the Designated VLAN, if there is sufficient room."

to produce a newer sentence

   "It is RECOMMENDED that, if there is sufficient room, a TRILL
   Neighbor TLV or TLVs, as described in Section 4.4.2.1 of
   [RFCtrill], covering the entire range of MAC addresses and listing
   all adjacencies with a non-zero Designated VLAN Hello Holding time,
   or an empty list of neighbors if there are no such adjacencies, be
   in TRILL Hellos sent on the Designated VLAN."

To be clear and to maintain the thrust of the output from the plug
fest, I think it is important to mention that, even if not necessarily
in every Hello, it is required to send a TRILL Neighbor TLV with an
empty neighbor list if you are not seeing any neighbors on the
Designated VLAN.

> The convergence issue is one which concerns me as in the presence of
> a large # of neighbors and/or a large number of supported VLANs
> hellos either have to be sent with higher frequency (=> poorer
> scalability) or a longer convergence time has to be accepted. But
> that is a larger issue which I hope we can discuss when you respond
> to my comments on "Reliable Circuit Scoped Flooding".

TRILL has chosen the longer convergence time alternative.

Thanks,
Donald

>   Les
>
>
>> It would be possible to add some general exhortation to implementers
>> not to dilly-dally around too much in sending TRILL Neighbor TLVs. It
>> seems like an issue in implementation quality that I can't believe
>> would be a problem in the real world. There are lots of ways people
>> can do an implementation with bad performance. For example, you could
>> implement or schedule the updating of topology and calculation of
>> shortest paths so that it took, say, an hour to process LSPs that
>> updated reachability. I believe such an implementation would be
>> conformant to the existing IS-IS specification but, somehow, I just
>> don't see people using it (or buying it if it were a product). Just
>> so, an implementation that, when the neighbor list was non-empty, only
>> sent a TRILL neighbor TLV once an hour wouldn't get used (or purchased
>> if it was a product), at least not for any environment that seems
>> plausible to me.
>>
>> In any case, "If there are such adjacencies, then the Hello MAY
>> contain a TRILL Neighbor TLV as described in Section 4.4.2.1 of
>> [RFCtrill]."  could be replaced with something like the following:
>>
>> "If there are such adjacencies, it is RECOMMENDED that a TRILL
>> Neighbor TLV or TLVs, as described in Section 4.4.2.1 of [RFCtrill],
>> covering the entire range of MAC addresses, be in TRILL Hellos sent on
>> the Designated VLAN, if there is sufficient room. If this is not
>> possible, then TRILL Neighbor TLV's covering sub-ranges of MAC
>> addresses should be sent so that the entire range is covered
>> reasonably promptly.  Delays in sending TRILL Neighbor TLVs will delay
>> the advancement of adjacencies to the Report state and the discovery
>> of some link failures. Rapid, for example sub-second, detection of
>> link or node failures is best addressed with a protocol designed for
>> that purpose, such as BFD [RFC5880], use of which with TRILL will be
>> specified in a separate document."

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street
 Milford, MA 01757 USA
 d3e3e3@gmail.com
_______________________________________________
rbridge mailing list
rbridge@postel.org
http://mailman.postel.org/mailman/listinfo/rbridge

From rbridge-bounces@postel.org  Mon Feb 21 00:37: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 42C513A6F84 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 21 Feb 2011 00:37:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.376
X-Spam-Level: 
X-Spam-Status: No, score=-104.376 tagged_above=-999 required=5 tests=[AWL=2.224, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 OCnwbem2+4Nt for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 21 Feb 2011 00:37:27 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 55F9D3A6DFF for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 21 Feb 2011 00:37: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 p1L8GjNa001646; Mon, 21 Feb 2011 00:16:46 -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 p1L8GGkP001542 for <rbridge@postel.org>; Mon, 21 Feb 2011 00:16:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 263FF3A6F84 for <rbridge@postel.org>; Mon, 21 Feb 2011 00:15:03 -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 N7HdyHJLJBXm; Mon, 21 Feb 2011 00:15:02 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2E2903A6FBE; Mon, 21 Feb 2011 00:15: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.12
Message-ID: <20110221081502.12217.32680.idtracker@localhost>
Date: Mon, 21 Feb 2011 00:15: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-03.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-03.txt
	Pages           : 29
	Date            : 2011-02-21

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-03.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-03.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2011-02-21001206.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 Feb 21 01:01:01 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 622563A6FBE for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 21 Feb 2011 01:01:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.736
X-Spam-Level: 
X-Spam-Status: No, score=-105.736 tagged_above=-999 required=5 tests=[AWL=0.863, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 5RzRSeOrdf8m for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 21 Feb 2011 01:01:00 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 3EA923A6F68 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 21 Feb 2011 01:01:00 -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 p1L8mGJN005150; Mon, 21 Feb 2011 00:48:17 -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 p1L8lXIm005057 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 21 Feb 2011 00:47:43 -0800 (PST)
Received: by wwd20 with SMTP id 20so6391293wwd.21 for <rbridge@postel.org>; Mon, 21 Feb 2011 00:47:32 -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:content-type:content-transfer-encoding; bh=g+40PuraFlRotX1ymGzweNn4MVMUWlFm4p1vejD5l4A=; b=BhZP14FFGhttZRU1eQyblUSA5+Gz2TBBJX8BK9UZxnObVlo13vW8f0i3pC3rBp51Yh ud9UfKRKFRmd0PMoyafpbfjcwbo3ngddifDQeBxKyDXDrD6+nblm1Kk0nSA+RLPyYfyf 6e0yLZ5ll3vlOHHYJfO62C+zoOp9kUfxxovOM=
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=jhUz9elHLmQPsLmEuNFTgnTP51XVTy8fpDHf0cEDKjaHbr7OBjP7YDZcqxyALxj6qy dwAHcRz/KLObTjJJZPy/B/xqzeMUGqN6iqlKrFwCZ2LyuBaibYMUMmbd1b8MMLEbrEwU obyoFsAUyofkJn9GrlzEiDkomfIZC3zYMOToQ=
Received: by 10.227.10.134 with SMTP id p6mr902245wbp.180.1298278052327; Mon, 21 Feb 2011 00:47:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.68.140 with HTTP; Mon, 21 Feb 2011 00:47:12 -0800 (PST)
In-Reply-To: <20110221081502.12217.32680.idtracker@localhost>
References: <20110221081502.12217.32680.idtracker@localhost>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 21 Feb 2011 00:47:12 -0800
Message-ID: <AANLkTikejvGhTUr08UCRCYCXu861X6OKi4nDd-tU55Gf@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 p1L8lXIm005057
Subject: Re: [rbridge] I-D Action:draft-ietf-trill-adj-03.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

This draft has some additional comment resolutions incorporated. There
is also now a change history appendix.

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

On Mon, Feb 21, 2011 at 12:15 AM,  <Internet-Drafts@ietf.org> wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts direct=
ories.
> This draft is a work item of the Transparent Interconnection of Lots of L=
inks Working Group of the IETF.
>
>
> =A0 =A0 =A0 =A0Title =A0 =A0 =A0 =A0 =A0 : RBridges: Adjacency
> =A0 =A0 =A0 =A0Author(s) =A0 =A0 =A0 : D. Eastlake 3rd, et al.
> =A0 =A0 =A0 =A0Filename =A0 =A0 =A0 =A0: draft-ietf-trill-adj-03.txt
> =A0 =A0 =A0 =A0Pages =A0 =A0 =A0 =A0 =A0 : 29
> =A0 =A0 =A0 =A0Date =A0 =A0 =A0 =A0 =A0 =A0: 2011-02-21
>
> 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-03.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.
>
>
> _______________________________________________
> 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 Feb 22 16:46: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 061043A6452 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 22 Feb 2011 16:46:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.932
X-Spam-Level: 
X-Spam-Status: No, score=-7.932 tagged_above=-999 required=5 tests=[AWL=-1.333, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 1D7zZ3j9mbsG for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 22 Feb 2011 16:46:40 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 9ABB33A6765 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 22 Feb 2011 16:46:39 -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 p1N0djQT005878; Tue, 22 Feb 2011 16:39:48 -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 p1N0dF6b005787 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Tue, 22 Feb 2011 16:39:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ginsberg@cisco.com; l=6978; q=dns/txt; s=iport; t=1298421564; x=1299631164; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=yFqWYWTUUuiOKiweaa+QoWgbQm5fPxFOaEbFox5gU5c=; b=MZrXEAl3Xhl7EZhDcU+UjVzGL6ATq2s9AIlFTW+6Rwlpi4IyHaXRZ/pB weQKhcYQbExqRu6NBDPNzXa0alsvNwRDEaIBbme+cqk2sqG0teFZ4QzJS jrKIAyN5sxx9oTpwbq6nX4jiPtH/Qv6SeaW2UPP26fAbv6loeH1rOtI6r s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUBAPPlY02rR7Hu/2dsb2JhbACXVo5Mc6E4m1WCfRqCRwSFDYpHgwo
X-IronPort-AV: E=Sophos;i="4.62,209,1297036800"; d="scan'208";a="333825520"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 23 Feb 2011 00:39:14 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p1N0dE2U011773; Wed, 23 Feb 2011 00:39:14 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);  Tue, 22 Feb 2011 16:39:14 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 22 Feb 2011 16:39:11 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D6A319C@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTi=G1=6Dkv5R_HBF8gdpUBRba3aKMaidAt3ypNuD@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: trill-adj Section 5 comments
Thread-Index: AcvQ3S5Wa/UICwjxR+qbjPVv3huhFwCEcf7Q
References: <AANLkTi=G1=6Dkv5R_HBF8gdpUBRba3aKMaidAt3ypNuD@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>, <rbridge@postel.org>
X-OriginalArrivalTime: 23 Feb 2011 00:39:14.0190 (UTC) FILETIME=[184E62E0:01CBD2F2]
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 p1N0dF6b005787
Cc: isis mailing list <isis-wg@ietf.org>
Subject: Re: [rbridge] trill-adj Section 5 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 -

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Sunday, February 20, 2011 1:04 AM
> To: Les Ginsberg (ginsberg); rbridge@postel.org
> Cc: isis mailing list
> Subject: trill-adj Section 5 comments
> =

> Response to some comments by Les Ginsberg:
> =

> > 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?
> =

> It is an implementation choice. Probably multicast is good to use
> initially or testing a new MTU value to all your neighbors, basically
> whenever there is a large or indefinite number of desired
> responders. Unicast would be good to use if a single new station has
> appeared on the link and you just want to test MTU to that station
> without bothering others. That sort of strategy would seem to minimize
> the burden on the link. (See some suggested text further below.)
> =

> > 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?
> =

> Receipt of such an MTU-ack confirms MTU but only one way from the
> sender, not to the sender. Whether that makes any difference is an
> implementation choice. If bidirectional MTU had previously been
> confirmed, perhaps an implementation would use such uni-directional
> confirmation to push out, by a bounded amount, the time until it next
> does a bi-directional MTU re-confirmation.

If RB1 sends a multicast MTU-ACK in response to a Probe from RB2 - and the =
ACK is received by RB3 - what use can RB3 make of this? As you have stated =
the ACK confirms receipt by RB1 of a Probe from RB2. I don't think this inf=
ormation is useful to RB3 - which argues that ACKs should always be unicast=
. But as you allow multicast ACKs I am trying to understand why??

> =

> Some text could be added, after the text you quote, such as:
> =

>    "Use of multicast or unicast is an implementation choice. However,
>    the burden on the link is generally minimized by unicasting MTU-ack
>    frames and by multicasting MTU-probes when a response from all
>    other RBridges on the link is desired, such as when initializing or
>    re-confirming MTU, and unicasting MTU-probes when a response from a
>    single RBridge, such as one that has just been detected on the
>    link, is desired."
> =

> Given that the MTU facility is new, it does not seem wise to be overly
> constraining at this point.
> =

> > 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.
> =

> I don't quite understand your comment.

If pseudo-node bypass is NOT set then - as you detail below - only neighbor=
s to the pseudo-node will be advertised in non-pseudo-node LSPs - so the ex=
istence of Report state between two non-DRB neighbors isn't useful. Given t=
hat the invention of pseudo-node bypass was solely to minimize the number o=
f LSPs generated I find it somewhat curious that you are unnecessarily prof=
ligate in the use of MTU PDUs.

??

> If MTU testing is enabled, then
> it is a part of determining if an adjacency is in the Report state. It
> seems to me that whether or not the adjacency from a non-DRB RBridge
> to the DRB is in Report state is important whether or not the DRB is
> asserting bypass pseudonode.
> =

> If bypass pseudo-node is set, then the RBridge's adjacency to the DRB
>    is not particularly special. It gets reported or not in the
>    RBridge's LSP, depending on whether that RBridge sees it as being
>    in the Report state, just like any other of the RBridge's
>    adjacencies on the link.
> =

> If bypass pseudo-node is not set, then the DRB is reporting its
>    adjacency to the pseudo-node and reports, in the pseudo-node LSP,
>    adjacency to other RBridge on the link only if the DRB sees its
>    adjacency to the other RBridge as being in the Report
>    state. Similarly, the other RBridge only reports its adjacency to
>    the pseudo-node if it sees its adjacency to the DRB as in Report
>    state; and it does not report adjacencies to any other RBridges on
>    the link regardless of the state of its adjacency to them.

Exactly my point. So why waste cycles sending MTU Probes between two non-DR=
Bs?

> =

> The second case above is not clear from the current wording in Section
> 6. Perhaps the sentence
> =

>    "If the DRB does not set the bypass pseudonode bit in its TRILL
>    Hellos, then (as in [IS-IS]) it sends LSPs on behalf of the
>    pseudonode, and all RBridges report only their adjacency to the
>    pseudonode."
> =

> should be replaced with
> =

>    "If the DRB does not set the bypass pseudonode bit in its TRILL
>    Hellos, then (1) the DRB reports in its LSP its adjacency to the
>    pseudonode, (2) the DRB sends LSPs on behalf of the pseudonode in
>    which it reports adjacency to all other RBridges on the link where
>    it sees that adjacency in the Report state, and (3) all other
>    RBridges on the link report their adjacency to the pseudonode if
>    they see their adjacency to the DRB as being in the Report state
>    and do not report any other adjacencies on the."

I thought you had previously agreed on revised wording based on Mike Shand'=
s suggestion. Are you proposing to revise the (updated) text again?

> =

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

> An RBridge can figure out what port an MTU PDU came from by looking at
> the source MAC address but normally I don't think it needs that.

Section 4.4.4 of RFCTrill allows that an RB can have multiple ports on a LA=
N which share the same MAC address. It therefore seems necessary to include=
 PortID to correctly identify the sender.

   Les

> The
> sender of an MTU-probe gets to encode things however they want into
> the Probe ID field in such a way that they can identify the resulting
> MTU-ack. The Probe ID field is opaque as far as the responder is
> concerned.  draft-ietf-isis-trill-05 says, concerning Probe ID: "For
> example, an IS creating an MTU-probe could compose this quantity from
> a port identifier and probe sequence number relative to that port."
> =

> > ...
> =

> 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  Tue Feb 22 18:03: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 3166B3A67DF for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 22 Feb 2011 18:03:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.872
X-Spam-Level: 
X-Spam-Status: No, score=-7.872 tagged_above=-999 required=5 tests=[AWL=-1.273, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 X8Nqezo56m+m for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Tue, 22 Feb 2011 18:02:58 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 7F34C3A6938 for <trill-archive-Osh9cae4@lists.ietf.org>; Tue, 22 Feb 2011 18:02: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 p1N1kpPt018677; Tue, 22 Feb 2011 17:46:53 -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 p1N1kL5M018612 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Tue, 22 Feb 2011 17:46:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=ginsberg@cisco.com; l=11071; q=dns/txt; s=iport; t=1298425590; x=1299635190; h=mime-version:content-transfer-encoding:subject:date: message-id:in-reply-to:references:from:to:cc; bh=WzKNYPa8ZNs9rjqDnzdB3g7sFNQlV51MnunWLLHrlpE=; b=ixodGXMENcvMN0t/dZoV7gjeuVwY1FMO7XNyG0xWVgGUcg2cDpaon9Xw 84L8JnupYZtmeUBFysAeWIQ67VdFv30Jqzf35NQNpXf8q/owrMy4qAfNs 4ycjdufJ7YekI8Ung5PQj7FfvXwI1zidMdmVpjlKYNEVlbqxEk1nymjLa 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwBAGr1Y02rR7Hu/2dsb2JhbACXV45Mc6Emm1eDF4JHBIUNikiDCg
X-IronPort-AV: E=Sophos;i="4.62,209,1297036800"; d="scan'208";a="333858077"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-5.cisco.com with ESMTP; 23 Feb 2011 01:46:21 +0000
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id p1N1kK5M022329; Wed, 23 Feb 2011 01:46:21 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);  Tue, 22 Feb 2011 17:46:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 22 Feb 2011 17:46:09 -0800
Message-ID: <AE36820147909644AD2A7CA014B1FB520D6A31D4@xmb-sjc-222.amer.cisco.com>
In-Reply-To: <AANLkTinSWKs4ZFrpLFH4OKX6wMGS3aGJnCQhWr4vWVoA@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Isis-wg] Fwd: trill-adj Section 7.2 comments
Thread-Index: AcvRIHzEZCO5qdwZTMKkerz1RVJLOgB2mT9g
References: <AANLkTikTUAxQ-zPaZwjsVKwAo_mXtJVZu4RAYmW1hyGU@mail.gmail.com> <AANLkTikAFQK5heaqc=hiBt4BeYM2EHQZVAskqLBvOi4z@mail.gmail.com> <AE36820147909644AD2A7CA014B1FB520D57BDEB@xmb-sjc-222.amer.cisco.com> <AANLkTinSWKs4ZFrpLFH4OKX6wMGS3aGJnCQhWr4vWVoA@mail.gmail.com>
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Donald Eastlake" <d3e3e3@gmail.com>, <rbridge@postel.org>
X-OriginalArrivalTime: 23 Feb 2011 01:46:20.0877 (UTC) FILETIME=[78660FD0:01CBD2FB]
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 p1N1kL5M018612
Cc: isis mailing list <isis-wg@ietf.org>
Subject: Re: [rbridge] [Isis-wg] Fwd: trill-adj Section 7.2 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="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

Donald -

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Sunday, February 20, 2011 9:06 AM
> To: Les Ginsberg (ginsberg); rbridge@postel.org
> Cc: isis mailing list
> Subject: Re: [Isis-wg] Fwd: trill-adj Section 7.2 comments
> 
> Hi Les,
> 
> On Mon, Feb 14, 2011 at 10:20 PM, Les Ginsberg (ginsberg)
> <ginsberg@cisco.com> wrote:
> > Hi Donald.
> ...
> 
> >> Response to some comments by Les Ginsberg:
> >>
> >> > Section 7.2
> >> > ------------
> >>
> >> > Is IIH padding ignored on receipt?? Or is a padded IIH discarded?
> >>
> >> I'm not sure why anyone would think that a padded TRILL Hello would
> be
> >> discarded on reciept because of the padding. But, in any case, to
> >> clear things up in a more general way, how about replacing
> >>
> >>   "TRILL Hellos MAY contain an Authentication TLV."
> >>
> >> at the end of the section with
> >>
> >>   "In addition to the TLVs mentioned in [RFCtisis] or above in this
> >>   document as occuring in TRILL Hellos, a TRILL Hello MAY also
> >>   contain any TLV permitted in a Layer 3 IS-IS Hello. Padding and
> >>   Neighbor TLVs, as well as any unimplemented or unknown TLVs, are
> >>   ignored."
> >
> > I asked about padding because TRILL makes it a point to deviate from
> > the base IS-IS spec in regards to padding - so I thought it worth
> > being "extra explicit".
> >
> > What now seems more important - and which I neglected to ask
> > previously - is what happens to a received IIH which exceeds 1470
> > bytes? Is it discarded? The draft says "TRILL Hello messages MUST
> > NOT exceed 1,470 octets in length..." - which suggests that any IIH
> > larger than this is "illegal". What is the intended behavior on
> > receipt of a too large IIH?
> 
> Ah, good point. This seems like an instance where the IETF maxim of
> being conservative in what you send and liberal in what you accept is
> the right thing. Should there be some TRILL implementation that padded
> TRILL Hellos to 1,471 bytes, on a link with multiple RBridges if those
> Hellos were accepted and processed, things would most likely work fine
> whereas if they were rejected, you would likely have a loop. So
> perhaps
> 
>    "TRILL Hello messages MUST NOT exceed 1,470 octets in length and
>    SHOULD NOT be padded."
> 
> should be replaced by
> 
>    "TRILL Hellos PDUs SHOULD NOT be padded and MUST NOT be sent
>    exceeding 1,470 octets; however, a received TRILL Hello longer than
>    1,470 octets is processed normally."

OK

> 
> > As far as your suggested wording above I would propose a modest
> rewrite:
> >
> > "A TRILL Hello MAY also contain any TLV permitted in a Layer 3 IS-IS
> > Hello. TLVs which either have no defined functionality for TRILL or
> > are unsupported/unknown are ignored."
> 
> Humm, well, what I don't like about the re-write is the "either...or"
> part. It seems to me that there could be things that are
> orthogonal/unrelated to TRILL and should be allowed and processed if
> they are both allowed in Layer 3 IS-IS LAN Hellos and are supported by
> a particular RBridge implementation. For example, IS-IS Authentication
> seems for the most part, logically, to be a facility completely
> orthogonal to everything else in IS-IS PDUs. An IS implementing
> Authentication can add an Authentication TLV to any IS-IS PDU it
> originates, check any Authentication TLV in any IS-IS PDU it receives,
> etc. While there is mention of IS-IS Authentication in TRILL documents
> and I'm not proposing its removal, one could argue that all those
> mentions are logically unnecessary. You could even model IS-IS
> Authentication as a separate layer between all the rest of IS-IS
> (whether Layer 3 or TRILL) and the network. In any case, what exactly
> would be your objeciton to simplifying the second sentence you propose
> to just "TLVs which are unsupported/unknown are ignored." which is a
> general principal of IS-IS anyway?

OK

> 
> >> > 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?
> >>
> >> It was the consensus of the participants in the TRILL interop at
UNH
> >> IOL to add a requirement for sending a TRILL Neighbor TLV with an
> >> empty list when you have no neighbors on the Designated VLAN and
the
> >> working group went along with them. I suppose it clears thing out
> more
> >> quickly in the case of some types of failures and, in any case, a
> >> TRILL Neighbor TLV with an empty list of neighbors is only 3 bytes
> >> long.
> >>
> >> > One of the underlying concerns is that the indication of a
> >> > connectivity change in a hello may already be delayed because of
> >> > space limitations. The behavior you suggest here only seems to
> make
> >> > that issue more significant.
> >>
> >> Since, in some cases, this provision requires information to be
sent
> >> sooner, I would have thought you would consider it an improvement.
> >
> > The mandatory requirement to send an empty neighbor TLV is not
> > useful. If I receive an IIH which has no neighbor TLV I am supposed
> > to conclude that the sender actually has some neighbors but they
> > chose (for whatever reason) not to send any in this particular
> > hello. But I can't draw any useful conclusion from this i.e. if they
> > subsequently send an IIH with an empty neighbor TLV (presumably w
> > both the smallest/largest flags set) am I to conclude that they lied
> > in the previous IIH? And if I did, what would I do about it?
> >
> > The relevant point to make - which you discuss below - is to
> > recommend that the full range of neighbors be advertised as
> > frequently as practical as the consequence of not doing so is to
> > impact convergence. I think the text about requiring an empty
> > neighbor TLV to be sent when you have no neighbors should be removed
> > for the sake of clarity.
> 
> I admit that it is a bit odd making the inclusion of a TRILL Neighbor
> TLV mandatory if their are no neighbors. Perhaps the existing sentence
> 
>    "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 sent on the designated VLAN."
> 
> could be combined with the new sentence
> 
>    "If there are such adjacencies, it is RECOMMENDED that a TRILL
>    Neighbor TLV or TLVs, as described in Section 4.4.2.1 of
>    [RFCtrill], covering the entire range of MAC addresses, be in TRILL
>    Hellos sent on the Designated VLAN, if there is sufficient room."
> 
> to produce a newer sentence
> 
>    "It is RECOMMENDED that, if there is sufficient room, a TRILL
>    Neighbor TLV or TLVs, as described in Section 4.4.2.1 of
>    [RFCtrill], covering the entire range of MAC addresses and listing
>    all adjacencies with a non-zero Designated VLAN Hello Holding time,
>    or an empty list of neighbors if there are no such adjacencies, be
>    in TRILL Hellos sent on the Designated VLAN."


OK. This clarifies that the motivation for sending TRILL Neighbor TLV is
the same in the no neighbor case as in the case where there are
neighbors.

   Les

> 
> To be clear and to maintain the thrust of the output from the plug
> fest, I think it is important to mention that, even if not necessarily
> in every Hello, it is required to send a TRILL Neighbor TLV with an
> empty neighbor list if you are not seeing any neighbors on the
> Designated VLAN.
> 
> > The convergence issue is one which concerns me as in the presence of
> > a large # of neighbors and/or a large number of supported VLANs
> > hellos either have to be sent with higher frequency (=> poorer
> > scalability) or a longer convergence time has to be accepted. But
> > that is a larger issue which I hope we can discuss when you respond
> > to my comments on "Reliable Circuit Scoped Flooding".
> 
> TRILL has chosen the longer convergence time alternative.
> 
> Thanks,
> Donald
> 
> >   Les
> >
> >
> >> It would be possible to add some general exhortation to
implementers
> >> not to dilly-dally around too much in sending TRILL Neighbor TLVs.
> It
> >> seems like an issue in implementation quality that I can't believe
> >> would be a problem in the real world. There are lots of ways people
> >> can do an implementation with bad performance. For example, you
> could
> >> implement or schedule the updating of topology and calculation of
> >> shortest paths so that it took, say, an hour to process LSPs that
> >> updated reachability. I believe such an implementation would be
> >> conformant to the existing IS-IS specification but, somehow, I just
> >> don't see people using it (or buying it if it were a product). Just
> >> so, an implementation that, when the neighbor list was non-empty,
> only
> >> sent a TRILL neighbor TLV once an hour wouldn't get used (or
> purchased
> >> if it was a product), at least not for any environment that seems
> >> plausible to me.
> >>
> >> In any case, "If there are such adjacencies, then the Hello MAY
> >> contain a TRILL Neighbor TLV as described in Section 4.4.2.1 of
> >> [RFCtrill]."  could be replaced with something like the following:
> >>
> >> "If there are such adjacencies, it is RECOMMENDED that a TRILL
> >> Neighbor TLV or TLVs, as described in Section 4.4.2.1 of
[RFCtrill],
> >> covering the entire range of MAC addresses, be in TRILL Hellos sent
> on
> >> the Designated VLAN, if there is sufficient room. If this is not
> >> possible, then TRILL Neighbor TLV's covering sub-ranges of MAC
> >> addresses should be sent so that the entire range is covered
> >> reasonably promptly.  Delays in sending TRILL Neighbor TLVs will
> delay
> >> the advancement of adjacencies to the Report state and the
discovery
> >> of some link failures. Rapid, for example sub-second, detection of
> >> link or node failures is best addressed with a protocol designed
for
> >> that purpose, such as BFD [RFC5880], use of which with TRILL will
be
> >> specified in a separate document."
> 
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street
>  Milford, MA 01757 USA
>  d3e3e3@gmail.com

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

From rbridge-bounces@postel.org  Sun Feb 27 19:13:40 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 BA7813A6A83 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun, 27 Feb 2011 19:13:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.721
X-Spam-Level: 
X-Spam-Status: No, score=-105.721 tagged_above=-999 required=5 tests=[AWL=0.878, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 Vb9W2qfIFg-Y for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Sun, 27 Feb 2011 19:13:39 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id D203D3A6A86 for <trill-archive-Osh9cae4@lists.ietf.org>; Sun, 27 Feb 2011 19:13:39 -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 p1S2sJ5l001168; Sun, 27 Feb 2011 18:54: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 p1S2ros0001133 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for <rbridge@postel.org>; Sun, 27 Feb 2011 18:54:00 -0800 (PST)
Received: by wwi14 with SMTP id 14so3478622wwi.21 for <rbridge@postel.org>; Sun, 27 Feb 2011 18:53:50 -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=kvaU64bAa7X14EWXE2DEph20RElnMHSdptUbuVRx4XI=; b=HnscEbFWH0DSwhTbzNjCwJdVfLRBuqSItUE1DLluH5hr0tvc/s5mq2cs6LO16n2cvw pGZ5H9IvCtm/3BY77gHqQv9IE6GtGmcIo7rlO37fdPhemZYXyfKlHAAK7XM2LTiDH8mf jbjU0nWmE3BNhofLlIxht4OiHEguvibikRAYQ=
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=vML/JoJqYwmw/TwiYRED/ZmseDPSW7pLd47xs3D6AfrQHQgD5ZcltMzlo8tnhTfzzj qv4aUJAQB1iBDx7WwEbcnxQgJzr0k9RXTj0m2NQRwceWgwfom4F81gsXRfKEXtcGyWK/ OUu9jA1KdVuu2j4aJSk/OlGj/A4PD6PQxM7K4=
Received: by 10.227.143.206 with SMTP id w14mr4462631wbu.66.1298861630102; Sun, 27 Feb 2011 18:53:50 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.68.140 with HTTP; Sun, 27 Feb 2011 18:53:30 -0800 (PST)
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 27 Feb 2011 21:53:30 -0500
Message-ID: <AANLkTikLfsG4YJoQMm2guY4UsoB15C5X9Mv6drg+9r=v@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 p1S2ros0001133
Subject: [rbridge] TRILL Header Options terminology
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,

The current TRILL options draft uses the terminology such as "bit
encoded options" for what are more commonly referred to as "flags".
Since these flags are in extensions to the basic fixed TRILL Header,
it seems reasonable to call them "extended flags" or the like instead
of "bit encoded options"... Any other opinions?

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 Feb 28 04:21:43 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 C985C3A6A80 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 28 Feb 2011 04:21:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.268
X-Spam-Level: 
X-Spam-Status: No, score=-104.268 tagged_above=-999 required=5 tests=[AWL=-0.458, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4, 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 amGFa7M3PqYv for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 28 Feb 2011 04:21:40 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 783743A6AC5 for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 28 Feb 2011 04:21:39 -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 p1SC20LD000122; Mon, 28 Feb 2011 04:02:00 -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 p1SC1iWG000107 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 28 Feb 2011 04:01:54 -0800 (PST)
Received: by wyf23 with SMTP id 23so4513382wyf.39 for <rbridge@postel.org>; Mon, 28 Feb 2011 04:01:44 -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=fUvzAa5s6t+jtjNBcd2z9PjaApoZbwlV0DxhejBykss=; b=bNFQkK8XTlRHdzUz7/AOLdxGz7IGJQpvsrOyEbsxFJ32Ecjq/rufsZvNq3eYyj8bqn riGdBjmMt2YstzA6U2EqCbUNRou/kftCjLCX4SDargdatGSkJhsWWEUzQvw0UatZSE2Y 5JbYCu8lQk3FzA9uiz3/qUgAP1ZFFOG8R7Oow=
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=Ay86bsxljZGEg80vCLdkYe2bWVWglS87vAqVQjsMOm6EDikkcpSK13WOIL1zJ/bVho tx63Z+dl41xG9NsrXW1JpPwZDvyn95AcNEH4lBWFO7AS57IGkkgjR67txHIaZdWE9RFu DIFu6XpkN9O87IG/Hv3OWNjHJXWHkMMiWFfs8=
Received: by 10.227.135.4 with SMTP id l4mr4851570wbt.95.1298894504092; Mon, 28 Feb 2011 04:01:44 -0800 (PST)
MIME-Version: 1.0
Received: by 10.227.68.140 with HTTP; Mon, 28 Feb 2011 04:01:24 -0800 (PST)
In-Reply-To: <001901cbd6f3$89477630$91626e0a@china.huawei.com>
References: <20110209200002.28071.93060.idtracker@localhost> <001901cbd6f3$89477630$91626e0a@china.huawei.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 28 Feb 2011 07:01:24 -0500
Message-ID: <AANLkTi=__jwJMKS_P3s-g6EReaZceUeqe50mhn0qbCQQ@mail.gmail.com>
To: Xu Xiaohu <xuxh@huawei.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 p1SC1iWG000107
Cc: rbridge@postel.org, isis-wg@ietf.org
Subject: Re: [rbridge] [Isis-wg] I-D Action:draft-ietf-isis-layer2-11.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: multipart/mixed; boundary="===============0398749677=="
Sender: rbridge-bounces@postel.org
Errors-To: rbridge-bounces@postel.org

--===============0398749677==
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: 8bit

Hi,

There has been discussion of "breaking the 4,096 limit" in the TRILL
WG, as you can see from the mailing list archives. Most, possible all,
the suggested solutions do not require any change in the size of a
"VLAN ID" but add other identifiers or use other techniques.

Thanks,
Donald

PS: I am about to leave on a trip and will probably be unable to
respond further until I arrive at my destination.
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street
 Milford, MA 01757 USA
 d3e3e3@gmail.com



2011/2/27 Xu Xiaohu <xuxh@huawei.com>:
> Hi all,
>
> As I heard from some could data center operators, 4096 VLANs would not be
> enough for isolating the huge amount of tenants in their future data center
> networks. Besides, the VLAN translation is a desirable feature in some
> scenarios (e.g., the same VLAN ID in different parts of the data center
> network is used for different tenants while different VLAN IDs in different
> parts of the data center network are used to connect a single tenant).
>
> Hence, I wonder whether it is possible to replace the fixed-length VLAN ID
> field (e.g., the VLAN-ID field in the MAC-reachability TLV as shown below)
> with a tenant/VPN instance ID TLV. With such TLV, at least the two problems
> mentioned above can be solved easily.
>
> Best wishes,
> Xiaohu
>
> ========================================================================
> 2.1.  The MAC-Reachability TLV
>
>   The MAC-Reachability (MAC-RI) TLV is IS-IS TLV type 141 and has the
>   following format:
>
>   +-+-+-+-+-+-+-+-+
>   | Type= MAC-RI  |                  (1 byte)
>   +-+-+-+-+-+-+-+-+
>   |   Length      |                  (1 byte)
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |   Topology-Id/ Nickname       |  (2 bytes)
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |   Confidence  |                  (1 byte)
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |  RESV |      VLAN-ID          |  (2 bytes)
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                          MAC (1)    (6 bytes)                 |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                   .................                           |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>   |                          MAC (N)    (6 bytes)                 |
>   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
>
>
>
>> -----邮件原件-----
>> 发件人: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org] 代表
>> Internet-Drafts@ietf.org
>> 发送时间: 2011年2月10日 4:00
>> 收件人: i-d-announce@ietf.org
>> 抄送: isis-wg@ietf.org
>> 主题: [Isis-wg] I-D Action:draft-ietf-isis-layer2-11.txt
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts
>> directories.
>> This draft is a work item of the IS-IS for IP Internets Working Group of
> the
>> IETF.
>>
>>
>>       Title           : Extensions to IS-IS for Layer-2 Systems
>>       Author(s)       : A. Banerjee, D. Ward
>>       Filename        : draft-ietf-isis-layer2-11.txt
>>       Pages           : 11
>>       Date            : 2011-02-09
>>
>> This document specifies the Intermediate System to Intermediate
>> System (IS-IS) extensions necessary to support link state routing for
>> any protocols running directly over Layer-2.  While supporting this
>> concept involves several pieces, this document only describes
>> extensions to IS-IS.  Furthermore, the Type, Length, Value pairs
>> (TLVs) described in this document are generic Layer-2 additions and
>> specific ones as needed are defined in the IS-IS technology specific
>> extensions.  We leave it to the systems using these IS-IS extensions
>> to explain how the information carried in IS-IS is used.
>>
>> A URL for this Internet-Draft is:
>> http://www.ietf.org/internet-drafts/draft-ietf-isis-layer2-11.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.
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/isis-wg
>


--===============0398749677==
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

--===============0398749677==--

From rbridge-bounces@postel.org  Mon Feb 28 11:46: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 BD71F3A6C2F for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 28 Feb 2011 11:46:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 34znYSbPKNuE for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Mon, 28 Feb 2011 11:46:18 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 1EA063A6C6E for <trill-archive-Osh9cae4@lists.ietf.org>; Mon, 28 Feb 2011 11:46: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 p1SJTCNj025438; Mon, 28 Feb 2011 11:29:14 -0800 (PST)
Received: from rtp-iport-1.cisco.com (rtp-iport-1.cisco.com [64.102.122.148]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p1SJScRq025315 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for <rbridge@postel.org>; Mon, 28 Feb 2011 11:28:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=rdroms@cisco.com; l=1058; q=dns/txt; s=iport; t=1298921327; x=1300130927; h=from:content-transfer-encoding:subject:date:message-id: cc:to:mime-version; bh=GSN4rreQt2gmpQbotAgejb3dCmZ8MsBnW3W/nC4PZI4=; b=YRAYh+hrjzdlEC5oIC+uuJjKF0S8XZRmWlXS/0AUD1sxOWmhLXaY5cqL 4JhqcErdCoLSIXOBCy7q/QRe2DYGNERMssfHUXvBELtGljVUzQvb5vKn7 vaf45d9Md7ivXsC1MdYyK4rcQBwZCaQySaZqtm7SF3YDGiZWqg1A0YD9E o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AsYHAEqGa01AZnwN/2dsb2JhbACYM44VdKA1m06FYQSFD4cNgz4
X-IronPort-AV: E=Sophos;i="4.62,242,1297036800"; d="scan'208";a="220811537"
Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 28 Feb 2011 19:28:38 +0000
Received: from [161.44.65.117] ([161.44.65.117]) by rtp-core-2.cisco.com (8.13.8/8.14.3) with ESMTP id p1SJRhJW020674; Mon, 28 Feb 2011 19:28:37 GMT
From: Ralph Droms <rdroms@cisco.com>
Date: Mon, 28 Feb 2011 14:28:37 -0500
Message-Id: <27B18EB2-AB0C-4858-A8B3-79D40D59180A@cisco.com>
To: rbridge@postel.org
Mime-Version: 1.0 (Apple Message framework v1082)
X-Mailer: Apple Mail (2.1082)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: rdroms@cisco.com
X-MIME-Autoconverted: from quoted-printable to 8bit by boreas.isi.edu id p1SJScRq025315
Cc: int-ads@tools.ietf.org, trill-chairs@tools.ietf.org
Subject: [rbridge] Rechartering trill WG
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

A new charter for the trill WG has been adopted, https://datatracker.ietf.org/wg/trill/charter  I know it's taken quite a while to get this charter in place; I hope the delay has not been an impediment to the WG.

Two trill WG work items were temporarily left out of the newly adopted charter:

(8) Support for RBridge campus VLAN and priority regions, so that a
VLAN ID or priority may have different meanings in different
regions, requiring configuration only at border RBridges
<draft-ietf-trill-rbridge-vlan-mapping>.

(9) Specify the use of the TRILL protocol in data centers, such as
by adding any support that may be need for IEEE 802.1 "Data Center
Bridging" standards <draft-eastlake-trill-rbridge-dcb>.

Because of the potential overlap between these work items and work in IEEE, the IESG wants to send a liaison about these work items for review and comment by IEEE 802.1.  Adoption of the two additional work items will be considered again by the IESG once we get a response from IEEE 802.1

- Ralph Droms


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