Scott
Thank you for your reply, look below for EV>
-----Original Message-----
From: "Hollenbeck, Scott" <shollenb...@verisign.com>
Date: Thursday, 18 February 2021 at 16:54
To: Eric Vyncke <evyn...@cisco.com>, "i...@ietf.org" <i...@ietf.org>
Cc: "draft-ietf-regext-rfc7482...@ietf.org"
<draft-ietf-regext-rfc7482...@ietf.org>, "regext-cha...@ietf.org"
<regext-cha...@ietf.org>, "regext@ietf.org" <regext@ietf.org>,
"mario.loffr...@iit.cnr.it" <mario.loffr...@iit.cnr.it>
Subject: RE: Éric Vyncke's No Objection on draft-ietf-regext-rfc7482bis-02:
(with COMMENT)
> -----Original Message-----
> From: Éric Vyncke via Datatracker <nore...@ietf.org>
> Sent: Thursday, February 18, 2021 8:39 AM
> To: The IESG <i...@ietf.org>
> Cc: draft-ietf-regext-rfc7482...@ietf.org; regext-cha...@ietf.org;
> regext@ietf.org; Mario Loffredo <mario.loffr...@iit.cnr.it>;
> mario.loffr...@iit.cnr.it
> Subject: [EXTERNAL] Éric Vyncke's No Objection on draft-ietf-regext-
> rfc7482bis-02: (with COMMENT)
>
> Caution: This email originated from outside the organization. Do not
click links
> or open attachments unless you recognize the sender and know the content
> is safe.
>
> Éric Vyncke has entered the following ballot position for
> draft-ietf-regext-rfc7482bis-02: No Objection
>
> 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.)
[SAH] [snip]
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thank you for the work put into this document. I found the document clear
> and easy to read.
>
> Please find below some non-blocking COMMENT points (but replies would
> be appreciated), and some nits.
>
> I hope that this helps to improve the document,
>
> Regards,
>
> -éric
>
> == COMMENTS ==
>
> -- Section 2 --
> Please use BCP14 template (cfr RFC 8714).
[SAH] Will fix.
> -- Section 3.1.1 --
> CIDR RFC 4632 only applies to IPv4... and also uses the words 'prefix
length'
> rather than 'bitmask length'.
[SAH] Do you know of an appropriate reference for IPv6? I can change
"bitmask length" to "prefix length".
EV> let's use indeed 'prefix length" as it is also used in RFC 4632
> "2001:db8::0" is not following the RFC 5952 that is RECOMMENDED just a
> couple of paragraphs above ;-)
[SAH] Please explain. What's needed for a fix?
EV> simply use "2001:db8::" ;-)
> == NITS ==
>
> Like Ben Kaduk, I wonder why using a 16-bit value for US-ASCII "('*',
US-ASCII
> value 0x002A)"...
[SAH] Will fix.
Scott
_______________________________________________
regext mailing list
regext@ietf.org
https://www.ietf.org/mailman/listinfo/regext
