Re: [Rfc-markdown] [xml2rfc] initials handling, was: New xml2rfc release: v2.22.3

Julian Reschke <> Thu, 11 April 2019 15:10 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 06ED712066D; Thu, 11 Apr 2019 08:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PtH450gLFEh8; Thu, 11 Apr 2019 08:10:50 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 892F81206BC; Thu, 11 Apr 2019 08:10:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=badeba3b8450; t=1554995446; bh=cBZtauIXTx4V33WA4UT1vSMjEwVOc+798+Txc25WJ5M=; h=X-UI-Sender-Class:Subject:To:Cc:References:From:Date:In-Reply-To; b=SGmAeAq1wkjwv6otc/xBU4uZduO9TpUNvGCP6V6+Qoh0E9QO7+ONsTn78EaS/G03N 1rw+DkSyoFKZF9hsVuHKD47xO2/l1UJSu/iHytwtnlscfMx+b05pb23hZ/jjqcxsDQ e9+iQHCGplhAnV4892lfbFB0N1jjH7TEVJmd9uG8=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from [] ([]) by (mrgmx001 []) with ESMTPSA (Nemesis) id 0MD9q8-1h6uld3gNQ-00Gcj6; Thu, 11 Apr 2019 17:10:45 +0200
To: Heather Flanagan <>
Cc: "" <>, "" <>, "" <>
References: <> <> <> <> <> <> <> <> <> <> <>
From: Julian Reschke <>
Message-ID: <>
Date: Thu, 11 Apr 2019 17:10:44 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
X-Provags-ID: V03:K1:WyrY1bUWDPLoi/MZLzRdFk9sP+jfTt9/DaYg+MRNgO1GWQ5BCSB hdvbopLAY5/XzLXlrREIXVRvUvmPOEf9e8eZPWp6BQuExMcTjz8Z9vaEEiwzhbFGJlOHtTs JXPm0aLyLEgMHpn96+v1W6keH4SN1UjKSNkQiLXRnt2kEsRgLIcc0WqkciIjWmxtEsjXAXa qOIPdiY8tNzjx22wzDeIA==
X-UI-Out-Filterresults: notjunk:1;V03:K0:trjc7gyZ2G8=:GchDk7Z9Pq+kZPSrEZfEq5 e4+4jedCzhdEpB6EU963/faRJbrLe5zjKsxGXosAFgfWvFJG4LJLJzddS0GJDKxrO5pLlFTiS 4+hZVClsIqsUD1FZ4brAu7Wg/T8BjOtx0s4MjNwC92R93BYfE+FXfQiB9R9ywHupZpuWW4kiD YZUO81vvEbMx+Pw/AccfKuYvvGB8bf0cJ/4/0UF6ZGjtqzPtlTbCqDSFE3V/GGo7OwzM9ZMBm 4416NcgNDz337KKtLBNF+oohvZBcBxC1DRAmHmSP13EifKEnNYhdZ7SdlWC+E0qCIfXFCN1Xn p3GG1wa+g52ZVhKCGYhcPl1gNTWZc485ZtJFbmQk6i7S0x7Ap8S7FhOKhhmEfhUuY94wnntMC 6A/63QE4XvlEVri+6qw73vGmuobwjgIB4+9ZGH7g55Vb/DYAodTMZ+8s+vK5iRptPidEjJ9un c5sc0QPx1mU6sWnhLEOHWhMJlXSPNQxwd2tdcnVt5M2AU8Cl+RNk1RFBKUJXX/hE8unNsC2o7 fmQssKNEcolDkF4fduFUxcSBNi1ZsHia/wOKlr2wteziNwy7C9W6giyoDeLfeY8oyUdPB1YH9 6NwjN1zgTaZRNF2zM03ba26JcK2dVHtY8MC+NOXtvd5asCfezr0k4pSNJ5FDtdlkD8/00mjad kbvhaOlfc0WsA6V8FefJsDqbHwlZ+cMXb2xXSP0BMyVyzGl1WR5RSmycdgaxWpFOlg9RIO61D fR3R8tuYM34tMZUTkeDnmAfm+7jyDzAqcPe3P0dM9MF6Y3K4WszX5GZ/VHBf7BrH3+P7ul0s7 h5qZXF1Fhq/jG8xHvYYfUi17skluOFN8ThliXyvAXLnRkjZtIkSyKf/1Usx43TcCucj1u1n75 8NPBG4H5FOTk0AnvGHymAHANG6DuUGtJqR2faMaKbPLi3H9+VNFbpHT5NFOFM7Q2dZEiYSkkY JCsjwbNVbQA==
Archived-At: <>
Subject: Re: [Rfc-markdown] [xml2rfc] initials handling, was: New xml2rfc release: v2.22.3
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." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Apr 2019 15:10:56 -0000

On 11.04.2019 17:06, Heather Flanagan wrote:
> ...
> And coming back to this:
> A longstanding principle for referencing RFCs is to make the reference
> match what is on the front page of the RFC itself, over what information
> is in any other location. This is something we should be clearer about
> in the Style Guide, but it is a practice we’ve enforced for quite a long
> time.
> Changing the tool to match this longstanding practice is not ideal, but
> it is expedient given that the proper way to handle this is an extensive
> data cleanup of the citation library. I’ve asked the RPC to prioritize
> getting documents published and format implementation over this kind of
> data cleanup for now.
> ...

FWIW, this indeed is *not* a change in the style, as far as I can tell.

Rather than that, it just highlights an inconsistency between the
published <reference> elements and the actual RFCs.

The fix IMHO is to fix the <reference> files when the problem shows up.

Putting extra logic into the formatter seems to be clearly the wrong

Best regards, Julian