Re: [apps-discuss] Content Types for Fonts?

Thomas Roessler <tlr@w3.org> Thu, 24 March 2011 20:02 UTC

Return-Path: <tlr@w3.org>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE7AD3A68C3 for <apps-discuss@core3.amsl.com>; Thu, 24 Mar 2011 13:02:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZuzxAFY6ACm for <apps-discuss@core3.amsl.com>; Thu, 24 Mar 2011 13:02:19 -0700 (PDT)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id B0F783A68BC for <apps-discuss@ietf.org>; Thu, 24 Mar 2011 13:02:19 -0700 (PDT)
Received: from [88.207.144.203] (helo=[192.168.2.114]) by jay.w3.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <tlr@w3.org>) id 1Q2ql6-0002Rb-NB; Thu, 24 Mar 2011 16:03:52 -0400
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Thomas Roessler <tlr@w3.org>
In-Reply-To: <4D8BA19A.2040606@gondrom.org>
Date: Thu, 24 Mar 2011 21:03:49 +0100
Content-Transfer-Encoding: 7bit
Message-Id: <18C87B21-16B2-44B7-89BD-6CC114352DC7@w3.org>
References: <4D8BA19A.2040606@gondrom.org>
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
X-Mailer: Apple Mail (2.1084)
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Content Types for Fonts?
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Mar 2011 20:02:21 -0000

Relevant here:
	http://www.w3.org/TR/WOFF/#appendix-b

Regards,
--
Thomas Roessler, W3C  <tlr@w3.org>  (@roessler)







On 24 Mar 2011, at 20:55, Tobias Gondrom wrote:

> Hello all,
> 
> maybe someone here can give some help/advice on this.
> At websec we have a draft on Mime type sniffing algorithms to improve on
> consistency of browser algorithms for mime type determination (and by
> thus improve security):
> http://www.ietf.org/id/draft-ietf-websec-mime-sniff-02.txt
> 
> Recently a comment came up with regard to identifying fonts (e.g.
> referenced in style sheets).
> AFAIK fonts don't have registered mime/content types, so browsers
> already just use sniffing algorithms for them.
> And without them having a registered content/mime type, it's kind of a
> flawed logic to add this to the draft for mime sniffing.
> 
> On the other hand it might make sense to add content types for fonts to
> the IANA registry?
> http://www.iana.org/assignments/media-types/index.html
> 
> Has that ever come up? Or are they already registered and I missed them?
> Or is this a bad idea?
> 
> Any opinions welcome...
> 
> BR, Tobias
> (websec chair)
> 
> _______________________________________________
> apps-discuss mailing list
> apps-discuss@ietf.org
> https://www.ietf.org/mailman/listinfo/apps-discuss
>