
From stpeter@stpeter.im  Wed Sep  1 15:30:12 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C3E43A6964 for <hasmat@core3.amsl.com>; Wed,  1 Sep 2010 15:30:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ixKGKxRXgBad for <hasmat@core3.amsl.com>; Wed,  1 Sep 2010 15:30:10 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 4D02D3A6849 for <hasmat@ietf.org>; Wed,  1 Sep 2010 15:30:10 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id C9E66400EE for <hasmat@ietf.org>; Wed,  1 Sep 2010 16:33:41 -0600 (MDT)
Message-ID: <4C7ED40F.9040106@stpeter.im>
Date: Wed, 01 Sep 2010 16:30:39 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: hasmat@ietf.org
References: <4C6EC48A.5020803@stpeter.im> <4C725267.3010908@kuix.de>	<4C729F21.3020900@gondrom.org> <4C72A195.4050507@extendedsubset.com>
In-Reply-To: <4C72A195.4050507@extendedsubset.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [HASMAT] moving forward - WG name
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 22:30:12 -0000

On 8/23/10 10:28 AM, Marsh Ray wrote:

> Personally, I think the current name is pretty awesome.

Thanks -- generation of catchy acronyms is one of my core competencies.
Some would say it's the only one. ;-)

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stpeter@stpeter.im  Wed Sep  1 15:38:55 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D61503A69D3 for <hasmat@core3.amsl.com>; Wed,  1 Sep 2010 15:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PiP1pph3qrso for <hasmat@core3.amsl.com>; Wed,  1 Sep 2010 15:38:54 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 177443A6964 for <hasmat@ietf.org>; Wed,  1 Sep 2010 15:38:51 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B8072400EE; Wed,  1 Sep 2010 16:41:53 -0600 (MDT)
Message-ID: <4C7ED5F9.30103@stpeter.im>
Date: Wed, 01 Sep 2010 16:38:49 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: Brandon Sterne <bsterne@mozilla.com>
References: <4C6EC48A.5020803@stpeter.im> <4C7D6949.5040401@mozilla.com>
In-Reply-To: <4C7D6949.5040401@mozilla.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: hasmat@ietf.org
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 22:38:56 -0000

On 8/31/10 2:42 PM, Brandon Sterne wrote:
> On 08/20/2010 11:08 AM, Peter Saint-Andre wrote:
>> Following up on the successful BoF we held in Maastricht, I'd like to
>> keep us moving toward formation of a working group. Here are some open
>> tasks:
> 
> Thanks, Peter, for keeping the ball rolling here.
> 
>> 2. Charter. We had some feedback at the BoF about charter revisions,
>> especially focusing on the three drafts under immediate consideration
>> and removing the text about developing a long-term framework for web
>> security.
> 
> Not being present at the BoF, I missed the discussion about removing the
> creation of a long-term security framework. 

A recording can be found here:

http://www.ietf.org/proceedings/78/

> If the group focuses on
> standardizing a small set of security mechanisms won't it be
> contributing to the "sprinkling" problem in the first part of the
> Objectives and Scope section?

Sort of. :)

As I recall, the objection was that we were making big promises and not
delivering, so either don't make big promises or else deliver mainly on
the big promises (but that's a large task and one that's not yet well
defined, thus perhaps leading the IESG to worry about scope creep).

>> 3. Name. Some people have said that "HASMAT" isn't very descriptive of
>> the subject matter, and that we might want something like "WEBSEC". As
>> long as folks don't think "WEBSEC" means that we'd be working on
>> everything under the sun related to the security of the web, I'd be fine
>> with a name like that. Other suggestions are welcome.
> 
> Personally, I do think WEBAPPSEC is the right name.  Someone pointed out
> that webappsec.org is registered already, but that space is occupied by
> the Web Application Security Consortium who generally go by the acronym
> WASC.  Other than the domain issue, is this still a problem?

The Secretariat strongly prefers (close to mandates) acronyms that are
at most 8 characters. Database and other tooling issues ensure if we try
to use longer acronyms.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stpeter@stpeter.im  Wed Sep  1 15:40:48 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E1F33A6855 for <hasmat@core3.amsl.com>; Wed,  1 Sep 2010 15:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mlfK97FNhLxV for <hasmat@core3.amsl.com>; Wed,  1 Sep 2010 15:40:46 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 1C3DB3A69C1 for <hasmat@ietf.org>; Wed,  1 Sep 2010 15:40:24 -0700 (PDT)
Received: from leavealone.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A085D400EE for <hasmat@ietf.org>; Wed,  1 Sep 2010 16:43:43 -0600 (MDT)
Message-ID: <4C7ED669.8090502@stpeter.im>
Date: Wed, 01 Sep 2010 16:40:41 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: hasmat@ietf.org
References: <4C745837.50104@KingsMountain.com> <AANLkTimGKP0SPzVojTrTSxPE0BjRbzR8uetr1Q_Y50Ji@mail.gmail.com>
In-Reply-To: <AANLkTimGKP0SPzVojTrTSxPE0BjRbzR8uetr1Q_Y50Ji@mail.gmail.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 01 Sep 2010 22:40:48 -0000

On 8/24/10 7:17 PM, Barry Leiba wrote:
> As I've said to Jeff back in Pays-Bas, I'm less concerned about the
> name than about the charter.  The problem description at the BoF said
> that a main issue is that this stuff has been previously dealt with in
> a haphazard manner.  We then looked at three haphazard drafts, which
> the charter proposes to standardize.  This doesn't address the core
> problem.
> 
> What does address the core problem is the part about studying the
> problem space.  From one of the proposed charters:
> 
>> In addition, this working group will consider the overall topic of HTTP
>> application security and compose a "problem statement and requirements"
>> document that can be used to guide further work.
> 
> I'd like to see much more emphasis placed on this part, and have the
> scope of this hashed out a bit more.  I think the focus of the WG
> should be on this, with the three existing drafts as something we do
> along the way... rather than the other way 'round, as it is now.

That is indeed the larger and more important goal, so I agree that its
well worth spending more of our time up front on a clear and
comprehensive problem statement that can drive our future work.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From tobias.gondrom@gondrom.org  Thu Sep  2 11:06:56 2010
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2DC53A6BF4 for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 11:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.805
X-Spam-Level: 
X-Spam-Status: No, score=-94.805 tagged_above=-999 required=5 tests=[AWL=0.557, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XsLdu5t9IiNj for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 11:06:49 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (lvps83-169-7-107.dedicated.hosteurope.de [83.169.7.107]) by core3.amsl.com (Postfix) with ESMTP id 2B5B03A6C25 for <hasmat@ietf.org>; Thu,  2 Sep 2010 10:52:27 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=s2r0C1z+9r2Cpqc7Y+eznwLQ2Zihk3hZazlAJRHUd7ySRik50v1JxJ/T0WmLuov4bgv2+/GF3clkUJ8eZk5yOmYENOwtF2/ziwSTmKr0UZNx13Izuizo2J38uJP3TGVb; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 20214 invoked from network); 2 Sep 2010 19:26:10 +0200
Received: from 94-194-102-93.zone8.bethere.co.uk (HELO seraphim.heaven) (94.194.102.93) by lvps83-169-7-107.dedicated.hosteurope.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Sep 2010 19:26:10 +0200
Message-ID: <4C7FDE3A.6050100@gondrom.org>
Date: Thu, 02 Sep 2010 18:26:18 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100802 SUSE/3.1.2 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: hasmat@ietf.org, bsterne@mozilla.com
References: <4C6EC48A.5020803@stpeter.im> <4C7D6949.5040401@mozilla.com> <4C7ED5F9.30103@stpeter.im>
In-Reply-To: <4C7ED5F9.30103@stpeter.im>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 18:06:56 -0000

 On 09/01/2010 11:38 PM, Peter Saint-Andre wrote:
> On 8/31/10 2:42 PM, Brandon Sterne wrote:
>> On 08/20/2010 11:08 AM, Peter Saint-Andre wrote:
>>> 3. Name. Some people have said that "HASMAT" isn't very descriptive of
>>> the subject matter, and that we might want something like "WEBSEC". As
>>> long as folks don't think "WEBSEC" means that we'd be working on
>>> everything under the sun related to the security of the web, I'd be fine
>>> with a name like that. Other suggestions are welcome.
>> Personally, I do think WEBAPPSEC is the right name.  Someone pointed out
>> that webappsec.org is registered already, but that space is occupied by
>> the Web Application Security Consortium who generally go by the acronym
>> WASC.  Other than the domain issue, is this still a problem?
> The Secretariat strongly prefers (close to mandates) acronyms that are
> at most 8 characters. Database and other tooling issues ensure if we try
> to use longer acronyms.
>
> Peter
@Brandon: I agree with Peter on the length of the WG name. (after all
its a technical short name, the WG scope is defined in the charter). So
far a couple of people suggested websec, which would be very close to
your proposal.
May I ask, how do you think about that name? Do you see strong reasons
against it compared to webappsec?

Greetings, Tobias


From bsterne@mozilla.com  Thu Sep  2 12:04:56 2010
Return-Path: <bsterne@mozilla.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B7093A6927 for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 12:04:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0+KwPm1exLMT for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 12:04:55 -0700 (PDT)
Received: from dm-mail02.mozilla.org (dm-mail02.mozilla.org [63.245.208.176]) by core3.amsl.com (Postfix) with ESMTP id ECB0F3A685E for <hasmat@ietf.org>; Thu,  2 Sep 2010 12:04:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at mozilla.org
Received: from [10.250.1.47] (v74-nslb.mozilla.org [10.2.74.4]) (Authenticated sender: bsterne@mozilla.com) by dm-mail02.mozilla.org (Postfix) with ESMTP id 378D88240C8; Thu,  2 Sep 2010 12:05:14 -0700 (PDT)
Message-ID: <4C7FF667.7000406@mozilla.com>
Date: Thu, 02 Sep 2010 12:09:27 -0700
From: Brandon Sterne <bsterne@mozilla.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3
MIME-Version: 1.0
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
References: <4C6EC48A.5020803@stpeter.im> <4C7D6949.5040401@mozilla.com> <4C7ED5F9.30103@stpeter.im> <4C7FDE3A.6050100@gondrom.org>
In-Reply-To: <4C7FDE3A.6050100@gondrom.org>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: hasmat@ietf.org
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 19:04:56 -0000

 On 09/02/2010 10:26 AM, Tobias Gondrom wrote:
> @Brandon: I agree with Peter on the length of the WG name. (after all
> its a technical short name, the WG scope is defined in the charter). So
> far a couple of people suggested websec, which would be very close to
> your proposal.
> May I ask, how do you think about that name? Do you see strong reasons
> against it compared to webappsec?
>
> Greetings, Tobias
>
I, personally, can live with "WEBSEC" and was unaware of the name length
constraints.  Mnot's "HTTPSEC" isn't bad either.

-Brandon

From stpeter@stpeter.im  Thu Sep  2 12:10:53 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0B5963A6962 for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 12:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.553
X-Spam-Level: 
X-Spam-Status: No, score=-102.553 tagged_above=-999 required=5 tests=[AWL=0.046, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QPUOADzZnYKP for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 12:10:51 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id D340B3A6886 for <hasmat@ietf.org>; Thu,  2 Sep 2010 12:10:51 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7986840074 for <hasmat@ietf.org>; Thu,  2 Sep 2010 13:14:27 -0600 (MDT)
Message-ID: <4C7FF6D7.8050202@stpeter.im>
Date: Thu, 02 Sep 2010 13:11:19 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: hasmat@ietf.org
References: <4C6EC48A.5020803@stpeter.im> <4C7D6949.5040401@mozilla.com>	<4C7ED5F9.30103@stpeter.im> <4C7FDE3A.6050100@gondrom.org> <4C7FF667.7000406@mozilla.com>
In-Reply-To: <4C7FF667.7000406@mozilla.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 19:10:53 -0000

On 9/2/10 1:09 PM, Brandon Sterne wrote:
>  On 09/02/2010 10:26 AM, Tobias Gondrom wrote:
>> @Brandon: I agree with Peter on the length of the WG name. (after all
>> its a technical short name, the WG scope is defined in the charter). So
>> far a couple of people suggested websec, which would be very close to
>> your proposal.
>> May I ask, how do you think about that name? Do you see strong reasons
>> against it compared to webappsec?
>>
>> Greetings, Tobias
>>
> I, personally, can live with "WEBSEC" and was unaware of the name length
> constraints.  Mnot's "HTTPSEC" isn't bad either.

Naming matters because folks might expect that the work could expand to
fill the space allotted. Might this group someday (after other work is
completed and after rechartering etc.) be interested in all things HTTP
security, e.g., proposals for new authentication methods? The "HTTPSEC"
and "WEBSEC" names are fairly broad.

In any case, more pressing is the issue Barry brought about getting the
charter right, especially with respect to the framework objectives.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From stpeter@stpeter.im  Thu Sep  2 12:16:31 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8A1913A6886 for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 12:16:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.556
X-Spam-Level: 
X-Spam-Status: No, score=-102.556 tagged_above=-999 required=5 tests=[AWL=0.043, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jF3KW9Y8Y2Ph for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 12:16:22 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 391BC3A6826 for <hasmat@ietf.org>; Thu,  2 Sep 2010 12:16:20 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 442B440074; Thu,  2 Sep 2010 13:19:56 -0600 (MDT)
Message-ID: <4C7FF821.2060002@stpeter.im>
Date: Thu, 02 Sep 2010 13:16:49 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: Kai Engert <kaie@kuix.de>
References: <4C6EC48A.5020803@stpeter.im> <4C725267.3010908@kuix.de>
In-Reply-To: <4C725267.3010908@kuix.de>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: hasmat@ietf.org
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 19:16:31 -0000

On 8/23/10 4:50 AM, Kai Engert wrote:
>  On 20.08.2010 20:08, Peter Saint-Andre wrote:
>> 3. Name. Some people have said that "HASMAT" isn't very descriptive of
>> the subject matter, and that we might want something like "WEBSEC". As
>> long as folks don't think "WEBSEC" means that we'd be working on
>> everything under the sun related to the security of the web, I'd be fine
>> with a name like that. Other suggestions are welcome.
> 
> "websec" sounds indeed very general, while the meaning of "hasmat"
> focuses on a smaller subset.
> 
> I wanted to propose "WebAppSec", but there's already
> http://www.webappsec.org/

That's a good group to reach out to. :) Is anyone here involved with
those folks? Are there other such groups to be aware of?

> What about HTSEC ? (hypertext security)

It's easier to pronounce than "HTTPSEC", that's for sure.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From asteingruebl@paypal-inc.com  Thu Sep  2 12:37:27 2010
Return-Path: <asteingruebl@paypal-inc.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7CAC63A68F1 for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 12:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.117
X-Spam-Level: 
X-Spam-Status: No, score=-5.117 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Alj2ElM2dv8Q for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 12:37:01 -0700 (PDT)
Received: from den-mipot-001.corp.ebay.com (den-mipot-001.corp.ebay.com [216.113.175.152]) by core3.amsl.com (Postfix) with ESMTP id 6A57B3A6781 for <hasmat@ietf.org>; Thu,  2 Sep 2010 12:37:00 -0700 (PDT)
DomainKey-Signature: s=ppinc; d=paypal-inc.com; c=nofws; q=dns; h=X-EBay-Corp:X-IronPort-AV:Received:Received:From:To:CC: Date:Subject:Thread-Topic:Thread-Index:Message-ID: References:In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage: Content-Type:Content-Transfer-Encoding:MIME-Version: X-CFilter; b=UVpQQAwPKc8ppQPQLvpHcRjz+anfQZxWiclrXrdFp7UZI53CEwttOWcl GzLCVolGQ3vgyUw5phMpRtjbR20VfF5qWpGPF/yiaR0UI2TnhaRAor9sB LCHQiEvPL8fAnHG;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=paypal-inc.com; i=asteingruebl@paypal-inc.com; q=dns/txt; s=ppinc; t=1283456251; x=1314992251; h=from:to:cc:date:subject:message-id:references: in-reply-to:content-transfer-encoding:mime-version; z=From:=20"Steingruebl,=20Andy"=20<asteingruebl@paypal-inc .com>|To:=20Peter=20Saint-Andre=20<stpeter@stpeter.im>, =20Kai=20Engert=20<kaie@kuix.de>|CC:=20"hasmat@ietf.org" =20<hasmat@ietf.org>|Date:=20Thu,=202=20Sep=202010=2013:3 7:28=20-0600|Subject:=20RE:=20[HASMAT]=20moving=20forward |Message-ID:=20<5EE049BA3C6538409BBE6F1760F328ABEAF281DEA D@DEN-MEXMS-001.corp.ebay.com>|References:=20<4C6EC48A.50 20803@stpeter.im>=20<4C725267.3010908@kuix.de>=0D=0A=20<4 C7FF821.2060002@stpeter.im>|In-Reply-To:=20<4C7FF821.2060 002@stpeter.im>|Content-Transfer-Encoding:=20quoted-print able|MIME-Version:=201.0; bh=Ocy9sFjWuhD2qaUcMzxRgj6kM+UfkunyQiJopIEouTw=; b=pMO7JLywCn0chguaLMyB24BOzf7xxEYkG5XFimsLaU+CgPpEAsFCk7ev Zc4hwtWXNlvUDCDFsF1co8QoV9TCi1fmjrwo6/+5WaEIkuWOfmeiB5vyU 0nx2jPdYpe2YyFQ;
X-EBay-Corp: Yes
X-IronPort-AV: E=Sophos;i="4.56,309,1280732400"; d="scan'208";a="71986199"
Received: from den-vtenf-002.corp.ebay.com (HELO DEN-MEXHT-002.corp.ebay.com) ([10.101.112.213]) by den-mipot-001.corp.ebay.com with ESMTP; 02 Sep 2010 12:37:30 -0700
Received: from DEN-MEXMS-001.corp.ebay.com ([10.241.16.225]) by DEN-MEXHT-002.corp.ebay.com ([10.241.17.53]) with mapi; Thu, 2 Sep 2010 13:37:29 -0600
From: "Steingruebl, Andy" <asteingruebl@paypal-inc.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Kai Engert <kaie@kuix.de>
Date: Thu, 2 Sep 2010 13:37:28 -0600
Thread-Topic: [HASMAT] moving forward
Thread-Index: ActK03uRpiN5AF+bRAmE5C/H7PmlAwAApTHQ
Message-ID: <5EE049BA3C6538409BBE6F1760F328ABEAF281DEAD@DEN-MEXMS-001.corp.ebay.com>
References: <4C6EC48A.5020803@stpeter.im> <4C725267.3010908@kuix.de> <4C7FF821.2060002@stpeter.im>
In-Reply-To: <4C7FF821.2060002@stpeter.im>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter: Scanned
Cc: "hasmat@ietf.org" <hasmat@ietf.org>
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 19:37:27 -0000

> -----Original Message-----
> From: hasmat-bounces@ietf.org [mailto:hasmat-bounces@ietf.org] On
> Behalf Of Peter Saint-Andre
> Sent: Thursday, September 02, 2010 12:17 PM
> To: Kai Engert
> Cc: hasmat@ietf.org
> Subject: Re: [HASMAT] moving forward
> >
> > I wanted to propose "WebAppSec", but there's already
> > http://www.webappsec.org/
>=20
> That's a good group to reach out to. :) Is anyone here involved with thos=
e
> folks? Are there other such groups to be aware of?

One of the Officers/Founders sits practically next to me.  I can definitely=
 check with the WASC folks if they are concerned about the name. =20


From robert@webappsec.org  Thu Sep  2 13:05:36 2010
Return-Path: <robert@webappsec.org>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A44583A68AB for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 13:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.863
X-Spam-Level: 
X-Spam-Status: No, score=0.863 tagged_above=-999 required=5 tests=[AWL=-1.300,  BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k0DuC-wfMEDo for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 13:05:35 -0700 (PDT)
Received: from cgisecurity.net (unknown [199.125.85.46]) by core3.amsl.com (Postfix) with SMTP id AD95A3A680B for <hasmat@ietf.org>; Thu,  2 Sep 2010 13:05:34 -0700 (PDT)
Received: (qmail 62613 invoked by uid 1016); 2 Sep 2010 21:00:48 -0000
Message-ID: <20100902210048.62612.qmail@cgisecurity.net>
From: robert@webappsec.org
To: hasmat@ietf.org
Date: Thu, 2 Sep 2010 17:00:48 -0400 (EDT)
X-Mailer: ELM [version 2.5 PL8]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: contact@webappsec.org
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 20:06:00 -0000

>>> -----Original Message-----
>>> From: hasmat-bounces@ietf.org [mailto:hasmat-bounces@ietf.org] On 
>>> Behalf Of Peter Saint-Andre
>>> Sent: Thursday, September 02, 2010 12:17 PM
>>> To: Kai Engert
>>> Cc: hasmat@ietf.org
>>> Subject: Re: [HASMAT] moving forward
>>>
>> > I wanted to propose "WebAppSec", but there's already 
>>> http://www.webappsec.org/
>> 
>> That's a good group to reach out to. :) Is anyone here involved with 
>> those folks? Are there other such groups to be aware of?
>
> One of the Officers/Founders sits practically next to me.  I can definitely check with the WASC folks if they 
> are concerned about the name.  

Hello Hasmat,
 
I am one of the cofounders of 'The Web Application Security Consortium' (http://www.webappsec.org/) and was recently
informed about this thread. Since this is a discussion about the name of your project it probably makes sense to pick 
something less generic; something that makes your unique cause stand out (for your benefit). As to what that name should be
I'm not going to step on anyone's toes as an outsider but I wanted to provide you with some common names/references
within the appsec space that you should be aware of. 

- OWASP (owasp.org): Open 'Web Application Security Project'
- WASC (webappsec.org): The Web Application Security Consortium
- Appsec: Used by SANS for a conference (http://www.sans.org/appsec-2010/) as well as owasp (http://appsecdc.org/)
- webappsec list: Securityfocus.com runs a mailing list called webappsec (http://www.securityfocus.com/archive/107/description)
- The Web Security Mailing List: run by WASC (http://www.webappsec.org/lists/websecurity/) also known as websecurity. 
  We were going to name it webappsec but didn't want to cause additional confusion :)

Feel free to ping me if you're debating related names and I can assist with letting you know if something
similar exists (I am well connected).

 
Regards,
- Robert Auger
WASC Co Founder/Moderator of The Web Security Mailing List
http://projects.webappsec.org/
http://www.cgisecurity.com/
http://www.qasec.com/


From Jeff.Hodges@KingsMountain.com  Thu Sep  2 15:17:56 2010
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C99C03A6967 for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 15:17:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.984
X-Spam-Level: 
X-Spam-Status: No, score=-101.984 tagged_above=-999 required=5 tests=[AWL=0.281, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5NYn2cUYmKFD for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 15:17:55 -0700 (PDT)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id B29F43A6874 for <hasmat@ietf.org>; Thu,  2 Sep 2010 15:17:55 -0700 (PDT)
Received: (qmail 9112 invoked by uid 0); 2 Sep 2010 22:18:25 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 2 Sep 2010 22:18:25 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=tt6/Il5CChdDb0ssLIk3aCk1+sZ3iru7v1W514tsjUkvb1utyPsKKMBSIfxYLmFO9is550NhXwPKC8mksDJE1xvWwwLSyYrgxahQ/IoEAk5cuZ5l9E70qdShN9O5728L;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.48.205]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1OrI6z-0007QD-9s for hasmat@ietf.org; Thu, 02 Sep 2010 16:18:25 -0600
Message-ID: <4C8022B0.9080102@KingsMountain.com>
Date: Thu, 02 Sep 2010 15:18:24 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: IETF HASMAT list <hasmat@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 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: Re: [HASMAT] moving forward - working group name
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 22:17:56 -0000

Brandon Sterne <bsterne@mozilla.com> noted:
 >
 > Personally, I do think WEBAPPSEC is the right name.  Someone pointed out
 > that webappsec.org is registered already, but that space is occupied by
 > the Web Application Security Consortium ...
 >  Other than the domain issue, is this still a problem?

I don't think this is a problem because we're talking about an IETF Working 
Group name here, where there usually isn't a stand-alone external domain name 
used in conjunction with it (tho it does occur sometimes).

That said, WebAppSec is 9 chars and that's a problem for various IETF tooling 
as previously noted (and I can attest to having messed around with "http-state" 
vs "httpstate").

as I said earlier (24-Aug)..

   ... we could use "websec" with the understanding (and explicitness in the
   charter) that it's "minus authn & transport".

   "websec" will [arguably] be easier for IETF newbies to find and grok
   than "hasmat".


=JeffH




From stpeter@stpeter.im  Thu Sep  2 15:20:24 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 263FB3A684C for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 15:20:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.559
X-Spam-Level: 
X-Spam-Status: No, score=-102.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xoCfOZNfj1ba for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 15:20:23 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 18AAF3A6784 for <hasmat@ietf.org>; Thu,  2 Sep 2010 15:20:23 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 7037340074; Thu,  2 Sep 2010 16:23:59 -0600 (MDT)
Message-ID: <4C802343.3090001@stpeter.im>
Date: Thu, 02 Sep 2010 16:20:51 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.11) Gecko/20100711 Thunderbird/3.0.6
MIME-Version: 1.0
To: "Steingruebl, Andy" <asteingruebl@paypal-inc.com>
References: <4C6EC48A.5020803@stpeter.im> <4C725267.3010908@kuix.de> <4C7FF821.2060002@stpeter.im> <5EE049BA3C6538409BBE6F1760F328ABEAF281DEAD@DEN-MEXMS-001.corp.ebay.com>
In-Reply-To: <5EE049BA3C6538409BBE6F1760F328ABEAF281DEAD@DEN-MEXMS-001.corp.ebay.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: "hasmat@ietf.org" <hasmat@ietf.org>
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 22:20:24 -0000

On 9/2/10 1:37 PM, Steingruebl, Andy wrote:
>> -----Original Message----- From: hasmat-bounces@ietf.org
>> [mailto:hasmat-bounces@ietf.org] On Behalf Of Peter Saint-Andre 
>> Sent: Thursday, September 02, 2010 12:17 PM To: Kai Engert Cc:
>> hasmat@ietf.org Subject: Re: [HASMAT] moving forward
>>> 
>>> I wanted to propose "WebAppSec", but there's already 
>>> http://www.webappsec.org/
>> 
>> That's a good group to reach out to. :) Is anyone here involved
>> with those folks? Are there other such groups to be aware of?
> 
> One of the Officers/Founders sits practically next to me.  I can
> definitely check with the WASC folks if they are concerned about the
> name.

I was less interested in the name and more interested in technical
input. :) The same would be true of the Open Web Application Security
Project (OWASP) and other similar groups.

However, we certainly don't want to stomp on names of existing groups...

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From Jeff.Hodges@KingsMountain.com  Thu Sep  2 15:39:10 2010
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A89023A67A5 for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 15:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.997
X-Spam-Level: 
X-Spam-Status: No, score=-101.997 tagged_above=-999 required=5 tests=[AWL=0.268, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6KqGEG4nGFBG for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 15:37:34 -0700 (PDT)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id C08583A6359 for <hasmat@ietf.org>; Thu,  2 Sep 2010 15:35:36 -0700 (PDT)
Received: (qmail 1890 invoked by uid 0); 2 Sep 2010 22:35:47 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 2 Sep 2010 22:35:47 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=FyXyUGF6Y8kiJ7N4zTaIwr/iMtb2cdAAtCnNPA6Hr1EBfINBni8P4kDr8ZQ9muX63iMjQdpMFMvs9PueTYSPgXw9p2pDDrQipW2EvzQGCeCL3ThxncZtYXb5lbHPuWuF;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.48.205]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1OrINn-0007F0-3D for hasmat@ietf.org; Thu, 02 Sep 2010 16:35:47 -0600
Message-ID: <4C8026C3.6020603@KingsMountain.com>
Date: Thu, 02 Sep 2010 15:35:47 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: IETF HASMAT list <hasmat@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 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: Re: [HASMAT] moving forward -
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 22:39:11 -0000

Brandon Sterne <bsterne@mozilla.com> observed..
 >
 > Not being present at the BoF, I missed the discussion about removing the
 > creation of a long-term security framework.

However, from one of the proposed versions of the charter..

 > In addition, this working group will consider the overall topic of HTTP
 > application security and compose a "problem statement and requirements"
 > document that can be used to guide further work.


Basically, we didn't so much "remove" the "creation of a long-term security 
framework" work item, but reduced scope at this time to deriving "problem 
statement(s) and requirements".  Then, based upon that work, we can either 
re-charter this WG or form a new one (not a ton of difference in those 
approaches) to actually address/fulfill said "problem statement(s) and 
requirements".

Breaking the scope/work up in this way helps keep things manageable and 
timeframes more realistic.

=JeffH


From tobias.gondrom@gondrom.org  Thu Sep  2 15:54:02 2010
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3E7C43A635F for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 15:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -94.842
X-Spam-Level: 
X-Spam-Status: No, score=-94.842 tagged_above=-999 required=5 tests=[AWL=0.520, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U-vdlJ0fhgbi for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 15:54:01 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (lvps83-169-7-107.dedicated.hosteurope.de [83.169.7.107]) by core3.amsl.com (Postfix) with ESMTP id 891BA3A6359 for <hasmat@ietf.org>; Thu,  2 Sep 2010 15:54:00 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=RIezZET0bpGA/Gzo1rf+L+2OHFR+hxvOs2R1fw8ROal6WjxSnAvhCdBajBBmztLKM0Nlx0qcYu2h7mmuJUIPbFTzF/6ft7PSxunpQOW9Au/cmZbhbysO7ajisUb6WO3d; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 18425 invoked from network); 3 Sep 2010 00:46:32 +0200
Received: from 94-194-102-93.zone8.bethere.co.uk (HELO seraphim.heaven) (94.194.102.93) by lvps83-169-7-107.dedicated.hosteurope.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 3 Sep 2010 00:46:32 +0200
Message-ID: <4C802951.5010209@gondrom.org>
Date: Thu, 02 Sep 2010 23:46:41 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100802 SUSE/3.1.2 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: hasmat@ietf.org
References: <4C6EC48A.5020803@stpeter.im> <4C725267.3010908@kuix.de>	<4C7FF821.2060002@stpeter.im>	<5EE049BA3C6538409BBE6F1760F328ABEAF281DEAD@DEN-MEXMS-001.corp.ebay.com> <4C802343.3090001@stpeter.im>
In-Reply-To: <4C802343.3090001@stpeter.im>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [HASMAT] moving forward
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 22:54:02 -0000

 On 09/02/2010 11:20 PM, Peter Saint-Andre wrote:
> On 9/2/10 1:37 PM, Steingruebl, Andy wrote:
>>> -----Original Message----- From: hasmat-bounces@ietf.org
>>> [mailto:hasmat-bounces@ietf.org] On Behalf Of Peter Saint-Andre 
>>> Sent: Thursday, September 02, 2010 12:17 PM To: Kai Engert Cc:
>>> hasmat@ietf.org Subject: Re: [HASMAT] moving forward
>>>> I wanted to propose "WebAppSec", but there's already 
>>>> http://www.webappsec.org/
>>> That's a good group to reach out to. :) Is anyone here involved
>>> with those folks? Are there other such groups to be aware of?
>> One of the Officers/Founders sits practically next to me.  I can
>> definitely check with the WASC folks if they are concerned about the
>> name.
> I was less interested in the name and more interested in technical
> input. :) The same would be true of the Open Web Application Security
> Project (OWASP) and other similar groups.
>
> However, we certainly don't want to stomp on names of existing groups...
>
> Peter
>
I got good connections to OWASP (been one their chapter leads back in
the day) and some other orgs.
I've been holding back a bit at the moment as our WG hadn't agreed on a
name yet and the charter.
And it can look quite odd if you invite people to a WG and say, but hey
we're not sure on the name/URL, it may change soon, and we don't really
know what will be in focus at the start either, yet....
(I know the state is better, but having at least the name ironed out
would feel much better when I run around and tell people about it to
bring them in...)

So far I have the impression the name issue is going towards a stable
tendency (for "websec"), which is good. And probably in a few days we
can settle that. And I urgently hope to see the revision of the initial
charter (Jeff?) soon, so that we can roll, i.e. have a discussion about
it and the drafts to work on.

Tobias


From Jeff.Hodges@KingsMountain.com  Thu Sep  2 16:43:36 2010
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 309853A677D for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 16:43:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.275
X-Spam-Level: 
X-Spam-Status: No, score=-101.275 tagged_above=-999 required=5 tests=[AWL=-0.499, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ovk7XZ3l+KZ0 for <hasmat@core3.amsl.com>; Thu,  2 Sep 2010 16:43:34 -0700 (PDT)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id B06B93A65A6 for <hasmat@ietf.org>; Thu,  2 Sep 2010 16:43:34 -0700 (PDT)
Received: (qmail 30087 invoked by uid 0); 2 Sep 2010 23:44:04 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 2 Sep 2010 23:44:04 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=OeJnRjkYWkT2VQakwt0tvY7xzJHZb7R2DMckPArwj7X6zLQLxh8ny0kE8r5SIrED40zwvJpojJBZpqOf1MX0FF46v35sfHJv3jiG2q2WoOZoQHNoBRvUvzM5tROTCGcg;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.48.205]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1OrJRs-0003ar-JM for hasmat@ietf.org; Thu, 02 Sep 2010 17:44:04 -0600
Message-ID: <4C8036C4.9060908@KingsMountain.com>
Date: Thu, 02 Sep 2010 16:44:04 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: IETF HASMAT list <hasmat@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 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: Re: [HASMAT] HASMAT Charter Proposal (revised)
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Sep 2010 23:43:36 -0000

I've revised the proposed charter per Barry's comment.

Further comments?

thanks,

=JeffH
------

Charter for WebSec -- Web Security WG
[ formerly known as HASMAT - HTTP Application Security Minus Authentication and 
Transport ]

Problem Statement

Although modern Web applications are built on top of HTTP, they provide
rich functionality and have requirements beyond the original vision of
static web pages.  HTTP, and the applications built on it, have evolved
organically.  Over the past few years, we have seen a proliferation of
AJAX-based web applications (AJAX being shorthand for asynchronous
JavaScript and XML), as well as Rich Internet Applications (RIAs), based
on so-called Web 2.0 technologies.  These applications bring both
luscious eye-candy and convenient functionality, e.g. social networking,
to their users, making them quite compelling.  At the same time, we are
seeing an increase in attacks against these applications and their
underlying technologies.

The list of attacks is long and includes Cross-Site-Request Forgery
(CSRF)-based attacks, content-sniffing cross-site-scripting (XSS)
attacks, attacks against browsers supporting anti-XSS policies,
clickjacking attacks, malvertising attacks, as well as man-in-the-middle
(MITM) attacks against "secure" (e.g. Transport Layer Security
(TLS/SSL)-based) web sites along with distribution of the tools to carry
out such attacks (e.g. sslstrip).


Objectives and Scope

With the arrival of new attacks the introduction of new web security
indicators, security techniques, and policy communication mechanisms
have sprinkled throughout the various layers of the Web and HTTP.

The goal of this working group is to compose an overall "problem
statement and requirements" document derived from surveying the
issues outlined in the above section ([1] provides a starting point).
The requirements guiding the work will be taken from the Web
application and Web security communities. The scope of this document
is HTTP applications security, but does not include HTTP authentication,
nor internals of transport security (although it may make reference to 
transport security as an available security "primitive"). See the "Out
of Scope" section, below.

Additionally, the WG will standardize a small number of
selected specifications that have proven to improve security of Internet
Web applications. Initial work will be limited to the following topics:

    - Same origin policy, as discussed in draft-abarth-origin

    - HTTP Strict transport security, as discussed in
      draft-hodges-strict-transport-sec

    - Media type sniffing, as discussed in draft-abarth-mime-sniff

This working group will work closely with IETF Apps Area WGs (such as
HYBI, HTTPstate, and HTTPbis), as well as W3C WebApps working group(s).


Out of Scope

As noted in the objectives and scope (above), this working group's
scope does not include working on HTTP Authentication nor underlying
transport (secure or not) topics. So, for example, these items are
out-of-scope for this WG:

    - Replacements for BASIC and DIGEST authentication

    - New transports (e.g. SCTP and the like)


Deliverables

1. A document illustrating the security problems Web applications are
facing and listing design requirements.  This document shall be
Informational.

2. A selected set of technical specifications documenting deployed
HTTP-based Web security solutions. These documents shall be Standards Track.


Goals and Milestones

Oct 2010    Submit "HTTP Application Security Problem Statement and
             Requirements" as initial WG item.

Oct 2010    Submit "Media Type Sniffing" as initial WG item.

Oct 2010    Submit "Web Origin Concept" as initial WG item.

Oct 2010    Submit "Strict Transport Security" as initial WG item.

Feb 2011    Submit "HTTP Application Security Problem Statement and
             Requirements" to the IESG for consideration as an
             Informational RFC.

Mar 2011    Submit "Media Type Sniffing" to the IESG for consideration
             as a Standards Track RFC.

Mar 2011    Submit "Web Origin Concept" to the IESG for consideration as
             a Standards Track RFC.

Mar 2011    Submit "Strict Transport Security" to the IESG for
             consideration as a Standards Track RFC.

Apr 2011    Possible re-chartering


References

[1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy
Framework", W2SP position paper, 2010.
http://w2spconf.com/2010/papers/p11.pdf


---
end




From tlr@w3.org  Fri Sep  3 02:01:54 2010
Return-Path: <tlr@w3.org>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BD2F03A6820 for <hasmat@core3.amsl.com>; Fri,  3 Sep 2010 02:01:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level: 
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sgVZlF82U9yH for <hasmat@core3.amsl.com>; Fri,  3 Sep 2010 02:01:53 -0700 (PDT)
Received: from jay.w3.org (ssh.w3.org [128.30.52.60]) by core3.amsl.com (Postfix) with ESMTP id D1D483A682D for <hasmat@ietf.org>; Fri,  3 Sep 2010 02:01:53 -0700 (PDT)
Received: from [87.240.232.183] (helo=[192.168.2.114]) by jay.w3.org with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from <tlr@w3.org>) id 1OrSA5-0003IV-29; Fri, 03 Sep 2010 05:02:17 -0400
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Thomas Roessler <tlr@w3.org>
In-Reply-To: <4C8036C4.9060908@KingsMountain.com>
Date: Fri, 3 Sep 2010 11:02:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3D718A9E-02EA-481E-B246-0E9C8B987F49@w3.org>
References: <4C8036C4.9060908@KingsMountain.com>
To: =JeffH <Jeff.Hodges@KingsMountain.com>, Adam Barth <abarth@eecs.berkeley.edu>, Brandon Sterne <bsterne@mozilla.com>
X-Mailer: Apple Mail (2.1081)
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] HASMAT Charter Proposal (revised)
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2010 09:01:54 -0000

On 3 Sep 2010, at 01:44, =3DJeffH wrote:

> I've revised the proposed charter per Barry's comment.

Thanks.

> Additionally, the WG will standardize a small number of
> selected specifications that have proven to improve security of =
Internet
> Web applications. Initial work will be limited to the following =
topics:
>=20
>   - Same origin policy, as discussed in draft-abarth-origin

draft-abarth-origin defines the origin concept and a corresponding HTTP =
header.

The same-origin policies typically involve a lengthy decision tree about =
where to take the origin from, e.g.:
	=
http://dev.w3.org/html5/spec/origin-0.html#relaxing-the-same-origin-restri=
ction

Adam, can you elaborate a bit more how, in detail, you see the =
relationship between your draft and HTML5 play out?  And can we talk =
about that in the charter?

> Deliverables
>=20
> 1. A document illustrating the security problems Web applications are
> facing and listing design requirements.  This document shall be
> Informational.
>=20
> 2. A selected set of technical specifications documenting deployed
> HTTP-based Web security solutions. These documents shall be Standards =
Track.
>=20
>=20
> Goals and Milestones
>=20
> Oct 2010    Submit "HTTP Application Security Problem Statement and
>            Requirements" as initial WG item.
>=20
> Oct 2010    Submit "Media Type Sniffing" as initial WG item.
>=20
> Oct 2010    Submit "Web Origin Concept" as initial WG item.
>=20
> Oct 2010    Submit "Strict Transport Security" as initial WG item.
>=20
> Feb 2011    Submit "HTTP Application Security Problem Statement and
>            Requirements" to the IESG for consideration as an
>            Informational RFC.
>=20
> Mar 2011    Submit "Media Type Sniffing" to the IESG for consideration
>            as a Standards Track RFC.
>=20
> Mar 2011    Submit "Web Origin Concept" to the IESG for consideration =
as
>            a Standards Track RFC.
>=20
> Mar 2011    Submit "Strict Transport Security" to the IESG for
>            consideration as a Standards Track RFC.
>=20
> Apr 2011    Possible re-chartering

I'm trying to think through the relationship between this time line and =
the Web Application Security WG idea at W3C:
	http://www.w3.org/2010/07/appsecwg-charter.html

In particular, to what extent do we expect the requirements document out =
of the IETF WG to directly influence whatever the W3C group does with =
CSP?

(Note that, on the IETF side of things, it's rational to recharter after =
the requirements document has been developed.  I'd prefer to avoid that =
on the W3C side if possible, since a rechartering is more costly -- =
though not impossible -- there.)

Thoughts?


From ietf@adambarth.com  Fri Sep  3 10:04:44 2010
Return-Path: <ietf@adambarth.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A5D243A68CB for <hasmat@core3.amsl.com>; Fri,  3 Sep 2010 10:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.067
X-Spam-Level: 
X-Spam-Status: No, score=-2.067 tagged_above=-999 required=5 tests=[AWL=-0.090, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YTWfGXALOhZc for <hasmat@core3.amsl.com>; Fri,  3 Sep 2010 10:04:43 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id 8814F3A6803 for <hasmat@ietf.org>; Fri,  3 Sep 2010 10:04:43 -0700 (PDT)
Received: by yxl31 with SMTP id 31so927905yxl.31 for <hasmat@ietf.org>; Fri, 03 Sep 2010 10:05:12 -0700 (PDT)
Received: by 10.103.229.2 with SMTP id g2mr148960mur.97.1283533510303; Fri, 03 Sep 2010 10:05:10 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id p2sm982926fak.22.2010.09.03.10.05.09 (version=SSLv3 cipher=RC4-MD5); Fri, 03 Sep 2010 10:05:09 -0700 (PDT)
Received: by iwn3 with SMTP id 3so1866853iwn.31 for <hasmat@ietf.org>; Fri, 03 Sep 2010 10:05:08 -0700 (PDT)
Received: by 10.231.15.8 with SMTP id i8mr1253059iba.12.1283533507923; Fri, 03 Sep 2010 10:05:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.187.218 with HTTP; Fri, 3 Sep 2010 10:04:34 -0700 (PDT)
In-Reply-To: <3D718A9E-02EA-481E-B246-0E9C8B987F49@w3.org>
References: <4C8036C4.9060908@KingsMountain.com> <3D718A9E-02EA-481E-B246-0E9C8B987F49@w3.org>
From: Adam Barth <ietf@adambarth.com>
Date: Fri, 3 Sep 2010 10:04:34 -0700
Message-ID: <AANLkTikMLwSkV9M6F-ThFXEJYaowUGN439TzM=2Ho-so@mail.gmail.com>
To: Thomas Roessler <tlr@w3.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] HASMAT Charter Proposal (revised)
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2010 17:04:44 -0000

On Fri, Sep 3, 2010 at 2:02 AM, Thomas Roessler <tlr@w3.org> wrote:
> On 3 Sep 2010, at 01:44, =3DJeffH wrote:
>> Additionally, the WG will standardize a small number of
>> selected specifications that have proven to improve security of Internet
>> Web applications. Initial work will be limited to the following topics:
>>
>> =A0 - Same origin policy, as discussed in draft-abarth-origin
>
> draft-abarth-origin defines the origin concept and a corresponding HTTP h=
eader.
>
> The same-origin policies typically involve a lengthy decision tree about =
where to take the origin from, e.g.:
> =A0 =A0 =A0 =A0http://dev.w3.org/html5/spec/origin-0.html#relaxing-the-sa=
me-origin-restriction
>
> Adam, can you elaborate a bit more how, in detail, you see the relationsh=
ip between your draft and HTML5 play out?

Sure.  draft-abarth-origin defines the nuts-and-bolts of working with
origins (computing them from URLs, comparing them to each other, etc).
 HTML5 defines HTML-specific usage of origins.  For example, when
making an HTTP request, HTML5 defines how to compute which origin
among all the origins rendering HTML is the one responsible for making
the request.  draft-abarth-origin then takes that origin, serializes
it to a string, and shoves it in a header.

Originally, draft-abarth-origin was part of HTML5, but there are a
number of other standards that wanted to interact with origins.  For
example, Hybi would like to serialize an origin and place the octets
somewhere on the wire.  Rather than have these folks refer "up the
stack" to the application layer (e.g., HTML5), it seems to make more
sense to move the non-application specific parts lower down in the
stack.  Of course, the application-specific parts (e.g., that the
toDataURL method on the <canvas> element behaves different depending
on the origins of things drawn on the canvas) will remain at the
application layer.

There also seems to be demand for a document that describes the
same-origin security model overall.  However, it seems like that
document ought to be more informative rather than normative.  I've
started sketching out something in that regard:

https://docs.google.com/document/pub?id=3D1p2t8ZOAcwduqrS-NPAlSMtBDaDBg3PDB=
ED625rTvctw

That's a pretty rough draft, but it should give you an idea of the
direction for that document.  Once I get that finished up, I'd like to
publish it in some forum, but it's unclear to me at this point what
forum would be most appropriate.

>=A0And can we talk about that in the charter?

I'll leave that up to the folks who've been working on the charter directly=
.

Adam

From Jeff.Hodges@KingsMountain.com  Fri Sep  3 15:53:50 2010
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3F6903A69A9 for <hasmat@core3.amsl.com>; Fri,  3 Sep 2010 15:53:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.236
X-Spam-Level: 
X-Spam-Status: No, score=-101.236 tagged_above=-999 required=5 tests=[AWL=-0.460, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Et7GB8a0erVg for <hasmat@core3.amsl.com>; Fri,  3 Sep 2010 15:53:48 -0700 (PDT)
Received: from cpoproxy3-pub.bluehost.com (cpoproxy3-pub.bluehost.com [67.222.54.6]) by core3.amsl.com (Postfix) with SMTP id AE5733A69A4 for <hasmat@ietf.org>; Fri,  3 Sep 2010 15:53:48 -0700 (PDT)
Received: (qmail 6653 invoked by uid 0); 3 Sep 2010 22:54:17 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 3 Sep 2010 22:54:17 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=d79EOH822UUNltEnfcxGSGO5vc3P6E7pyCyw06rai9Uh1Tl1tzBxR4/1Nn+/mB6F9oTvshnP/qkLEkbJjCsaIKlv5Td8V8VTEoWu0V4x7GYzXnKtw4wAWuIbk1HapJBa;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.48.205]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Orf9F-00034c-JH for hasmat@ietf.org; Fri, 03 Sep 2010 16:54:17 -0600
Message-ID: <4C817C9A.1060105@KingsMountain.com>
Date: Fri, 03 Sep 2010 15:54:18 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: IETF HASMAT list <hasmat@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 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: Re: [HASMAT] HASMAT Charter Proposal (revised-01)
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2010 22:53:50 -0000

enhanced per Roessler's and ABarth's comments/discussion.

Further comments?

thanks,

=JeffH
------

Charter for WebSec -- Web Security WG
[ formerly known as HASMAT - HTTP Application Security Minus Authentication and
Transport ]

Problem Statement

Although modern Web applications are built on top of HTTP, they provide
rich functionality and have requirements beyond the original vision of
static web pages.  HTTP, and the applications built on it, have evolved
organically.  Over the past few years, we have seen a proliferation of
AJAX-based web applications (AJAX being shorthand for asynchronous
JavaScript and XML), as well as Rich Internet Applications (RIAs), based
on so-called Web 2.0 technologies.  These applications bring both
luscious eye-candy and convenient functionality, e.g. social networking,
to their users, making them quite compelling.  At the same time, we are
seeing an increase in attacks against these applications and their
underlying technologies.

The list of attacks is long and includes Cross-Site-Request Forgery
(CSRF)-based attacks, content-sniffing cross-site-scripting (XSS)
attacks, attacks against browsers supporting anti-XSS policies,
clickjacking attacks, malvertising attacks, as well as man-in-the-middle
(MITM) attacks against "secure" (e.g. Transport Layer Security
(TLS/SSL)-based) web sites along with distribution of the tools to carry
out such attacks (e.g. sslstrip).


Objectives and Scope

With the arrival of new attacks the introduction of new web security
indicators, security techniques, and policy communication mechanisms
have sprinkled throughout the various layers of the Web and HTTP.

The goal of this working group is to compose an overall "problem
statement and requirements" document derived from surveying the
issues outlined in the above section ([1] provides a starting point).
The requirements guiding the work will be taken from the Web
application and Web security communities. The scope of this document
is HTTP applications security, but does not include HTTP authentication,
nor internals of transport security (although it may make reference to
transport security as an available security "primitive"). See the "Out
of Scope" section, below.

Additionally, the WG will standardize a small number of
selected specifications that have proven to improve security of Internet
Web applications. Initial work will be limited to the following topics:

    - Same origin policy, as discussed in draft-abarth-origin
      (see also Appendices A and B, below)

    - HTTP Strict transport security, as discussed in
      draft-hodges-strict-transport-sec

    - Media type sniffing, as discussed in draft-abarth-mime-sniff

This working group will work closely with IETF Apps Area WGs (such as
HYBI, HTTPstate, and HTTPbis), as well as appropriate W3C working group(s)
(e.g. HTML5, WebApps).


Out of Scope

As noted in the objectives and scope (above), this working group's
scope does not include working on HTTP Authentication nor underlying
transport (secure or not) topics. So, for example, these items are
out-of-scope for this WG:

    - Replacements for BASIC and DIGEST authentication

    - New transports (e.g. SCTP and the like)


Deliverables

1. A document illustrating the security problems Web applications are
facing and listing design requirements.  This document shall be
Informational.

2. A selected set of technical specifications documenting deployed
HTTP-based Web security solutions. These documents shall be Standards Track.


Goals and Milestones

Oct 2010    Submit "HTTP Application Security Problem Statement and
             Requirements" as initial WG item.

Oct 2010    Submit "Media Type Sniffing" as initial WG item.

Oct 2010    Submit "Web Origin Concept" as initial WG item.

Oct 2010    Submit "Strict Transport Security" as initial WG item.

Feb 2011    Submit "HTTP Application Security Problem Statement and
             Requirements" to the IESG for consideration as an
             Informational RFC.

Mar 2011    Submit "Media Type Sniffing" to the IESG for consideration
             as a Standards Track RFC.

Mar 2011    Submit "Web Origin Concept" to the IESG for consideration as
             a Standards Track RFC.

Mar 2011    Submit "Strict Transport Security" to the IESG for
             consideration as a Standards Track RFC.

Apr 2011    Possible re-chartering


References

[1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy
Framework", W2SP position paper, 2010.
http://w2spconf.com/2010/papers/p11.pdf

Appendix

A. Relationship of Origin work in IETF WebSec and in W3C HTML5

draft-abarth-origin defines the nuts-and-bolts of working with
origins (computing them from URLs, comparing them to each other, etc).
  HTML5 defines HTML-specific usage of origins.  For example, when
making an HTTP request, HTML5 defines how to compute which origin
among all the origins rendering HTML is the one responsible for making
the request.  draft-abarth-origin then takes that origin, serializes
it to a string, and shoves it in a header.


B. Origin work may yield two specifications

There also seems to be demand for a document that describes the
same-origin security model overall.  However, it seems like that
document ought to be more informative rather than normative. The
working group may split draft-abarth-origin into separate informative
and standards track specifications, the former describing same-origin
security model, and the latter specifying the nuts-and-bolts of working
with origins (computing them from URLs, comparing them to each other,
etc).


---
end





From tobias.gondrom@gondrom.org  Sat Sep  4 09:15:37 2010
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D784F3A685E for <hasmat@core3.amsl.com>; Sat,  4 Sep 2010 09:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -93.945
X-Spam-Level: 
X-Spam-Status: No, score=-93.945 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_20=-0.74, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id flKeHueEMA-v for <hasmat@core3.amsl.com>; Sat,  4 Sep 2010 09:15:35 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (lvps83-169-7-107.dedicated.hosteurope.de [83.169.7.107]) by core3.amsl.com (Postfix) with ESMTP id 33B713A686A for <hasmat@ietf.org>; Sat,  4 Sep 2010 09:15:34 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=EozdkChb14HUwi2Ngsa1ybfPOondIBdn8FfUe5K3D0h635FYxIUl2bnfA4/oVXkkcCBm12JnMBq0GBJ24dCKiOWoXN6CdT4F04kQwIvRSMQNklAW7Z31dPsVkNv2INo3; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:X-Priority:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 21930 invoked from network); 4 Sep 2010 18:15:55 +0200
Received: from 94-194-102-93.zone8.bethere.co.uk (HELO seraphim.heaven) (94.194.102.93) by lvps83-169-7-107.dedicated.hosteurope.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Sep 2010 18:15:55 +0200
Message-ID: <4C8270C8.3010605@gondrom.org>
Date: Sat, 04 Sep 2010 17:16:08 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100802 SUSE/3.1.2 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: IETF HASMAT list <hasmat@ietf.org>
X-Priority: 2 (High)
References: <4C817C9A.1060105@KingsMountain.com>
In-Reply-To: <4C817C9A.1060105@KingsMountain.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [HASMAT] HASMAT/Websec Charter Proposal - last call - comments until Sep-8
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 16:15:37 -0000

 Dear all,

as I haven't seen too much controversy on the charter, to get the work
going I like to close final comments on the initial charter and the name
of the new WG until Sep-8. After that we should submit the final
proposal to the AD and get to the more important work on the drafts.
Best regards, Tobias


Ps.: We need to finish the formal stuff (name, charter) for the WG until
Sep-12 so that we are in time before the cut-off date to book the
meeting slot for Beijing and so we can focus on the real stuff: the drafts.



======================================================


Charter for WebSec -- Web Security WG

Problem Statement

Although modern Web applications are built on top of HTTP, they provide
rich functionality and have requirements beyond the original vision of
static web pages.  HTTP, and the applications built on it, have evolved
organically.  Over the past few years, we have seen a proliferation of
AJAX-based web applications (AJAX being shorthand for asynchronous
JavaScript and XML), as well as Rich Internet Applications (RIAs), based
on so-called Web 2.0 technologies.  These applications bring both
luscious eye-candy and convenient functionality, e.g. social networking,
to their users, making them quite compelling.  At the same time, we are
seeing an increase in attacks against these applications and their
underlying technologies.

The list of attacks is long and includes Cross-Site-Request Forgery
(CSRF)-based attacks, content-sniffing cross-site-scripting (XSS)
attacks, attacks against browsers supporting anti-XSS policies,
clickjacking attacks, malvertising attacks, as well as man-in-the-middle
(MITM) attacks against "secure" (e.g. Transport Layer Security
(TLS/SSL)-based) web sites along with distribution of the tools to carry
out such attacks (e.g. sslstrip).


Objectives and Scope

With the arrival of new attacks the introduction of new web security
indicators, security techniques, and policy communication mechanisms
have sprinkled throughout the various layers of the Web and HTTP.

The goal of this working group is to compose an overall "problem
statement and requirements" document derived from surveying the
issues outlined in the above section ([1] provides a starting point).
The requirements guiding the work will be taken from the Web
application and Web security communities. The scope of this document
is HTTP applications security, but does not include HTTP authentication,
nor internals of transport security which are addressed by other working
groups
(although it may make reference to transport security as an available
security "primitive").
See the "Out of Scope" section, below.

Additionally, the WG will standardize a small number of
selected specifications that have proven to improve security of Internet
Web applications. Initial work will be the following topics:

   - Same origin policy, as discussed in draft-abarth-origin
     (see also Appendices A and B, below)

   - HTTP Strict transport security, as discussed in
     draft-hodges-strict-transport-sec

   - Media type sniffing, as discussed in draft-abarth-mime-sniff

This working group will work closely with IETF Apps Area WGs (such as
HYBI, HTTPstate, and HTTPbis), as well as appropriate W3C working group(s)
(e.g. HTML5, WebApps).


Out of Scope

As noted in the objectives and scope (above), this working group's
scope does not include working on HTTP Authentication nor underlying
transport (secure or not) topics. So, for example, these items are
out-of-scope for this WG:

   - Replacements for BASIC and DIGEST authentication

   - New transports (e.g. SCTP and the like)


Deliverables

1. A document illustrating the security problems Web applications are
facing and listing design requirements.  This document shall be
Informational.

2. A selected set of technical specifications documenting deployed
HTTP-based Web security solutions. These documents shall be Standards
Track.


Goals and Milestones

Oct 2010    Submit "HTTP Application Security Problem Statement and
            Requirements" as initial WG item.

Oct 2010    Submit "Media Type Sniffing" as initial WG item.

Oct 2010    Submit "Web Origin Concept" as initial WG item.

Oct 2010    Submit "Strict Transport Security" as initial WG item.

Feb 2011    Submit "HTTP Application Security Problem Statement and
            Requirements" to the IESG for consideration as an
            Informational RFC.

Mar 2011    Submit "Media Type Sniffing" to the IESG for consideration
            as a Standards Track RFC.

Mar 2011    Submit "Web Origin Concept" to the IESG for consideration as
            a Standards Track RFC.

Mar 2011    Submit "Strict Transport Security" to the IESG for
            consideration as a Standards Track RFC.

Apr 2011    Possible re-chartering


References

[1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy
Framework", W2SP position paper, 2010.
http://w2spconf.com/2010/papers/p11.pdf

Appendix

A. Relationship of Origin work in IETF WebSec and in W3C HTML5

draft-abarth-origin defines the nuts-and-bolts of working with
origins (computing them from URLs, comparing them to each other, etc).
 HTML5 defines HTML-specific usage of origins.  For example, when
making an HTTP request, HTML5 defines how to compute which origin
among all the origins rendering HTML is the one responsible for making
the request.  draft-abarth-origin then takes that origin, serializes
it to a string, and shoves it in a header.


B. Origin work may yield two specifications

There also seems to be demand for a document that describes the
same-origin security model overall.  However, it seems like that
document ought to be more informative rather than normative. The
working group may split draft-abarth-origin into separate informative
and standards track specifications, the former describing same-origin
security model, and the latter specifying the nuts-and-bolts of working
with origins (computing them from URLs, comparing them to each other,
etc).


---
end



From tobias.gondrom@gondrom.org  Sat Sep  4 09:21:44 2010
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C40543A6869 for <hasmat@core3.amsl.com>; Sat,  4 Sep 2010 09:21:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -93.919
X-Spam-Level: 
X-Spam-Status: No, score=-93.919 tagged_above=-999 required=5 tests=[AWL=-0.416, BAYES_20=-0.74, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H4hRJ-4uxT6e for <hasmat@core3.amsl.com>; Sat,  4 Sep 2010 09:21:43 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (lvps83-169-7-107.dedicated.hosteurope.de [83.169.7.107]) by core3.amsl.com (Postfix) with ESMTP id 9471E3A6852 for <hasmat@ietf.org>; Sat,  4 Sep 2010 09:21:42 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=C7eQ6vTV3xjN6RRxrI2im5nAKlRFrJ3f6xEGlP2EjPGNUEL3Tir13rwnWv/i4+r3DN7rt8HKklOgNOo0hosOSeZE3WaCjIbI+bOPvWcuKcZ0XuXPsKsMtbmxh01YfeN0; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 21538 invoked from network); 4 Sep 2010 17:53:12 +0200
Received: from 94-194-102-93.zone8.bethere.co.uk (HELO seraphim.heaven) (94.194.102.93) by lvps83-169-7-107.dedicated.hosteurope.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 4 Sep 2010 17:53:11 +0200
Message-ID: <4C826B75.30000@gondrom.org>
Date: Sat, 04 Sep 2010 16:53:25 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100802 SUSE/3.1.2 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: =JeffH <Jeff.Hodges@KingsMountain.com>
References: <4C817C9A.1060105@KingsMountain.com>
In-Reply-To: <4C817C9A.1060105@KingsMountain.com>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] HASMAT Charter Proposal (revised-01)
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 Sep 2010 16:21:44 -0000

 Jeff,

excellent. Thank you. I like the charter and think it's good to go.

Maybe two  very minor personal editorial suggestions
1. in the section "Objectives and Scope" second paragraph.
current: "The scope of this document is HTTP applications security, but
does not include HTTP authentication, nor internals of transport
security (although it may make reference to transport security as an
available security "primitive")."
revised: "The scope of this document is HTTP applications security, but
does not include HTTP authentication, nor internals of transport
security which are addressed by other working groups (although it may
make reference to transport security as an available security "primitive")."

reason: This way unfamiliar readers will know the rationale why we
excluded this and can look elsewhere.

2. section "Objectives and Scope", third paragraph:
current: "Initial work will be limited to the following topics:"
new: "Initial work will be the following topics:"

reason: no need to limit this so formally, but rather state what we are
doing first, allows it open to add stuff which is in scope of the
charter later once the ball is rolling.

These are only my personal comments and from my perspective only very
minor and editorial.

Best regards, Tobias




On 09/03/2010 11:54 PM, =JeffH wrote:
> enhanced per Roessler's and ABarth's comments/discussion.
>
> Further comments?
>
> thanks,
>
> =JeffH
> ------
>
> Charter for WebSec -- Web Security WG
> [ formerly known as HASMAT - HTTP Application Security Minus
> Authentication and
> Transport ]
>
> Problem Statement
>
> Although modern Web applications are built on top of HTTP, they provide
> rich functionality and have requirements beyond the original vision of
> static web pages.  HTTP, and the applications built on it, have evolved
> organically.  Over the past few years, we have seen a proliferation of
> AJAX-based web applications (AJAX being shorthand for asynchronous
> JavaScript and XML), as well as Rich Internet Applications (RIAs), based
> on so-called Web 2.0 technologies.  These applications bring both
> luscious eye-candy and convenient functionality, e.g. social networking,
> to their users, making them quite compelling.  At the same time, we are
> seeing an increase in attacks against these applications and their
> underlying technologies.
>
> The list of attacks is long and includes Cross-Site-Request Forgery
> (CSRF)-based attacks, content-sniffing cross-site-scripting (XSS)
> attacks, attacks against browsers supporting anti-XSS policies,
> clickjacking attacks, malvertising attacks, as well as man-in-the-middle
> (MITM) attacks against "secure" (e.g. Transport Layer Security
> (TLS/SSL)-based) web sites along with distribution of the tools to carry
> out such attacks (e.g. sslstrip).
>
>
> Objectives and Scope
>
> With the arrival of new attacks the introduction of new web security
> indicators, security techniques, and policy communication mechanisms
> have sprinkled throughout the various layers of the Web and HTTP.
>
> The goal of this working group is to compose an overall "problem
> statement and requirements" document derived from surveying the
> issues outlined in the above section ([1] provides a starting point).
> The requirements guiding the work will be taken from the Web
> application and Web security communities. The scope of this document
> is HTTP applications security, but does not include HTTP authentication,
> nor internals of transport security (although it may make reference to
> transport security as an available security "primitive"). See the "Out
> of Scope" section, below.
>
> Additionally, the WG will standardize a small number of
> selected specifications that have proven to improve security of Internet
> Web applications. Initial work will be limited to the following topics:
>
>    - Same origin policy, as discussed in draft-abarth-origin
>      (see also Appendices A and B, below)
>
>    - HTTP Strict transport security, as discussed in
>      draft-hodges-strict-transport-sec
>
>    - Media type sniffing, as discussed in draft-abarth-mime-sniff
>
> This working group will work closely with IETF Apps Area WGs (such as
> HYBI, HTTPstate, and HTTPbis), as well as appropriate W3C working
> group(s)
> (e.g. HTML5, WebApps).
>
>
> Out of Scope
>
> As noted in the objectives and scope (above), this working group's
> scope does not include working on HTTP Authentication nor underlying
> transport (secure or not) topics. So, for example, these items are
> out-of-scope for this WG:
>
>    - Replacements for BASIC and DIGEST authentication
>
>    - New transports (e.g. SCTP and the like)
>
>
> Deliverables
>
> 1. A document illustrating the security problems Web applications are
> facing and listing design requirements.  This document shall be
> Informational.
>
> 2. A selected set of technical specifications documenting deployed
> HTTP-based Web security solutions. These documents shall be Standards
> Track.
>
>
> Goals and Milestones
>
> Oct 2010    Submit "HTTP Application Security Problem Statement and
>             Requirements" as initial WG item.
>
> Oct 2010    Submit "Media Type Sniffing" as initial WG item.
>
> Oct 2010    Submit "Web Origin Concept" as initial WG item.
>
> Oct 2010    Submit "Strict Transport Security" as initial WG item.
>
> Feb 2011    Submit "HTTP Application Security Problem Statement and
>             Requirements" to the IESG for consideration as an
>             Informational RFC.
>
> Mar 2011    Submit "Media Type Sniffing" to the IESG for consideration
>             as a Standards Track RFC.
>
> Mar 2011    Submit "Web Origin Concept" to the IESG for consideration as
>             a Standards Track RFC.
>
> Mar 2011    Submit "Strict Transport Security" to the IESG for
>             consideration as a Standards Track RFC.
>
> Apr 2011    Possible re-chartering
>
>
> References
>
> [1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy
> Framework", W2SP position paper, 2010.
> http://w2spconf.com/2010/papers/p11.pdf
>
> Appendix
>
> A. Relationship of Origin work in IETF WebSec and in W3C HTML5
>
> draft-abarth-origin defines the nuts-and-bolts of working with
> origins (computing them from URLs, comparing them to each other, etc).
>  HTML5 defines HTML-specific usage of origins.  For example, when
> making an HTTP request, HTML5 defines how to compute which origin
> among all the origins rendering HTML is the one responsible for making
> the request.  draft-abarth-origin then takes that origin, serializes
> it to a string, and shoves it in a header.
>
>
> B. Origin work may yield two specifications
>
> There also seems to be demand for a document that describes the
> same-origin security model overall.  However, it seems like that
> document ought to be more informative rather than normative. The
> working group may split draft-abarth-origin into separate informative
> and standards track specifications, the former describing same-origin
> security model, and the latter specifying the nuts-and-bolts of working
> with origins (computing them from URLs, comparing them to each other,
> etc).
>
>
> ---
> end
>
>
>
>
> _______________________________________________
> HASMAT mailing list
> HASMAT@ietf.org
> https://www.ietf.org/mailman/listinfo/hasmat


From julian.reschke@gmx.de  Wed Sep  8 06:38:22 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 056B73A6949 for <hasmat@core3.amsl.com>; Wed,  8 Sep 2010 06:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.425
X-Spam-Level: 
X-Spam-Status: No, score=-103.425 tagged_above=-999 required=5 tests=[AWL=-3.240, BAYES_40=-0.185, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IxmCEDPrjOLz for <hasmat@core3.amsl.com>; Wed,  8 Sep 2010 06:38:19 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 5FE283A68D5 for <hasmat@ietf.org>; Wed,  8 Sep 2010 06:38:11 -0700 (PDT)
Received: (qmail invoked by alias); 08 Sep 2010 13:38:23 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.143]) [217.91.35.233] by mail.gmx.net (mp062) with SMTP; 08 Sep 2010 15:38:23 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18FrAAUOkMFBGM8HkXZLfy1vwfdATwyoabEmMdKLJ 57+vONTgaah0/Q
Message-ID: <4C8791CA.1010305@gmx.de>
Date: Wed, 08 Sep 2010 15:38:18 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: Tobias Gondrom <tobias.gondrom@gondrom.org>
References: <4C817C9A.1060105@KingsMountain.com> <4C8270C8.3010605@gondrom.org>
In-Reply-To: <4C8270C8.3010605@gondrom.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] HASMAT/Websec Charter Proposal - last call - comments until Sep-8
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Sep 2010 13:38:23 -0000

On 04.09.2010 18:16, Tobias Gondrom wrote:
>   Dear all,
>
> as I haven't seen too much controversy on the charter, to get the work
> going I like to close final comments on the initial charter and the name
> of the new WG until Sep-8. After that we should submit the final
> proposal to the AD and get to the more important work on the drafts.
> Best regards, Tobias
>
>
> Ps.: We need to finish the formal stuff (name, charter) for the WG until
> Sep-12 so that we are in time before the cut-off date to book the
> meeting slot for Beijing and so we can focus on the real stuff: the drafts.
>
>
>
> ======================================================
>
>
> Charter for WebSec -- Web Security WG
>
> Problem Statement
>
> Although modern Web applications are built on top of HTTP, they provide
> rich functionality and have requirements beyond the original vision of
> static web pages.  HTTP, and the applications built on it, have evolved
> organically.  Over the past few years, we have seen a proliferation of
> AJAX-based web applications (AJAX being shorthand for asynchronous
> JavaScript and XML), as well as Rich Internet Applications (RIAs), based
> on so-called Web 2.0 technologies.  These applications bring both
> luscious eye-candy and convenient functionality, e.g. social networking,
> to their users, making them quite compelling.  At the same time, we are
> seeing an increase in attacks against these applications and their
> underlying technologies.

This has many Buzzwords. Maybe it could be shortened.

> The list of attacks is long and includes Cross-Site-Request Forgery
> (CSRF)-based attacks, content-sniffing cross-site-scripting (XSS)

"content-sniffing cross-site-scripting"?

> ...
> This working group will work closely with IETF Apps Area WGs (such as
> HYBI, HTTPstate, and HTTPbis), as well as appropriate W3C working group(s)
> (e.g. HTML5, WebApps).

It's the W3C "HTML" Working Group...

> References
>
> [1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy
> Framework", W2SP position paper, 2010.
> http://w2spconf.com/2010/papers/p11.pdf
>
> Appendix
>
> A. Relationship of Origin work in IETF WebSec and in W3C HTML5
>
> draft-abarth-origin defines the nuts-and-bolts of working with
> origins (computing them from URLs, comparing them to each other, etc).
 > ...

 From URIs or IRIs, I assume :-)

Best regards, Julian

From julian.reschke@gmx.de  Thu Sep  9 02:48:48 2010
Return-Path: <julian.reschke@gmx.de>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BCC843A6768 for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 02:48:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.641
X-Spam-Level: 
X-Spam-Status: No, score=-104.641 tagged_above=-999 required=5 tests=[AWL=-2.042, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 92Ba+tDzREyE for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 02:48:47 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id AD2223A6403 for <hasmat@ietf.org>; Thu,  9 Sep 2010 02:48:46 -0700 (PDT)
Received: (qmail invoked by alias); 09 Sep 2010 09:49:11 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.143]) [217.91.35.233] by mail.gmx.net (mp022) with SMTP; 09 Sep 2010 11:49:11 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1/cmQ9OosfcZcsLK2dGYkBor9Ad0FeYhD9HBYNVFi dFLseBEZE27CnE
Message-ID: <4C88AD91.4090301@gmx.de>
Date: Thu, 09 Sep 2010 11:49:05 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3
MIME-Version: 1.0
To: IETF HASMAT list <hasmat@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Subject: [HASMAT] X-FRAME-OPTIONS
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 09:48:49 -0000

Hi,

see

<http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-clickjacking-defenses.aspx> 
and <http://www.mozilla.com/en-US/firefox/3.6.9/releasenotes/>.

Is this something the WG should consider as well?

Best regards, Julian

From tobias.gondrom@gondrom.org  Thu Sep  9 06:49:10 2010
Return-Path: <tobias.gondrom@gondrom.org>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A61C73A68C4 for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 06:49:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.825
X-Spam-Level: 
X-Spam-Status: No, score=-95.825 tagged_above=-999 required=5 tests=[AWL=1.537, BAYES_00=-2.599, FH_HELO_EQ_D_D_D_D=1.597, FH_HOST_EQ_D_D_D_D=0.765, FM_DDDD_TIMES_2=1.999, GB_I_LETTER=-2, HELO_DYNAMIC_IPADDR=2.426, HELO_EQ_DE=0.35, RDNS_DYNAMIC=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Sv0d1XV+XZ4O for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 06:49:09 -0700 (PDT)
Received: from lvps83-169-7-107.dedicated.hosteurope.de (lvps83-169-7-107.dedicated.hosteurope.de [83.169.7.107]) by core3.amsl.com (Postfix) with ESMTP id A8F063A680F for <hasmat@ietf.org>; Thu,  9 Sep 2010 06:49:07 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=U5uDCe/72NRv6081G/OHsixQ5jKPQNMvlcETAWbmNMpBxOYVH+Qmie5vGbhhewbC7u7ANeFpE8a8twqLqqFifFnQj1Lm9buIxecEPIbbVV6Tvbq7wUDosypxhz6AnTPs; h=Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:X-Priority:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
Received: (qmail 5134 invoked from network); 9 Sep 2010 15:49:19 +0200
Received: from 94-194-102-93.zone8.bethere.co.uk (HELO seraphim.heaven) (94.194.102.93) by lvps83-169-7-107.dedicated.hosteurope.de with (DHE-RSA-AES256-SHA encrypted) SMTP; 9 Sep 2010 15:49:19 +0200
Message-ID: <4C88E5E4.9000101@gondrom.org>
Date: Thu, 09 Sep 2010 14:49:24 +0100
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.8) Gecko/20100802 SUSE/3.1.2 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
X-Priority: 4 (Low)
References: <4C817C9A.1060105@KingsMountain.com> <4C8270C8.3010605@gondrom.org> <4C8791CA.1010305@gmx.de>
In-Reply-To: <4C8791CA.1010305@gmx.de>
X-Enigmail-Version: 1.1.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] HASMAT/Websec Charter Proposal - last call - comments until Sep-8
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 13:49:10 -0000

 Dear Julian,
