Re: [websec] font sniffing

Adam Barth <ietf@adambarth.com> Wed, 09 November 2011 18:14 UTC

Return-Path: <ietf@adambarth.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7605811E8085 for <websec@ietfa.amsl.com>; Wed, 9 Nov 2011 10:14:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.56
X-Spam-Level:
X-Spam-Status: No, score=-2.56 tagged_above=-999 required=5 tests=[AWL=0.417, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6Fy8svqjYZ4B for <websec@ietfa.amsl.com>; Wed, 9 Nov 2011 10:14:34 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id DC4EF11E8083 for <websec@ietf.org>; Wed, 9 Nov 2011 10:14:33 -0800 (PST)
Received: by iaeo4 with SMTP id o4so2583859iae.31 for <websec@ietf.org>; Wed, 09 Nov 2011 10:14:33 -0800 (PST)
Received: by 10.42.158.9 with SMTP id f9mr4321443icx.31.1320862472663; Wed, 09 Nov 2011 10:14:32 -0800 (PST)
Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by mx.google.com with ESMTPS id dd36sm7797068ibb.7.2011.11.09.10.14.27 (version=SSLv3 cipher=OTHER); Wed, 09 Nov 2011 10:14:27 -0800 (PST)
Received: by iaeo4 with SMTP id o4so2583716iae.31 for <websec@ietf.org>; Wed, 09 Nov 2011 10:14:27 -0800 (PST)
Received: by 10.231.73.196 with SMTP id r4mr1014110ibj.19.1320862467097; Wed, 09 Nov 2011 10:14:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.231.50.14 with HTTP; Wed, 9 Nov 2011 10:13:56 -0800 (PST)
In-Reply-To: <4EBABAEC.6000907@stpeter.im>
References: <CAJE5ia82hhiyQHboBg5cWLe_=VdSZ1pFgFi0_TiiwgJKxKesfw@mail.gmail.com> <C68CB012D9182D408CED7B884F441D4D0605EFA3B4@nambxv01a.corp.adobe.com> <4EA4D8B8.7010108@gondrom.org> <op.v3umd8p264w2qv@annevk-macbookpro.local> <4EA52C49.1090308@gondrom.org> <op.v3umz3sv64w2qv@annevk-macbookpro.local> <4EA6143D.8060009@it.aoyama.ac.jp> <op.v3vysenw64w2qv@annevk-macbookpro.local> <4EA65768.60205@it.aoyama.ac.jp> <4EA65A59.6010005@gondrom.org> <4EBAB866.2020209@stpeter.im> <CAJE5ia9sU+g6WZC4wb5MEFCqb=TceaFD2yLMXe3f1e5T=h=VSA@mail.gmail.com> <4EBABAEC.6000907@stpeter.im>
From: Adam Barth <ietf@adambarth.com>
Date: Wed, 09 Nov 2011 10:13:56 -0800
Message-ID: <CAJE5ia8QFi=kXwRbAQyTTqst6bXgaUKu8VpWV9RcQGgvJ9=vOA@mail.gmail.com>
To: Peter Saint-Andre <stpeter@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: websec@ietf.org
Subject: Re: [websec] font sniffing
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Nov 2011 18:14:34 -0000

On Wed, Nov 9, 2011 at 9:39 AM, Peter Saint-Andre <stpeter@stpeter.im> wrote:
> On 11/9/11 10:30 AM, Adam Barth wrote:
>>
>> On Wed, Nov 9, 2011 at 9:29 AM, Peter Saint-Andre<stpeter@stpeter.im>
>>  wrote:
>>>
>>> On 10/25/11 12:42 AM, Tobias Gondrom wrote:
>>>>
>>>> On 25/10/11 07:30, "Martin J. Dürst" wrote:
>>>>>
>>>>> On 2011/10/25 11:34, Anne van Kesteren wrote:
>>>>>>
>>>>>> On Tue, 25 Oct 2011 10:43:25 +0900, Martin J. Dürst
>>>>>> <duerst@it.aoyama.ac.jp>  wrote:
>>>>>>>>
>>>>>>>> But who is at fault is not what we are interested in here I think.
>>>>>>>> We
>>>>>>>> are interested in defining when implementations have to sniff. They
>>>>>>>> very
>>>>>>>> much have to sniff for fonts.
>>>>>>>
>>>>>>> Yes. If somebody has enough energy, it would still make sense to
>>>>>>> register font types.
>>>>>>
>>>>>> Because..?
>>>>>
>>>>> - Font formats, as well as other Mime types, are not only used by Web
>>>>> browsers.
>>>>> - There may be new formats, for which no sniffing is done yet.
>>>>> - Servers may prefer to declare what they are sending out rather than
>>>>> to be silent about it, even if not all clients use that information.
>>>>> - Once we have registered types, sniffing could in the long term maybe
>>>>> even go away.
>>>>>
>>>>> Regards,   Martin.
>>>>
>>>> +1 for that.
>>>
>>> Based on discussion here and at the W3C TPAC last week, I raised this
>>> issue
>>> on the apps-discuss list:
>>>
>>> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg03447.html
>>>
>>> The immediate reaction was: "do you mean fonts or typefaces?"
>>>
>>> Before taking on this work, it would be helpful to understand exactly
>>> what
>>> typographic entities are being sent around by browsers and other
>>> applications.
>>
>> Mechanically, resource representations that might get shoved into
>> @font-face rules.
>
> Based on Anne's previous message to this list [1], it seems that we're
> actually talking about font representation formats (his examples are
> TrueType Collection, OpenType, TrueType, and Web Open Font Format) instead
> of particular fonts (e.g., "12pt Georgia Bold Italic") or typefaces (e.g.,
> "Georgia").
>
> Correct?

Yep.

Adam