Re: [http-state] 'HTTP State Management Mechanism' to Proposed Standard

=JeffH <Jeff.Hodges@KingsMountain.com> Thu, 03 March 2011 18:19 UTC

Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: http-state@core3.amsl.com
Delivered-To: http-state@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 664983A6A28 for <http-state@core3.amsl.com>; Thu, 3 Mar 2011 10:19:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.307
X-Spam-Level:
X-Spam-Status: No, score=-102.307 tagged_above=-999 required=5 tests=[AWL=-0.042, 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 cWP-tQ0mqquS for <http-state@core3.amsl.com>; Thu, 3 Mar 2011 10:19:02 -0800 (PST)
Received: from cpoproxy1-pub.bluehost.com (cpoproxy1-pub.bluehost.com [69.89.21.11]) by core3.amsl.com (Postfix) with SMTP id 46D633A69ED for <http-state@ietf.org>; Thu, 3 Mar 2011 10:19:02 -0800 (PST)
Received: (qmail 8280 invoked by uid 0); 3 Mar 2011 18:20:10 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy1.bluehost.com with SMTP; 3 Mar 2011 18:20:09 -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:CC:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=eC4+8+qfAd2cyB1GNt+Jr67XMH5u5udma+4vJEwIh+XXnXn/RFAQ1TDz6vnBepkKu2GJtOxXwcEDWQc7GKaNjzeWUu7iKtKfc2uO1M25IsWcDHS0Kv0ZJXb18s/EdjHT;
Received: from outbound4.ebay.com ([216.113.168.128] helo=[10.244.137.181]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1PvD8C-0007Rn-Kz; Thu, 03 Mar 2011 11:20:08 -0700
Message-ID: <4D6FDBD7.5020907@KingsMountain.com>
Date: Thu, 03 Mar 2011 10:20:07 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
MIME-Version: 1.0
To: IETF HTTP State WG <http-state@ietf.org>, Internet Architecture Board <iab@iab.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}
Cc: httpstate chair <httpstate-chairs@tools.ietf.org>
Subject: Re: [http-state] 'HTTP State Management Mechanism' to Proposed Standard
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/http-state>
List-Post: <mailto:http-state@ietf.org>
List-Help: <mailto:http-state-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-state>, <mailto:http-state-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2011 18:19:03 -0000

This is great news!

 > Personnel
 >
 >    The Document Shepherd is Jeff Hodges.  The Responsible Area
 >    Director is Peter Saint-Andre.

But the person who did the vast majority of the work, and who's idea it was to 
tackle this in the first place, is _Adam Barth_, who deserves an outsized chunk 
of the credit. Thanks for hanging in there and making this happen Adam. 
Additionally, Peter Saint-Andre's expert navigation of the IETF document and 
IESG processes was an instrumental contribution. Thanks Peter.

I also thank the broad array of participants in the working group, both online 
and in person at our sessions at IETF meetings -- your contributions were 
critical to crafting a high-quality spec and navigating the approval process. 
THANKS.

This spec is a milestone in that HTTP "cookie" syntax and behavior has been 
effectively a matter of undocumented folklore all these years. Getting this 
finally explicitly documented will be a key underlying piece of moving "the 
Web", and the wider Internet its built upon, on towards its next stage(s).

thanks again,

=JeffH
IETF HTTP State WG Chair
PayPal Information Risk Management