thanks a lot for your feedback. I corrected the points you mentioned
except for the "buzzword part". Answers inline.
I think we are ready to go now.
Best regards, Tobias


On 09/08/2010 02:38 PM, Julian Reschke wrote:
> On 04.09.2010 18:16, Tobias Gondrom wrote:
>>   Dear all,
>>
>> as I haven't seen too much controversy on the charter, to get the work
>> going I like to close final comments on the initial charter and the name
>> of the new WG until Sep-8. After that we should submit the final
>> proposal to the AD and get to the more important work on the drafts.
>> Best regards, Tobias
>>
>>
>> Ps.: We need to finish the formal stuff (name, charter) for the WG until
>> Sep-12 so that we are in time before the cut-off date to book the
>> meeting slot for Beijing and so we can focus on the real stuff: the
>> drafts.
>>
>>
>>
>> ======================================================
>>
>>
>> Charter for WebSec -- Web Security WG
>>
>> Problem Statement
>>
>> Although modern Web applications are built on top of HTTP, they provide
>> rich functionality and have requirements beyond the original vision of
>> static web pages.  HTTP, and the applications built on it, have evolved
>> organically.  Over the past few years, we have seen a proliferation of
>> AJAX-based web applications (AJAX being shorthand for asynchronous
>> JavaScript and XML), as well as Rich Internet Applications (RIAs), based
>> on so-called Web 2.0 technologies.  These applications bring both
>> luscious eye-candy and convenient functionality, e.g. social networking,
>> to their users, making them quite compelling.  At the same time, we are
>> seeing an increase in attacks against these applications and their
>> underlying technologies.
>
> This has many Buzzwords. Maybe it could be shortened.
Hm, yes maybe, reminds me of Pascal ("I have made this [letter] longer,
because I have not had the time to make it shorter.") Shortening it
would have required rewriting it, which would mean new review (and time
delay), so left the Problem Statement as it is with the buzzwords.

>> The list of attacks is long and includes Cross-Site-Request Forgery
>> (CSRF)-based attacks, content-sniffing cross-site-scripting (XSS)
>
> "content-sniffing cross-site-scripting"?
>
thanks. Added the comma between the words.

>> ...
>> This working group will work closely with IETF Apps Area WGs (such as
>> HYBI, HTTPstate, and HTTPbis), as well as appropriate W3C working
>> group(s)
>> (e.g. HTML5, WebApps).
>
> It's the W3C "HTML" Working Group...
>
Corrected.
>> References
>>
>> [1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy
>> Framework", W2SP position paper, 2010.
>> http://w2spconf.com/2010/papers/p11.pdf
>>
>> Appendix
>>
>> A. Relationship of Origin work in IETF WebSec and in W3C HTML5
>>
>> draft-abarth-origin defines the nuts-and-bolts of working with
>> origins (computing them from URLs, comparing them to each other, etc).
> > ...
>
> From URIs or IRIs, I assume :-)
Yes, it's URI. Corrected.

>
> Best regards, Julian



From ietf@adambarth.com  Thu Sep  9 07:00:10 2010
Return-Path: <ietf@adambarth.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AAADA3A6841 for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 07:00:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.053
X-Spam-Level: 
X-Spam-Status: No, score=-2.053 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJiqB+Csdkfr for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 07:00:09 -0700 (PDT)
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) by core3.amsl.com (Postfix) with ESMTP id 87A8B3A686A for <hasmat@ietf.org>; Thu,  9 Sep 2010 07:00:09 -0700 (PDT)
Received: by vws10 with SMTP id 10so1436016vws.31 for <hasmat@ietf.org>; Thu, 09 Sep 2010 07:00:37 -0700 (PDT)
Received: by 10.220.128.201 with SMTP id l9mr721495vcs.73.1284040836759; Thu, 09 Sep 2010 07:00:36 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id r15sm882917vbp.10.2010.09.09.07.00.35 (version=SSLv3 cipher=RC4-MD5); Thu, 09 Sep 2010 07:00:35 -0700 (PDT)
Received: by iwn3 with SMTP id 3so1359751iwn.31 for <hasmat@ietf.org>; Thu, 09 Sep 2010 07:00:34 -0700 (PDT)
Received: by 10.231.59.13 with SMTP id j13mr11880417ibh.77.1284040834311; Thu, 09 Sep 2010 07:00:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.143.1 with HTTP; Thu, 9 Sep 2010 07:00:04 -0700 (PDT)
In-Reply-To: <4C88AD91.4090301@gmx.de>
References: <4C88AD91.4090301@gmx.de>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 9 Sep 2010 07:00:04 -0700
Message-ID: <AANLkTi=TZ2Z+2fo7B0+wid2K1zTKxAQo4V974RSvw34M@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] X-FRAME-OPTIONS
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 14:00:10 -0000

