Re: [websec] of quoted-string header field param value syntax (was: Strict-Transport-Security syntax redux)

Julian Reschke <julian.reschke@gmx.de> Mon, 16 January 2012 12:22 UTC

Return-Path: <julian.reschke@gmx.de>
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 548E621F85AA for <websec@ietfa.amsl.com>; Mon, 16 Jan 2012 04:22:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.328
X-Spam-Level:
X-Spam-Status: No, score=-103.328 tagged_above=-999 required=5 tests=[AWL=-1.329, BAYES_00=-2.599, J_CHICKENPOX_41=0.6, 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 SqO-xK7tjvBC for <websec@ietfa.amsl.com>; Mon, 16 Jan 2012 04:22:13 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 7808F21F85A8 for <websec@ietf.org>; Mon, 16 Jan 2012 04:22:12 -0800 (PST)
Received: (qmail invoked by alias); 16 Jan 2012 12:22:09 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp014) with SMTP; 16 Jan 2012 13:22:09 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/gbahsxAHgxZ3AyitvhTi5InDWJfVWAoI0GF9D6E xhPJ81TT+AvYSA
Message-ID: <4F14166A.4090102@gmx.de>
Date: Mon, 16 Jan 2012 13:22:02 +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: "Manger, James H" <James.H.Manger@team.telstra.com>
References: <587AC02A-BB93-4260-BBEC-EBB649440F4E@team.telstra.com>
In-Reply-To: <587AC02A-BB93-4260-BBEC-EBB649440F4E@team.telstra.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: "websec@ietf.org" <websec@ietf.org>
Subject: Re: [websec] of quoted-string header field param value syntax (was: 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: Mon, 16 Jan 2012 12:22:13 -0000

On 2012-01-16 12:43, Manger, James H wrote:
>> agreed. that's why I'm leaning towards spec'g it with quoted-string at this time. It future-proofs the spec
>
> Quoted-string provides no "future-proofing".<token>  supports about 77 chars;<quoted-string>  adds about 18 more -- there are another 100,000 chars to support (and even more code points) if you actually want future- proofing.
>
> Supporting quoted-string is all about past compromises. It adds no value to a new header.

Well, it allows putting in ASCII characters not allowed otherwise, such 
as whitespace and delimiters such as ";", "," and double quotes.

I agree it doesn't help with I18N.

 > ...

Best regards, Julian