Re: Anything to discuss during our telcon tomorrow?

On 2016-12-14 13:07, Ned Holbrook wrote:
> I don’t have anything to discuss on the call.
>
> Two comments on the media type registration:
> 1. "Macintosh file type code(s)" are obsolete.
They are, and I asked on media-types@ietf.org why they were still listed 
in the registration template and if they should be removed. The answer 
seems to be "because older registrations have them". For the font top 
level type document, I just left these all as "(none specified)".

> 2. "Macintosh Universal Type Identifier code" would be more accurately 
> termed "Apple Universal Type Identifier".
Right, because these are also used on iOS?

Is it worth changing this in the draft?

The IESG is discussing it *today* and ballotting is already in progress,
https://datatracker.ietf.org/doc/draft-ietf-justfont-toplevel/ballot/

but I could make a small change still I think.

If you want to suggest the media type registration template be changed, 
then media-types@ietf.org would be the place 9and it would be good to 
have someone from Apple offer an opinion on that aspect).


>
>> On Dec 13, 2016, at 8:14 PM, Levantovsky, Vladimir 
>> <Vladimir.Levantovsky@monotype.com 
>> <mailto:Vladimir.Levantovsky@monotype.com>> wrote:
>>
>> Hello WG,
>> We have our regular time slot for WebEx call tomorrow at 1 pm PST / 4 
>> pm Eastern / 10 pm CET.
>> Are there any updates to discuss to discuss tomorrow? I will be 
>> traveling to NYC tomorrow arriving just in time for our telcon, but 
>> if we don’t have any updates on the remaining action items we might 
>> as well postpone the call until later. Considering the upcoming 
>> holidays, it would be practical to have the call tomorrow, before we 
>> enter the holiday season, but if we don’t have much to discuss we can 
>> push the telcon to the beginning of the next year (the first 
>> opportunity would be Wednesday, Jan. 4^th ).
>> What do you guys think?
>> On a related subject – there have been updates on the top-level font 
>> media type registration. Chris Lilley has been busy at work (thank 
>> you Chris!) addressing some of the issues reported by the 
>> IETF-assigned reviewer, and the new version of the document has been 
>> created as a result. Please review and send you comments, if any. The 
>> details on the document progression can be seen at 
>> https://datatracker.ietf.org/doc/draft-ietf-justfont-toplevel/
>> Thank you,
>> Vlad
>