We could.  I'd be happy to edit it.  There's isn't much (any?)
flexibility in the protocol though.

Adam


On Thu, Sep 9, 2010 at 2:49 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> Hi,
>
> see
>
> <http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-clickjacking-defenses.aspx>
> and <http://www.mozilla.com/en-US/firefox/3.6.9/releasenotes/>.
>
> Is this something the WG should consider as well?
>
> Best regards, Julian
> _______________________________________________
> HASMAT mailing list
> HASMAT@ietf.org
> https://www.ietf.org/mailman/listinfo/hasmat
>

From asteingruebl@paypal-inc.com  Thu Sep  9 09:32:39 2010
Return-Path: <asteingruebl@paypal-inc.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3B2E3A68B3 for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 09:32:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.079
X-Spam-Level: 
X-Spam-Status: No, score=-4.079 tagged_above=-999 required=5 tests=[AWL=-1.038, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, RCVD_IN_DNSWL_MED=-4, SUBJ_ALL_CAPS=2.077]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dXcva1WKtxWp for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 09:32:37 -0700 (PDT)
Received: from den-mipot-002.corp.ebay.com (den-mipot-002.corp.ebay.com [216.113.175.153]) by core3.amsl.com (Postfix) with ESMTP id D459F3A67FF for <hasmat@ietf.org>; Thu,  9 Sep 2010 09:32:36 -0700 (PDT)
DomainKey-Signature: s=ppinc; d=paypal-inc.com; c=nofws; q=dns; h=X-EBay-Corp:X-IronPort-AV:Received:Received:From:To:Date: Subject:Thread-Topic:Thread-Index:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:acceptlanguage: Content-Type:Content-Transfer-Encoding:MIME-Version: X-CFilter; b=ibOMT5xJP34I4QblBV3spD5NV4b+HmVpZrmzdl+3uKiBjbIgrymvhCLV Et0bBYVLFiOrlqotfkEKeKB0SZS7MuLpztvrXXoMq3O/DvE9XuN66p4hV RR4MYDVGm2J7Sfd;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=paypal-inc.com; i=asteingruebl@paypal-inc.com; q=dns/txt; s=ppinc; t=1284049985; x=1315585985; h=from:to:date:subject:message-id:references:in-reply-to: content-transfer-encoding:mime-version; z=From:=20"Steingruebl,=20Andy"=20<asteingruebl@paypal-inc .com>|To:=20Julian=20Reschke=20<julian.reschke@gmx.de>, =20IETF=20HASMAT=20list=20<hasmat@ietf.org>|Date:=20Thu, =209=20Sep=202010=2010:32:56=20-0600|Subject:=20RE:=20[HA SMAT]=20X-FRAME-OPTIONS|Message-ID:=20<5EE049BA3C6538409B BE6F1760F328ABEAF852CA70@DEN-MEXMS-001.corp.ebay.com> |References:=20<4C88AD91.4090301@gmx.de>|In-Reply-To:=20< 4C88AD91.4090301@gmx.de>|Content-Transfer-Encoding:=20quo ted-printable|MIME-Version:=201.0; bh=qx+MCO7O0uwRMumVRXEtDMQeOx645vGoIryeEqgf8hM=; b=X3T159b7MJZfwcEd3AEg2EOXj36RzrJogGG6Cb3jz25jbwv2/VCf8D2W t6PotiToADPFKJZrDNVQSAzI/1La/Y/jErRh8p7LwPLak0l1+2xpjq+wy gv43lak++1qD+Xc;
X-EBay-Corp: Yes
X-IronPort-AV: E=Sophos;i="4.56,340,1280732400"; d="scan'208";a="72112060"
Received: from den-vtenf-001.corp.ebay.com (HELO DEN-MEXHT-002.corp.ebay.com) ([10.101.112.212]) by den-mipot-002.corp.ebay.com with ESMTP; 09 Sep 2010 09:32:59 -0700
Received: from DEN-MEXMS-001.corp.ebay.com ([10.241.16.228]) by DEN-MEXHT-002.corp.ebay.com ([10.241.17.53]) with mapi; Thu, 9 Sep 2010 10:32:57 -0600
From: "Steingruebl, Andy" <asteingruebl@paypal-inc.com>
To: Julian Reschke <julian.reschke@gmx.de>, IETF HASMAT list <hasmat@ietf.org>
Date: Thu, 9 Sep 2010 10:32:56 -0600
Thread-Topic: [HASMAT] X-FRAME-OPTIONS
Thread-Index: ActQBFGS43NOoZO9RHmeDyQ84k2hxwAN33aQ
Message-ID: <5EE049BA3C6538409BBE6F1760F328ABEAF852CA70@DEN-MEXMS-001.corp.ebay.com>
References: <4C88AD91.4090301@gmx.de>
In-Reply-To: <4C88AD91.4090301@gmx.de>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter: Scanned
Subject: Re: [HASMAT] X-FRAME-OPTIONS
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 16:32:39 -0000

