Re: [trill] Adam Roach's No Objection on draft-ietf-trill-address-flush-05: (with COMMENT)

Donald Eastlake <d3e3e3@gmail.com> Fri, 09 February 2018 16:42 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 5F3D3129515; Fri, 9 Feb 2018 08:42:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 nLtlkBwryTRE; Fri, 9 Feb 2018 08:42:28 -0800 (PST)
Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51D2F129C6D; Fri, 9 Feb 2018 08:42:28 -0800 (PST)
Received: by mail-ot0-x231.google.com with SMTP id q9so8296841oti.0; Fri, 09 Feb 2018 08:42:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=ezufeprAhKlukMuYQ9sK0qFaMCI6vgC8PBd69USVupA=; b=AR+30pSmDlw0stdb45Yw1C0QMIJSg034sysaJgLnu7Qj5NlaImusfdaDYRVkL0BfBR s37ZIkKKKt+PhxnshkKJ9YSfODhy+d+J9VcsVD4Js7DzpowCxAKpqiORRkrjRo8EwTo7 rdB30Ng+JTwZ97F/gV0+TKRkLxgHUNn137zIcUjokYZlxqmGwmDod4oIRvgqxxJlciKV eMAewE8yPZrZnPxTH4bKQm9oLb9EYO9LabpLsK6lv2OxqSkvimAiRCMnb1fAPkQz9m7j hSlZ6k868QHvWwymsDDj1xIAEPIw9xx1f+T4uKRDlZopZAfLGDDz+6KVPXs8ZUm8ZKSu gFaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=ezufeprAhKlukMuYQ9sK0qFaMCI6vgC8PBd69USVupA=; b=U6PIP89k6uDVgPEKarlp/BZBl9cz88GBHwLlHQiu90W+65I/MP2hVpjTGqarJoWqbf YO5GA+QiZcUjIGk9MslPi9/sc8nybczlg0fjFM9I6gmEDY5C+I9R2zMO6F+cWWqxj3ft DggY8Vicz3ZbreBqSP7rAyCWSCjEjsPTPhKQeAM0QQF5LKD6nujXQS0Ow3zqxBfcuXmj rodoTNyAsaZDe5zwvV9ucB04qXUD7vkzTObU/GNbh3MVdDg9O4gWlPHGzVS/0ePBNNAS FjDQG4Bdm6Z9gCddieCJue8ifwLZaxG1tXloQRVmnrcBL/pJUSv3zDJSZlXmmmKGm0oz wTAA==
X-Gm-Message-State: APf1xPAPsavRbHrODeMegfpZPXxNQGRpRfXeyDctNTen5Rdh6v9j9U2I pzhYkHYR+m6p3isIY2pgYG1Nd9AzkXJGQF7OD48=
X-Google-Smtp-Source: AH8x226U5Ye+K/SCy4R6GNLSGKTqYkHVFtkGyo43dqezShbSRfgBBzLFUGPLmZkbM+HeDHJXJX0HPVp5KfZYObTm/+0=
X-Received: by 10.157.54.11 with SMTP id w11mr2532366otb.334.1518194547511; Fri, 09 Feb 2018 08:42:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.168.67.205 with HTTP; Fri, 9 Feb 2018 08:42:12 -0800 (PST)
In-Reply-To: <151806425843.17204.5605050960821568285.idtracker@ietfa.amsl.com>
References: <151806425843.17204.5605050960821568285.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 9 Feb 2018 11:42:12 -0500
Message-ID: <CAF4+nEEiwzzhKfRcciqx-40acD0Fge7GOK36miyh7psXM0k_fg@mail.gmail.com>
To: Adam Roach <adam@nostrum.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-trill-address-flush@ietf.org, Susan Hares <shares@ndzh.com>, trill-chairs@ietf.org, trill@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/O5kVuzFb2OGfJ_Byy3xm1-uxrDw>
Subject: Re: [trill] Adam Roach's No Objection on draft-ietf-trill-address-flush-05: (with COMMENT)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 09 Feb 2018 16:42:30 -0000

Hi Adam,

On Wed, Feb 7, 2018 at 11:30 PM, Adam Roach <adam@nostrum.com> wrote:
> Adam Roach has entered the following ballot position for
> draft-ietf-trill-address-flush-05: No Objection
>
> ...
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks to everyone who contributed to writing this document.
>
> I'm concerned that the interaction between the various extensible Address Flush
> message TLVs isn't very clearly spelled out. As far as I can tell, the text that
> attempts to describe the interactions is:
>
>>     If the set of MAC addresses accumulated from parsing the address
>>  flush message is null, the message applies to all MAC addresses.
>>     If the flag indicating the presence of an All Data Labels TLV is
>>  true, then the address flush message applies to all Data Labels and
>>  the set of Data Labels and block of Data labels specified has no
>>  effect. If the flag indicating the presence of an All Data Labels TLV
>>  is false, then the address flush messages applies only to the set of
>>  Data Labels accumulated from parsing the message; if that set is
>>  null, the address flush message does nothing.

The TLVs are all parsed accumulated a possibly null set of Data
Labels, an "All Data Labels flag", and a possibly null set of MAC
addresses.

> Based on this (and the fact that their implementation is optional), I infer
> that the MAC address TLVs are intended to further restrict the addresses
> indicated by TLV types 1 through 5, rather than expand upon them.

That's right.

> I'm less
> sure about whether they have any impact on Type 6. I would expect that they
> do, but the text above ("applies to all Data Labels") kind of sounds like they
> don't.

Type 6 only affects the Data Labels that are being flushed. It has no
effect on the set of MAC addresses which set defaults to "all".

> What would seem to make sense here (inasmuch as it provides maximal flexibility)
> is:
>
> if (TLV7 ∪ TLV8 = {})
>   Addresses to Flush = (TLV1 ∪ TLV2 ∪ TLV3 ∪ TLV4 ∪ TLV5 ∪ TLV6)
> else
>   Addresses to Flush = (TLV1 ∪ TLV2 ∪ TLV3 ∪ TLV4 ∪ TLV5 ∪ TLV6) ∩ (TLV7 ∪ TLV8)

That's correct but not complete. If the set of Data Labels indicated
by any of TLV1 though TLV5 that are present is null, the the Address
Flush applies to the Data Label after the TRILL Header and Inner MAC
addresses. It also seems quite confusing to have TLV7 and 8 as if they
were the same sort of thing as the other TLVs when they are MAC
addresses and the others all relate to .

Every entry that is flushed consists of a nickname, a Data Label, and
a MAC address. Nicknames are handled the same way for both the VLAN
Block only case and the extensible case. The complete set of entries
that is flushed is the cross product of a set of nicknames, a set of
Data Labels, and a set of MAC addresses, where the set of Data Labels
and/or MAC addresses can be "all".

> If that's the intention, I think the normative explanation needs to be clearer.
> If that's not the intention, I sill think the normative explanation needs to be
> clearer.

We'll see what we can do to clarify.

> My remaining comments are editorial.
> ---------------------------------------------------------------------------

I'm fine with the changes below and have provided and explanation of "RB1".

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

> Please expand the following acronyms upon first use and in the title;
> see https://www.rfc-editor.org/materials/abbrev.expansion.txt for guidance.
>
>  - TRILL
>  - TC
>  - TCN
>  - MSTP
>
> While the following terms are defined in cited documents, you may wish to also
> consider expanding them in this document's acronym list for the convenience of
> the reader:
>
>  - MAC
>  - FCS
>
> Finally, please explain the use of "RB1" in the Introduction.

It's use in this case is pretty much non-existent... :-) A typical
style in TRILL document is to say "A TRILL switch RB1 ..." Then later
you can just reference RB1 rather than having to talk about it in some
more complex say. (Usually there is also an RB2, RB3, ... but not
always.) Since the "RB1" is never referenced again in this case, it
can just be deleted.

> ---------------------------------------------------------------------------
>
> §1:
>
>>  Another example is based on Appendix A.3 of [RFC6325] ("Wiring Closet
>>  Topology") presents a bridged LAN connected to a TRILL network via
>>  multiple RBridge ports.
>
> This should be either:
>
>    Another example, based on Appendix A.3 of [RFC6325] ("Wiring Closet
>    Topology"), presents a bridged LAN connected to a TRILL network via
>    multiple RBridge ports.
>
> or...
>
>    Another example is based on Appendix A.3 of [RFC6325] ("Wiring Closet
>    Topology"), which presents a bridged LAN connected to a TRILL network
>    via multiple RBridge ports.
>
> ---------------------------------------------------------------------------
>
> §1.1:
>
>>  The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>>  "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
>>  document are to be interpreted as described in [RFC2119].
>
> This document makes use of lowercase versions of these terms as well; please
> consider using the RFC 8174 boilerplate.
>
> ---------------------------------------------------------------------------
>
> §2.2:
>
>>  VLANs/FGLs if it occurs in any TLV in the address flush message. A
>>  MAC addresses might be indicated more than once due to overlapping
>
> "A MAC address..." or "MAC addresses..."
>
>
> ---------------------------------------------------------------------------
>
> §2.2:
>
>>  MAC addresses if it occurs in any TLV in the address flush message.
>>     If the set of MAC addresses accumulated from parsing the address
>>  flush message is null, the message applies to all MAC addresses.
>>     If the flag indicating the presence of an All Data Labels TLV is
>>  true, then the address flush message applies to all Data Labels and
>
> The staggered indenting here looks a bit odd. Were these intended to be a
> bulleted list?