Re: [http-state] RFC 6265 on HTTP State Management Mechanism
Peter Saint-Andre <stpeter@stpeter.im> Thu, 28 April 2011 04:32 UTC
Return-Path: <stpeter@stpeter.im>
X-Original-To: http-state@ietfa.amsl.com
Delivered-To: http-state@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4285DE0682 for <http-state@ietfa.amsl.com>; Wed, 27 Apr 2011 21:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level:
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rgbUUmAzGv-I for <http-state@ietfa.amsl.com>; Wed, 27 Apr 2011 21:32:08 -0700 (PDT)
Received: from stpeter.im (stpeter.im [207.210.219.233]) by ietfa.amsl.com (Postfix) with ESMTP id 8DFD2E0680 for <http-state@ietf.org>; Wed, 27 Apr 2011 21:32:08 -0700 (PDT)
Received: from squire.local (198-135-0-233.cisco.com [198.135.0.233]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 8B47240022 for <http-state@ietf.org>; Wed, 27 Apr 2011 22:36:27 -0600 (MDT)
Message-ID: <4DB8EDC7.9060005@stpeter.im>
Date: Thu, 28 Apr 2011 00:32:07 -0400
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.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: http-state@ietf.org
References: <20110427233455.0E95BE07A5@rfc-editor.org>
In-Reply-To: <20110427233455.0E95BE07A5@rfc-editor.org>
X-Enigmail-Version: 1.1.1
OpenPGP: url=http://www.saint-andre.com/me/stpeter.asc
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="------------ms050602060003080001000901"
Subject: Re: [http-state] RFC 6265 on HTTP State Management Mechanism
X-BeenThere: http-state@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discuss HTTP State Management Mechanism <http-state.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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, 28 Apr 2011 04:32:09 -0000
Congratulations to Adam and to the WG on completing this work! On 4/27/11 7:34 PM, rfc-editor@rfc-editor.org wrote: > > A new Request for Comments is now available in online RFC libraries. > > > RFC 6265 > > Title: HTTP State Management Mechanism > Author: A. Barth > Status: Standards Track > Stream: IETF > Date: April 2011 > Mailbox: abarth@eecs.berkeley.edu > Pages: 37 > Characters: 79724 > Obsoletes: RFC2965 > > I-D Tag: draft-ietf-httpstate-cookie-23.txt > > URL: http://www.rfc-editor.org/rfc/rfc6265.txt > > This document defines the HTTP Cookie and Set-Cookie header fields. > These header fields can be used by HTTP servers to store state > (called cookies) at HTTP user agents, letting the servers maintain a > stateful session over the mostly stateless HTTP protocol. Although > cookies have many historical infelicities that degrade their security > and privacy, the Cookie and Set-Cookie header fields are widely used > on the Internet. This document obsoletes RFC 2965. [STANDARDS-TRACK] > > This document is a product of the HTTP State Management Mechanism Working Group of the IETF. > > This is now a Proposed Standard Protocol. > > STANDARDS TRACK: This document specifies an Internet standards track > protocol for the Internet community,and requests discussion and suggestions > for improvements. Please refer to the current edition of the Internet > Official Protocol Standards (STD 1) for the standardization state and > status of this protocol. Distribution of this memo is unlimited. > > This announcement is sent to the IETF-Announce and rfc-dist lists. > To subscribe or unsubscribe, see > http://www.ietf.org/mailman/listinfo/ietf-announce > http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist > > For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. > For downloading RFCs, see http://www.rfc-editor.org/rfc.html. > > Requests for special distribution should be addressed to either the > author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless > specifically noted otherwise on the RFC itself, all RFCs are for > unlimited distribution. > > > The RFC Editor Team > Association Management Solutions, LLC > > > _______________________________________________ > http-state mailing list > http-state@ietf.org > https://www.ietf.org/mailman/listinfo/http-state
- [http-state] RFC 6265 on HTTP State Management Me… rfc-editor
- Re: [http-state] RFC 6265 on HTTP State Managemen… Peter Saint-Andre
- Re: [http-state] RFC 6265 on HTTP State Managemen… Richard Moore