Hello, Thank you for your input. We've gone through all SHOULDs in the document, and added additional clarification for about half of them: https://github.com/mxsasha/nrtmv4/commit/00fe50596f2200427998aba1815370695e07e39b
For the others, we felt there was sufficient context already. Sasha On 10 Apr 2026, at 17:38, Eric Vyncke (evyncke) <[email protected]> wrote: > > About the SHOULD, the comment is about ALL of the BCP 14 (uppercase) "SHOULD" > > About SVG, I agree that adding SVG when using XML is not easy at all... So, > ignore my suggestion. > > -éric > > From: Sasha Romijn <[email protected]> > Date: Friday, 10 April 2026 at 15:01 > To: Eric Vyncke (evyncke) <[email protected]> > Cc: The IESG <[email protected]>, [email protected] > <[email protected]>, [email protected] > <[email protected]>, [email protected] <[email protected]>, [email protected] > <[email protected]> > Subject: Re: Éric Vyncke's No Objection on draft-ietf-grow-nrtm-v4-09: (with > COMMENT) > > Hello Éric, > > Thank you for your review. > > On 10 Apr 2026, at 13:45, Éric Vyncke via Datatracker <[email protected]> > wrote: > I have a major comment as there are several "SHOULD" in the text without the > required guidance per > https://datatracker.ietf.org/doc/statement-iesg-statement-on-clarifying-the-use-of-bcp-14-key-words/ > > Could you elaborate on which SHOULDs in the document you think need > additional guidance? > > Another cosmetic suggestion: use SVG graphics rather than ASCII art, the HTML > rendering is much nicer (and easy to do if the authors use the Markdown > format). > > Our source format is XML: > https://github.com/mxsasha/nrtmv4/blob/5d4918454b3fcc3902ccb797f11d33bb58e82c5c/draft-ietf-grow-nrtm-v4.xml#L141-L163 > I did explore adding an SVG graphic, but could not get it right, hence we > stayed (and prefer to stay with) ASCII art. > > Sasha
_______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
