Re: [Rfc-markdown] revising RFC8366 -- upgrade it for me?
Carsten Bormann <cabo@tzi.org> Sun, 04 July 2021 22:17 UTC
Return-Path: <cabo@tzi.org>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 4CBC63A24B0
for <rfc-markdown@ietfa.amsl.com>; Sun, 4 Jul 2021 15:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001,
SPF_HELO_NONE=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 AcgCLyJ3mJX0 for <rfc-markdown@ietfa.amsl.com>;
Sun, 4 Jul 2021 15:17:50 -0700 (PDT)
Received: from gabriel-2.zfn.uni-bremen.de (gabriel-2.zfn.uni-bremen.de
[134.102.50.19])
(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 21C0C3A24C2
for <rfc-markdown@ietf.org>; Sun, 4 Jul 2021 15:17:50 -0700 (PDT)
Received: from [192.168.217.118] (p548dcc89.dip0.t-ipconnect.de
[84.141.204.137])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by gabriel-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4GJ39632vcz2xGt;
Mon, 5 Jul 2021 00:17:46 +0200 (CEST)
Content-Type: text/plain;
charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5628.1625435754@localhost>
Date: Mon, 5 Jul 2021 00:17:46 +0200
Cc: rfc-markdown@ietf.org
X-Mao-Original-Outgoing-Id: 647129866.592864-7fe5038ba2efef2ee0de593c1ba57002
Content-Transfer-Encoding: quoted-printable
Message-Id: <22B32BA7-4BA8-4FBD-B3D8-1C7B21AD5319@tzi.org>
References: <20210625190512.GB30200@faui48e.informatik.uni-erlangen.de>
<5025.1624653668@localhost>
<20210625224810.GC30200@faui48e.informatik.uni-erlangen.de>
<AM7PR07MB6248F9002860D02203B1CC71A0039@AM7PR07MB6248.eurprd07.prod.outlook.com>
<20210628120924.xuuwnhnvz4jid7sp@anna.jacobs.jacobs-university.de>
<26783.1624896286@localhost>
<20210628161448.23zzsb2iazxgakmd@anna.jacobs.jacobs-university.de>
<5322.1624898378@localhost>
<20210628182043.krqzcflymazra52d@anna.jacobs.jacobs-university.de>
<22009.1625005448@localhost> <E5E503BE-67D2-4913-969B-A7E990866F13@tzi.org>
<5628.1625435754@localhost>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/ue2b7NJ4Y2Hcn_URIkYvBXi8t6A>
Subject: Re: [Rfc-markdown] revising RFC8366 -- upgrade it for me?
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs
in Markdown and the authors of the tools used for that."
<rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>,
<mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>,
<mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 04 Jul 2021 22:17:55 -0000
On 2021-07-04, at 23:55, Michael Richardson <mcr+ietf@sandelman.ca> wrote: > > Signed PGP part > > Carsten has just given me a Markdown version of RFC8366. > > I'm not sure if it's kdrfc or xml2rfc or... > but the datatracker.ietf.org/doc/html/rfcXXXX seems to be used rather than > rfc-editor.org/info/rfcXXXX. Is this a conscious choice somewhere? > > https://www.ietf.org/rfcdiff?url1=rfc8366&url2=https://www.sandelman.ca/tmp/draft-richardson-anima-rfc8366bis.txt > > (look at the normative references. I don't know how to encode that I want > html wdiff in the URL for rfcdiff, but that version is more obvious) The choice of URL prefix for target URIs in RFC and I-D references is a parameter to xml2rfc [1]. Kdrfc calls xml2rfc with default parameters here, which seem to yield what you are seeing, probably a bug: <https://www.ietf.org/archive/id/draft-... <https://www.rfc-editor.org/info/rfc... I could put in some parameter mangling, as Martin Thomson did for I-D-template (which calls xml2rfc by itself, with these parameters:) XML2RFC_RFC_BASE_URL := https://datatracker.ietf.org/doc/html/ XML2RFC_ID_BASE_URL := https://datatracker.ietf.org/doc/html/ xml2rfc ?= xml2rfc -q -s 'Setting consensus="true" for IETF STD document' --rfc-base-url $(XML2RFC_RFC_BASE_URL) --id-base-url $(XML2RFC_ID_BASE_URL) None of these is “right”. Which ones do you want? Grüße, Carsten [1]: https://xml2rfc.tools.ietf.org/xml2rfc-doc.html#name-html-format-options-2
- Re: [Rfc-markdown] revising RFC8366 -- upgrade it… Michael Richardson
- Re: [Rfc-markdown] revising RFC8366 -- upgrade it… Carsten Bormann
- Re: [Rfc-markdown] revising RFC8366 -- upgrade it… Michael Richardson