IETF Logo Mail Archive

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

=JeffH <Jeff.Hodges@KingsMountain.com> Fri, 30 December 2011 01:02 UTC

Return-Path: <Jeff.Hodges@KingsMountain.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 CC1F51F0C4A for <websec@ietfa.amsl.com>; Thu, 29 Dec 2011 17:02:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.776
X-Spam-Level:
X-Spam-Status: No, score=-100.776 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
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 bDq4YIkVbzWl for <websec@ietfa.amsl.com>; Thu, 29 Dec 2011 17:02:13 -0800 (PST)
Received: from oproxy8-pub.bluehost.com (oproxy8-pub.bluehost.com [69.89.22.20]) by ietfa.amsl.com (Postfix) with SMTP id 35BBA21F8B44 for <websec@ietf.org>; Thu, 29 Dec 2011 17:02:13 -0800 (PST)
Received: (qmail 29048 invoked by uid 0); 30 Dec 2011 01:01:50 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy8.bluehost.com with SMTP; 30 Dec 2011 01:01:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=ZtkBPy1PwhTZwHOF+lvW0sR4xA7+CLc2rTsVJ5yj5d0=; b=ZRjtwmeM/J9pg7ptTg8IfCswvNvBcI+xQHcCFwCccPncPD2kYWP9GhMDhC2ENr2dhTps+2kAIR1dX3a1dVRBkSy0KMyc30OfCRryj3PCrtSm8oml5vCQbjrptzVgEXm0;
Received: from c-24-4-122-173.hsd1.ca.comcast.net ([24.4.122.173] helo=[192.168.11.18]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1RgQr0-0000oA-EW; Thu, 29 Dec 2011 18:01:50 -0700
Message-ID: <4EFD0D7D.7040908@KingsMountain.com>
Date: Thu, 29 Dec 2011 17:01:49 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111108 Thunderbird/3.1.16
MIME-Version: 1.0
To: Adam Barth <ietf@adambarth.com>, IETF WebSec WG <websec@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
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, 30 Dec 2011 01:02:13 -0000

Adam Barth noted:
 >
 > I would also define the precise requirements for parsing all possible
 > input sequences, but I understand that's not fashionable.

By that, you are suggesting specification of parsing algorithms as done in 
RFC6265 "HTTP State Management Mechanism", yes?

=JeffH

v2.23.0 | Report a Bug | By Email