[Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
Erik Kline via Datatracker <noreply@ietf.org> Thu, 13 August 2020 08:19 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: anima@ietf.org
Delivered-To: anima@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C2B803A08A3; Thu, 13 Aug 2020 01:19:25 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Erik Kline via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-anima-autonomic-control-plane@ietf.org, anima-chairs@ietf.org, anima@ietf.org, Sheng Jiang <jiangsheng@huawei.com>, jiangsheng@huawei.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Erik Kline <ek.ietf@gmail.com>
Message-ID: <159730676576.12387.18205135091671983859@ietfa.amsl.com>
Date: Thu, 13 Aug 2020 01:19:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/rRmSs6PhGQi55lB0TME80DTy7Zg>
Subject: [Anima] Erik Kline's Discuss on draft-ietf-anima-autonomic-control-plane-28: (with DISCUSS and COMMENT)
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2020 08:19:26 -0000
Erik Kline has entered the following ballot position for draft-ietf-anima-autonomic-control-plane-28: Discuss When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-anima-autonomic-control-plane/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- [ section 2 ] * "It is the approximate IPv6 counterpart of the IPv4 private address ([RFC1918])." I understand the intent but I don't think this statement is complete. I think we shouldn't let this sentence out into the wild as is since it could be read without any context nor even any pretense of interest in nuance. May I suggest: "It is often thought of as the approximate IPv6 counterpart of the IPv4 private address space ([RFC1918]), though it is in fact meaningfully different in important and subtle ways [and upon which this document relies]." [ section 6.10.2 ] * Please clarify the table at the end of this section. It looks like only two Types are listed, but should all 4 bit values be present? Where are the Z, F, and V bits in the address? I realize these are defined in the following sections, so it probably suffices to say something like "The Z, F, and V bits are allocated from within the sub-scheme portion of the address according to the following sections..." or something. Unassigned/unused Type values should maybe be listed in the table as "Reserved"? [ section 8.1.3 ] * Why is an RIO for ::/0 with a lifetime of 0 required? Doesn't it suffice it set the default router lifetime to 0? Separately, are all nodes required to be Type C? ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- [ section 1 ] * "as good as possible" might be "as well as possible", but I'm unsure if I have any grammatical basis for this (adverbial phrase vs adjectival phrase?). * "ACPs functions" -> "ACP's functions"? * "overview how" perhaps: "overview of how" * "propriety extensions" -> "proprietary extensions" [ section 2 ] * "On virtual nodes their equivalent." isn't really a complete sentence. I think if you just join it to the previous sentence with ";" it works grammatically. [ section 6.1.1 ] * s/devices "serialNumber"/device's "serialNumber"/ [ section 6.1.2 ] * The example "fd89b714F3db00000200000064000000" contains an uppercase "F" and therefore doesn't conform to 32HEXLC, I believe. * 2. 2.1, "a nodes ACP" -> "a node's ACP" (it is correct in the immediately preceding sentence). [ section 6.1.3 ] * The rsub field, even if deliberately not pertinent, is a bit conspicuous by its absence from this section I think. It might good to state so explicitly (at least I, as a reader, was expecting to see some mention of it). [ section 6.1.5.1 ] * I think the 32 hex lowercase IPv6 addresses in the examples are each missing a single hex character (31 instead of 32)? Or maybe that's not what these fields are (or I've miscounted)? [ section 6.3 ] * "does not include ACP nodes ACP certificate" perhaps -> "does not include the ACP node's ACP certificate" * With respect to DULL GRASP message fragmentation due to certificate inclusion: is it of any value to include the fingerprint of the ACP cert, for diagnostics...? [ section 6.5 ] * s/to easier distinguish/to more easily distinguish/ [ section 6.6 ] * Feel free to phrase the backoff implementation in reference to RFC 8415 section 15 semantics (I think: IRT = 10 seconds, MRT = 640 seconds). [ section 6.7.3.2 ] * Should Responder-IPv6-ACP-LL-addr be in the TSr set? [ section 6.10.1 ] * "not expected to be end-user host." --> "... hosts." [ section 6.11.1.11 ] * What does a manual configuration (6.10.4) advertise? Just its /128? * Where does the /96 come from? [ section 6.12.3 ] * "meant to be prioritize reliability" -> "meant to prioritize reliability" [ section 6.12.5.1 ] * s/adddress/address/ * (see Figure 15 --> (see Figure 15) * on other type -> on other types [ section 6.12.5.2.2 ] * "ACP nodes MAY reduce the amount of link-local IPv6 multicast packets from ND by learning the IPv6 link-local neighbor address to ACP secure channel mapping from other messages such as the source address of IPv6 link-local multicast RPL messages - and therefore forego the need to send Neighbor Solicitation messages." Isn't this only true on links with configurations such that a node can trust that the source link layer address of the received RPL message is guaranteed to be that of the original sender? [ Appendix A.1 ] * Yeah, I gotta say I didn't understand why the acp-address scheme wouldn't support giving each ACP loopback its own /64 from the start. That's 14-16 bits of /64s in a single rsub ULA's /48 which would seem pretty simple to implement (a /64 per router in some deployments).
- [Anima] Erik Kline's Discuss on draft-ietf-anima-… Erik Kline via Datatracker
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Barry Leiba
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Toerless Eckert
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Toerless Eckert
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Erik Kline
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Toerless Eckert
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Eliot Lear
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Eric Vyncke (evyncke)
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Brian E Carpenter
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Eric Vyncke (evyncke)
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Toerless Eckert
- Re: [Anima] Erik Kline's Discuss on draft-ietf-an… Erik Kline