IETF Logo Mail Archive

Re: [trill] WG Last Call: draft-ietf-trill-fine-labeling-02.txt

Donald Eastlake <d3e3e3@gmail.com> Thu, 06 December 2012 23:37 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41A9921F8564 for <trill@ietfa.amsl.com>; Thu, 6 Dec 2012 15:37:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.399
X-Spam-Level:
X-Spam-Status: No, score=-103.399 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uulfftSSIF9H for <trill@ietfa.amsl.com>; Thu, 6 Dec 2012 15:37:56 -0800 (PST)
Received: from mail-ia0-f181.google.com (mail-ia0-f181.google.com [209.85.210.181]) by ietfa.amsl.com (Postfix) with ESMTP id DB17621F8561 for <trill@ietf.org>; Thu, 6 Dec 2012 15:37:54 -0800 (PST)
Received: by mail-ia0-f181.google.com with SMTP id s32so4870902iak.26 for <trill@ietf.org>; Thu, 06 Dec 2012 15:37:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2pNtDKjLO7PDVca1dqdmPHPG35Ok3aRNp27wmx1XRqs=; b=Di/cdXv/bQTC9af/rb7+CbEGyBgo5tyU1zgUxn9bTlh4SpP5GBRe5ktVuNr738qL8Y 2+U9I610yu2ZILeExAYcKVbK3KydqQaDBAFr/75HsZLPrRqSKZP3Nc+zMurrOjd2+2fd lfcl6AzTHgfc0H8dbk/NCCFhbVuzw3fX8iQc4uAwgOcR7A2AfaSd1sOrSJiu0r0jK5gB mNZNLY/SjYDgyA5nYUjTaspGz0BUxHlBpQaxR2IX4eeFn3JVpnO5a0mLZ9E91xpcjk5N s/j5gGSRUwtY/TT23/w//Wl/JnCzshqHr7grEfEJ8HGFgT0VksfmwhzKGHDhxpgp+3n5 874g==
Received: by 10.50.34.200 with SMTP id b8mr3213855igj.52.1354837074471; Thu, 06 Dec 2012 15:37:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.28.209 with HTTP; Thu, 6 Dec 2012 15:37:33 -0800 (PST)
In-Reply-To: <201211291545.qATFj0YK005513@cichlid.raleigh.ibm.com>
References: <CAF4+nEE+rT9x_MgiWLCx7xut4SgDJ7=pRK1L_PovrwBCg3OaVw@mail.gmail.com> <CCCE73BA.C6A2%ostokes@extremenetworks.com> <CAF4+nEFioN3TmDj7sGchr4atPijRNiGCwiBLe8ROB79fqA0kAg@mail.gmail.com> <A3C4E51A53661B4EBEE7C5F5E6FCDEB5026F93353CEE@USEXCHANGE.corp.extremenetworks.com> <CAF4+nEFuaJQrPXCSD0rsu_sJiSQzNNL0eU6Vp3_mwWGThXfQLg@mail.gmail.com> <A3C4E51A53661B4EBEE7C5F5E6FCDEB5026F9347058C@USEXCHANGE.corp.extremenetworks.com> <201211281553.qASFrAgu013237@cichlid.raleigh.ibm.com> <CAFOuuo6_BNzaGaSaOyfet=DhB3+4Yxc-Mazgp6Y4=f5E1UPD0g@mail.gmail.com> <CAF4+nEHsemn1jMEORyV7KmgkLU-w0iOL5p43jv43u_=+jiFo8w@mail.gmail.com> <201211291545.qATFj0YK005513@cichlid.raleigh.ibm.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 06 Dec 2012 18:37:33 -0500
Message-ID: <CAF4+nEH5x2qaeGYPrqyzHAEx=odpYuz9ZwbpTHPMdU895H8EwA@mail.gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] WG Last Call: draft-ietf-trill-fine-labeling-02.txt
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Dec 2012 23:37:57 -0000

Hi Thomas,

On Thu, Nov 29, 2012 at 10:45 AM, Thomas Narten <narten@us.ibm.com> wrote:
> I think it is clear that there are circumstances where using unicast
> rather than multicast would be a useful optimization. What the
> document would benefit from is text explaining where that might be
> useful and making it clear that implementations might want to do that
> - as an optimization under appropriate circumstances. It doesn't have
> that background, just a couple of MAY/SHOULD statements. Taking some
> of the explanation in this email thread and putting it into the
> document would probably help clarify the intent.

I will incorporate such text.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> I suggested pulling out the text because it was apparently confusing,
> and I didn't think it was necessary. There are lots of optimizations a
> product might make besides this one. The document surely doesn't aim
> to cover them all.
>
> Thomas

v2.23.0 | Report a Bug | By Email