Re: [HASMAT] moving forward -

=JeffH <Jeff.Hodges@KingsMountain.com> Thu, 02 September 2010 22:38 UTC

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