Re: [regext] Éric Vyncke's No Objection on draft-ietf-regext-rfc7482bis-02: (with COMMENT)

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 18 February 2021 15:54 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FC2C3A13B9; Thu, 18 Feb 2021 07:54:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.399
X-Spam-Level:
X-Spam-Status: No, score=-4.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
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 5N7D6LYYo9WA; Thu, 18 Feb 2021 07:54:21 -0800 (PST)
Received: from mail1.verisign.com (mail1.verisign.com [72.13.63.30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFB333A138D; Thu, 18 Feb 2021 07:54:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2818; q=dns/txt; s=VRSN; t=1613663662; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=8McRMuPAsGbUFc3hy/7jMkI+DB8k7VXrOgUez5ygWX4=; b=aaozOMTdlvMYXNs5iC/tlLZSkGtMuCbjx2hb/0bD2gYMVFe0WzArgwxb G8s142K+pBvlf+K6ODmTVvsrBlBq32TiIxcviqP8iMiV+KgyO5GpZyV1J YsAZqMaFgvlDqj9d11mvHBzGUwnWkCq5bQFotCLcaP7N1E7BBowOeA2rz YPCPakQH2O04LeV1wSDj8gU49stqNZjcgnZmhZQTXLtY+4KCVDM1X9XJR FjvbdlBR703iq+oKVyKbgKg1hthXmdVtwsFp01HoeWoeK6RYvhrCpXCw0 budmAZM2uJ5l0YEmTIkuIyDKwByomfgbVzCiKP1PAo0AVacXGgu3I/ZHj A==;
IronPort-SDR: 2YkIqtUP5KjyW3v5stAWpEgL9ABEmpR7mHmc6clugaOsSSDCqSD7uZk1yXMDQ2UKp+BWL8UOZn PYxOxFKz45kGYm+F1+YtsWmDl6LK3oWXKaelzNloGjpyPP1dYDhbSks50WdaBi8Tuy1qu33ZLR qH1+6PqxL22j19iaFtwyEghZdmspU7u0WWsiFAO3BC6He2cC4m26x4gPkcQG6qna18K6kavwR5 jMl5ctnIZ9gRZHp0vcfbYlnt4ch8g2+gCB127HdvOlvCK0+WtBw7V6QBaqIyo5uvnaPQpxj+KN KrE=
X-IronPort-AV: E=Sophos;i="5.81,187,1610409600"; d="scan'208";a="5809048"
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.2; Thu, 18 Feb 2021 10:54:19 -0500
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde]) by BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde%4]) with mapi id 15.01.2176.002; Thu, 18 Feb 2021 10:54:19 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "evyncke@cisco.com" <evyncke@cisco.com>, "iesg@ietf.org" <iesg@ietf.org>
CC: "draft-ietf-regext-rfc7482bis@ietf.org" <draft-ietf-regext-rfc7482bis@ietf.org>, "regext-chairs@ietf.org" <regext-chairs@ietf.org>, "regext@ietf.org" <regext@ietf.org>, "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it>
Thread-Topic: [EXTERNAL] Éric Vyncke's No Objection on draft-ietf-regext-rfc7482bis-02: (with COMMENT)
Thread-Index: AQHXBftx4C5X4/3BF0+2KrOfhYzrgapeDtNA
Date: Thu, 18 Feb 2021 15:54:19 +0000
Message-ID: <c1d4b0be4163461897e115c51595423d@verisign.com>
References: <161365555006.28152.13195381447082400063@ietfa.amsl.com>
In-Reply-To: <161365555006.28152.13195381447082400063@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/spY-mbcgLbzRRDzdUSofA0Em7PA>
Subject: Re: [regext] Éric Vyncke's No Objection on draft-ietf-regext-rfc7482bis-02: (with COMMENT)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2021 15:54:23 -0000

> -----Original Message-----
> From: Éric Vyncke via Datatracker <noreply@ietf.org>
> Sent: Thursday, February 18, 2021 8:39 AM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-regext-rfc7482bis@ietf.org; regext-chairs@ietf.org;
> regext@ietf.org; Mario Loffredo <mario.loffredo@iit.cnr.it>;
> mario.loffredo@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".

> "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?

> == NITS ==
> 
> Like Ben Kaduk, I wonder why using a 16-bit value for US-ASCII "('*', US-ASCII
> value 0x002A)"...

[SAH] Will fix.

Scott