Return-Path: <jay@staff.ietf.org>
X-Original-To: rswg@ietfa.amsl.com
Delivered-To: rswg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
	by ietfa.amsl.com (Postfix) with ESMTP id 3C253C157915
	for <rswg@ietfa.amsl.com>; Fri, 12 Jul 2024 09:04:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5
	tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
	HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001,
	T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
	header.d=staff-ietf-org.20230601.gappssmtp.com
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 3tfQxM6VWB5w for <rswg@ietfa.amsl.com>;
	Fri, 12 Jul 2024 09:04:54 -0700 (PDT)
Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com
 [IPv6:2a00:1450:4864:20::335])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest
 SHA256)
	(No client certificate requested)
	by ietfa.amsl.com (Postfix) with ESMTPS id C135AC151551
	for <rswg@rfc-editor.org>; Fri, 12 Jul 2024 09:04:54 -0700 (PDT)
Received: by mail-wm1-x335.google.com with SMTP id
 5b1f17b1804b1-426526d30aaso14871455e9.0
        for <rswg@rfc-editor.org>; Fri, 12 Jul 2024 09:04:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=staff-ietf-org.20230601.gappssmtp.com; s=20230601; t=1720800293;
 x=1721405093; darn=rfc-editor.org;
        h=references:to:cc:in-reply-to:date:subject:mime-version:message-id
         :from:from:to:cc:subject:date:message-id:reply-to;
        bh=TsZ8vH/iaEfNLoZxUom8tr5VIUsGn4u5kLg+dGysVVE=;
        b=dF1+Wwir8coS40zLqleju3WDef4czkoccgomWhgVNR2KAq1bqcnbjfonP2+ggKpxL/
         dSgu2wm/LP+UVzQUI9hwqAmfh3kwF8u/SGVVyFokfkObKGMSumlBxYkUqrI2n7Py2hzC
         XIRPGrgQyPPJzNqpvylEtSF+dZk4kurFxhB+GHKC19tcTw+yDAPUvmrwmoj8u/8ZGFCz
         PNfl2VU6nnFNXb5k9+MtYPT9oZQOZCEUQtUZXvc5XLBLqI5/9nHN0NRROC7hI2BOkJb1
         cIfwKzH68dkeiajOlugyaGCKqw1+F1hBwOTLrXmxVF3NYs3bjonPBxcCDHFgbOO9vs3s
         Yleg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1720800293; x=1721405093;
        h=references:to:cc:in-reply-to:date:subject:mime-version:message-id
         :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to;
        bh=TsZ8vH/iaEfNLoZxUom8tr5VIUsGn4u5kLg+dGysVVE=;
        b=himvuGpGSYOYMbdMXFrPCwTZ7duxR+8NZ74iqwQx9T5et7ubB9+jh5bh1pR/+1yGOv
         8Ri4CDa/+pFu8woBxIk5Yq5EVHl6Xl6H/Ias8v720COBm6zzdBk3oKQIphmnR5wqiW26
         M99YmZH2+Z5Q3oB4op058uW5tkK5pbxASeFuzcmiRlF7LNHzChynr7JC0NT14i3gpM+J
         +pC4zzgaZhTg206oAIlpXWKRgVfpjqh0U0bv4Zt9Ih/O9wDD1dux7I+KBDea64UTb9PK
         MCcGOLRRWLd2v3haSQcnaHCMxB50dmSS2ShRSDQZh3F9Zv8eI7EbfuCLPPoPjUZo8509
         PSdw==
X-Gm-Message-State: AOJu0YyT2aPZh49houYpWbN+sDbF/L2+1VJr54ZOc130jCn31tr3Qyhl
	nYK59Y3YhJug4RGUQfu4L3iM3GHIRqF9cPFrShhD7gBAnHUN+3gkVXdiT4jNxwMpAS+g56d7FtV
	KGNvlWQ==
X-Google-Smtp-Source: 
 AGHT+IHHEbIDFfAbRfcRVxzRdbrqkU+TdT1s+escdeqPKq16ttMqnR6sbsADdrBXvq8tYUFz8lbFqw==
X-Received: by 2002:a05:600c:245:b0:426:6fd3:1547 with SMTP id
 5b1f17b1804b1-426707cf19fmr76725055e9.2.1720800292985;
        Fri, 12 Jul 2024 09:04:52 -0700 (PDT)
Received: from smtpclient.apple ([92.27.125.209])
        by smtp.gmail.com with ESMTPSA id
 5b1f17b1804b1-4279f2cc286sm27954105e9.33.2024.07.12.09.04.52
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Fri, 12 Jul 2024 09:04:52 -0700 (PDT)
From: Jay Daley <exec-director@ietf.org>
Message-Id: <EBCAC3E9-8405-47AF-8885-DD1140686E2C@ietf.org>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_05E2966C-A826-4CA0-8E60-91164BEE41D5"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Date: Fri, 12 Jul 2024 17:04:41 +0100
In-Reply-To: <E423CF6F-24C3-4A4D-89B4-A38757EDBCFC@icann.org>
To: Paul Hoffman <paul.hoffman@icann.org>
References: <E423CF6F-24C3-4A4D-89B4-A38757EDBCFC@icann.org>
X-Mailer: Apple Mail (2.3774.600.62)
Message-ID-Hash: RWEYWJIYFUPMWWCAFGWLAHV524FKUGU5
X-Message-ID-Hash: RWEYWJIYFUPMWWCAFGWLAHV524FKUGU5
X-MailFrom: jay@staff.ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency;
 loop; banned-address; member-moderation; nonmember-moderation; administrivia;
 implicit-dest; max-recipients; max-size; news-moderation; no-subject;
 digests; suspicious-header
CC: RSWG <rswg@rfc-editor.org>, Sandy Ginoza <sginoza@amsl.com>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: =?utf-8?q?=5BRswg=5D_Re=3A_Response_to_RSAB_Last_Call_comments_on_draft-rswg?=
 =?utf-8?q?-rfc7990-updates-10_from_the_RPC?=
List-Id: "RFC Series Working Group (RSWG)" <rswg.rfc-editor.org>
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/rswg/piIOX2cWE9t4p48CWZZDfX6ep_k>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rswg>
List-Help: <mailto:rswg-request@rfc-editor.org?subject=help>
List-Owner: <mailto:rswg-owner@rfc-editor.org>
List-Post: <mailto:rswg@rfc-editor.org>
List-Subscribe: <mailto:rswg-join@rfc-editor.org>
List-Unsubscribe: <mailto:rswg-leave@rfc-editor.org>


--Apple-Mail=_05E2966C-A826-4CA0-8E60-91164BEE41D5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 12 Jul 2024, at 16:15, Paul Hoffman <paul.hoffman@icann.org> wrote:
>=20
>> 3) Section 1.3 (not related to terminology)
>>=20
>> Current:
>>  The first RFC to be published following the guidance of the group of
>>  RFCs described in [RFC7990] was [RFC8650], published in November
>>  2019.=20
>>=20
>> Suggested (because the first RFC published was RFC 8651):=20
>> The first RFC (by date order) to be published following the the =
guidance of the group of
>> RFCs described in [RFC7990] was [RFC8651], published in October 2019.=20=

>>=20
>> Or:=20
>> The first RFC (by RFC number order) to be published following the the =
guidance of the group of
>> RFCs described in [RFC7990] was [RFC8650], published in November =
2019.
>=20
> Ouch. I (Paul) carefully checked this, but obviously did so =
incorrectly. We'll go with the first version (8651).

This might seem trivial, but I think it=E2=80=99s better to go with RFC =
number order, not date order, and therefore RFC 8650.  The reasoning is =
because it=E2=80=99s more important to tell people at what point in the =
series the formats change, not precisely when the change happened.

Jay

--=20
Jay Daley
IETF Executive Director
exec-director@ietf.org


--Apple-Mail=_05E2966C-A826-4CA0-8E60-91164BEE41D5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"overflow-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: =
after-white-space;"><div><blockquote type=3D"cite"><div>On 12 Jul 2024, =
at 16:15, Paul Hoffman &lt;paul.hoffman@icann.org&gt; =
wrote:</div><div><div><br><blockquote type=3D"cite">3) Section 1.3 (not =
related to terminology)<br><br>Current:<br> &nbsp;The first RFC to be =
published following the guidance of the group of<br> &nbsp;RFCs =
described in [RFC7990] was [RFC8650], published in November<br> =
&nbsp;2019. <br><br>Suggested (because the first RFC published was RFC =
8651): <br>The first RFC (by date order) to be published following the =
the guidance of the group of<br>RFCs described in [RFC7990] was =
[RFC8651], published in October 2019. <br><br>Or: <br>The first RFC (by =
RFC number order) to be published following the the guidance of the =
group of<br>RFCs described in [RFC7990] was [RFC8650], published in =
November 2019. <br></blockquote><br>Ouch. I (Paul) carefully checked =
this, but obviously did so incorrectly. We'll go with the first version =
(8651).<br></div></div></blockquote><div><br></div><div>This might seem =
trivial, but I think it=E2=80=99s better to go with RFC number order, =
not date order, and therefore RFC 8650. &nbsp;The reasoning is because =
it=E2=80=99s more important to tell people at what point in the series =
the formats change, not precisely when the change =
happened.</div><div><br></div><div>Jay</div></div><br><div>
<meta charset=3D"UTF-8"><div>--&nbsp;<br>Jay Daley<br>IETF Executive =
Director</div><div>exec-director@ietf.org</div>
</div>
<br></body></html>=

--Apple-Mail=_05E2966C-A826-4CA0-8E60-91164BEE41D5--