> -----Original Message-----
> From: hasmat-bounces@ietf.org [mailto:hasmat-bounces@ietf.org] On
> Behalf Of Julian Reschke
>=20
> <http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-
> clickjacking-defenses.aspx>
> and <http://www.mozilla.com/en-US/firefox/3.6.9/releasenotes/>.
>=20
> Is this something the WG should consider as well?

I definitely agree that there ought to be a spec for this.  What I'm a bit =
torn about though is where its home should be. =20

Because X-Frame-Options deals exclusively with HTML processing agents and h=
ow they want to visually represent content, I think this may more properly =
belong to the nascent W3C Web Application Security Working Group - http://w=
ww.w3.org/2010/07/appsecwg-charter.html

My hope is that we can come up with some sort of logical grouping Or, dare =
I say it taxonomy, of security controls/indicators and group them into thin=
gs that are core protocol related, and those that are content/display/inter=
pretation related.  The first group could be done in the IETF, the second i=
n the W3C.  My thinking isn't especially well-formed on this as I don't hav=
e that grouping/taxonomy laid out.

Admittedly HSTS mostly only applies to web browsers as well since they are =
the main target, and yet we're working on that here.  At the same time CORS=
 and CSP are both presumably going to be done/continue at the W3C, and X-Fr=
ame-Options seems closer to them than it does to HSTS.

