Re: [websec] handling STS header field extendability

=JeffH <Jeff.Hodges@KingsMountain.com> Thu, 06 September 2012 23:38 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 D0DEE21F863B for <websec@ietfa.amsl.com>; Thu, 6 Sep 2012 16:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.495
X-Spam-Level:
X-Spam-Status: No, score=-100.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fYNA4urAvXr2 for <websec@ietfa.amsl.com>; Thu, 6 Sep 2012 16:38:29 -0700 (PDT)
Received: from oproxy7-pub.bluehost.com (oproxy7.bluehost.com [IPv6:2605:dc00:100:2::a7]) by ietfa.amsl.com (Postfix) with SMTP id 3480D21F8653 for <websec@ietf.org>; Thu, 6 Sep 2012 16:38:29 -0700 (PDT)
Received: (qmail 10227 invoked by uid 0); 6 Sep 2012 23:38:25 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy7.bluehost.com with SMTP; 6 Sep 2012 23:38:25 -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=Od1iREY9KveT5A8kmqBREM5KYuVHaBe/3fd9EOLGn0M=; b=acnRWagyKcasdqrKYcFjiC+6J9o50EygFdmyJFiZnDIffR9w4j73nFdpvfDBwZYfczc0el/lHjGVrS9wCeKzQT1Ius/czDZ9ml5gAu82yjqGg8a2Rx0q5wNPRfOxth9D;
Received: from [24.4.122.173] (port=57085 helo=[192.168.11.12]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1T9leT-0006hh-2F for websec@ietf.org; Thu, 06 Sep 2012 17:38:25 -0600
Message-ID: <504933EF.80602@KingsMountain.com>
Date: Thu, 06 Sep 2012 16:38:23 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: 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] handling STS header field extendability
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: Thu, 06 Sep 2012 23:38:29 -0000

Alexey replied:
 >
 > On 27/08/2012 21:18, Tobias Gondrom wrote:
 >> Hello dear websec fellows,
 >>
 >> <hat="WG chair">
 >> we have so far only very few comments regarding this. If you feel
 >> strongly either way, please say so ASAP, within the next 5 days (until
 >> Sep-1), otherwise we will have to go with the few comments we received
 >> to judge consensus based on them.
 >
 > <hat type="participant">
 >
 > I don't have strong feelings either way. I don't believe we have many
 > (if any at all) standardized extensions anyway.

yes, we don't have any imagined extensions on the table at this time. But given 
how we defined the ABNF, it's inherently extensible.

 > If people believe that there would be extensions,

I don't imagine any extensions at this time (as I've said before in this 
thread), however..

Ben Campbell's suggestion to select an IANA registry policy now is procedurally 
driven -- i.e., without specifying it now, someone could down the road create an 
independent-submission-stream I-D that extends the STS header, creates an IANA 
registry with a policy of their choice, and many of us might never notice


 > I have a slight
 > preference for picking an IANA policy now. Probably IETF review.

agreed.  I have already have the requisite language in -12..

    Additional directives extending the semantic functionality of the STS
    header field can be defined in other specifications, with a registry
    (having an IANA policy definition of FOO [RFC5226]) defined for them
    at such time.

..I just need to stick "IETF Review" in for FOO.

ok?

thanks,

=JeffH