Re: [trill] [RTG-DIR] RD Review of draft-ietf-trill-address-flush-00

Donald Eastlake <d3e3e3@gmail.com> Fri, 09 December 2016 02:23 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 5FDA412962B; Thu, 8 Dec 2016 18:23:01 -0800 (PST)
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 ijV8CElElPiC; Thu, 8 Dec 2016 18:22:59 -0800 (PST)
Received: from mail-io0-x241.google.com (mail-io0-x241.google.com [IPv6:2607:f8b0:4001:c06::241]) (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 A9EFF1295FA; Thu, 8 Dec 2016 18:22:54 -0800 (PST)
Received: by mail-io0-x241.google.com with SMTP id p13so3979102ioi.0; Thu, 08 Dec 2016 18:22: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-transfer-encoding; bh=5VqhQwxDoY143i48XMzMBd36cIChtJpbHcwUdrQeiJA=; b=OA0nOLQ5GkHmY8chluiSOck04DY5bi/0oTmojJi7mbOeTURfUZoHKTMecMng8dN/yM puVHP1aI+XX2/bslZzE6jTeRsj+QxSE1q8I2yqrydF9uMKEYxPcPNYGzP7hQZFZUZKYc EYQo1m02Bv9jSxVXBFEv30v3gObawMG580DbKJKI5e0Zub8ORiQylLTLu94WPhs7eyrf hRuvAKEudpf3/cbx1nD6HCKlwKtaKAPXSwOjTB/vAPeKQdRnPkJllT0/Fpf+iWJe/4dw CGVEgXUiokFmrGeh849j+v8FoJuh6d45gi9xFIi2nIaMBUuf+HV8lTXGhDz8MOdMgBz9 a0aA==
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=5VqhQwxDoY143i48XMzMBd36cIChtJpbHcwUdrQeiJA=; b=jMI9IoKB3XKyJqAYQLuxVrjoKUhen878XVOOfZXJ+akiRXP7IP3YoBmXx3bg+3REs+ xKZSrijfjewWWw2BnE7y/21kuMMYPog8iKraYH/cj/8m2rl4RyFIsTTU48nRcxxQmilE mN6/AeMUQUKsf/ndKqI9ZOZCJFkBVD9oteyf7+qqbSTXshvu3wnTKoMNEmo6AU0yOgJt qxk99oY4ECgkfR2xn+wczFl+jwrLmG35v5cNlgPKg9+hgVsYgzJZwO9Z5h2epYSHEdHE diKf4BbnWGi1aUuMDKsNpE5T4MVq45C/rT4ePJp1gyVxUZQId2b4vTv+LenPn2upneI8 OfrA==
X-Gm-Message-State: AKaTC02qKfLqFiQaFCjH2tzQ324ZlbNGb6MErzhLmoRFnKKPOyg/ganTZuSi+vcJI6HIITacBDNVVqJSIdMNvA==
X-Received: by 10.107.34.207 with SMTP id i198mr60649756ioi.16.1481250173929; Thu, 08 Dec 2016 18:22:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.107.33.6 with HTTP; Thu, 8 Dec 2016 18:22:38 -0800 (PST)
In-Reply-To: <a3381f0f-c0e8-69c3-e509-9f8713459787@fkie.fraunhofer.de>
References: <CAGnRvuqH9f5XvnafvjNXYK9923ausr1r9xcOX+hXbOTiD4XJiw@mail.gmail.com> <CAF4+nEGkwgU07e=6+GMAGeLNTsjsnnFBQMY2yoHTy2gcArSv2Q@mail.gmail.com> <a3381f0f-c0e8-69c3-e509-9f8713459787@fkie.fraunhofer.de>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 8 Dec 2016 21:22:38 -0500
Message-ID: <CAF4+nEGEO9M_13jpoeQX3LqcjjAkrBmZLkNzXF-7NtWWksmWiQ@mail.gmail.com>
To: Henning Rogge <henning.rogge@fkie.fraunhofer.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/trill/Wf7CY3_xdWlsWg36fvpDKuc9lME>
Cc: draft-ietf-trill-address-flush@ietf.org, "rtg-dir@ietf.org" <rtg-dir@ietf.org>, Henning Rogge <hrogge@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] [RTG-DIR] RD Review of draft-ietf-trill-address-flush-00
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: Fri, 09 Dec 2016 02:23:01 -0000

Hi Henning,

Sorry for the delay but the draft has been revised to be more in line
with your recommendations. See
https://tools.ietf.org/html/draft-ietf-trill-address-flush-01

In particular, the extended version uses a TLV encoding. Can you take
a look when convenient?

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


On Wed, Sep 7, 2016 at 2:19 AM, Henning Rogge
<henning.rogge@fkie.fraunhofer.de>; wrote:
> On 03.09.2016 22:15, Donald Eastlake wrote:
>>>
>>> - the difference between the "VLAN Block Case" (2.1) and "Extensible
>>> Case" (2.2) feels artificial. Why not add a "VLAN block TLV", which
>>> contains the list of VLAN start/end fields?
>>
>>
>> As I recall this was in order to make the VLAN Block case closer to,
>> for convenience, an existing implemented address flush RBridge channel
>> message (using one of the "Private Use" RBridge Channel message
>> protocol numbers) that only applies to VLAN blocks.
>
>
> Okay, I didn't check for similarity with older messages.
>
>  > I'll see what people think about merging the cases.
>
> One more question, is case 2.2 optional to implement or is it mandatory?
>
>>> - maybe the Nicknames could also be moved into a TLV, allowing to
>>> process the whole message with a single TLV based parser.
>>
>>
>> I can see making a common TLV format for all the non-nickname lists
>> but I'm not sure there is much advantage to doing so for nicknames.
>
>
> Unified parser codepath... maybe even with checking the TLVs against some
> kind of "schema" before processing them.
>
> Henning Rogge
> --
> Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
> Kommunikation, Informationsverarbeitung und Ergonomie FKIE
> Kommunikationssysteme (KOM)
> Zanderstrasse 5, 53177 Bonn, Germany
> Telefon +49 228 50212-469
> mailto:henning.rogge@fkie.fraunhofer.de http://www.fkie.fraunhofer.de