Re: [Roll] WGLC for draft-ietf-roll-dao-projection-26

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 19 October 2022 21:16 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 329FEC14F749; Wed, 19 Oct 2022 14:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.426
X-Spam-Level: *
X-Spam-Status: No, score=1.426 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rEruUOmECFGC; Wed, 19 Oct 2022 14:16:06 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F16DDC1522A2; Wed, 19 Oct 2022 14:16:05 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [208.94.110.98]) by relay.sandelman.ca (Postfix) with ESMTPS id 4D9ED1F479; Wed, 19 Oct 2022 21:16:03 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id ABE35A18CB; Wed, 19 Oct 2022 17:15:58 -0400 (EDT)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id A8DAFA0197; Wed, 19 Oct 2022 17:15:58 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "dominique.barthel@orange.com" <dominique.barthel@orange.com>, roll <roll@ietf.org>, "draft-ietf-roll-dao-projection@ietf.org" <draft-ietf-roll-dao-projection@ietf.org>
In-reply-to: <C6878E79-6336-4834-99B7-499193A5B8BC@cisco.com>
References: <CAP+sJUei2+syMHrgp0NbBetvHV1y7ZtMrG9JY+ZX93Rnob1dwg@mail.gmail.com> <CAP+sJUcpY8j6NsDULjzZrkwW5+Fs=aJ5uU28e--X2S+duK+pZw@mail.gmail.com> <4289_1656084766_62B5D91E_4289_213_1_4c7f1f6899254fcc91a2bce6eb5d1451@orange.com> <CAP+sJUfpvoBz7ZqbKQJe46groyfOxc_3DQ-C6_W1vRxN-+UK3A@mail.gmail.com> <29152_1658413550_62D961EE_29152_352_1_9310f3edb47540de9c47f9d280b3dc43@orange.com> <CO1PR11MB4881456AD7EB0A238DA15C98D8909@CO1PR11MB4881.namprd11.prod.outlook.com> <2006073.1658513924@dooku> <C6878E79-6336-4834-99B7-499193A5B8BC@cisco.com>
Comments: In-reply-to "Pascal Thubert (pthubert)" <pthubert@cisco.com> message dated "Fri, 22 Jul 2022 20:51:45 -0000."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 19 Oct 2022 17:15:58 -0400
Message-ID: <370145.1666214158@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/VTvLZ7s2gFcty02BeMNK2wX3Oj0>
Subject: Re: [Roll] WGLC for draft-ietf-roll-dao-projection-26
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Oct 2022 21:16:10 -0000

{time warp mail warning!}

Pascal Thubert (pthubert) <pthubert@cisco.com> wrote:
    > That {doing aasvg for diagrams} would be neat Michael !

I think that we have to move to markdown to get auto aasvg processing.
That's about an hour's work for me to do, but you authors need to agree to
switch at this late point.

I took the dozen diagrams through aasvg to get you:
   https://www.sandelman.ca/tmp/dao/

There are slight improvements in a few of the diagrms.
Figure 4 is one I had hoped to get way more out of, but it will need tweaking
to the ascii.
Figure 6, okay.
Figure 7 got worse, needs tweaks.
The packet diagrams do not benefit, I'd leave the out.
Figure 13 went well.
Figure 14... not so good.

So, let me know if this is worth doing.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-