[rfc-i] An update to subseries references

Jean Mahoney <jmahoney@amsl.com> Tue, 13 February 2024 20:26 UTC

Return-Path: <jmahoney@amsl.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 B58FAC151090 for <rfc-interest@ietfa.amsl.com>; Tue, 13 Feb 2024 12:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-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
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 z5bmAb09g_V8 for <rfc-interest@ietfa.amsl.com>; Tue, 13 Feb 2024 12:26:18 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 F27C0C15107E for <rfc-interest@rfc-editor.org>; Tue, 13 Feb 2024 12:26:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id E2035424CD3F for <rfc-interest@rfc-editor.org>; Tue, 13 Feb 2024 12:26:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yq8oKTDofunq for <rfc-interest@rfc-editor.org>; Tue, 13 Feb 2024 12:26:17 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.48.51]) by c8a.amsl.com (Postfix) with ESMTPSA id BF205424B455 for <rfc-interest@rfc-editor.org>; Tue, 13 Feb 2024 12:26:17 -0800 (PST)
Message-ID: <c4d95ba8-a003-49d9-8089-f102ab274e92@amsl.com>
Date: Tue, 13 Feb 2024 14:26:16 -0600
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: RFC Interest <rfc-interest@rfc-editor.org>
From: Jean Mahoney <jmahoney@amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/bOI3PYuE9ZZoglxeVO9jqDz_9eg>
Subject: [rfc-i] An update to subseries references
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: Tue, 13 Feb 2024 20:26:21 -0000

Hi all,

The RPC is updating the style for subseries references by adding 
introductory text to the reference and also adding DOIs and links for 
RFCs listed for the subseries. Note that we are adding "At the time of 
writing" because the RFCs within a subseries can change over time.
We have opened an xml2rfc feature request:
https://github.com/ietf-tools/xml2rfc/issues/1100

An example of a single-RFC subseries reference:

OLD:

    [STD72]    Gellens, R. and J. Klensin, "Message Submission for Mail",
               STD 72, RFC 6409, November 2011.

               <https://www.rfc-editor.org/info/std72>

NEW:

    [STD72]    Internet Standard 72,
               <https://www.rfc-editor.org/info/std/std72>.
               At the time of writing, this STD comprises the following:

               Gellens, R. and J. Klensin, "Message Submission for Mail",
               STD 72, RFC 6409, DOI 10.17487/RFC6409, November 2011,
               <https://www.rfc-editor.org/info/rfc6409>.


An example of a multiple-RFC subseries reference:

OLD:

    [STD69]    Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
               STD 69, RFC 5730, August 2009.

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
               Domain Name Mapping", STD 69, RFC 5731, August 2009.

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
               Host Mapping", STD 69, RFC 5732, August 2009.

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
               Contact Mapping", STD 69, RFC 5733, August 2009.

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
               Transport over TCP", STD 69, RFC 5734, August 2009.

               <https://www.rfc-editor.org/info/std69>

NEW:

    [STD69]    Internet Standard 69,
               <https://www.rfc-editor.org/info/std69>.
               At the time of writing, this STD comprises the following:

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)",
               STD 69, RFC 5730, DOI 10.17487/RFC5730, August 2009,
               <https://www.rfc-editor.org/info/rfc5730>.

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
               Domain Name Mapping", STD 69, RFC 5731,
               DOI 10.17487/RFC5731, August 2009,
               <https://www.rfc-editor.org/info/rfc5731>.

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
               Host Mapping", STD 69, RFC 5732, DOI 10.17487/RFC5732,
               August 2009,
               <https://www.rfc-editor.org/info/rfc5732>.

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
               Contact Mapping", STD 69, RFC 5733,
               DOI 10.17487/RFC5733, August 2009,
               <https://www.rfc-editor.org/info/rfc5733>.

               Hollenbeck, S., "Extensible Provisioning Protocol (EPP)
               Transport over TCP", STD 69, RFC 5734,
               DOI 10.17487/RFC5734, August 2009,
               <https://www.rfc-editor.org/info/rfc5734>.


Best regards,
Jean