IETF Logo Mail Archive

[Gendispatch] Re: New Version Notification for draft-rsalz-2026bis-11.txt

"Salz, Rich" <rsalz@akamai.com> Tue, 15 October 2024 20:08 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: gendispatch@ietfa.amsl.com
Delivered-To: gendispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD20EC1D4A72 for <gendispatch@ietfa.amsl.com>; Tue, 15 Oct 2024 13:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level:
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.148, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.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 t7fvRMSWts4e for <gendispatch@ietfa.amsl.com>; Tue, 15 Oct 2024 13:08:02 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) by ietfa.amsl.com (Postfix) with ESMTP id EF487C180B63 for <gendispatch@ietf.org>; Tue, 15 Oct 2024 13:08:01 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.18.1.2/8.18.1.2) with ESMTP id 49FDXi6X011216; Tue, 15 Oct 2024 21:07:57 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h= content-id:content-transfer-encoding:content-type:date:from :in-reply-to:message-id:mime-version:references:subject:to; s= jan2016.eng; bh=KJmB6oKQQpcdBPmbG2UE7WLylVDzExsjtV8/CLcoO+I=; b= S4v6xPgWN5LmkhzRx3luSSOgsOnyiGHK/QdTINBBowctB8e4b7x8NANpkuXqXOjx 5PTsfwl6cAAUPRIQ6kMEj31A7WFE1mhqLc/bgik0V+4KeoSIxRwq4iH+qJQXXGgD 2cz0izV/nGCNmtPb1gOG63H4oJATKsv2psfjOLtNUQ6oDiqQuGckTrUf9cYxcaS8 gK9TfxSCTKeIrvycchMKSPtOhwmTClF0GMw3ocN8zNHkm6S2LRPwIThWGLmcc4rc bY3aahOpSofiZ8d2x/ycnzKz0w14Z2vdKOuMeKUPCd1eQ8yyK+8hvr5/yBFYpwtP VHMrQ4xneYaG4pPvz9mHMg==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by mx0a-00190b01.pphosted.com (PPS) with ESMTPS id 427gcc6wtg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 15 Oct 2024 21:07:57 +0100 (BST)
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.18.1.2/8.18.1.2) with ESMTP id 49FIsBVv013388; Tue, 15 Oct 2024 16:07:55 -0400
Received: from email.msg.corp.akamai.com ([172.27.50.207]) by prod-mail-ppoint1.akamai.com (PPS) with ESMTPS id 427mevma8v-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 15 Oct 2024 16:07:55 -0400
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com (172.27.50.203) by ustx2ex-dag4mb8.msg.corp.akamai.com (172.27.50.207) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Tue, 15 Oct 2024 13:07:54 -0700
Received: from ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) by ustx2ex-dag4mb4.msg.corp.akamai.com ([172.27.50.203]) with mapi id 15.02.1544.011; Tue, 15 Oct 2024 13:07:54 -0700
From: "Salz, Rich" <rsalz@akamai.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Rob Wilton (rwilton)" <rwilton@cisco.com>, "gendispatch@ietf.org" <gendispatch@ietf.org>
Thread-Topic: [Gendispatch] Re: New Version Notification for draft-rsalz-2026bis-11.txt
Thread-Index: AQHbGZKawejN6c9Fe0SDVjkzZtCFZbJ9JiKA///SvLmAAGMhAIADhm2A//++ToCACBVDgP//xP8A
Date: Tue, 15 Oct 2024 20:07:54 +0000
Message-ID: <BA6A4C3B-DCF0-450F-9ADB-2F5195F83597@akamai.com>
References: <172839953364.104721.10816128696930288653@dt-datatracker-74758d9965-nl2b7> <0203667C-B9D0-4B11-8C7C-39DCFC860922@akamai.com> <LV8PR11MB85360E564DE32795A077B7D1B57E2@LV8PR11MB8536.namprd11.prod.outlook.com> <29B8565D-9FF6-4B78-8F84-D4A55630F9E4@akamai.com> <c6464a4c-f98d-4bc8-b879-069499ee584e@gmail.com> <082BC9D7-403D-4711-AF95-C8D10D74C6E9@akamai.com> <530a1253-41df-4567-ab10-b2d90e67ee6d@gmail.com>
In-Reply-To: <530a1253-41df-4567-ab10-b2d90e67ee6d@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.89.24091630
x-originating-ip: [172.27.118.139]
Content-Type: text/plain; charset="utf-8"
Content-ID: <3B5C53DBD68F5E4393839CFE7E7065B9@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1051,Hydra:6.0.680,FMLib:17.12.62.30 definitions=2024-10-15_15,2024-10-15_01,2024-09-30_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 mlxlogscore=736 mlxscore=0 bulkscore=0 malwarescore=0 suspectscore=0 spamscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2409260000 definitions=main-2410150135
X-Proofpoint-GUID: UrQUKDna18jzVOpY8BW2K7kkqCyjTsLW
X-Proofpoint-ORIG-GUID: UrQUKDna18jzVOpY8BW2K7kkqCyjTsLW
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.293,Aquarius:18.0.1039,Hydra:6.0.680,FMLib:17.12.60.29 definitions=2024-09-06_09,2024-09-06_01,2024-09-02_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 impostorscore=0 malwarescore=0 spamscore=0 phishscore=0 mlxscore=0 clxscore=1015 mlxlogscore=486 suspectscore=0 priorityscore=1501 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.19.0-2409260000 definitions=main-2410150135
Message-ID-Hash: HYRSNMCH2XE2AF7VDZDK7FHR347W5RGR
X-Message-ID-Hash: HYRSNMCH2XE2AF7VDZDK7FHR347W5RGR
X-MailFrom: rsalz@akamai.com
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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Gendispatch] Re: New Version Notification for draft-rsalz-2026bis-11.txt
List-Id: General Area Dispatch <gendispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gendispatch/5qHqO6FLaT68-B3lbU_anR-K9Es>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gendispatch>
List-Help: <mailto:gendispatch-request@ietf.org?subject=help>
List-Owner: <mailto:gendispatch-owner@ietf.org>
List-Post: <mailto:gendispatch@ietf.org>
List-Subscribe: <mailto:gendispatch-join@ietf.org>
List-Unsubscribe: <mailto:gendispatch-leave@ietf.org>

