Re: [xml2rfc] [irsg] UPDATE regarding <u> Re: AUTH48: RFC-to-be 9340 <draft-irtf-qirg-principles-11> for your review

Carsten Bormann <> Fri, 03 March 2023 22:14 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id C26CEC151AE2 for <>; Fri, 3 Mar 2023 14:14:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id BV8qSj6z4_Kv for <>; Fri, 3 Mar 2023 14:14:19 -0800 (PST)
Received: from ( []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 48CE2C151557 for <>; Fri, 3 Mar 2023 14:14:19 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPSA id 4PT2Lx5W2JzDCbm; Fri, 3 Mar 2023 23:14:17 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: Carsten Bormann <>
In-Reply-To: <20230303193126.BAAEAA3C41DE@ary.qy>
Date: Fri, 03 Mar 2023 23:14:11 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <20230303193126.BAAEAA3C41DE@ary.qy>
To: "John R. Levine" <>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <>
Subject: Re: [xml2rfc] [irsg] UPDATE regarding <u> Re: AUTH48: RFC-to-be 9340 <draft-irtf-qirg-principles-11> for your review
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: XML2RFC discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 03 Mar 2023 22:14:23 -0000

On 3. Mar 2023, at 20:31, John Levine <> wrote:
> Getting the fonts right is surprisingly tricky. If you look at the
> earler PDF RFCs, you'll see junk fonts SourceCodePro and
> TimesNewRomanPSMT which I think were installed on the machine used to
> make the PDFs so Weasyprint included them just in case.

Right.  That is a (rather pesky!) implementation problem that I was hoping we are already addressing.

Extracting the repertoire resulting from the fonts that we do want to have appears to me to be just a SMOP (small matter of programming).
Making the process explicit of expanding this repertoire is probably a sane way to handle the requirement for this process now that we have drawn it into the light.

Grüße, Carsten