[Tools-discuss] xml2rfc, and BCP references
Michael Richardson <mcr+ietf@sandelman.ca> Fri, 03 March 2017 17:36 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67CDD1294ED for <tools-discuss@ietfa.amsl.com>; Fri, 3 Mar 2017 09:36:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, 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 30ZX0bohA7_5 for <tools-discuss@ietfa.amsl.com>; Fri, 3 Mar 2017 09:36:36 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA949127735 for <tools-discuss@ietf.org>; Fri, 3 Mar 2017 09:36:36 -0800 (PST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 9C38F2055E for <tools-discuss@ietf.org>; Fri, 3 Mar 2017 12:59:00 -0500 (EST)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 6D3F5636BB for <tools-discuss@ietf.org>; Fri, 3 Mar 2017 12:36:35 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: tools-discuss <tools-discuss@ietf.org>
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 03 Mar 2017 12:36:35 -0500
Message-ID: <19529.1488562595@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/0kpN7DWCmvjFzo7LH08FE7jHIho>
Subject: [Tools-discuss] xml2rfc, and BCP references
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Mar 2017 17:36:38 -0000
I tried this today:
<?rfc include="reference.BCP.38" ?>
but there is no such file generated that I can find.
https://www.rfc-editor.org/info/bcp38 exists.
Shouldn't I be able to reference BCPs (and STDs) this way?
(And will the RFC-editor start hosting/providing the .xml files
for the references with links into the info/XXX pages?)
--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-
- [Tools-discuss] xml2rfc, and BCP references Michael Richardson
- Re: [Tools-discuss] xml2rfc, and BCP references Carsten Bormann