>>> I think there are bogons in there, e.g. RFC 3450 (chosen at random) references 2026 but doesn't cite the reference. But quite a few to check...
 
>> Are there? Do we udate references when RFC N becomes RFC Nbis? I thought we just assume that the obsoleted-by tag is good enough.

>We don't. Possibly we should, but that's an RSWG topic. I just wanted to observe that to do complete due diligence, we'd need to look at all of them to see if any of them are significant.

I do not think I understand what you are saying.

Suppose that RFC N references 2026, but isn't on the updated-by list[2]. Are you saying that we need to see if any of the nearly 300 in that list [1] actually do update 2026? If that is what you are saying, I disagree. We're not verifying that the RFC Editor/Publication Center did their job correctly and that the updated-by  field in [2] is correct. I am not aware of any bis-type draft that has done this; are you?

Another option is that you could be pointing out that many RFC's reference 2026 (as opposed to, say, BCP 9). I don't think that is a problem either, since if anyone fetches RFC N, and then goes to look up RFC 2026 (in either the datatracker or the RFC Editor website), they'll see that it is obsoleted by this new document. Sure, there are probably copies of 2026 floating around that will not have that information, but this is the Web and there's not much we can do about that. I think if RFC N references 2026, then when RFC N-bis is published the 2026 reference will be updated. Unless and until then, there is nothing to do.

If you are not saying either of the above, please explain it to me.

[1] https://datatracker.ietf.org/doc/rfc2026/referencedby/
[2] https://www.rfc-editor.org/info/rfc2026

v2.46.0 | Report a Bug | By Email | System Status