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

gayle noble <windy_1@skyhighway.com> Thu, 26 February 2015 04:44 UTC

Return-Path: <windy_1@skyhighway.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 3720A1A00F9 for <trill@ietfa.amsl.com>; Wed, 25 Feb 2015 20:44:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level:
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 I8BM1taWUds8 for <trill@ietfa.amsl.com>; Wed, 25 Feb 2015 20:44:57 -0800 (PST)
Received: from skyhighway.com (skyhighway.com [63.249.82.6]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D6591A000F for <trill@ietf.org>; Wed, 25 Feb 2015 20:44:57 -0800 (PST)
Received: from Firefly.skyhighway.com (dsl-63-249-88-160.static.cruzio.com [63.249.88.160]) by skyhighway.com with ESMTP id t1Q4il77078158 for <trill@ietf.org>; Wed, 25 Feb 2015 20:44:48 -0800 (PST)
Message-Id: <201502260444.t1Q4il77078158@skyhighway.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 25 Feb 2015 20:44:49 -0800
To: "trill@ietf.org" <trill@ietf.org>
From: gayle noble <windy_1@skyhighway.com>
In-Reply-To: <80A2EAE0-74F0-420F-9B21-3D30D96EC5F1@gmail.com>
References: <024501d04953$8e16da80$aa448f80$@ndzh.com> <4552F0907735844E9204A62BBDD325E76AB33DE6@nkgeml512-mbx.china.huawei.com> <4A95BA014132FF49AE685FAB4B9F17F645EE20DF@dfweml701-chm> <80A2EAE0-74F0-420F-9B21-3D30D96EC5F1@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/8hQK4dBhMyc145Ki9297-DnUTtA>
Subject: [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 04:44:59 -0000

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