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

Donald Eastlake <d3e3e3@gmail.com> Thu, 30 June 2016 01:49 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 94A6112D565; Wed, 29 Jun 2016 18:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level:
X-Spam-Status: No, score=-2.45 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 9EPT1W_DpKrB; Wed, 29 Jun 2016 18:49:48 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (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 DC34912D59E; Wed, 29 Jun 2016 18:49:47 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id r2so44971704oih.2; Wed, 29 Jun 2016 18:49:47 -0700 (PDT)
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-transfer-encoding; bh=N1106qFkeTowhAPOQsBb+GHqXheiKTNM2Woxe2xon/U=; b=fBwL+Hv2KPe/E84hHAkgs/dtxN9Gn0knDJNKqcdF+C9rAOSB79CMJS1/amQ9868AAJ rROpLNTNoeq0xf6mjFxhUJke87o2gUvi0bBEDpiIHvTUQivPLjTMRQlXWA7qA9UUXHJx AwxsxsB8KFem6L5L/bKgCYhhf64YdXrqi2ajf9boJSEpzQcZAJQXKeR2CcTB+Igj3GRx yVG92r/738TX1yfw/TRSjJ6RPuMbi92l79fQLUF7pgJVhq8w+tdxe+MRKjT8VvihCZfq 67m5Q08RzzDf5rUwHTU6u+JmztH89y8DZrWAGH7Jg7luo0c0NvWSHDfTfEoSztFgEAwx 7VHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=N1106qFkeTowhAPOQsBb+GHqXheiKTNM2Woxe2xon/U=; b=alaWrB2bK/GsXcPcV+H3K8HW7M/V+y9VU6hdrvlZN/HP2B3ZMGllmfhlO4PJeMdn3c 8ffJ0n/MUcIXQsjQpobuAcmHNWksmkYys8l4gSXQGZzwDdesSQEkF16CWV62NTsx31pj MY5mtHaddDSmo2MQpzvIPWYMS9oqIN3nlvpIfBUj0lwLuKiNVYsjie7D+OvKuzZV7rFL g0hjCUhgBmzTzn/sD1WjWJueT7JH9D+l6u+lBvJ5D2Yp/x3pHSSahxwF/4u5cZuaRMIf RAhiduCjrT3jBh3O/9bovgWN6ANoVxVNh1i45cs6vGq6iqQnwbGD7UTEhA5W/FwHf8qP I6eA==
X-Gm-Message-State: ALyK8tIN+l5tQeBuf31paJhw3rQpuX+oK2Z1kw4wNHiebpN7ZdZy/u+nui/qjfrH8W8pFa2D+vZHha/I5UYFJA==
X-Received: by 10.202.183.139 with SMTP id h133mr7075911oif.6.1467251387097; Wed, 29 Jun 2016 18:49:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.52.242 with HTTP; Wed, 29 Jun 2016 18:49:32 -0700 (PDT)
In-Reply-To: <20160629221311.30384.53041.idtracker@ietfa.amsl.com>
References: <20160629221311.30384.53041.idtracker@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 29 Jun 2016 21:49:32 -0400
Message-ID: <CAF4+nEECEqNqmEwNHggAjcxF=nYfhF5rTvN=taEAptVtXy6NKQ@mail.gmail.com>
To: Mirja Kuehlewind <ietf@kuehlewind.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/HmX-2P3RRf99UTy2gqzDBAt0QDg>
Cc: "trill-chairs@ietf.org" <trill-chairs@ietf.org>, The IESG <iesg@ietf.org>, "trill@ietf.org" <trill@ietf.org>, draft-ietf-trill-irb@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: Thu, 30 Jun 2016 01:49:49 -0000

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