Re: [rfc-i] Includes for BCPs and STDs [Was: Making a v3 document manually]

"Pete Resnick" <resnick@episteme.net> Thu, 19 December 2019 19:03 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 807C2120B3B for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 19 Dec 2019 11:03:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.95
X-Spam-Level:
X-Spam-Status: No, score=-4.95 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 KuL7aO9Rn6SF for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 19 Dec 2019 11:03:46 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6B11120B28 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 19 Dec 2019 11:03:46 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id B7C69F40725; Thu, 19 Dec 2019 11:03:26 -0800 (PST)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 5E512F40725 for <rfc-interest@rfc-editor.org>; Thu, 19 Dec 2019 11:03:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wwRya89h6vNB for <rfc-interest@rfc-editor.org>; Thu, 19 Dec 2019 11:03:25 -0800 (PST)
Received: from episteme.net (episteme.net [216.169.5.102]) by rfc-editor.org (Postfix) with ESMTPS id 5C3C2F40720 for <rfc-interest@rfc-editor.org>; Thu, 19 Dec 2019 11:03:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by episteme.net (Postfix) with ESMTP id C202E981ED36; Thu, 19 Dec 2019 13:03:43 -0600 (CST)
Received: from episteme.net ([127.0.0.1]) by localhost (episteme.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ueFSV1F4MPT0; Thu, 19 Dec 2019 13:03:42 -0600 (CST)
Received: from [172.16.1.10] (episteme.net [216.169.5.102]) by episteme.net (Postfix) with ESMTPSA id 02197981ED2D; Thu, 19 Dec 2019 13:03:41 -0600 (CST)
From: Pete Resnick <resnick@episteme.net>
To: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 19 Dec 2019 13:03:41 -0600
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <7E9D0B45-7780-4BCF-BED6-327DB86E343A@episteme.net>
In-Reply-To: <CA+9kkMA1mm4=5RpO+iC1YJBWkcy5HZ6XQruOSC9WDvA26dcekQ@mail.gmail.com>
References: <0e6427dd-df73-4946-a688-e02e9d68ae65@joelhalpern.com> <64ec190d-62fe-bcf1-ffd6-012d0da403f3@gmx.de> <8A76E9C0-921E-42CF-8EDD-6F95A91C06F4@amsl.com> <84D67BB2-D6A0-4CE6-827F-ABD130E7B512@episteme.net> <78286BEB-CC6E-43D4-A43F-79E2FA9C19E0@att.com> <CBDB7365-B362-4660-BEE4-C92D34BB2AAB@tzi.org> <CA+9kkMA1mm4=5RpO+iC1YJBWkcy5HZ6XQruOSC9WDvA26dcekQ@mail.gmail.com>
MIME-Version: 1.0
Subject: Re: [rfc-i] Includes for BCPs and STDs [Was: Making a v3 document manually]
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Cc: "HANSEN, TONY L" <tony@att.com>, rfc-interest@rfc-editor.org
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 19 Dec 2019, at 12:46, Ted Hardie wrote:

> On Wed, Dec 18, 2019 at 9:52 PM Carsten Bormann <cabo@tzi.org> wrote:
>
>> On Dec 19, 2019, at 06:06, HANSEN, TONY L <tony@att.com> wrote:
>>>
>>> Oh goody, a small programming task for my end-of-year vacation. :)
>>>
>>> Please peruse these directories and let me know what you think.
>>>
>>>     http://xml2rfc.tools.ietf.org/public/rfc/bibxml-test/	uses 
>>> xi:include
>>>     http://xml2rfc.tools.ietf.org/public/rfc/bibxml-test2/	expands 
>>> the references
>>>
>>> If either is acceptable, I'll turn them loose with a more permanent 
>>> reference name.

Either works for me; some folks obviously prefer the expanded reference 
version. Since the data for the RFCs themselves is static, I see no harm 
in going with the expanded version.

>>> What do you think of this as the permanent reference name?
>>>
>>>    http://xml2rfc.tools.ietf.org/public/rfc/bibxml-bcp-fyi-std

RFC 2026 refers to these as "subseries". Perhaps "bibxml-rfcsubseries"?

>> That would be the expanded form?
>>
>> I’d probably have separate directories for BCP and STD

Or that. There are few enough of them that a single directory is not 
unreasonable, but overall I'd say "implementer's choice."

>> (are we still doing FYIs?)
>
> The FYI subseries was closed by RFC 6360
> <https://tools.ietf.org/html/rfc6360>.

Which does say, "The FYI numbers continue to provide reference points 
for these documents, and the FYI number can be used in citations to 
these documents", so it's probably reasonable to have the entries for 
them.

pr
-- 
Pete Resnick https://www.episteme.net/
All connections to the world are tenuous at best
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest