Re: [Gen-art] Gen-ART IETF Last Call review of draft-ietf-justfont-toplevel-03

"Chris Lilley" <> Thu, 08 December 2016 21:57 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3B160129A27; Thu, 8 Dec 2016 13:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 54xvA0I2Ydsk; Thu, 8 Dec 2016 13:57:27 -0800 (PST)
Received: from ( [IPv6:2001:470:8b2d:804:52:12:128:0]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7B3B0129A57; Thu, 8 Dec 2016 13:56:54 -0800 (PST)
Received: from ([]) by with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from <>) id 1cF6gP-0002zd-49; Thu, 08 Dec 2016 21:56:53 +0000
Content-Type: multipart/alternative; boundary="----=_NextPart_27557949.992505054546"
MIME-Version: 1.0
Date: Thu, 08 Dec 2016 16:56:46 -0500
Message-ID: <>
From: Chris Lilley <>
To: "Dale R. Worley" <>,,,
In-Reply-To: <>
References: <>
User-Agent: Mailbird/
Archived-At: <>
Subject: Re: [Gen-art] Gen-ART IETF Last Call review of draft-ietf-justfont-toplevel-03
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 08 Dec 2016 21:57:29 -0000

On 2016-10-30 18:18:29, Dale R. Worley <> wrote:

7.1. Generic SFNT font type

I can see why a comma-separated list is necessary, but that means that
"Values: TTF, CFF, SVG" is not strictly correct. Perhaps something
like the following (and let IANA figure out how to express that in

Values: a comma-separated subset of: TTF, CFF, SVG
Chris Lilley:
I adopted your suggested wording (and removed the optional whitespace).

Similarly for other parameters which can take a comma-separated list
of defined values.

Parameter definitions seem to need specification of registration
procedures. (See the sub-type-parameter registry mentioned above;
each parameter has a listed registration procedure.)
Chris Lilley: 

I had a look at the xml source of the MIME Media Type Sub-Parameter Registries:

and created a small XML file with updates for the two parameters (outlines and layout) defined in this draft.

The file is on GitHub as

and here is the commit.

Chris Lilley
Technical Director @ W3C
W3C Strategy Team, Core Web Design
W3C Architecture & Technology Team, Core Web & Media