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

• From: Julian Reschke <julian.reschke@gmx.de>
• Date: Mon, 21 May 2018 09:16:31 +0200
• To: ietf-http-wg@w3.org
• Message-ID: <7a312f6b-0436-3834-460a-042c5d7489d2@gmx.de>

"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.

Given these points, I believe the simplest possible fix is to drop this 
section.

Best regards, Julian

Received on Monday, 21 May 2018 07:17:03 UTC