From nobody Tue Sep 20 06:13:07 2016 Return-Path: X-Original-To: justfont@ietfa.amsl.com Delivered-To: justfont@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 227E712B150 for ; Tue, 20 Sep 2016 06:13:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.216 X-Spam-Level: X-Spam-Status: No, score=-4.216 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-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 bRF_zqBFDnAU for ; Tue, 20 Sep 2016 06:13:01 -0700 (PDT) Received: from raoul.w3.org (raoul.w3.org [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 ietfa.amsl.com (Postfix) with ESMTPS id 5560C12B1C2 for ; Tue, 20 Sep 2016 06:13:00 -0700 (PDT) Received: from [62.28.231.86] (helo=[10.10.14.107]) by raoul.w3.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1bmKr3-0004Kr-M0; Tue, 20 Sep 2016 13:12:58 +0000 References: To: =?UTF-8?Q?Martin_J._D=c3=bcrst?= , "justfont@ietf.org" From: Chris Lilley Organization: W3C X-Forwarded-Message-Id: Message-ID: Date: Tue, 20 Sep 2016 14:12:55 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/mixed; boundary="------------02FEB239EE6AC53247BE10FA" Archived-At: Subject: [Justfont] Fwd: Re: Working Group Last Call: draft-ietf-justfont-toplevel-02.txt X-BeenThere: justfont@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Font Top Level Media Type \(just font\) WG" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2016 13:13:06 -0000 This is a multi-part message in MIME format. --------------02FEB239EE6AC53247BE10FA Content-Type: multipart/alternative; boundary="------------E1C917CFC67D564A090C15C7" --------------E1C917CFC67D564A090C15C7 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Martin, Could you confirm that the edits made address your comments, or suggest further changes if they do not? -------- Forwarded Message -------- Subject: Re: [Justfont] Working Group Last Call: draft-ietf-justfont-toplevel-02.txt Date: Tue, 26 Jul 2016 10:42:54 -0400 From: Chris Lilley Organization: W3C To: Wendy Seltzer , justfont@ietf.org Hi Wendy On 2016-07-15 15:49, Wendy Seltzer wrote: > We seem to have stalled here, though we're very close. Can anyone poke > at the three open issues to suggest resolutions? > https://github.com/svgeesus/ietf-justfont/issues *Wording too tentative* https://github.com/svgeesus/ietf-justfont/issues/15 These were all in the "Background and Justification" section. The wording has been tightened up by ea46d07. As this was editorial and trivial, I closed the issue *Long sentences* https://github.com/svgeesus/ietf-justfont/issues/16 I marked this as editorial and am going through looking for overly long sentences. *Where are @font-face format identifiers defined?* https://github.com/svgeesus/ietf-justfont/issues/14 This is substantive. To-date, the authoritative definition has been the CSS 3 Fonts specification (and before that, the CSS 2.0 specification). Thus my initial thought was that this should continue. Martin asked whether new registrations should give that info too, and I agree that they should. I In that case, IANA would check for uniqueness (as they already do for subtype names) and the authoritative definition would be the registration itself (including the registrations included in the present document) and CSS 3 Fonts would update to state that the registrations are the official source, once the RFC was published. It still seems useful to have a list of @font-face formats, so they would stay in CSS 3 Fonts as an informative list. The W3C errata mechanism could be used in the event of new registrations after CSS 3 Fonts becomes a W3C Recommendation. I recalled seeing a registration template in earlier MIME specifications and went looking for it. I had planned to copy it into the present document, adding the @font-face format field. However, reading through RFC 6838 it seems that this has been replaced by an online form: http://www.iana.org/form/media-types I have added this as an informative reference in the IANA considerations section. I have started to add a section on 'New Registrations' which points to this form, and also references the ABNF of section /4.2. Naming Requirements/ of RFC 6838 . Should this document then state that it updates RFC 6838? How should we go about getting the online form updated to include the @font-face format to the "additional information" section of that form? Also, is that form the sole way to do new registrations or is there still a textual template somewhere which people can edit as a plain text email for ietf-types as was done previously? (Off topic, but it would also be good to know who to contact about updates to the form because it has a link to RFC 3013, which was obsoleted by RFC 7303; this should be corrected). > Chris, can you please review the open pull requests? > https://github.com/svgeesus/ietf-justfont/pulls Both reviewed and merged -- Chris Lilley @svgeesus Technical Director, W3C Interaction Domain --------------E1C917CFC67D564A090C15C7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Martin,

Could you confirm that the edits made address your comments, or suggest further changes if they do not?

-------- Forwarded Message --------
Subject: Re: [Justfont] Working Group Last Call: draft-ietf-justfont-toplevel-02.txt
Date: Tue, 26 Jul 2016 10:42:54 -0400
From: Chris Lilley <chris@w3.org>
Organization: W3C
To: Wendy Seltzer <wseltzer@w3.org>, justfont@ietf.org


Hi Wendy

On 2016-07-15 15:49, Wendy Seltzer wrote:
We seem to have stalled here, though we're very close. Can anyone poke
at the three open issues to suggest resolutions?
https://github.com/svgeesus/ietf-justfont/issues
Wording too tentative
https://github.com/svgeesus/ietf-justfont/issues/15

These were all in the "Background and Justification" section. The wording has been tightened up by
ea46d07. As this was editorial and trivial, I closed the issue

Long sentences
https://github.com/svgeesus/ietf-justfont/issues/16

I marked this as editorial and am going through looking for overly long sentences.

Where are @font-face format identifiers defined?
https://github.com/svgeesus/ietf-justfont/issues/14

This is substantive. To-date, the authoritative definition has been the CSS 3 Fonts specification (and before that, the CSS 2.0 specification). Thus my initial thought was that this should continue. Martin asked whether new registrations should give that info too, and I agree that they should. I

In that case, IANA would check for uniqueness (as they already do for subtype names) and the authoritative definition would be the registration itself (including the registrations included in the present document) and CSS 3 Fonts would update to state that the registrations are the official source, once the RFC was published.

It still seems useful to have a list of @font-face formats, so they would stay in CSS 3 Fonts as an informative list. The W3C errata mechanism could be used in the event of new registrations after CSS 3 Fonts becomes a W3C Recommendation.

I recalled seeing a registration template in earlier MIME specifications and went looking for it. I had planned to copy it into the present document, adding the @font-face format field. However, reading through RFC 6838 it seems that this has been replaced by an online form:
http://www.iana.org/form/media-types

I have added this as an informative reference in the IANA considerations section. I have started to add a section on 'New Registrations' which points to this form, and also references the ABNF of section 4.2. Naming Requirements of RFC 6838. Should this document then state that it updates RFC 6838? How should we go about getting the online form updated to include the @font-face format to the "additional information" section of that form?

Also, is that form the sole way to do new registrations or is there still a textual template somewhere which people can edit as a plain text email for ietf-types as was done previously?

(Off topic, but it would also be good to know who to contact about updates to the form because it has a link to RFC 3013, which was obsoleted by RFC 7303; this should be corrected).

 
Chris, can you please review the open pull requests?
https://github.com/svgeesus/ietf-justfont/pulls
Both reviewed and merged

-- 
Chris Lilley
@svgeesus
Technical Director, W3C Interaction Domain
--------------E1C917CFC67D564A090C15C7-- --------------02FEB239EE6AC53247BE10FA Content-Type: text/plain; charset=UTF-8; name="Attached Message Part" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Attached Message Part" X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkp1c3Rm b250IG1haWxpbmcgbGlzdA0KSnVzdGZvbnRAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYu b3JnL21haWxtYW4vbGlzdGluZm8vanVzdGZvbnQNCg0K --------------02FEB239EE6AC53247BE10FA-- From nobody Wed Sep 28 12:10:20 2016 Return-Path: X-Original-To: justfont@ietf.org Delivered-To: justfont@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FE6312B32B; Wed, 28 Sep 2016 12:10:19 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Meeting Session Request Tool\"" To: X-Test-IDTracker: no X-IETF-IDTracker: 6.34.1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <147508981902.16569.8395721026983853680.idtracker@ietfa.amsl.com> Date: Wed, 28 Sep 2016 12:10:19 -0700 Archived-At: Cc: justfont-chairs@ietf.org, justfont@ietf.org, wendy@seltzer.org, aamelnikov@fastmail.fm Subject: [Justfont] justfont - Not having a session at IETF 97 X-BeenThere: justfont@ietf.org X-Mailman-Version: 2.1.17 List-Id: "Font Top Level Media Type \(just font\) WG" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Sep 2016 19:10:19 -0000 Wendy Seltzer, a chair of the justfont working group, indicated that the justfont working group does not plan to hold a session at IETF 97. This message was generated and sent by the IETF Meeting Session Request Tool.