Re: [regext] Robert Wilton's No Objection on draft-ietf-regext-rfc7482bis-02: (with COMMENT)

"Hollenbeck, Scott" <shollenbeck@verisign.com> Thu, 18 February 2021 15:12 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 286593A1341; Thu, 18 Feb 2021 07:12:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 br9aE7fY6OBA; Thu, 18 Feb 2021 07:12:11 -0800 (PST)
Received: from mail4.verisign.com (mail4.verisign.com [69.58.187.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 5BB6C3A1343; Thu, 18 Feb 2021 07:12:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=2714; q=dns/txt; s=VRSN; t=1613661132; h=from:to:cc:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=kPVEiIGY4v3736W7GnzFknTdAiqpa1b72mmc9jsg2Dk=; b=dsfwTljvPyISTBcnZHRNJYVV63ue0sCwCqAPjcRoUxudQbm3ZC6EoO7f qvE2YpIlN4Oa+lQ3sqzBSqSCARduC0JQnGVdQEXZO3AevA6dQk62OfDE8 B8iEwlfd1/OhJFS8OBWKUUMXiAkBaNc5SxR5P6H6mo9ifuxJdNpRPwf1O Lpvwz3hgVibIHlhHakDEsmKYXqCb+DBdktZN950awq1rqWqcu4/5kXD0W hQ9fDc+MnGZ4T2I2bR+ulTv0/ORS+gz7pgzTK2CnlboDZcey/licJcHmg 1Kq2cFzzHcgkHFY/34AMIYmh1vYd0pCJBstLaowBfGwdwi4iZxnQ3XYyu w==;
IronPort-SDR: 3LucOU/FetJsOme7vEZfAgmWc7cGMlNtVZ6Nwi+mitB5a7bWbOup7Nje68r32iIbgdXitZwCHN h2aghbTSzlanf12j3ddNwjI8gnfUxRKsSFSr1rtTQae/gXLZmhcqYuYut6WePihgkbRODrRkFr zgMA9g4GyvT4Ue3Jh4cJ3Xy/+MLqkqV2xt/6+gKQCaBMlNEwz5NWHI0BVeYong+2SMWggmZPQv KrvFgPQiV+PfqES0OlXuPjdo1feFie7n/habNyA4QaQ1jKavIH2Fb6FzVCp/6RRzZiQWTnCQZe aPs=
X-IronPort-AV: E=Sophos;i="5.81,187,1610427600"; d="scan'208";a="5242131"
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:12:10 -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:12:10 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "rwilton@cisco.com" <rwilton@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] Robert Wilton's No Objection on draft-ietf-regext-rfc7482bis-02: (with COMMENT)
Thread-Index: AQHXA476Ycn3KSjiJ0uTVHun2bAhp6peCN4A
Date: Thu, 18 Feb 2021 15:12:09 +0000
Message-ID: <938458f4b97f4e5ab24b699549180cc4@verisign.com>
References: <161338906354.11541.10799402082022849319@ietfa.amsl.com>
In-Reply-To: <161338906354.11541.10799402082022849319@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/epKIYUGG1Tt_-gEuLoh92nxhB2A>
Subject: Re: [regext] Robert Wilton'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:12:13 -0000

> -----Original Message-----
> From: Robert Wilton via Datatracker <noreply@ietf.org>
> Sent: Monday, February 15, 2021 6:38 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] Robert Wilton'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.
>
> Robert Wilton 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:
> ----------------------------------------------------------------------
>
> Hi,
>
> Thanks for this document.  Only one minor comment:
>
> It wasn't clear to me whether the Appendix "Changes from RFC 7482" was
> going to be kept - there is no RFC editor note to suggest that it be removed.
>
> Generally, I think that have a short section explaining how a RFC has changed
> from a previously published version is helpful.  But if this is kept, then I would
> try and condense this text down to the list of important changes from RFC
> 7482.  E.g., added "implementation status" wouldn't apply if that is going to
> be stripped before the RFC is published.

[SAH] My intention was for the appendix to be kept as-is to provide a detailed list of editorial and explanatory changes, confirming that the protocol itself has not been changed. Has the RFC Editor been removing such sections? If so, I can add a note to request that it be preserved.

Scott