W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2018

Re: draft-ietf-httpbis-expect-ct-04, "2.3.2. HTTP-Equiv <meta> Element Attribute"

From: Emily Stark <estark@google.com>
Date: Mon, 21 May 2018 10:07:55 -0700
Message-ID: <CAPP_2SYKcQhUReWDHbREFvrooODvS3a1J=stJ0FRTSF2pVqR7A@mail.gmail.com>
To: julian.reschke@gmx.de
Cc: httpbis <ietf-http-wg@w3.org>
On Mon, May 21, 2018 at 12:27 AM Julian Reschke <julian.reschke@gmx.de>
wrote:

> "UAs MUST NOT heed http-equiv="Expect-CT" attribute settings on <meta>
> elements [HTML] [HTML5] in received content."
>
> Here be dragons.
>
> 1. HTML and HTML5 appear in a "MUST NOT" statement, yet are listed as
> informative references.
>
> 2. Even if they were normative references, we'd have to tell readers
> which one takes precedence (surprise: the description of http-equiv is
> indeed different in these two - see
> <https://www.w3.org/Bugs/Public/show_bug.cgi?id=18025>).
>
> 3. AFAIU, this spec *can't* make normative requirements on HTML
> consumers. That's what the HTML spec is for.
>
> 4. Finally, the HTML spec already says that "Expect-CT" is
> non-conforming and to be ignored.
>

Where is that? I don't see any mention of Expect-CT in either HTML.


>
> Given these points, I believe the simplest possible fix is to drop this
> section.
>
> Best regards, Julian
>
>
Received on Monday, 21 May 2018 17:08:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:21 UTC