Re: [websec] Strict-Transport-Security syntax redux

Adam Barth <ietf@adambarth.com> Fri, 28 October 2011 06:47 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 99F571F0C42 for <websec@ietfa.amsl.com>; Thu, 27 Oct 2011 23:47:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.325
X-Spam-Level:
X-Spam-Status: No, score=-2.325 tagged_above=-999 required=5 tests=[AWL=0.652, 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 tgggbwrNLLbJ for <websec@ietfa.amsl.com>; Thu, 27 Oct 2011 23:47:58 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 091671F0C54 for <websec@ietf.org>; Thu, 27 Oct 2011 23:47:57 -0700 (PDT)
Received: by gyh20 with SMTP id 20so4033173gyh.31 for <websec@ietf.org>; Thu, 27 Oct 2011 23:47:57 -0700 (PDT)
Received: by 10.101.65.12 with SMTP id s12mr213165ank.88.1319784477528; Thu, 27 Oct 2011 23:47:57 -0700 (PDT)
Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by mx.google.com with ESMTPS id z15sm22109868anl.15.2011.10.27.23.47.53 (version=SSLv3 cipher=OTHER); Thu, 27 Oct 2011 23:47:53 -0700 (PDT)
Received: by ywt2 with SMTP id 2so4014532ywt.31 for <websec@ietf.org>; Thu, 27 Oct 2011 23:47:53 -0700 (PDT)
Received: by 10.236.131.106 with SMTP id l70mr1410840yhi.29.1319784473386; Thu, 27 Oct 2011 23:47:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.236.103.37 with HTTP; Thu, 27 Oct 2011 23:47:22 -0700 (PDT)
In-Reply-To: <4EA99CFB.30801@KingsMountain.com>
References: <4EA99CFB.30801@KingsMountain.com>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 27 Oct 2011 23:47:22 -0700
Message-ID: <CAJE5ia9r=9FQGCV4ZLODJ=NigTxFBhg3Vj3K7gefCjy2FbWudw@mail.gmail.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF WebSec WG <websec@ietf.org>
Subject: Re: [websec] Strict-Transport-Security syntax redux
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: Fri, 28 Oct 2011 06:47:58 -0000

On Thu, Oct 27, 2011 at 11:03 AM, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
> I've been working with Julian on simplifying the STS header field syntax.
> Here's where it's presently at -- thoughts?
>
> thanks again to Julian and Ryan for their earlier feedback.
>
> =JeffH
>
>
> ###
>
> 5.1. Strict-Transport-Security HTTP Response Header Field
>
>   The Strict-Transport-Security HTTP response header field indicates to
>   a UA that it MUST enforce the HSTS Policy in regards to the host
>   emitting the response message containing this header field.
>
>   Note: this specification uses the augmented BNF (ABNF) notation from
>   Section 2 of [RFC2616], including its rules for "implied linear
>   whitespace (LWS)", and case-insensitivity of quoted-string literals.
>
>   The ABNF syntax for the Strict-Transport-Security (STS) HTTP Response
>   Header field is:
>
>
>    Strict-Transport-Security = "Strict-Transport-Security" ":"
>                                directive *( ";" [ directive ] )
>
>
>   STS directives:
>
>    directive         = max-age | includeSubDomains | STS-d-ext
>
>    max-age           = "max-age" "=" delta-seconds
>
>    includeSubDomains = "includeSubDomains"
>
>
>   The max-age directive MUST appear once in the Strict-Transport-Security
>   header field value. The includeSubDomains directive MAY appear once.
>   The order of appearance of directives in the Strict-Transport-Security
>   header field value is not significant.
>
>   Additional directives extending the the semantic functionality of
>   the Strict-Transport-Security header field may be defined in other

MAY or might ?

>   specifications, using the STS directive extension point (STS-d-ext)
>   syntax:
>
>    STS-d-ext     = token [ "=" ( token | quoted-string ) ]
>
>
>   Defined in [RFC2616]:
>
>    delta-seconds = <1*DIGIT, defined in [RFC2616], Section 3.3.2>
>    token         = <token, defined in [RFC2616], Section 2.2>
>    quoted-string = <quoted-string, defined in [RFC2616], Section 2.2>
>
>
> ###
>
>
>
> _______________________________________________
> websec mailing list
> websec@ietf.org
> https://www.ietf.org/mailman/listinfo/websec
>