Re: [trill] Mirja Kühlewind's No Objection on draft-ietf-trill-irb-13: (with COMMENT)

Mirja Kühlewind <ietf@kuehlewind.net> Tue, 05 July 2016 13:59 UTC

Return-Path: <ietf@kuehlewind.net>
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 3B90712D572 for <trill@ietfa.amsl.com>; Tue, 5 Jul 2016 06:59:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.328
X-Spam-Level:
X-Spam-Status: No, score=-3.328 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h6Jo0mvc7nfS for <trill@ietfa.amsl.com>; Tue, 5 Jul 2016 06:59:49 -0700 (PDT)
Received: from kuehlewind.net (kuehlewind.net [83.169.45.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A98E512D134 for <trill@ietf.org>; Tue, 5 Jul 2016 06:59:48 -0700 (PDT)
Received: (qmail 18142 invoked from network); 5 Jul 2016 15:53:05 +0200
Received: from nb-10510.ethz.ch (HELO ?82.130.103.143?) (82.130.103.143) by kuehlewind.net with ESMTPSA (DHE-RSA-AES128-SHA encrypted, authenticated); 5 Jul 2016 15:53:05 +0200
To: Donald Eastlake <d3e3e3@gmail.com>
References: <20160629221311.30384.53041.idtracker@ietfa.amsl.com> <CAF4+nEECEqNqmEwNHggAjcxF=nYfhF5rTvN=taEAptVtXy6NKQ@mail.gmail.com> <CAF4+nEFRZj543L+2krRj6jf0S1sSsu6d7UzgR48c=0CJtJoWHg@mail.gmail.com>
From: =?UTF-8?Q?Mirja_K=c3=bchlewind?= <ietf@kuehlewind.net>
Message-ID: <577BBBAC.7050906@kuehlewind.net>
Date: Tue, 5 Jul 2016 15:52:44 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <CAF4+nEFRZj543L+2krRj6jf0S1sSsu6d7UzgR48c=0CJtJoWHg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/CZaA0a6wsil06FruxNWLmjxY70I>
Cc: "trill-chairs@ietf.org" <trill-chairs@ietf.org>, The IESG <iesg@ietf.org>, draft-ietf-trill-irb@ietf.org, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] =?utf-8?q?Mirja_K=C3=BChlewind=27s_No_Objection_on_draft-?= =?utf-8?q?ietf-trill-irb-13=3A_=28with_COMMENT=29?=
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 05 Jul 2016 13:59:51 -0000

Thanks! I had a quick look and this looks good to me. Also on the 2. point 
below, I know understand why there is a SHOULD; you potentially could add one 
more sentence to explain why this is a SHOULD. But I leave this on you.

Mirja


On 05.07.2016 15:35, Donald Eastlake wrote:
> Hi Mirja,
>
> A -14 version has been uploaded that is intended to resolve your comment.
>
> Thanks,
> Donald
> ===============================
>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>   155 Beaver Street, Milford, MA 01757 USA
>   d3e3e3@gmail.com
>
>
> On Wed, Jun 29, 2016 at 9:49 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
>> Hi Mirja,
>>
>> Thanks for your comments. See below.
>>
>> On Wed, Jun 29, 2016 at 6:13 PM, Mirja Kuehlewind <ietf@kuehlewind.net> wrote:
>>> Mirja Kühlewind has entered the following ballot position for
>>> draft-ietf-trill-irb-13: No Objection
>>>
>>> ...
>>>
>>> ----------------------------------------------------------------------
>>> COMMENT:
>>> ----------------------------------------------------------------------
>>>
>>> Two minor comments:
>>>
>>> 1) There are only a few SHOULDs and MUSTs in this whole document
>>>     and where they are used it is often not very clear what the action
>>>     is that should follow and how it should be implemented
>>>    (e.g. "The network operator MUST ensure the consistency of the
>>>     tenant ID on each edge RBridge for each routing domain.").
>>>    And maybe there are actually more case where normative
>>>    language should be used?
>>>    Please double-check the use of normative language in this document!
>>
>> OK.
>>
>>>   2) A similar question on the following part:
>>>    „If a tenant is deleted on an edge RBridge RB1, RB1 SHOULD re-
>>>     advertise the local tenant Data Label, tenant gateway MAC, and
>>>     related IP prefixes information of the rest tenants to other edge
>>>     RBridges. […] Therefore the transient routes consistency won't
>>>    cause issues other than wasting some network bandwidth.“
>>>    Wasting network resources actually can be an issue.
>>>    So why is this not an MUST?
>>
>> Wasting bandwidth can be an issue but is not necessarily an issue,
>> particularly if it occurs only during a brief transient period. TRILL
>> does not make it mandatory to implement with the maximum link
>> utilization efficiency. For example, TRILL multi-destination traffic
>> is send over a distribution tree. If there are no devices interested
>> in traffic in a particular VLAN further down a branch of the tree, it
>> is recommended that traffic heading down that branch be pruned. But
>> this is not mandatory. The TRILL campus will operate "correctly"
>> without such pruning and if someone wants to make a very simple, low
>> end implementation without pruning, so be it. (As far as I know, all
>> existing TRILL implementation do prune distribution trees.)
>>
>> Thanks,
>> Donald
>> ===============================
>>   Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>   155 Beaver Street, Milford, MA 01757 USA
>>   d3e3e3@gmail.com
>