Re: [trill] draft-zhang-trill-multi-level-single-nickname - WG Adoption Call extension (7/16 to 8/16/2015)
gayle noble <windy_1@skyhighway.com> Thu, 06 August 2015 21:38 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 979661A8986 for <trill@ietfa.amsl.com>; Thu, 6 Aug 2015 14:38:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.509
X-Spam-Level:
X-Spam-Status: No, score=-0.509 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HTML_MESSAGE=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 rOmoIgOeil8p for <trill@ietfa.amsl.com>; Thu, 6 Aug 2015 14:38:37 -0700 (PDT)
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 005241A8982 for <trill@ietf.org>; Thu, 6 Aug 2015 14:38:36 -0700 (PDT)
Received: from Firefly.skyhighway.com (dsl-63-249-88-160.static.cruzio.com [63.249.88.160]) by skyhighway.com with ESMTP id t76LcXW6096520 for <trill@ietf.org>; Thu, 6 Aug 2015 14:38:33 -0700 (PDT)
Message-Id: <201508062138.t76LcXW6096520@skyhighway.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 06 Aug 2015 14:38:28 -0700
To: trill@ietf.org
From: gayle noble <windy_1@skyhighway.com>
In-Reply-To: <023401d0cebb$533d8010$f9b88030$@ndzh.com>
References: <023401d0cebb$533d8010$f9b88030$@ndzh.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_1431678193==.ALT"
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/FPjA9rkvu60uRELHcTXy1j8gToc>
Subject: Re: [trill] draft-zhang-trill-multi-level-single-nickname - WG Adoption Call extension (7/16 to 8/16/2015)
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: <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, 06 Aug 2015 21:38:38 -0000
I support this draft for adoption. I do have the following suggestions and corrections These are the acronyms used but not defined APPsub-TLV Application sub-TLV E-L1FS Extended Level 1 Flooding Scope [RFC7356] E-L2FS Extended Level 2 Flooding Scope [RFC7356] FGL Fine Grained Label [RFC7172] FS-LSP Flooding Scoped Link State PDU [RFC7356] PDU Protocol Data Unit TLV Type Length Value corrections 1. page 5 section 3.2 - first paragraph - first sentence [Both L1 and L2 are areas so "each L1 area and L2" reads a bit weird.] (as written) Distribution trees for flooding of multi-destination packets are calculated separately within each L1 area and L2. (I'd write) Distribution trees for flooding of multi-destination packets are calculated separately within each L1 and L2 area. 2. page 9 second paragraph - first sentence ["packet is originated" is weird wording. I don't think "is" is needed.] (as written) if this packet is originated from an area out of the connected areas, RB1 should replicate this packet and flood it on the proper Level 1 trees of all the areas in which it acts as the DBRB. (I'd write) if this packet originated from an area out of the connected areas, RB1 should replicate this packet and flood it on the proper Level 1 trees of all the areas in which it acts as the DBRB. 3. page nine third paragraph - first sentence ["packet is originated" is weird wording. I don't think "is" is needed.] (as written) if the packet is originated from one of the connected areas, RB1 should replicate the packet it receives from the Level 1 tree and flood it on other proper Level 1 trees of all the areas in which it acts as the DBRB except the originating area (i.e., the area connected to the incoming interface). (I'd write) if the packet originated from one of the connected areas, RB1 should replicate the packet it receives from the Level 1 tree and flood it on other proper Level 1 trees of all the areas in which it acts as the DBRB except the originating area (i.e., the area connected to the incoming interface). 4. page 9 fourth paragraph - third sentence ["can well appear" would read smoother as "can appear"] (as written) RBridges that do not support either E-L1FS or E-L2FS cannot serve as area border RBridges but they can well appear in an L1 area acting as non-area-border RBridges. (I'd write) RBridges that do not support either E-L1FS or E-L2FS cannot serve as area border RBridges but they can appear in an L1 area acting as non-area-border RBridges. 5. page 11 second paragraph - third sentence ["will finally flooded" should be "will finally be flooded"] (as written) This packet will finally flooded to RB77 via RB30. (should be) This packet will finally be flooded to RB77 via RB30.
- [trill] draft-zhang-trill-multi-level-single-nick… Susan Hares
- Re: [trill] draft-zhang-trill-multi-level-single-… Haoweiguo
- Re: [trill] draft-zhang-trill-multi-level-single-… Liyizhou
- Re: [trill] draft-zhang-trill-multi-level-single-… Donald Eastlake
- Re: [trill] draft-zhang-trill-multi-level-single-… gayle noble
- Re: [trill] draft-zhang-trill-multi-level-single-… Liyizhou
- Re: [trill] draft-zhang-trill-multi-level-single-… Mingui Zhang
- Re: [trill] draft-zhang-trill-multi-level-single-… honjun.zhai