Re: [HASMAT] moving forward

=JeffH <Jeff.Hodges@KingsMountain.com> Tue, 24 August 2010 23:39 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 E1F043A6953 for <hasmat@core3.amsl.com>; Tue, 24 Aug 2010 16:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.804
X-Spam-Level:
X-Spam-Status: No, score=-100.804 tagged_above=-999 required=5 tests=[AWL=-0.953, BAYES_40=-0.185, 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 yvOBPef8MdV5 for <hasmat@core3.amsl.com>; Tue, 24 Aug 2010 16:39:02 -0700 (PDT)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id C703A3A6960 for <hasmat@ietf.org>; Tue, 24 Aug 2010 16:39:02 -0700 (PDT)
Received: (qmail 7308 invoked by uid 0); 24 Aug 2010 23:39:35 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 24 Aug 2010 23:39:35 -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=Q3nmMz9+QWR4ng3KZc9cR3T0lqP3/T6DpHKikNs8sU2E4ZnwsXvTOSUWDYLgB+X6YAXN+gnGmcPcUjAbDbO9BrXNy9zhQxDD8aMDXYky8quGgp8f8dIuctcWlwrewHM0;
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 1Oo35b-0005eO-Fr for hasmat@ietf.org; Tue, 24 Aug 2010 17:39:35 -0600
Message-ID: <4C745837.50104@KingsMountain.com>
Date: Tue, 24 Aug 2010 16:39:35 -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: Tue, 24 Aug 2010 23:39:04 -0000

Thanks Peter for keeping the ball moving.

 > Following up on the successful BoF we held in Maastricht,

yea! thanks all who attended (it was standing-room-only)


 > I'd like to
 > keep us moving toward formation of a working group. Here are some open
 > tasks:
 >
 > 1. Chairs. Tobias Gondrom (currently co-chair of the LTANS WG in the
 > Security Area) has stepped forward to volunteer and I think he'll make a
 > good co-chair. Thanks, Tobias!

Indeed, thanks Tobias.


 > However, we need someone to work with Tobias,

thoughts / volunteers?

I'm presently slated to hack on specs, thus am not a chair candidate.


 > 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. Jeff or Hannes, could you send updated charter text to the
 > list for discussion?

working on it. tomorrow or Wed.



 > 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

It isn't descriptive unless one knows what the acronym represents -- HTTP app 
sec minus authn & transport -- and then it's very descriptive.

It's also sort of an "inside joke" in that HTTP authn is something that gets 
derided often but no one has really wanted to take up and try to do something 
about (AFAIK Peter S-A came up with the HASMAT moniker), and transport 
security, ie TLS/SSL, is addressed elsewhere already, and no one really wants 
to step on their toes. Hence the "HASMAT" double-entendre.

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

"websec" will be easier for IETF newbies to find and grok than "hasmat". Tho it 
might get a bit confusing wrt the in-genesis W3C "WebAppSec" WG.

more thoughts?

=JeffH