From dromasca@avaya.com Wed Nov 4 01:22:56 2009 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9E6573A6A9B for ; Wed, 4 Nov 2009 01:22:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.475 X-Spam-Level: X-Spam-Status: No, score=-2.475 tagged_above=-999 required=5 tests=[AWL=0.124, 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 GDCE0pCcATmq for ; Wed, 4 Nov 2009 01:22:56 -0800 (PST) Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by core3.amsl.com (Postfix) with ESMTP id D9C4F3A6995 for ; Wed, 4 Nov 2009 01:22:55 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.44,679,1249272000"; d="scan'208";a="189123300" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 04 Nov 2009 04:23:16 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.12]) by co300216-co-erhwest-out.avaya.com with ESMTP; 04 Nov 2009 04:23:16 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Wed, 4 Nov 2009 10:22:55 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: No AAA-Doctors meeting in Hiroshima Thread-Index: AcpdMGP3LteOBQ8WQmKbNz/sIB4y1Q== From: "Romascanu, Dan (Dan)" To: Subject: [AAA-DOCTORS] No AAA-Doctors meeting in Hiroshima X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Nov 2009 09:22:56 -0000 I received only two confirmations of participation at the AAA-Doctors lunch in Hiroshima. I suggest that we skip it this time. We can plan for a virtual meeting (conference call) in the weeks after Hiroshima. Of course folks who are in Hiroshima and wish to talk with me about AAA-related issues are welcome to approach me at any time during the meeting. Regards, Dan From dromasca@avaya.com Fri Nov 13 05:20:34 2009 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F02103A6A66; Fri, 13 Nov 2009 05:20:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.506 X-Spam-Level: X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=0.093, 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 JLUW2bBLpksq; Fri, 13 Nov 2009 05:20:33 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id AD3213A67E1; Fri, 13 Nov 2009 05:20:29 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.44,736,1249272000"; d="scan'208";a="163176913" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 13 Nov 2009 08:20:57 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.16]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 13 Nov 2009 08:20:56 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 13 Nov 2009 14:20:40 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for November 19, 2009 Telechat thread-index: Acpj/kuv0luLOSvDRmihmkYlJ+mLJgAZHk8A From: "Romascanu, Dan (Dan)" To: , , , "IETF DNS Directorate" Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for November 19, 2009 Telechat X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Nov 2009 13:20:35 -0000 Please find below the preliminary agenda of the 11/19 IESG telechat. Please send me your questions, comments and concerns before 11/18 COB.=20 Thanks and Regards, Dan =20 2.1 WG Submissions 2.1.1 New Item o draft-ietf-syslog-sign-28.txt Signed syslog Messages (Proposed Standard) - 1 of 8=20 Token: Pasi Eronen o draft-ietf-mboned-rfc3171bis-07.txt IANA Guidelines for IPv4 Multicast Address Assignments (BCP) - 2 of 8 Token: Ron Bonica o draft-ietf-6man-overlap-fragment-03.txt Handling of overlapping IPv6 fragments (Proposed Standard) - 3 of 8=20 Note: Brian Haberman (brian@innovationslab.net) is the document shepherd.=20 Token: Jari Arkko o draft-ietf-tsvwg-rsvp-l3vpn-03.txt Support for RSVP in Layer 3 VPNs (Proposed Standard) - 4 of 8=20 Token: Magnus Westerlund o draft-ietf-pkix-authorityclearanceconstraints-03.txt Clearance Attribute and Authority Clearance Constraints Certificate=20 Extension (Proposed Standard) - 5 of 8=20 Token: Tim Polk o draft-ietf-dna-simple-11.txt Simple procedures for Detecting Network Attachment in IPv6 (Proposed Standard) - 6 of 8=20 Note: (no document shepherd)=20 Token: Jari Arkko o draft-ietf-mmusic-connectivity-precon-06.txt Connectivity Preconditions for Session Description Protocol Media Streams=20 (Proposed Standard) - 7 of 8=20 Note: Please note sec-dir review comments were addressed in RFC Ed Note..=20 Document Shepherd: Jean-Francois Mule (jf.mule@cablelabs.com)=20 Token: Cullen Jennings o draft-ietf-forces-sctptml-06.txt SCTP based TML (Transport Mapping Layer) for ForCES protocol (Proposed =20 Standard) - 8 of 8=20 Note: The document shepherd has been changed to Joel Halpern=20 (jmh@joelhalpern.com).=20 Token: Ross Callon 2.1.2 Returning Item o draft-ietf-mipshop-pfmipv6-09.txt Fast Handovers for Proxy Mobile IPv6 (Proposed Standard) - 1 of 2=20 Note: Vijay Devarapalli (vijay@wichorus.com) is the document shepherd. =20 Token: Jari Arkko o draft-ietf-l3vpn-2547bis-mcast-bgp-08.txt BGP Encodings and Procedures for Multicast in MPLS/BGP IP VPNs (Proposed=20 Standard) - 2 of 2=20 Token: Ross Callon 2.2 Individual Submissions 2.2.1 New Item NONE 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item o draft-ietf-ccamp-mpls-graceful-shutdown-12.txt Graceful Shutdown in MPLS and Generalized MPLS Traffic Engineering Networks=20 (Informational) - 1 of 3=20 Note: Lou Berger (lberger@labn.net) is the document shepherd.=20 Token: Adrian Farrel o draft-ietf-bmwg-ipsec-term-12.txt Terminology for Benchmarking IPsec Devices (Informational) - 2 of 3=20 Note: Al Morton (acmorton@att.com) is the document shepherd.=20 Token: Ron Bonica o draft-ietf-bmwg-ipsec-meth-05.txt Methodology for Benchmarking IPsec Devices (Informational) - 3 of 3=20 Note: Al Morton (acmorton@att.com) is the document shepherd.=20 Token: Ron Bonica 3.1.2 Returning Item NONE 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item o draft-turner-deviceowner-attribute-02.txt Device Owner Attribute (Informational) - 1 of 4=20 Token: Tim Polk o draft-turner-clearancesponsor-attribute-02.txt Clearance Sponsor Attribute (Informational) - 2 of 4=20 Token: Tim Polk o draft-carpenter-renum-needs-work-04.txt Renumbering still needs work (Informational) - 3 of 4=20 Token: Dan Romascanu o draft-melnikov-sasl-scram-ldap-04.txt LDAP schema for storing SCRAM secrets (Informational) - 4 of 4=20 Token: Pasi Eronen 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item NONE 3.3.2 Returning Item o draft-levy-sip-diversion-10.txt Diversion Indication in SIP (Historic) - 1 of 1=20 Token: Robert Sparks 3.3.3 For Action o draft-nsri-aria-02.txt A Description of the ARIA Encryption Algorithm (Informational) - 1 of 1=20 Token: Russ Housley 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review o HTTP State Management Mechanism (http-state) - 1 of 1 Token: Lisa Dusseault 4.1.2 Proposed for Approval o Internet Area Working Group (intareawg) - 1 of 1 Token: Jari Arkko 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval o Handover Keying (hokey) - 1 of 1 Token: Tim Polk From dromasca@avaya.com Sun Nov 29 04:59:14 2009 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 61BB53A672F; Sun, 29 Nov 2009 04:59:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.435 X-Spam-Level: X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[AWL=0.164, 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 wWvLLFjhBHK9; Sun, 29 Nov 2009 04:59:13 -0800 (PST) Received: from de307622-de-outbound.net.avaya.com (de307622-de-outbound.net.avaya.com [198.152.71.100]) by core3.amsl.com (Postfix) with ESMTP id 2D3E83A6892; Sun, 29 Nov 2009 04:59:11 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.47,307,1257138000"; d="scan'208";a="164802636" Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by de307622-de-outbound.net.avaya.com with ESMTP; 29 Nov 2009 07:58:54 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15]) by co300216-co-erhwest-out.avaya.com with ESMTP; 29 Nov 2009 07:58:53 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Sun, 29 Nov 2009 13:58:39 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: PRELIMINARY Agenda and Package for December 3, 2009 Telechat Thread-Index: Acpvtl/KjSHvH0wVQZytyL81OpwI3wBPMOUw From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , , "MIB Doctors (E-mail)" Subject: [AAA-DOCTORS] FW: PRELIMINARY Agenda and Package for December 3, 2009 Telechat X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Nov 2009 12:59:14 -0000 Please find below the preliminary agenda of the 12/3 IESG telechat. Please send me your questions, comments and concerns about the documents and charters brought for approval before 1`2/2 COB.=20 Thanks and Regards, Dan -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Saturday, November 28, 2009 1:07 AM 2.1 WG Submissions 2.1.1 New Item o draft-ietf-sasl-gs2-18.txt Using GSS-API Mechanisms in SASL: The GS2 Mechanism Family (Proposed Standard) - 1 of 8=20 Note: Alexey Melnikov (alexey.melnikov@isode.com) is the document shepherd=20 Token: Pasi Eronen o draft-ietf-ipfix-mib-08.txt Definitions of Managed Objects for IP Flow Information Export (Proposed=20 Standard) - 2 of 8=20 Token: Dan Romascanu o draft-ietf-tsvwg-rsvp-l3vpn-05.txt Support for RSVP in Layer 3 VPNs (Proposed Standard) - 3 of 8=20 Token: Magnus Westerlund o draft-ietf-pim-sm-linklocal-09.txt Authentication and Confidentiality in PIM-SM Link-local Messages (Proposed=20 Standard) - 4 of 8=20 Note: Document shepherd is Stig Venaas =20 Token: Adrian Farrel o draft-ietf-ospf-af-alt-09.txt Support of address families in OSPFv3 (Proposed Standard) - 5 of 8=20 Token: Ross Callon o draft-ietf-ospf-te-node-addr-06.txt Advertising a Router's Local Addresses in OSPF TE Extensions (Proposed =20 Standard) - 6 of 8=20 Note: Acee Lindem (acee@redback.com) is the document shepherd.=20 Token: Ross Callon o draft-ietf-ccamp-lsp-dppm-10.txt Label Switched Path (LSP) Dynamic Provisioning Performance Metrics in Generalized MPLS Networks (Proposed Standard) - 7 of 8=20 Note: Lou Berger (lberger@labn.net) is the document shepherd.=20 Token: Adrian Farrel o draft-ietf-16ng-ipv4-over-802-dot-16-ipcs-06.txt Transmission of IPv4 packets over IEEE 802.16's IP Convergence Sublayer=20 (Proposed Standard) - 8 of 8=20 Note: Gabriel Montenegro (g_e_montenegro@yahoo.com) is the document=20 shepherd.=20 Token: Ralph Droms 2.1.2 Returning Item NONE 2.2 Individual Submissions 2.2.1 New Item o draft-dusseault-http-patch-16.txt PATCH Method for HTTP (Proposed Standard) - 1 of 4=20 Note: Mark Nottingham agreed to be the document shepherd..=20 Token: Alexey Melnikov o draft-klensin-ftp-registry-02.txt FTP Extension Registry (Proposed Standard) - 2 of 4=20 Note: Barry Leiba is the document=20 shepherd..=20 Token: Alexey Melnikov o draft-nottingham-site-meta-04.txt Defining Well-Known URIs (Proposed Standard) - 3 of 4=20 Token: Lisa Dusseault o draft-melnikov-imap-keywords-07.txt IMAP4 Keyword Registry (Proposed Standard) - 4 of 4=20 Note: Barry Leiba is the document shepherd.=20 Token: Lisa Dusseault 2.2.2 Returning Item NONE 3. Document Actions 3.1 WG Submissions Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.1.1 New Item o draft-ietf-hip-native-api-09.txt Basic Socket Interface Extensions for Host Identity Protocol (HIP)=20 (Experimental) - 1 of 1=20 Note: Gonzalo Camarillo (Gonzalo.Camarillo@ericsson.com) is the document=20 shepherd.=20 Token: Ralph Droms 3.1.2 Returning Item o draft-ietf-csi-sndp-prob-03.txt Securing Neighbor Discovery Proxy Problem Statement (Informational) - 1 of=20 1=20 Note: The document shepherd is Marcelo Bagnulo (marcelo@it.uc3m.es)=20 Token: Ralph Droms 3.2 Individual Submissions Via AD Reviews should focus on these questions: "Is this document a reasonable contribution to the area of Internet engineering which it covers? If not, what changes would make it so?" 3.2.1 New Item o draft-combes-ipdvb-mib-rcs-08.txt The SatLabs Group DVB-RCS MIB (Informational) - 1 of 3=20 Note: Document Shepherd is Gorry Fairhurst =20 Token: Jari Arkko o draft-reschke-rfc2731bis-04.txt RFC 2731 ("Encoding Dublin Core Metadata in HTML") is Obsolete=20 (Informational) - 2 of 3=20 Note: Bernard Desruisseaux is the=20 document shepherd.. RFC Editor seems to be fine with the idea of obsoleting=20 an RFC submitted directly to RFC Editor (e.g. RFC 2731) with an AD=20 sponsored document.=20 Token: Alexey Melnikov o draft-hammer-oauth-07.txt The OAuth Core 1.0 Protocol (Informational) - 3 of 3=20 Token: Lisa Dusseault 3.2.2 Returning Item NONE 3.3 Independent Submissions Via RFC Editor The IESG will use RFC 3932 responses: 1) The IESG has not found any conflict between this document and IETF work; 2) The IESG thinks that this work is related to IETF work done in WG , but this does not prevent publishing; 3) The IESG thinks that publication is harmful to work in WG and recommends not publishing at this time; 4) The IESG thinks that this document violates the IETF procedures for and should therefore not be published without IETF review and IESG approval; 5) The IESG thinks that this document extends an IETF protocol in a way that requires IETF review and should therefore not be published without IETF review and IESG approval. The document shepherd must propose one of these responses in the Data Tracker note and supply complete text in the IESG Note portion of the write-up. The Area Director ballot positions indicate consensus with the response proposed by the document shepherd. Other matters may be recorded in comments, and the comments will be passed on to the RFC Editor as community review of the document. 3.3.1 New Item NONE 3.3.2 Returning Item o draft-wu-softwire-4over6-03.txt 4over6 Transit Solution using IP Encapsulation and MP-BGP Extensions (Experimental) - 1 of 1=20 Token: Ralph Droms 4. Working Group Actions 4.1 WG Creation 4.1.1 Proposed for IETF Review NONE 4.1.2 Proposed for Approval o HTTP State Management Mechanism (httpstate) - 1 of 1 Token: Lisa Dusseault 4.2 WG Rechartering 4.2.1 Under evaluation for IETF Review NONE 4.2.2 Proposed for Approval NONE From dromasca@avaya.com Mon Nov 30 07:50:06 2009 Return-Path: X-Original-To: aaa-doctors@core3.amsl.com Delivered-To: aaa-doctors@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D646D3A68E4; Mon, 30 Nov 2009 07:50:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.442 X-Spam-Level: X-Spam-Status: No, score=-2.442 tagged_above=-999 required=5 tests=[AWL=0.157, 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 DytmFDaKBDo3; Mon, 30 Nov 2009 07:50:05 -0800 (PST) Received: from nj300815-nj-outbound.net.avaya.com (nj300815-nj-outbound.net.avaya.com [198.152.12.100]) by core3.amsl.com (Postfix) with ESMTP id C77873A6937; Mon, 30 Nov 2009 07:50:04 -0800 (PST) X-IronPort-AV: E=Sophos;i="4.47,314,1257138000"; d="scan'208";a="182076605" Received: from unknown (HELO nj300815-nj-erheast.avaya.com) ([198.152.6.5]) by nj300815-nj-outbound.net.avaya.com with ESMTP; 30 Nov 2009 10:49:56 -0500 Received: from unknown (HELO 307622ANEX5.global.avaya.com) ([135.64.140.15]) by nj300815-nj-erheast-out.avaya.com with ESMTP; 30 Nov 2009 10:49:56 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 30 Nov 2009 16:49:52 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: WG Review: HTTP State Management Mechanism (httpstate) Thread-Index: AcptL/eSOFPid35ASKm8nDKgozEwxAEpL5/A From: "Romascanu, Dan (Dan)" To: , "IETF DNS Directorate" , "MIB Doctors (E-mail)" , Subject: [AAA-DOCTORS] FW: WG Review: HTTP State Management Mechanism (httpstate) X-BeenThere: aaa-doctors@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: AAA Doctors E-mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Nov 2009 15:50:07 -0000 =20 -----Original Message----- From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org] On Behalf Of IESG Secretary Sent: Tuesday, November 24, 2009 8:00 PM To: new-work@ietf.org Subject: WG Review: HTTP State Management Mechanism (httpstate)=20 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, December 1, 2009. HTTP State Management Mechanism (httpstate) --------------------------------------------------- Current Status: Proposed Working Group Last modified: 2009-11-11 Chair(s): TBD Applications Area Director(s): Lisa Dusseault Alexey Melnikov=20 Applications Area Advisor: Lisa Dusseault=20 Mailing Lists:=20 General Discussion: http-state@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/http-state Archive: http://www.ietf.org/mail-archive/web/http- state/current/maillist.html Alternative Archive: http://groups.google.com/group/http-state =20 Description of Working Group: =20 The HTTP State Management Mechanism (aka Cookies) was originally created by Netscape Communications in their informal Netscape cookie specification ("cookie_spec.html"), from which formal specifications RFC 2109 and RFC 2965 evolved. The formal specifications, however, were never fully implemented in practice; RFC 2109, in addition to cookie_spec.html, more closely resemble real-world implementations than RFC 2965, even though RFC 2965 officially obsoletes the former.=20 Compounding the problem are undocumented features (such as HTTPOnly), and varying behaviors among real-world implementations. =20 The working group will create a new RFC that obsoletes RFC 2109 and specifies Cookies as they are actually used in existing implementations and deployments. Where differences exist among the most commonly used implementations, the working group will document the variations. Where consensus exists among the most commonly used implementations, the working group will specify the consensus behavior. =20 The working group must not introduce any new syntax or new semantics not already in common use. =20 The working group's specific deliverables are:=20 * A standards-track document that is suitable to supersede RFC 2109 (likely based on draft-abarth-cookie) * An informational document cataloguing the differences between major implementations In doing so, the working group should consider: =20 * cookie_spec.html - Netscape Cookie Specification http://web.archive.org/web/20070805052634/http://wp.netscape.com/newsre f/std/cookie_spec.html=20 * RFC 2109 - HTTP State Management Mechanism (Obsoleted by RFC 2965) =20 http://tools.ietf.org/html/rfc2109=20 * RFC 2964 - Use of HTTP State Management =20 http://tools.ietf.org/html/rfc2964=20 * RFC 2965 - HTTP State Management Mechanism (Obsoletes RFC 2109) =20 http://tools.ietf.org/html/rfc2965=20 * I-D - HTTP State Management Mechanism v2 =20 http://tools.ietf.org/html/draft-pettersen-cookie-v2=20 * I-D - Cookie-based HTTP Authentication =20 http://tools.ietf.org/html/draft-broyer-http-cookie-auth=20 * Widely Implemented - HTTPOnly =20 http://www.owasp.org/index.php/HTTPOnly * Browser Security Handbook - Cookies http://code.google.com/p/browsersec/wiki/Part2#Same- origin_policy_for_cookies=20 * HTTP Cookies: Standards, Privacy, and Politics by David M. Kristol =20 http://arxiv.org/PS_cache/cs/pdf/0105/0105018v1.pdf =20 Goals and Milestones:=20 =20 Jan 2010 - Feature-complete Internet-Draft of Cookie specification Mar 2010 - Feature-complete test suite of Cookie specification May 2010 - First fully conforming implementation in a major browser Jul 2010 - Last Call for Cookie specification Sep 2010 - Second fully conforming implementation in a major browser Nov 2010 - Submit Cookie specification to IESG for consideration as=20 a Draft Standard Nov 2010 - Submit deviation description to IESG for consideration as=20 Informational