Re: [trill] My thoughts/wording corrections -> draft-ietf-trill-ia-appsubtlv-02.txt

Donald Eastlake <d3e3e3@gmail.com> Thu, 26 February 2015 18:50 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 463FD1A038D for <trill@ietfa.amsl.com>; Thu, 26 Feb 2015 10:50:59 -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, SPF_PASS=-0.001] autolearn=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 OJ6iH1yhZ17x for <trill@ietfa.amsl.com>; Thu, 26 Feb 2015 10:50:57 -0800 (PST)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (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 599391A037A for <trill@ietf.org>; Thu, 26 Feb 2015 10:50:57 -0800 (PST)
Received: by mail-ob0-f173.google.com with SMTP id uy5so13306752obc.4 for <trill@ietf.org>; Thu, 26 Feb 2015 10:50:56 -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=muLkR1FJ+jMzux6ajcdhTjjcv8YPemmnnL79/ssNICI=; b=rUjhfo0mXw7TNuIMfT/EPWBI8A9mVIVarytXbcYVCq/yeZzKl71k0nkaC1gLj/ewP/ ZjBOjFYab/E7O6iLr0ZeVCh/pM709/ABcDA+WI5g/HSFSle9Egymb5v15NORv6uXMfoB uVrOLdNsbVfcyKOwWi8RvNYdRDOKNPxpbsFs7PkTTxuuIln4rH8Y7rpKyEpi6Cfpitk/ UIsI98EOvNFru/DJQpWVUDA1JaA8ayq/44Z5aVOi9iAtwafYqcdTOnlfb3iFicaE78xK Wzp7obO7bBdLPfbHWqVtz7za1pWsQijdSDUW/+aMY4RUmJL1URYqNVzwdGfrFaKGaLPd Gllg==
X-Received: by 10.60.131.238 with SMTP id op14mr7088997oeb.59.1424976656611; Thu, 26 Feb 2015 10:50:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.155.134 with HTTP; Thu, 26 Feb 2015 10:50:36 -0800 (PST)
In-Reply-To: <201502260444.t1Q4il77078158@skyhighway.com>
References: <024501d04953$8e16da80$aa448f80$@ndzh.com> <4552F0907735844E9204A62BBDD325E76AB33DE6@nkgeml512-mbx.china.huawei.com> <4A95BA014132FF49AE685FAB4B9F17F645EE20DF@dfweml701-chm> <80A2EAE0-74F0-420F-9B21-3D30D96EC5F1@gmail.com> <201502260444.t1Q4il77078158@skyhighway.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 26 Feb 2015 13:50:36 -0500
Message-ID: <CAF4+nEHhCzaQnhZm8qW3C3TJ6TXP40K-2nW4SDqE8JPwaL9gFw@mail.gmail.com>
To: gayle noble <windy_1@skyhighway.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/6MrPFT9o7KiUOO-uyuwl-etXPgg>
Cc: "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] My thoughts/wording corrections -> draft-ietf-trill-ia-appsubtlv-02.txt
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
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, 26 Feb 2015 18:50:59 -0000

Hi Gayle,

Thanks. Those changes looks like good clarifications and corrections
to the draft. I'll go over them more closely and incorporate them.

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


On Wed, Feb 25, 2015 at 11:44 PM, gayle noble <windy_1@skyhighway.com> wrote:
> My thoughts/wording corrections ->[trill]
> draft-ietf-trill-ia-appsubtlv-02.txt
>
> 1)     Abstract
> (this sentence is very long and complicated.)
> This document specifies a TRILL (Transparent Interconnection of Lots of
> Links) IS-IS application sub-TLV that enables the reporting by a TRILL
> switch of sets of addresses such that all of the addresses in each set
> designate the same interface (port) and the reporting for such a set of the
> TRILL switch by which it is reachable.
> (maybe re-adjust it something like this)
> This document specifies a TRILL (Transparent Interconnection of Lots of
> Links) IS-IS application sub-TLV that enables the reporting by a TRILL
> switch of sets of information; each set consists of addresses and a nickname
> of the TRILL switch by which those addresses can be reached; all of the
> addresses in a set designate the same end station interface (port).
>
> 2)      page 10
> (I would change "the" to "then")
> (as written)
> If they were used in a IA-APPsubTLV in a traditional LSP [ISO-10589], the
> only one byte Types and Lengths could be used.
> (it would become)
> If they were used in a IA-APPsubTLV in a traditional LSP [ISO-10589], then
> only one byte Types and Lengths could be used.
>
> 3)    page 12
> (Should be "topology given" instead of "topology give")
> (as written)
>   The presence of this sub-sub-TLV indicates that the interfaces given in
> the IA APPsub-TLV are reachable in the topology give.
> (I'd change it to)
>   The presence of this sub-sub-TLV indicates that the interfaces given in
> the IA APPsub-TLV are reachable in the topology given.
>
> 4)    page 12
> (This is not real clear as to what it is trying to communicate .. at least
> to me)
> (what is written)
> It is useful if the IA APPsub-TLV occurs outside of the context of a message
> indicating the topology or if it is desired and permitted to override that
> specification.
> (if I figured this out)
> You might want to use the Data Label or Topology sub-sub-TLVs where the IA
> APPsub-TLV is not in a message or some other context that specifies the Data
> Label or Topology. (Multi-topologyTRILL really isn't fully specified yet but
> the Topology sub-sub-TLV is provided for future use.) Alternatively, even if
> the IA APPsub-TLV is inside a message or some other context, you might want
> to specify that for some particular IA APPsub-TLV, a different Data Label or
> different Topology should be used, so you might want to use the sub-sub-TLV
> to override that specification.
>
> 5)    page 14
> (I'd change "providing" to "provided")
> (what is written)
> Security on the wire, or in storage, for this data is to be providing by the
> transport or storage used.
> (What I'd put)
> Security on the wire, or in storage, for this data is to be provided by the
> transport or storage used.
>
> 6)    page 19 last paragraph
> (the word "give" is used where I'd use "given")
> (as written)
> The Fixed Address sub-sub-TLV causes the IPv6/64 value give to be treated as
> if it occurred as a 4th entry inside each of the three Address Sets.
> (I'd write)
> The Fixed Address sub-sub-TLV causes the IPv6/64 value given to be treated
> as if it occurred as a 4th entry inside each of the three Address Sets.
>
> 7)    page 20 last paragraph
> (I think "them" should be "then")
> (as written)
> The OUI would them be supplied by a second Fixed Address sub-sub-TLV proving
> the OUI.
> (I think it should be)
> The OUI would then be supplied by a second Fixed Address sub-sub-TLV proving
> the OUI.
>
> acronyms
> AFN              Address Family Number
> APPsub-TLV    Application sub-TLV
> ARP              Address Resolution Protocol
> Data Label     VLAN or FGL
> ESADI           End Station Address Distribution Information
> FGL              Fine Grained Label
> FS-LSP                   Flooding Scoped Label Switched Paths
> IA                Interface Addresses
> IETF             Internet Engineering Task Force
> IS-IS            Intermediate System to Intermediate System
> LAN              Local-Area Network
> MAC             Media Access Control
> ND               Neighbor Discovery
> OUI              Organizationally Unique Identifier
> PDU              Protocol Data Unit
> RARP            Reverse Address Resolution Protocol
> RBridge         An alternative name for a TRILL switch
> TLV              Type Length Value
> TRILL             Transparent Interconnection of Lots of Links
> TRILL switch   A device that implements the TRILL protocol
> VLAN            Virtual Local-Area Network
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill