[websec] STS ABNF, was: new rev: draft-ietf-websec-strict-transport-sec-04

Julian Reschke <julian.reschke@gmx.de> Tue, 31 January 2012 20:40 UTC

Message-ID: <4F2851D1.5040505@gmx.de>
Date: Tue, 31 Jan 2012 21:40:49 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: =JeffH <Jeff.Hodges@KingsMountain.com>
References: <4F2347C5.8090406@KingsMountain.com>
In-Reply-To: <4F2347C5.8090406@KingsMountain.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: IETF WebSec WG <websec@ietf.org>
Subject: [websec] STS ABNF, was: new rev: draft-ietf-websec-strict-transport-sec-04
Precedence: list

On 2012-01-28 01:56, =JeffH wrote:
> ...

Hi Jeff,

thanks for the update.

The ABNF now is:

      Strict-Transport-Security = "Strict-Transport-Security" ":"
                                     directive *( ";" [ directive ] )


      directive                 = token [ "=" ( token | quoted-string ) ]

...and I think this is almost right.

It does allow empty directives (thus repeated or trailing semicolons), 
but not leading semicolons.

So

   STS: foo ;

parses, but

   STS: ; foo

does not. This could be fixed by saying:

      Strict-Transport-Security = "Strict-Transport-Security" ":"
                                  *( ";" [ directive ] )

I like the subsequent prose about the additional constraints.

For 6.1.1 and 6.1.2, we still need to decide whether a) quoted-string 
should be legal here (I understand that's 
<http://trac.tools.ietf.org/wg/websec/trac/ticket/33>), and if it was, 
b) how the syntax should be described.

Best regards, Julian

[websec] new rev: draft-ietf-websec-strict-transp… =JeffH
[websec] STS ABNF, was: new rev: draft-ietf-webse… Julian Reschke