Perhaps a good exercise would be for us to enumerate a bunch f the policy m=
echanisms we've been envisioning, and then group them according to type, ho=
me, etc.  I don't know that we need a full taxonomy of them,  but I'm open =
to being persuaded.

- Andy

From ietf@adambarth.com  Thu Sep  9 09:47:39 2010
Return-Path: <ietf@adambarth.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B150D3A68FA for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 09:47:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.052
X-Spam-Level: 
X-Spam-Status: No, score=-2.052 tagged_above=-999 required=5 tests=[AWL=-0.075, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BbsdkHnK8nAz for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 09:47:38 -0700 (PDT)
Received: from mail-ew0-f44.google.com (mail-ew0-f44.google.com [209.85.215.44]) by core3.amsl.com (Postfix) with ESMTP id 66B323A6970 for <hasmat@ietf.org>; Thu,  9 Sep 2010 09:47:38 -0700 (PDT)
Received: by ewy26 with SMTP id 26so438934ewy.31 for <hasmat@ietf.org>; Thu, 09 Sep 2010 09:48:05 -0700 (PDT)
Received: by 10.213.20.13 with SMTP id d13mr108412ebb.83.1284050884406; Thu, 09 Sep 2010 09:48:04 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by mx.google.com with ESMTPS id v59sm2287980eeh.4.2010.09.09.09.48.03 (version=SSLv3 cipher=RC4-MD5); Thu, 09 Sep 2010 09:48:04 -0700 (PDT)
Received: by iwn3 with SMTP id 3so1475425iwn.31 for <hasmat@ietf.org>; Thu, 09 Sep 2010 09:48:02 -0700 (PDT)
Received: by 10.231.154.75 with SMTP id n11mr11914094ibw.40.1284050383210; Thu, 09 Sep 2010 09:39:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.231.143.1 with HTTP; Thu, 9 Sep 2010 09:39:12 -0700 (PDT)
In-Reply-To: <5EE049BA3C6538409BBE6F1760F328ABEAF852CA70@DEN-MEXMS-001.corp.ebay.com>
References: <4C88AD91.4090301@gmx.de> <5EE049BA3C6538409BBE6F1760F328ABEAF852CA70@DEN-MEXMS-001.corp.ebay.com>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 9 Sep 2010 09:39:12 -0700
Message-ID: <AANLkTinF4=O4TRr_FS8QK+c5mDWdAAo5t=hJ4MAmXUoH@mail.gmail.com>
To: "Steingruebl, Andy" <asteingruebl@paypal-inc.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] X-FRAME-OPTIONS
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 16:47:39 -0000

