Re: [Tools-discuss] submit and IDNits issue with draft-ietf-avtcore-multi-party-rtt-mix-12

Carsten Bormann <> Thu, 11 February 2021 09:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1206C3A1420 for <>; Thu, 11 Feb 2021 01:55:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AIZBBf8l4JMp for <>; Thu, 11 Feb 2021 01:55:36 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 878693A141E for <>; Thu, 11 Feb 2021 01:55:36 -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 4DbsSk0MsTzybX; Thu, 11 Feb 2021 10:55:34 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Carsten Bormann <>
In-Reply-To: <>
Date: Thu, 11 Feb 2021 10:55:33 +0100
Cc: tools-discuss <>
X-Mao-Original-Outgoing-Id: 634730133.391813-e73c22c2fad4cba2aa2da9c01b7e494f
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <> <> <> <>
To: Gunnar Hellström <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Tools-discuss] submit and IDNits issue with draft-ietf-avtcore-multi-party-rtt-mix-12
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 11 Feb 2021 09:55:40 -0000

> Questions:

(My) Answers:

> 1. Can this problem be bypassed for now by just submitting the xml file including a reference to RFC 8865?


> 2. Will the submit tool be updated to allow non-ascii contents in txt files, so that others referencing e.g. RFC 8865 will not be stopped by errors in the submission?

(Don’t know.)

> 3. RFC 7997 recommends to let a non-ascii string be followed by a corresponding ascii string in parenthesis. That will look awkward for this case where the non-ascii is "Hellström" and the evident corresponding string is "Hellstrom". Should the author in RFC 8865 have been "Hellström (Hellstrom)" or is it up to the editor to assess the need for the explaining parenthesis?

The current state, as hinted at in
is that Latin script is generally allowed in the places where RFC 7991 uses the term ASCII, except in running text (a specification limitation that I hope will soon be addressed); and that non-Latin script requires an ASCII equivalent, so that if somebody is called “毛泽东” the reader gets to know that they could try to remember that name as “Mao Zedong”.

The ö in Hellström is Latin script, as are č and ć in the name Mališa Vučinić, so you can “read” that (even if you have no clue what the difference in pronunciation is going to be :-)

Grüße, Carsten