Re: [rfc-i] What obsoletes what?

Brian E Carpenter <brian.e.carpenter@gmail.com> Sun, 18 February 2024 03:00 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63019C14F5E3 for <rfc-interest@ietfa.amsl.com>; Sat, 17 Feb 2024 19:00:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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=gmail.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 3FAVZgSBKV8i for <rfc-interest@ietfa.amsl.com>; Sat, 17 Feb 2024 19:00:57 -0800 (PST)
Received: from mail-pj1-x1036.google.com (mail-pj1-x1036.google.com [IPv6:2607:f8b0:4864:20::1036]) (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 BEAC5C14E515 for <rfc-interest@rfc-editor.org>; Sat, 17 Feb 2024 19:00:52 -0800 (PST)
Received: by mail-pj1-x1036.google.com with SMTP id 98e67ed59e1d1-296c562ac70so1597606a91.2 for <rfc-interest@rfc-editor.org>; Sat, 17 Feb 2024 19:00:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1708225252; x=1708830052; darn=rfc-editor.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=lfm+5i0EyMcp3JljvF+vcSpLE6L0Fkg1NfAVE5UUIDc=; b=LHdhKeDh/KROt8+U6c7zDHFS2G+u5VfHID9pSArCl6VGkJaJg1mRemwKAr985MiydU kSwQG1U9KTahCCJDKzNkUYEsZD7Pird049QfeTpKgxw20gTHoApbZW9p9SZB7lIRACUB Udkz72LIEkoXlo80ozYJdSvkKGr2ZrY4U8xDN8zaWy5xISYGHotGqVxRIvyXsMIvseRS AqgV0JjBwqQK9Y5mWQDcezN21mAMfEwSiQMowJzV53pc9cQfc7YLZh8Ueb76AB0RKGR2 FnMjVDHx+EO6LjRi2/U2DO96XBOkNBc5RXywWtLazmvjRJef665nLbVE4MkJpOcYlkM2 KVNQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708225252; x=1708830052; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=lfm+5i0EyMcp3JljvF+vcSpLE6L0Fkg1NfAVE5UUIDc=; b=GXmjtz0w/f7rVM08oWT0k9vPn1cxL9LxoZiqkJfwyVbdZU3aSTuRWJA+n4Qq8m27fh AFWlJ9KB13yEFFHefQrqM3AzaAuFFReh4Y9VqvumqSMBI+0p4PavP7aOokDC8V8aBfYL /Kkf18cXtWoXfsGip7aSNjDQYoH9f7/6mY+sO6oczoTvvsymC2AccLrJqbm4C+CgOP5S 8zXQCom2PALM+iZ0YLkTuIgEXDxMd/CEhl6MozOED+ZRyoyyYuK61/OyjsS6aCggyUKj L86PN+XrB621KxYXqPnR/OCW4P1sPBirXbW2WnZmdTOsaPzPwGf0/XC8bXQDVkkEHhEV mrcA==
X-Forwarded-Encrypted: i=1; AJvYcCUuSqaasM4+NOrIaf4AiwYOeabnc7vyWtQjQAVCAiJilgS5rBHBpI1Iu5yJYRdyAmFKFILcsYfMGZirJCA0/jGhWLH5jB6x4iVDSoM=
X-Gm-Message-State: AOJu0Yyc8ocHZJtMkhJbBZLJ9ZY84bVbz6BJfqDX0MevLvnyQD0pBZCh 1JX1QPLGUjc6s4sLo7kg+VsjWpzc6vgknlUXFrqV/yOH+C4BAJ6i
X-Google-Smtp-Source: AGHT+IFYwdzCE6KbDZY9IqFNkYouvwnjsErCieq6A7ZyRBhApzhraRVCzsZAd8d7lQqQdZ1mGzjmkQ==
X-Received: by 2002:a17:902:e548:b0:1db:e9ed:bbca with SMTP id n8-20020a170902e54800b001dbe9edbbcamr1631plf.52.1708225251580; Sat, 17 Feb 2024 19:00:51 -0800 (PST)
Received: from ?IPV6:2404:4400:541d:a600:44b7:2c2e:2bc6:8707? ([2404:4400:541d:a600:44b7:2c2e:2bc6:8707]) by smtp.gmail.com with ESMTPSA id 6-20020a170902e9c600b001d706e373a9sm2031940plk.292.2024.02.17.19.00.50 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 17 Feb 2024 19:00:51 -0800 (PST)
Message-ID: <2abac40c-1918-ddec-e54d-6864f7f187dd@gmail.com>
Date: Sun, 18 Feb 2024 16:00:45 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: "Salz, Rich" <rsalz@akamai.com>, RFC Interest <rfc-interest@rfc-editor.org>
References: <9c7191d3-74d4-3d43-8f77-925191d12b5e@gmail.com> <03F2CE3F-EBAA-4A34-AA19-72082AB94E39@akamai.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <03F2CE3F-EBAA-4A34-AA19-72082AB94E39@akamai.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/X2Q0kddB5VvbWHakpd-ikI6o1z8>
Subject: Re: [rfc-i] What obsoletes what?
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Sun, 18 Feb 2024 03:00:58 -0000

On 18-Feb-24 15:37, Salz, Rich wrote:
>> TL;DR: RFC 6248 obsoleted a BCP (RFC 4148), and RFC1574 and RFC1575 *both* obsoleted a PS (RFC 1139).
> 
> When did the "downref" thing become a common practice? RFC 3797? If so, 1574 and 1575 pre-date it and 6248 could be corrected with an IESG action, right?

I don't think the underlying rules about downrefs have really changed since RFC 2026. I think you meant RFC 3967, and that was needed to clarify existing practice. But anyway, since the IESG approved RFC 6248, they must have decided it was OK at the time. Maybe there's an answer deep in the ietf-announce archive.

     Brian