On Thu, Sep 9, 2010 at 9:32 AM, Steingruebl, Andy
<asteingruebl@paypal-inc.com> wrote:
>> -----Original Message-----
>> From: hasmat-bounces@ietf.org [mailto:hasmat-bounces@ietf.org] On
>> Behalf Of Julian Reschke
>>
>> <http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-
>> clickjacking-defenses.aspx>
>> and <http://www.mozilla.com/en-US/firefox/3.6.9/releasenotes/>.
>>
>> Is this something the WG should consider as well?
>
> I definitely agree that there ought to be a spec for this. =A0What I'm a =
bit torn about though is where its home should be.
>
> Because X-Frame-Options deals exclusively with HTML processing agents and=
 how they want to visually represent content, I think this may more properl=
y belong to the nascent W3C Web Application Security Working Group - http:/=
/www.w3.org/2010/07/appsecwg-charter.html
>
> My hope is that we can come up with some sort of logical grouping Or, dar=
e I say it taxonomy, of security controls/indicators and group them into th=
ings that are core protocol related, and those that are content/display/int=
erpretation related. =A0The first group could be done in the IETF, the seco=
nd in the W3C. =A0My thinking isn't especially well-formed on this as I don=
't have that grouping/taxonomy laid out.
>
> Admittedly HSTS mostly only applies to web browsers as well since they ar=
e the main target, and yet we're working on that here. =A0At the same time =
CORS and CSP are both presumably going to be done/continue at the W3C, and =
X-Frame-Options seems closer to them than it does to HSTS.
>
> Perhaps a good exercise would be for us to enumerate a bunch f the policy=
 mechanisms we've been envisioning, and then group them according to type, =
home, etc. =A0I don't know that we need a full taxonomy of them, =A0but I'm=
 open to being persuaded.

Yeah, X-Frame-Options seems like a special case of CSP.

Adam

