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

"HANSEN, TONY L" <tony@att.com> Sun, 22 December 2019 02:14 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 C330112008B for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 21 Dec 2019 18:14:24 -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 qfiw6I8EgmKB for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Sat, 21 Dec 2019 18:14:22 -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 90E4E120072 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Sat, 21 Dec 2019 18:14:22 -0800 (PST)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 97614F406CB; Sat, 21 Dec 2019 18:14:22 -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 F14FEF406CB for <rfc-interest@rfc-editor.org>; Sat, 21 Dec 2019 18:14:21 -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 l1b-FRjh6vjq for <rfc-interest@rfc-editor.org>; Sat, 21 Dec 2019 18:14:18 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0a-00191d01.pphosted.com [67.231.149.140]) by rfc-editor.org (Postfix) with ESMTPS id 57DE8F406C6 for <rfc-interest@rfc-editor.org>; Sat, 21 Dec 2019 18:14:18 -0800 (PST)
Received: from pps.filterd (m0049295.ppops.net [127.0.0.1]) by m0049295.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id xBM27xAg004760; Sat, 21 Dec 2019 21:14:07 -0500
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049295.ppops.net-00191d01. with ESMTP id 2x1g85365a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 21 Dec 2019 21:14:07 -0500
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id xBM2E6sJ029453; Sat, 21 Dec 2019 21:14:06 -0500
Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [135.66.87.31]) by alpi155.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id xBM2E0ln029439 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sat, 21 Dec 2019 21:14:00 -0500
Received: from zlp27127.vci.att.com (zlp27127.vci.att.com [127.0.0.1]) by zlp27127.vci.att.com (Service) with ESMTP id 46B92400A012; Sun, 22 Dec 2019 02:14:00 +0000 (GMT)
Received: from MISOUT7MSGHUBAH.ITServices.sbc.com (unknown [130.9.129.152]) by zlp27127.vci.att.com (Service) with ESMTPS id 3245E400A011; Sun, 22 Dec 2019 02:14:00 +0000 (GMT)
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.138]) by MISOUT7MSGHUBAH.ITServices.sbc.com ([130.9.129.152]) with mapi id 14.03.0468.000; Sat, 21 Dec 2019 21:13:58 -0500
From: "HANSEN, TONY L" <tony@att.com>
To: Pete Resnick <resnick@episteme.net>
Thread-Topic: [rfc-i] Includes for BCPs and STDs [Was: Making a v3 document manually]
Thread-Index: AQHVtcYM4tABaWwSq02ZR4RhB/cWA6fA6LWAgABgYwCAANhvgIAABMyAgANJEAA=
Date: Sun, 22 Dec 2019 02:13:58 +0000
Message-ID: <D60DAB7B-66A8-4942-B3DE-93E6AA54D738@att.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> <7E9D0B45-7780-4BCF-BED6-327DB86E343A@episteme.net>
In-Reply-To: <7E9D0B45-7780-4BCF-BED6-327DB86E343A@episteme.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.9.133.199]
Content-ID: <9CB642876F66A846906B3555A146482A@LOCAL>
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-12-22_01:2019-12-17,2019-12-21 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 clxscore=1015 malwarescore=0 lowpriorityscore=0 mlxscore=0 suspectscore=0 impostorscore=0 mlxlogscore=999 spamscore=0 bulkscore=0 adultscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1912220016
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: "rfc-interest@rfc-editor.org" <rfc-interest@rfc-editor.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

On 12/19/19, 2:03 PM, "Pete Resnick" <resnick@episteme.net> wrote:

    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.
    >>> . . .
    >>> 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.

Given the discussion, and the small number of files, I decided to put them all into http://xml2rfc.tools.ietf.org/public/rfc/bibxml-rfcsubseries as suggested. The documentation at https://xml2rfc.tools.ietf.org/ has been updated as well.

They are the expanded versions of the files -- no xi:includes involved.

All three subseries are included: BCP, FYI and STD. The then-current rfc-index.xml file is checked hourly to see if any changes are needed.

Hope they are found useful. If any further tweaks are needed, please raise them on rfc-interest.

	Tony

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest