Re: [rbridge] Review of draft-ietf-trill-rbridge-protocol-13.txt

Donald Eastlake <d3e3e3@gmail.com> Thu, 17 September 2009 02:51 UTC

Return-Path: <rbridge-bounces@postel.org>
X-Original-To: ietfarch-trill-archive-Osh9cae4@core3.amsl.com
Delivered-To: ietfarch-trill-archive-Osh9cae4@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CB4B33A68E8 for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 16 Sep 2009 19:51:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.544
X-Spam-Level:
X-Spam-Status: No, score=-2.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vE7wlcP4Q2Dk for <ietfarch-trill-archive-Osh9cae4@core3.amsl.com>; Wed, 16 Sep 2009 19:51:33 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id C0A903A69E1 for <trill-archive-Osh9cae4@lists.ietf.org>; Wed, 16 Sep 2009 19:51:33 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n8H2j5T5015178; Wed, 16 Sep 2009 19:45:06 -0700 (PDT)
Received: from mail-ew0-f214.google.com (mail-ew0-f214.google.com [209.85.219.214]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id n8H2ir98015104 for <rbridge@postel.org>; Wed, 16 Sep 2009 19:44:55 -0700 (PDT)
Received: by ewy10 with SMTP id 10so19929ewy.13 for <rbridge@postel.org>; Wed, 16 Sep 2009 19:44:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=lJMA8GgNxrJMXclgnA3czks6kuXzS+hibgNduXpdq38=; b=wQR97PxJBz64Inm42/lIwE0bj+GB2XqBSOBbCOpIphj2LI8lWzTigInhH07SD/zJWo qeI5yzjj/4FNERP3pcVpzVL0T+nTTrTM5CWFKf00lazugWbkwzdsxM3bw5epNSQ6Wexl 2ppBArkdUBUmQGcWVU7dXLT58DLDvIfis6C6U=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=k9uypIlqsq4gFsaZ/gBUhdcqGGRNAxB8zCaqVtpCh2DFyTQqPn3+2G6KPp2kVPNqXW Y9Q12PQZ3bH4t4F0QCHXTuzl8EhwMtgbWGWNe0Yradix2b6XjxSTtDMwIZbcrzaCWPnd Krwp2hSP5Anw7eTM6DHoWcb2oZClBeVSegYJ4=
MIME-Version: 1.0
Received: by 10.216.24.141 with SMTP id x13mr272wex.191.1253155493051; Wed, 16 Sep 2009 19:44:53 -0700 (PDT)
In-Reply-To: <78F2E9EF10EF9447A0FDAF9E6036E24E1172DC84@zharhxm0.corp.nortel.com>
References: <78F2E9EF10EF9447A0FDAF9E6036E24E1172DC84@zharhxm0.corp.nortel.com>
Date: Wed, 16 Sep 2009 22:44:52 -0400
Message-ID: <1028365c0909161944u7d6ab76dubecc8429cec24c5c@mail.gmail.com>
From: Donald Eastlake <d3e3e3@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 n8H2ir98015104
Subject: Re: [rbridge] Review of draft-ietf-trill-rbridge-protocol-13.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

On Mon, Sep 14, 2009 at 5:04 PM, Roger Lapuh <roger.lapuh@nortel.com> wrote:
> Hi Don (Eastlake)
>
> I know you were not trying to imply this, but I got the impression from your
> comments that others might infer that the current link-state based  IEEE
> 802.1 project could take a long time ...

I'm sorry if my remarks were not clear. I did not mean to say anything
about the length of time it takes to complete standards efforts in
IEEE 802.1. In fact, as far as I can tell, there are roughly equal
complaints in the IETF and in IEEE 802 that standards efforts take too
long. My point was that, as Caitlin said, if you were to wait until
all current 802.1 efforts that might in some way bear on TRILL were
completed, you would find that additional 802.1 efforts of that type
had been started in the mean time. And if you were to then wait for
those to be completed, you would find that yet other new 802.1 efforts
of that type had been started. And so on. So, as I said, "to wait for
802.1 standards efforts to end", meaning to wait until there are no
802.1 standards activities in process, "would be to wait forever."

In any evert, given that TRILL is layered above 802.1, it is mostly
independent of IEEE. if there were problems with future IEEE work,
then it is likely that all the IP protocols would be impacted.

>...
>
> Also, while going through the TRILL draft I was wondering how well you
> perceive end-stations and applications will handle the out-of-ordered
> (Unicast) packets that you point out within the TRILL design in section 4.5
> page 48?

That seems like an odd question. If you have applications where such
occasional out-of-order unicast frames were a problem you would
configure your RBridge campus so as to make sure they were of
extremely low probability. For example by calculating a distribution
tree per RBridge or configuring addresses to eliminate unknown unicast
frames for connected end-stations or other techniques. In fact, a few
words should probably be added to the draft about this.

Thanks,
Donald

>
> regards,
>
> Roger
> Nortel

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