From tony@att.com  Thu Sep  9 10:11:30 2010
Return-Path: <tony@att.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 088163A6866 for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 10:11:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.551
X-Spam-Level: 
X-Spam-Status: No, score=-105.551 tagged_above=-999 required=5 tests=[AWL=-0.244, BAYES_00=-2.599, MISSING_HEADERS=1.292, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J-0g2KruQF0j for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 10:11:24 -0700 (PDT)
Received: from mail167.messagelabs.com (mail167.messagelabs.com [216.82.253.179]) by core3.amsl.com (Postfix) with ESMTP id 4EAF53A6870 for <hasmat@ietf.org>; Thu,  9 Sep 2010 10:11:24 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: tony@att.com
X-Msg-Ref: server-2.tower-167.messagelabs.com!1284052307!16000721!1
X-StarScan-Version: 6.2.4; banners=-,-,-
X-Originating-IP: [144.160.20.146]
Received: (qmail 22040 invoked from network); 9 Sep 2010 17:11:48 -0000
Received: from sbcsmtp7.sbc.com (HELO mlpd194.enaf.sfdc.sbc.com) (144.160.20.146) by server-2.tower-167.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 9 Sep 2010 17:11:48 -0000
Received: from enaf.sfdc.sbc.com (localhost.localdomain [127.0.0.1]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o89HBG0u031271 for <hasmat@ietf.org>; Thu, 9 Sep 2010 13:11:16 -0400
Received: from klpd017.kcdc.att.com (klpd017.kcdc.att.com [135.188.40.86]) by mlpd194.enaf.sfdc.sbc.com (8.14.4/8.14.4) with ESMTP id o89HBC3i031180 for <hasmat@ietf.org>; Thu, 9 Sep 2010 13:11:12 -0400
Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klpd017.kcdc.att.com (8.14.4/8.14.4) with ESMTP id o89HBhj6013879 for <hasmat@ietf.org>; Thu, 9 Sep 2010 12:11:43 -0500
Received: from dns.maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by klpd017.kcdc.att.com (8.14.4/8.14.4) with ESMTP id o89HBeqX013792 for <hasmat@ietf.org>; Thu, 9 Sep 2010 12:11:41 -0500
Received: from [135.91.110.95] (dn135-91-110-95.dhcpn.ugn.att.com[135.91.110.95]) by maillennium.att.com (mailgw1) with ESMTP id <20100909171140gw100627pue> (Authid: tony); Thu, 9 Sep 2010 17:11:40 +0000
X-Originating-IP: [135.91.110.95]
Message-ID: <4C89154C.50903@att.com>
Date: Thu, 09 Sep 2010 13:11:40 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1
MIME-Version: 1.0
CC: IETF HASMAT list <hasmat@ietf.org>
References: <4C88AD91.4090301@gmx.de>
In-Reply-To: <4C88AD91.4090301@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [HASMAT] X-FRAME-OPTIONS
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 17:11:31 -0000

Has the ship sailed with respect to naming the header "FRAME-OPTIONS" 
instead of "X-FRAME-OPTIONS"?

     Tony Hansen

On 9/9/2010 5:49 AM, Julian Reschke wrote:
> Hi,
>
> see
>
> <http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-clickjacking-defenses.aspx> 
> and <http://www.mozilla.com/en-US/firefox/3.6.9/releasenotes/>.
>
> Is this something the WG should consider as well?
>
> Best regards, Julian

From ietf@adambarth.com  Thu Sep  9 10:17:14 2010
Return-Path: <ietf@adambarth.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A233E3A68A0 for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 10:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.051
X-Spam-Level: 
X-Spam-Status: No, score=-2.051 tagged_above=-999 required=5 tests=[AWL=-0.074, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EXhg19OY+w5w for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 10:17:12 -0700 (PDT)
Received: from mail-fx0-f44.google.com (mail-fx0-f44.google.com [209.85.161.44]) by core3.amsl.com (Postfix) with ESMTP id 628A13A6870 for <hasmat@ietf.org>; Thu,  9 Sep 2010 10:17:12 -0700 (PDT)
Received: by fxm18 with SMTP id 18so1233695fxm.31 for <hasmat@ietf.org>; Thu, 09 Sep 2010 10:17:39 -0700 (PDT)
Received: by 10.223.121.196 with SMTP id i4mr55130far.11.1284052659352; Thu, 09 Sep 2010 10:17:39 -0700 (PDT)
Received: from mail-px0-f172.google.com (mail-px0-f172.google.com [209.85.212.172]) by mx.google.com with ESMTPS id j14sm828846faa.23.2010.09.09.10.17.38 (version=SSLv3 cipher=RC4-MD5); Thu, 09 Sep 2010 10:17:39 -0700 (PDT)
Received: by pxi6 with SMTP id 6so749247pxi.31 for <hasmat@ietf.org>; Thu, 09 Sep 2010 10:17:37 -0700 (PDT)
Received: by 10.114.134.5 with SMTP id h5mr46691wad.145.1284052647435; Thu, 09 Sep 2010 10:17:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.91.140 with HTTP; Thu, 9 Sep 2010 10:16:56 -0700 (PDT)
In-Reply-To: <4C89154C.50903@att.com>
References: <4C88AD91.4090301@gmx.de> <4C89154C.50903@att.com>
From: Adam Barth <ietf@adambarth.com>
Date: Thu, 9 Sep 2010 10:16:56 -0700
Message-ID: <AANLkTi=3kZ5gCdGw=kkOk-kbY1cW_j7oooei8-+dhxaT@mail.gmail.com>
To: Tony Hansen <tony@att.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] X-FRAME-OPTIONS
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 17:17:14 -0000

We could add support for Frame-Options, but we would likely not remove
support for X-Frame-Options.  The name was chosen by Microsoft when
they shipped IE8.

Adam


On Thu, Sep 9, 2010 at 10:11 AM, Tony Hansen <tony@att.com> wrote:
> Has the ship sailed with respect to naming the header "FRAME-OPTIONS"
> instead of "X-FRAME-OPTIONS"?
>
> =A0 =A0Tony Hansen
>
> On 9/9/2010 5:49 AM, Julian Reschke wrote:
>>
>> Hi,
>>
>> see
>>
>>
>> <http://blogs.msdn.com/b/ie/archive/2009/01/27/ie8-security-part-vii-cli=
ckjacking-defenses.aspx>
>> and <http://www.mozilla.com/en-US/firefox/3.6.9/releasenotes/>.
>>
>> Is this something the WG should consider as well?
>>
>> Best regards, Julian
>
> _______________________________________________
> HASMAT mailing list
> HASMAT@ietf.org
> https://www.ietf.org/mailman/listinfo/hasmat
>

From dev.akhawe@gmail.com  Thu Sep  9 10:52:33 2010
Return-Path: <dev.akhawe@gmail.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F26223A6819 for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 10:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUrPFFOr9oFb for <hasmat@core3.amsl.com>; Thu,  9 Sep 2010 10:52:32 -0700 (PDT)
Received: from mail-qy0-f179.google.com (mail-qy0-f179.google.com [209.85.216.179]) by core3.amsl.com (Postfix) with ESMTP id DBAC73A68FA for <hasmat@ietf.org>; Thu,  9 Sep 2010 10:52:25 -0700 (PDT)
Received: by qyk9 with SMTP id 9so1842679qyk.10 for <hasmat@ietf.org>; Thu, 09 Sep 2010 10:52:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=Jf8G/PWfYUpPWg10fM2z+YSypvPAt31t+Ed0XVflHkU=; b=tY/+1lA8hWrfD7QA3r/cMpbcrZv3wz5dKOUge5gnJdtDt8c/fqj7/3BTNeIEM5DPBe 1UMtDwZg1cQqLUIaOrnOsb+Y7XY41Y/pwvBzQ0BcR/GosLvYv2+u/CIYI38BPtwSPP0l 3ni43I0XjSkKGeQjunidMh9Gf8MES/X3uK4LU=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=aI0+VT7SNLn0ieMLX0tqkpjeDpCRV1/E2hG7SzzAKU0it/9XMZvAKUcpJJUMojqCNx w7aJ4qCS/bJi570RoYgwrdsqv5apuqT8c4jW1NkIJkVaewCN2+tuaDvg86Ir7tHBF5eI 93YwTjFbV2GKyjmV1cn9Ke3AeUSE6XYVbpF0A=
Received: by 10.229.28.140 with SMTP id m12mr222692qcc.93.1284054773242; Thu, 09 Sep 2010 10:52:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.11.25 with HTTP; Thu, 9 Sep 2010 10:52:33 -0700 (PDT)
In-Reply-To: <AANLkTinF4=O4TRr_FS8QK+c5mDWdAAo5t=hJ4MAmXUoH@mail.gmail.com>
References: <4C88AD91.4090301@gmx.de> <5EE049BA3C6538409BBE6F1760F328ABEAF852CA70@DEN-MEXMS-001.corp.ebay.com> <AANLkTinF4=O4TRr_FS8QK+c5mDWdAAo5t=hJ4MAmXUoH@mail.gmail.com>
From: Devdatta Akhawe <dev.akhawe@gmail.com>
Date: Thu, 9 Sep 2010 10:52:33 -0700
Message-ID: <AANLkTi=PNP0oFRdLSXtFPiYKRy0Uiv07UeZmbFBkA16O@mail.gmail.com>
To: Adam Barth <ietf@adambarth.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF HASMAT list <hasmat@ietf.org>
Subject: Re: [HASMAT] X-FRAME-OPTIONS
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Sep 2010 17:52:33 -0000

>
> Yeah, X-Frame-Options seems like a special case of CSP.

Additionally, CSP's version has some of the flexibility that Adam was
talking about.

cheers
devdatta

From Jeff.Hodges@KingsMountain.com  Fri Sep 10 10:42:46 2010
Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 485893A6866 for <hasmat@core3.amsl.com>; Fri, 10 Sep 2010 10:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.122
X-Spam-Level: 
X-Spam-Status: No, score=-102.122 tagged_above=-999 required=5 tests=[AWL=0.143, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J+1-4nlGR0PL for <hasmat@core3.amsl.com>; Fri, 10 Sep 2010 10:42:45 -0700 (PDT)
Received: from cpoproxy1-pub.bluehost.com (cpoproxy1-pub.bluehost.com [69.89.21.11]) by core3.amsl.com (Postfix) with SMTP id 0BA3A3A67EB for <hasmat@ietf.org>; Fri, 10 Sep 2010 10:42:45 -0700 (PDT)
Received: (qmail 29747 invoked by uid 0); 10 Sep 2010 17:43:11 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy1.bluehost.com with SMTP; 10 Sep 2010 17:43:11 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=U2U1pje0B9HJSG/I4nF9ngO/kccaGxku2ZcF9qIaAGwNWwILmQUX9BrAIbX5wtSAJrxgL3iRUd87ees1JA/xyomNDvrzG/h2Vg2t7yMNuXebaI+OQucdbokfFz+E7Vct;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.49.193]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Ou7d0-0001fT-KH for hasmat@ietf.org; Fri, 10 Sep 2010 11:43:10 -0600
Message-ID: <4C8A6E2C.60707@KingsMountain.com>
Date: Fri, 10 Sep 2010 10:43:08 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: IETF HASMAT list <hasmat@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 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: [HASMAT] fyi: Stop it with the X- Already! (was: X-FRAME-OPTIONS)
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 17:42:46 -0000

Tangentially appropriate to keep in mind...

Stop it with the X- Already!
http://www.mnot.net/blog/2009/02/18/x-


=JeffH

From stpeter@stpeter.im  Fri Sep 10 10:44:17 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D616B3A68D7 for <hasmat@core3.amsl.com>; Fri, 10 Sep 2010 10:44:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.574
X-Spam-Level: 
X-Spam-Status: No, score=-102.574 tagged_above=-999 required=5 tests=[AWL=0.025, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T3ZTzIzBxDWK for <hasmat@core3.amsl.com>; Fri, 10 Sep 2010 10:44:13 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id 6E9633A67EB for <hasmat@ietf.org>; Fri, 10 Sep 2010 10:44:12 -0700 (PDT)
Received: from dhcp-64-101-72-245.cisco.com (dhcp-64-101-72-245.cisco.com [64.101.72.245]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 1FDDF400EE for <hasmat@ietf.org>; Fri, 10 Sep 2010 11:48:29 -0600 (MDT)
Message-ID: <4C8A6E86.4010009@stpeter.im>
Date: Fri, 10 Sep 2010 11:44:38 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.12) Gecko/20100824 Thunderbird/3.0.7
MIME-Version: 1.0
To: hasmat@ietf.org
References: <4C8A6E2C.60707@KingsMountain.com>
In-Reply-To: <4C8A6E2C.60707@KingsMountain.com>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [HASMAT] fyi: Stop it with the X- Already! (was: X-FRAME-OPTIONS)
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Sep 2010 17:44:17 -0000

On 9/10/10 11:43 AM, =JeffH wrote:
> Tangentially appropriate to keep in mind...
> 
> Stop it with the X- Already!
> http://www.mnot.net/blog/2009/02/18/x-

That reminds me, I need to update this:

http://tools.ietf.org/html/draft-saintandre-xdash-considered-harmful

/psa


From stpeter@stpeter.im  Wed Sep 15 11:48:22 2010
Return-Path: <stpeter@stpeter.im>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 13CC93A6914 for <hasmat@core3.amsl.com>; Wed, 15 Sep 2010 11:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.555
X-Spam-Level: 
X-Spam-Status: No, score=-102.555 tagged_above=-999 required=5 tests=[AWL=0.044, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4cmY+Op01lQb for <hasmat@core3.amsl.com>; Wed, 15 Sep 2010 11:48:21 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by core3.amsl.com (Postfix) with ESMTP id B03983A6A17 for <hasmat@ietf.org>; Wed, 15 Sep 2010 11:48:19 -0700 (PDT)
Received: from moveme.cisco.com (72-163-0-129.cisco.com [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id A27AC400EE for <hasmat@ietf.org>; Wed, 15 Sep 2010 12:53:01 -0600 (MDT)
Message-ID: <4C91150B.90708@stpeter.im>
Date: Wed, 15 Sep 2010 12:48:43 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.12) Gecko/20100824 Thunderbird/3.0.7
MIME-Version: 1.0
To: "hasmat@ietf.org" <hasmat@ietf.org>
X-Enigmail-Version: 1.0.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [HASMAT] IETF 79 preparations
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Sep 2010 18:48:22 -0000

Folks, this is just a quick note to let you all know that preparations
are proceeding for a websec meeting at IETF 79 in Beijing.

1. Tobias has requested a session from the Secretariat and I have added
a placeholder on the BoF wiki page (because the WG has not yet been
approved):

http://trac.tools.ietf.org/bof/trac/wiki/WikiStart

Tobias, it would help if you could fill in more of the information
there, such as the conflicts to avoid and the agenda + drafts. That
means we'll need to work on an agenda, but I assume Tobias and others
can work up a draft of that for discussion on the list here.

2. Would it be reasonable for one or two people to perhaps outline a
strawman I-D about the requirements / problem statement (it'll be fine
for it to be fairly incomplete with lots of "TDB" sections) before the
I-D cutoff date on October 18?

http://www.ietf.org/meeting/cutoff-dates-2010.html#IETF79

Volunteers? Perhaps something loosely based on Jeff and Andy's whitepaper?

3. The WG charter is currently in IESG/IAB internal review and will be
discussed during the IESG telechat on September 23, after which we'll
incorporate IESG/IAB feedback. Then it will go out for community-wide
review, perhaps leading to further tweaks as needed.

4. If and when the WG is approved (which I expect will happen, but I've
included the "if" so that we don't make any unwarranted assumptions),
we'll complete some administrivial tasks such as mailing list changes
(from hasmat to websec). But no matter what I think we can start
planning for the meeting in Beijing.

Feel free to ping the list if you have any questions or comments. And
we're still looking for a co-chair to work with Tobias, so contact me if
you're interested.

I think that's it for now!

Peter

-- 
Peter Saint-Andre
https://stpeter.im/



From hannes.tschofenig@gmx.net  Thu Sep 23 08:47:34 2010
Return-Path: <hannes.tschofenig@gmx.net>
X-Original-To: hasmat@core3.amsl.com
Delivered-To: hasmat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E18D3A6B13 for <hasmat@core3.amsl.com>; Thu, 23 Sep 2010 08:47:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.049
X-Spam-Level: 
X-Spam-Status: No, score=-101.049 tagged_above=-999 required=5 tests=[AWL=-0.750, BAYES_00=-2.599, MANGLED_WRLDWD=2.3, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tZxCO5STs0iO for <hasmat@core3.amsl.com>; Thu, 23 Sep 2010 08:47:24 -0700 (PDT)
Received: from mail.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 123673A6B0E for <hasmat@ietf.org>; Thu, 23 Sep 2010 08:47:21 -0700 (PDT)
Received: (qmail invoked by alias); 23 Sep 2010 15:47:48 -0000
Received: from unknown (EHLO [10.254.0.174]) [192.100.123.77] by mail.gmx.net (mp004) with SMTP; 23 Sep 2010 17:47:48 +0200
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18jGvMy03kj6rn+SWenppoaiabeO/HrmadVxniQ63 GKrFkewJFy2OUD
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1081)
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Date: Thu, 23 Sep 2010 18:47:46 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9EED822-5E5C-46CF-9A24-D4E6293BF328@gmx.net>
References: <20100920210002.96EF53A6876@core3.amsl.com>
To: IETF HASMAT list <hasmat@ietf.org>
X-Mailer: Apple Mail (2.1081)
X-Y-GMX-Trusted: 0
Subject: [HASMAT] Fwd: Internet Privacy Workshop: 8 and 9 December 2010
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Sep 2010 15:47:34 -0000

Hi all,=20

I believe that this workshop is relevant to this group. You may consider =
submitting a position paper.=20

Ciao
Hannes


Begin forwarded message:

> From: IETF Secretariat <ietf-secretariat@ietf.org>
> Date: September 21, 2010 12:00:02 AM GMT+03:00
> To: ietf-announce@ietf.org
> Subject: Internet Privacy Workshop: 8 and 9 December 2010=20
>=20
> The Internet Architecture Board (IAB), World Wide Web Consortium =
(W3C),
> Internet Society (ISOC) and Massachusetts Institute of Technology =
(MIT)
> will hold a joint Internet privacy workshop on 8 and 9 December 2010 =
at
> MIT, Cambridge, Massachusetts on the question:
>=20
> "How Can Technology Help to Improve Privacy on the Internet?"
>=20
> Information about who we are, what we own, what we have experienced, =
how
> we behave, where we are located, and how we can be reached are among =
the
> most personal pieces of information about us. This information is
> increasingly being made more easily available electronically via the
> Internet, often without the consent of the subject.
>=20
> The question for the workshop therefore is: How can we ensure that
> architectures and technologies for the Internet, including the World
> Wide Web, are developed in ways that respects users=82 intentions =
about
> their privacy?
>=20
> This workshop aims to explore the experience and approaches taken by
> developers of Internet including Web technology, when designing =
privacy
> into these protocols and architectures. Engineers know that many =
design
> considerations need to be taken into account when developing =
solutions.
> Balancing between the conflicting goals of openness, privacy, =
economics,
> and security is often difficult, as illustrated by Clark, et al. in
> "Tussle in Cyberspace: Defining Tomorrow's Internet", see
> http://groups.csail.mit.edu/ana/Publications/PubPDFs/Tussle2002.pdf
>=20
> As a member of the technical community, we invite you to share your
> experiences by participating in this important workshop. Workshop
> participants will focus on the core privacy challenges, the approaches
> taken to deal with them, and the status of the work in the field. The
> objective is to draw a relationship with other application areas and
> other privacy work in an effort to discuss how specific approaches can
> be generalized.
>=20
> Interested parties must submit a brief contribution describing their
> work or approach as it relates to the workshop theme. We welcome
> visionary ideas for how to tackle Internet privacy problems, as well =
as
> write-ups of existing concepts, deployed technologies, and
> lessons-learned from successful or failed attempts at deploying =
privacy
> technologies. Contributions are not required to be original in =
content.
>=20
> Submitters of accepted position papers will be invited to the =
workshop.
> The workshop will be structured as a series of working sessions,
> punctuated by invited speakers, who will present relevant background
> information or controversial ideas that will motivate participants to
> reach a deeper understanding of the subject. The organizing committee
> may ask submitters of particularly topical papers to present their =
ideas
> and experiences to the workshop.
>=20
> We will publish submitted position papers and slides together with a
> summary report of the workshop.
>=20
> There are no plans for any remote participation in this workshop.
>=20
> To be invited to the workshop, please submit position papers to
> privacy@iab.org by November, 5th 2010.
>=20
> More detailed information about the workshop, including further =
details
> about the position paper requirements, is available at:
> http://www.iab.org/about/workshops/privacy/
>=20
> We look forward to your input,
> Bernard Aboba (IAB), Trent Adams (ISOC), Daniel Appelquist (W3C), =
Karen
> O'Donoghue (ISOC), Jon Peterson (IAB), Thomas Roessler (W3C), Karen
> Sollins (MIT), Hannes Tschofenig (IAB)
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce


From root@core3.amsl.com  Tue Sep 28 10:15:12 2010
Return-Path: <root@core3.amsl.com>
X-Original-To: hasmat@ietf.org
Delivered-To: hasmat@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 0) id B3DE63A6DC6; Tue, 28 Sep 2010 10:15:05 -0700 (PDT)
From: IESG Secretary <iesg-secretary@ietf.org>
To: ietf-announce@ietf.org
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20100928171508.B3DE63A6DC6@core3.amsl.com>
Date: Tue, 28 Sep 2010 10:15:06 -0700 (PDT)
Cc: hasmat@ietf.org
Subject: [HASMAT] WG Review: Web Security (websec)
X-BeenThere: hasmat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.org
List-Id: HTTP Application Security Minus Authentication and Transport <hasmat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hasmat>
List-Post: <mailto:hasmat@ietf.org>
List-Help: <mailto:hasmat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>, <mailto:hasmat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Sep 2010 17:15:12 -0000

A new IETF working group has been proposed in the Applications Area.  The
IESG has not made any determination as yet. The following draft charter
was submitted, and is provided for informational purposes only. Please
send your comments to the IESG mailing list (iesg@ietf.org) by Tuesday,
October 5, 2010.  

Web Security (websec)
---------------------------------------------
Status: Proposed Working Group
Last updated: 2010-09-23

Chairs(s)
   Tobias Gondrom <tobias.gondrom@gondrom.org>

Applications Area Directors:
   Alexey Melnikov <alexey.melnikov@isode.com>
   Peter Saint-Andre <stpeter@stpeter.im>

Applications Area Advisor:
   Peter Saint-Andre <stpeter@stpeter.im>

Security Area Advisor:
   Sean Turner <turners@ieca.com>

Mailing Lists:
  General Discussion: hasmat@ietf.org
  To Subscribe: <https://www.ietf.org/mailman/listinfo/hasmat>
  Archive: <http://www.ietf.org/mail-archive/web/hasmat/>
  [to be changed to websec@ietf.org if approved]

Problem Statement

Although modern Web applications are built on top of HTTP, they provide
rich functionality and have requirements beyond the original vision of
static web pages.  HTTP, and the applications built on it, have evolved
organically.  Over the past few years, we have seen a proliferation of
AJAX-based web applications (AJAX being shorthand for asynchronous
JavaScript and XML), as well as Rich Internet Applications (RIAs), based
on so-called Web 2.0 technologies.  These applications bring both
luscious eye-candy and convenient functionality, e.g. social networking,
to their users, making them quite compelling.  At the same time, we are
seeing an increase in attacks against these applications and their
underlying technologies.

The list of attacks is long and includes Cross-Site-Request Forgery
(CSRF)-based attacks, content-sniffing, cross-site-scripting (XSS)
attacks, attacks against browsers supporting anti-XSS policies,
clickjacking attacks, malvertising attacks, as well as man-in-the-middle
(MITM) attacks against "secure" (e.g. Transport Layer Security
(TLS/SSL)-based) web sites along with distribution of the tools to carry
out such attacks (e.g. sslstrip).

Objectives and Scope

With the arrival of new attacks the introduction of new web security
indicators, security techniques, and policy communication mechanisms
have sprinkled throughout the various layers of the Web and HTTP.

The goal of this working group is to compose an overall "problem
statement and requirements" document derived from surveying the
issues outlined in the above section ([1] provides a starting point).
The requirements guiding the work will be taken from the Web
application and Web security communities.  The scope of this document
is HTTP applications security, but does not include HTTP authentication,
nor internals of transport security which are addressed by other working
groups (although it may make reference to transport security as an
available security "primitive").  See the "Out of Scope" section, below.

Additionally, the WG will standardize a small number of selected
specifications that have proven to improve security of Internet
Web applications.  Initial work will be the following topics:

  - Same origin policy, as discussed in draft-abarth-origin
    (see also Appendices A and B, below)

  - HTTP Strict transport security, as discussed in
    draft-hodges-strict-transport-sec

  - Media type sniffing, as discussed in draft-abarth-mime-sniff

This working group will work closely with IETF Apps Area WGs (such as
HYBI, HTTPstate, and HTTPbis), as well as appropriate W3C working
group(s) (e.g. HTML, WebApps).

Out of Scope

As noted in the objectives and scope (above), this working group's
scope does not include working on HTTP Authentication nor underlying
transport (secure or not) topics. So, for example, these items are
out-of-scope for this WG:

  - Replacements for BASIC and DIGEST authentication

  - New transports (e.g. SCTP and the like)

Deliverables

1. A document illustrating the security problems Web applications are
facing and listing design requirements.  This document shall be
Informational.

2. A selected set of technical specifications documenting deployed
HTTP-based Web security solutions. These documents shall be Standards
Track.

Goals and Milestones

Oct 2010    Submit "HTTP Application Security Problem Statement and
           Requirements" as initial WG item.

Oct 2010    Submit "Media Type Sniffing" as initial WG item.

Oct 2010    Submit "Web Origin Concept" as initial WG item.

Oct 2010    Submit "Strict Transport Security" as initial WG item.

Feb 2011    Submit "HTTP Application Security Problem Statement and
           Requirements" to the IESG for consideration as an
           Informational RFC.

Mar 2011    Submit "Media Type Sniffing" to the IESG for consideration
           as a Standards Track RFC.

Mar 2011    Submit "Web Origin Concept" to the IESG for consideration as
           a Standards Track RFC.

Mar 2011    Submit "Strict Transport Security" to the IESG for
           consideration as a Standards Track RFC.

Apr 2011    Possible re-chartering

References

[1] Hodges and Steingruebl, "The Need for a Coherent Web Security Policy
Framework", W2SP position paper, 2010.
http://w2spconf.com/2010/papers/p11.pdf

Appendices

A. Relationship between origin work in IETF WebSec and W3C HTML WG

draft-abarth-origin defines the nuts-and-bolts of working with
origins (computing them from URIs, comparing them to each other, etc).
HTML5 defines HTML-specific usage of origins.  For example, when
making an HTTP request, HTML5 defines how to compute which origin
among all the origins rendering HTML is the one responsible for making
the request.  draft-abarth-origin then takes that origin, serializes
it to a string, and shoves it in a header.

B. Origin work may yield two specifications

There also seems to be demand for a document that describes the
same-origin security model overall.  However, it seems like that
document ought to be more informative rather than normative. The
working group may split draft-abarth-origin into separate informative
and standards track specifications, the former describing same-origin
security model, and the latter specifying the nuts-and-bolts of working
with origins (computing them from URLs, comparing them to each other,
etc).
