
From Jeff.Hodges@KingsMountain.com  Thu Dec  6 08:06:41 2012
Return-Path: <Jeff.Hodges@KingsMountain.com>
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 2E0B421F85E8 for <http-state@ietfa.amsl.com>; Thu,  6 Dec 2012 08:06:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.265
X-Spam-Level: 
X-Spam-Status: No, score=-102.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 lqzuZL1EycP4 for <http-state@ietfa.amsl.com>; Thu,  6 Dec 2012 08:06:40 -0800 (PST)
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com [67.222.55.9]) by ietfa.amsl.com (Postfix) with SMTP id 4AD6221F8582 for <http-state@ietf.org>; Thu,  6 Dec 2012 08:06:40 -0800 (PST)
Received: (qmail 20974 invoked by uid 0); 6 Dec 2012 16:06:18 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy7.bluehost.com with SMTP; 6 Dec 2012 16:06:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=J32l3+TGlhjK9n5rYIrEnbsEi9H/sIAOPZhsYmAvlx4=;  b=AZq3X7tnvUFGqnZedTktQhEjPQ00j02sumngQk8kZfsyr+7lYBSdE/Figa5AjqGlZWkvWe01HtyTfXpUHh/lh+ZefIt9Mf7Q6DuBym/ceVTWng3IsOzuvLdPqAQ62WJ2;
Received: from [216.113.168.128] (port=26266 helo=[10.244.137.210]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Tgdxp-0005qY-MJ; Thu, 06 Dec 2012 09:06:17 -0700
Message-ID: <50C0C278.7050302@KingsMountain.com>
Date: Thu, 06 Dec 2012 08:06:16 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: HTTP State <http-state@ietf.org>, IETF WebSec WG <websec@ietf.org>,  HTTP Working Group <ietf-http-wg@w3.org>, Apps Discuss <apps-discuss@ietf.org>, IETF oauth WG <oauth@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: [http-state] fyi: IETF conflict review results for draft-secure-cookie-session-protocol
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, 06 Dec 2012 16:06:41 -0000

[ I was nosing around and noticed this relatively recent decision, it didn't 
appear to have been fwd'd to these lists. fyi/fwiw... ]


Subject: Results of IETF-conflict review for
	draft-secure-cookie-session-protocol-08
From: The IESG <iesg-secretary@ietf.org>
Date: Mon, 19 Nov 2012 14:46:52 -0800
To: "Nevil Brownlee" <rfc-ise@rfc-editor.org>,
	draft-secure-cookie-session-protocol@tools.ietf.org
Cc: iana@iana.org, The IESG <iesg@ietf.org>, ietf-announce@ietf.org

The IESG has completed a review of
draft-secure-cookie-session-protocol-08 consistent with RFC5742.


The IESG has no problem with the publication of 'SCS: Secure Cookie
Sessions for HTTP' <draft-secure-cookie-session-protocol-08.txt> as an
Informational RFC.


The IESG has concluded that this work is related to IETF work done in the
websec and httpbis working groups, but this relationship does not prevent
publishing.

The IESG would also like the RFC-Editor to review the comments in the
datatracker related to this document and determine whether or not they
merit incorporation into the document. Comments may exist in both the
ballot and the history log.

The IESG review is documented at:
http://datatracker.ietf.org/doc/conflict-review-secure-cookie-session-protocol/

A URL of the reviewed Internet Draft is:
http://datatracker.ietf.org/doc/draft-secure-cookie-session-protocol/

The process for such documents is described at
http://www.rfc-editor.org/indsubs.html

Thank you,

The IESG Secretary

###

IETF conflict review for draft-secure-cookie-session-protocol
[conflict-review-secure-cookie-session-protocol-00]

https://datatracker.ietf.org/doc/conflict-review-secure-cookie-session-protocol/


Conflict Review State:		Approved No Problem - announcement sent

Shepherding AD: 		Barry Leiba

Last updated:			2012-11-19


Conflict Review for draft-secure-cookie-session-protocol-09

The IESG has concluded that this work is related to IETF work done in the
websec and httpbis working groups, but this relationship does not prevent
publishing.


###

From daniel@haxx.se  Thu Dec  6 08:20:34 2012
Return-Path: <daniel@haxx.se>
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 1FEFE21F86FC for <http-state@ietfa.amsl.com>; Thu,  6 Dec 2012 08:20:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 tVQfYyKyi6tQ for <http-state@ietfa.amsl.com>; Thu,  6 Dec 2012 08:20:33 -0800 (PST)
Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) by ietfa.amsl.com (Postfix) with ESMTP id E03E621F86EC for <http-state@ietf.org>; Thu,  6 Dec 2012 08:20:32 -0800 (PST)
Received: from giant.haxx.se (localhost.localdomain [127.0.0.1]) by giant.haxx.se (8.14.4/8.14.4/Debian-2) with ESMTP id qB6GKTAd016893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Dec 2012 17:20:29 +0100
Received: from localhost (dast@localhost) by giant.haxx.se (8.14.4/8.14.4/Submit) with ESMTP id qB6GKSUj016889; Thu, 6 Dec 2012 17:20:28 +0100
X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs
Date: Thu, 6 Dec 2012 17:20:28 +0100 (CET)
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: HTTP State <http-state@ietf.org>
In-Reply-To: <50C0C278.7050302@KingsMountain.com>
Message-ID: <alpine.DEB.2.00.1212061715400.371@tvnag.unkk.fr>
References: <50C0C278.7050302@KingsMountain.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: [http-state] fyi: IETF conflict review results for draft-secure-cookie-session-protocol
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, 06 Dec 2012 16:20:34 -0000

On Thu, 6 Dec 2012, =JeffH wrote:

(I removed a few receivers, leaving http-state and ietf-http-wg only.)

> The IESG has no problem with the publication of 'SCS: Secure Cookie Sessions 
> for HTTP' <draft-secure-cookie-session-protocol-08.txt> as an Informational 
> RFC.

I'm curious if this work has been done in cooperation with any particular HTTP 
client or server vendor/author. Is there anyone "backing" this protocol and 
who is going to or perhaps already have implemented/deployed it in the wild?

I'm personally involved with libcurl, but I have no plans in walking down this 
path unless there's at least some _potential_ use of it...

-- 

  / daniel.haxx.se

From Jeff.Hodges@KingsMountain.com  Thu Dec  6 08:29:16 2012
Return-Path: <Jeff.Hodges@KingsMountain.com>
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 A227921F8666 for <http-state@ietfa.amsl.com>; Thu,  6 Dec 2012 08:29:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.03
X-Spam-Level: 
X-Spam-Status: No, score=-102.03 tagged_above=-999 required=5 tests=[AWL=-1.624, BAYES_20=-0.74, IP_NOT_FRIENDLY=0.334, 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 nBML5iIluEn9 for <http-state@ietfa.amsl.com>; Thu,  6 Dec 2012 08:29:15 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id CFBD521F866F for <http-state@ietf.org>; Thu,  6 Dec 2012 08:29:15 -0800 (PST)
Received: (qmail 32026 invoked by uid 0); 6 Dec 2012 16:28:32 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 6 Dec 2012 16:28:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=oij+OB/IL54LP1Awz8SxoTxICouheaPYMnldPCaVUSM=;  b=GIxmAErk/LNyI2Bj9IbZxWwoPEByQQA1Fj4s3Fya9C84soTwoIoxYeAKwelEnFDNVwr3NgJ1OtmR80dUfj+/yuqBUzP1bkhdfdB3Hi+Mp+is7gPeReFCUt13osju4j+m;
Received: from [216.113.168.128] (port=28140 helo=[10.244.137.210]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1TgeJJ-0000C8-Pu for http-state@ietf.org; Thu, 06 Dec 2012 09:28:29 -0700
Message-ID: <50C0C7AC.7020109@KingsMountain.com>
Date: Thu, 06 Dec 2012 08:28:28 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: HTTP State <http-state@ietf.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Subject: [http-state] fyi: Interactive Advertising Bureau - The Future of the Cookie
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, 06 Dec 2012 16:29:16 -0000

Just an fyi/fwiw.  The slides..

   http://www.slideshare.net/slideshow/embed_code/14132478

=2E.have a bit more detail on their thoughts wrt process and schedule. AF=
AIK this=20
is a iab.net (Interactive Advertising Bureau) membership-only effort at t=
his time.

=3DJeffH
------

The Future of the Cookie
By Jordan Mitchell on October 16, 2012 4:14 PM | Permalink | Comments
https://www.iab.net/iablog/2012/10/the-future-of-the-cookie.html

As someone who=92s been involved with web-based software development sinc=
e before=20
Netscape went public, I can confidently say that the use of cookies has g=
otten=20
out of hand.

Originally designed for simple, temporary data storage, the cookie now fo=
rms a=20
fundamental infrastructure of the Internet; it=92s used for user profilin=
g,=20
segmentation and optimization, targeting and retargeting, mapping user ID=
s=20
between platforms, buying and selling of data, end-user privacy controls,=
=20
frequency capping of ads, web analytics, online advertising attribution a=
nd=20
verification, session management, shopping cart management=85and the list=
 goes on.

The problem=97speaking from a Product Manager perspective=97is that the u=
se cases=20
and requirements for a persistent and anonymous online tracking mechanism=
 have=20
long surpassed the capabilities of the cookie. The square peg has been ha=
mmered=20
into the round hole for too many years, evidenced by numerous issues expe=
rienced=20
by online publishers, consumers, and the online ad industry as a whole.

For online publishers, the proliferation of 3rd-party pixels has slowed p=
age=20
load times, increased discrepancy counts, and led to concerns of data lea=
kage.=20
It=92s also encouraged a broken compensation model=97publishers risk reve=
nue loss if=20
they don=92t support 3rd-party pixels, revenue loss from users who block =
or delete=20
cookies, and a tilted playing field favoring large consumer website brand=
s who=20
can track users for longer periods of time. And publishers are certain to=
=20
experience additional operational and privacy policy burdens as various=20
initiatives such as Do Not Track, browser opt-in defaults, and regulatory=
=20
measures gain traction.

For the ad industry as a whole, the reliance on cookies (and 3rd-party pi=
xels)=20
combined with the magnitude of cookie deletion (churn) has resulted in a =
battle=20
between a rapidly degrading economic model, and the costly, persistent, a=
nd=20
high-volume deployment of cookies. Even though cookies are unreliable as =
a user=20
tracking mechanism (especially across devices), the industry continues to=
 deploy=20
them at an escalating pace, causing excessive network traffic and related=
 costs,=20
=93internet bloat,=94 regulatory threats, and anxiety among consumers and=
 publishers=20
alike.

But there is a future for the cookie and an opportunity to turn the indus=
try=92s=20
most negative issue into a positive (or at least a neutral) one that will=
 result=20
in a win/win/win for publishers, consumers, and advertisers. Along with P=
hilip=20
Smolin (Turn), Susan Pierce (Google), Amy Kuznicki (Verizon Wireless) and=
 Brian=20
Murphy (AOL), I=92m proud to be co-chairing an ambitious IAB Advertising =

Technology Council initiative called The Future of the Cookie along with =
the=20
IAB=92s Mobile Marketing Center of Excellence.

We=92re recruiting leaders from the top companies in the digital advertis=
ing=20
industry to join us in a mission to discuss and propose responsible solut=
ions to=20
the problems that exist today=97and then execute a plan that leads us int=
o the=20
future of online user tracking, transparency, and control. So if you=92re=
 a=20
technology-oriented thought leader, please consider participating! (If=20
interested, please email committees@iab.net)



From Jeff.Hodges@KingsMountain.com  Thu Dec  6 10:23:28 2012
Return-Path: <Jeff.Hodges@KingsMountain.com>
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 C64B721F8654 for <http-state@ietfa.amsl.com>; Thu,  6 Dec 2012 10:23:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.728
X-Spam-Level: 
X-Spam-Status: No, score=-102.728 tagged_above=-999 required=5 tests=[AWL=-0.462, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, 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 YjPM1JinJ+-H for <http-state@ietfa.amsl.com>; Thu,  6 Dec 2012 10:23:27 -0800 (PST)
Received: from oproxy6-pub.bluehost.com (oproxy6-pub.bluehost.com [67.222.54.6]) by ietfa.amsl.com (Postfix) with SMTP id 8406021F8674 for <http-state@ietf.org>; Thu,  6 Dec 2012 10:23:26 -0800 (PST)
Received: (qmail 11588 invoked by uid 0); 6 Dec 2012 18:22:33 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy3.bluehost.com with SMTP; 6 Dec 2012 18:22:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default;  h=Content-Transfer-Encoding:Content-Type:Subject:CC:To:MIME-Version:From:Date:Message-ID; bh=/LcTftt9dstM4AvNNSeLMwMtF6gAtB9TswZkMckJPC0=;  b=2153ZFyY5fQgvnlMFVrno0Enc4nVNmOWLTO0aatEIZcuhaqtEP6uxUlOSBNbGSnWm6AE8iaiCic3sbY+Qko9EoJM8Q8f9WnpCO1lL5J/p1oxHM1bKDjNyWk79eXv3tmD;
Received: from [216.113.168.128] (port=12806 helo=[10.244.137.210]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Tgg5e-0000mB-1C; Thu, 06 Dec 2012 11:22:30 -0700
Message-ID: <50C0E264.1010601@KingsMountain.com>
Date: Thu, 06 Dec 2012 10:22:28 -0800
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Daniel Stenberg <daniel@haxx.se>
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: HTTP State <http-state@ietf.org>
Subject: Re: [http-state] fyi: IETF conflict review results for draft-secure-cookie-session-protocol
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, 06 Dec 2012 18:23:28 -0000

 >> The IESG has no problem with the publication of 'SCS: Secure Cookie Sessions
 >> for HTTP' <draft-secure-cookie-session-protocol-08.txt> as an Informational
 >> RFC.
 >
 > I'm curious if this work has been done in cooperation with any particular HTTP
 > client or server vendor/author. Is there anyone "backing" this protocol and
 > who is going to or perhaps already have implemented/deployed it in the wild?

that spec was/is driven by KoanLogic folks, whom I presume have an implementation.

=JeffH



From barryleiba.mailing.lists@gmail.com  Thu Dec  6 11:34:55 2012
Return-Path: <barryleiba.mailing.lists@gmail.com>
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 7C3C921F88C1; Thu,  6 Dec 2012 11:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.093
X-Spam-Level: 
X-Spam-Status: No, score=-103.093 tagged_above=-999 required=5 tests=[AWL=-0.116, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 Zf1yeV96Vi7G; Thu,  6 Dec 2012 11:34:55 -0800 (PST)
Received: from mail-lb0-f172.google.com (mail-lb0-f172.google.com [209.85.217.172]) by ietfa.amsl.com (Postfix) with ESMTP id 47D3E21F867A; Thu,  6 Dec 2012 11:34:49 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id y2so5909765lbk.31 for <multiple recipients>; Thu, 06 Dec 2012 11:34:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6hgqy6AxD2R9SZxoPfFAKdFGbY/9J4+Dx5UZdm8Mfqo=; b=w9guA4XFOKSC774g7SX+soD1m+Y6+QRF6mkNXKlBVdISLQvhx9Hihwr00e+plLeDPP yHZR2tTQo0G+zV3FyM7tZu/jQu9cdx1jzjKKCLCoPU4OqwQM3PqqDd0n2rL7zJ36MugA ccWGI3qYiDQoC/bOh+YVlm2u1VmQvsTaJUdbO54KGju5CkNy9mYKgaUF0Ui0519+H4u6 IInq3oMD3sep0OCh+sxvkgSyXmusixHxB0tIu1UzxDyW6GakQEeVI0jl4ZCkAO2KaKi9 o017MtkfpQ72bYWg5x8FqEaQhtDNa6Ak0iYQ8D+GS3/CyLk2EDeLfSIudBKZaEuHGDWL 9P8A==
MIME-Version: 1.0
Received: by 10.112.25.34 with SMTP id z2mr1449204lbf.125.1354822488183; Thu, 06 Dec 2012 11:34:48 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.112.12.166 with HTTP; Thu, 6 Dec 2012 11:34:48 -0800 (PST)
In-Reply-To: <50C0C278.7050302@KingsMountain.com>
References: <50C0C278.7050302@KingsMountain.com>
Date: Thu, 6 Dec 2012 14:34:48 -0500
X-Google-Sender-Auth: OX0NyyE18yghle8XQywQyo6h5PI
Message-ID: <CAC4RtVAOCyn2Zzj96U0+Vxw4QOU_GvvJ+Q8XTQs1eKgD=gpTqw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: IETF oauth WG <oauth@ietf.org>, IETF WebSec WG <websec@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, Apps Discuss <apps-discuss@ietf.org>, HTTP State <http-state@ietf.org>
Subject: Re: [http-state] [OAUTH-WG] fyi: IETF conflict review results for draft-secure-cookie-session-protocol
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, 06 Dec 2012 19:34:55 -0000

> [ I was nosing around and noticed this relatively recent decision, it didn't
> appear to have been fwd'd to these lists. fyi/fwiw... ]
...
> The IESG has no problem with the publication of 'SCS: Secure Cookie
> Sessions for HTTP' <draft-secure-cookie-session-protocol-08.txt> as an
> Informational RFC.
>
> The IESG has concluded that this work is related to IETF work done in the
> websec and httpbis working groups, but this relationship does not prevent
> publishing.

Yes, Jeff, and thanks for forwarding this.  To make sure people have
the background...

I announced on 17 Oct to this set of mailing lists that we were
looking for input to the conflict review to be posted to the SAAG
mailing list.  The discussion thread starts here:
http://www.ietf.org/mail-archive/web/saag/current/msg04049.html

On 9 November, I closed the discussion with this message on the SAAG list:
http://www.ietf.org/mail-archive/web/saag/current/msg04164.html

If anyone has any questions about the document, I suggest they contact
the authors directly.  You can do that with the following tools alias:
<draft-secure-cookie-session-protocol@tools.ietf.org>

Barry, App AD

From tho@koanlogic.com  Fri Dec  7 03:03:16 2012
Return-Path: <tho@koanlogic.com>
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 2928D21F86CB for <http-state@ietfa.amsl.com>; Fri,  7 Dec 2012 03:03:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 oUhSoVS1zZMb for <http-state@ietfa.amsl.com>; Fri,  7 Dec 2012 03:03:15 -0800 (PST)
Received: from mail-la0-f44.google.com (mail-la0-f44.google.com [209.85.215.44]) by ietfa.amsl.com (Postfix) with ESMTP id 64BBA21F86B9 for <http-state@ietf.org>; Fri,  7 Dec 2012 03:03:15 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id d3so288885lah.31 for <http-state@ietf.org>; Fri, 07 Dec 2012 03:03:14 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=qkzeoLNmg4t8S1libHIjEy5rWzfFTeACILQ15FU3QnU=; b=YDT/vZ4nTh/QIvEImv4nGpic1IC8/irt0/defZkTYYTZ8agAHNDI7gChzmdx0QLNRS 5NI4d07fqpiZc24M27UBqLxdKd75w+VqbFaqx6SdlcLoRg9Cs7xNks2C5wDjHCRkmGKz qGxJPgsTx63mkajTVL16I3OkaVkRmeqjU6YlsQEh1ApTmU2xkVslhkwEwmYGDcrNtHzG oAJkZFPVDWHODRhlHjn+Th71cuffSn//doQvtoY3g4pOvsUfbRs0GFwSgRafXhlLrqGp 6ByOXCY5y7J/A/2E2A2dxuERe9ycW1qfReI1UbVNLOAs3ihy1QFWhESKcwtRfFUv9o8A zevQ==
MIME-Version: 1.0
Received: by 10.152.147.100 with SMTP id tj4mr4963645lab.42.1354878194064; Fri, 07 Dec 2012 03:03:14 -0800 (PST)
Received: by 10.114.29.10 with HTTP; Fri, 7 Dec 2012 03:03:14 -0800 (PST)
X-Originating-IP: [81.134.152.4]
In-Reply-To: <50C0E264.1010601@KingsMountain.com>
References: <50C0E264.1010601@KingsMountain.com>
Date: Fri, 7 Dec 2012 11:03:14 +0000
Message-ID: <CAByMhx8d9YzgvOKLb=9X=Kq-tVrLD2PAm778JR6PJ8OZ3U3r7A@mail.gmail.com>
From: Thomas Fossati <tho@koanlogic.com>
To: Daniel Stenberg <daniel@haxx.se>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQnWrOnTftiSMw4c63u0vD42nDpjPNoeBtp9qCbTYzdO9xXiFBXX76UvYHesl52jWwvILLQU
Cc: HTTP State <http-state@ietf.org>
Subject: Re: [http-state] fyi: IETF conflict review results for draft-secure-cookie-session-protocol
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: Fri, 07 Dec 2012 11:03:16 -0000

Daniel,

On Thu, Dec 6, 2012 at 6:22 PM, =JeffH <Jeff.Hodges@kingsmountain.com> wrote:
> that spec was/is driven by KoanLogic folks, whom I presume have an
> implementation.

we have a reference implementation here:

  https://github.com/koanlogic/libscs

Anyway, SCS is basically a server side tool, I guess it would not add
any value to libcurl.

Cheers, Thomas.

From wwwrun@rfc-editor.org  Thu Dec 13 14:31:23 2012
Return-Path: <wwwrun@rfc-editor.org>
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 A4B7221F8B59 for <http-state@ietfa.amsl.com>; Thu, 13 Dec 2012 14:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.152
X-Spam-Level: 
X-Spam-Status: No, score=-102.152 tagged_above=-999 required=5 tests=[AWL=0.448, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 rfx-tKZTgVah for <http-state@ietfa.amsl.com>; Thu, 13 Dec 2012 14:31:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 24DE721F8BBD for <http-state@ietf.org>; Thu, 13 Dec 2012 14:31:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id C5069B1E006; Thu, 13 Dec 2012 14:22:37 -0800 (PST)
To: abarth@eecs.berkeley.edu, barryleiba@computer.org, presnick@qti.qualcomm.com, Jeff.Hodges@kingsmountain.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20121213222237.C5069B1E006@rfc-editor.org>
Date: Thu, 13 Dec 2012 14:22:37 -0800 (PST)
Cc: rfc-editor@rfc-editor.org, zhong.j.yu@gmail.com, http-state@ietf.org
Subject: [http-state] [Technical Errata Reported] RFC6265 (3430)
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, 13 Dec 2012 22:31:23 -0000

The following errata report has been submitted for RFC6265,
"HTTP State Management Mechanism".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6265&eid=3430

--------------------------------------
Type: Technical
Reported by: Zhong Yu <zhong.j.yu@gmail.com>

Section: 4.1.1

Original Text
-------------
 max-age-av        = "Max-Age=" non-zero-digit *DIGIT
                       ; In practice, both expires-av and max-age-av
                       ; are limited to dates representable by the
                       ; user agent.
 non-zero-digit    = %x31-39
                       ; digits 1 through 9


Corrected Text
--------------
 max-age-av        = "Max-Age=" 1*DIGIT
                       ; In practice, both expires-av and max-age-av
                       ; are limited to dates representable by the
                       ; user agent.


Notes
-----
The current text forbids a server to send Max-Age=0.

Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6265 (draft-ietf-httpstate-cookie-23)
--------------------------------------
Title               : HTTP State Management Mechanism
Publication Date    : April 2011
Author(s)           : A. Barth
Category            : PROPOSED STANDARD
Source              : HTTP State Management Mechanism
Area                : Applications
Stream              : IETF
Verifying Party     : IESG

From barryleiba@gmail.com  Fri Dec 14 06:30:48 2012
Return-Path: <barryleiba@gmail.com>
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 1A5E021F87C9 for <http-state@ietfa.amsl.com>; Fri, 14 Dec 2012 06:30:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.045
X-Spam-Level: 
X-Spam-Status: No, score=-103.045 tagged_above=-999 required=5 tests=[AWL=-0.068, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 ucrUPbXElJYI for <http-state@ietfa.amsl.com>; Fri, 14 Dec 2012 06:30:47 -0800 (PST)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 0A23F21F87C5 for <http-state@ietf.org>; Fri, 14 Dec 2012 06:30:46 -0800 (PST)
Received: by mail-vb0-f44.google.com with SMTP id fc26so3954706vbb.31 for <http-state@ietf.org>; Fri, 14 Dec 2012 06:30:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=c9LxroKw8fF0xzRx1lROvHl8lJSoLcBwNMl2GPpGGG0=; b=ocy/Kn8yOQUbrR2iv72evBBQy9p+ApkyrVf2KFmJeZcqzwu56ZlOYkV6vNCCz6L4LK JEICLmTJEHPDrAnACZW4UqdCKR1KVl+4aQ3pCGJzQx4QENPspmgUzZ3LaH+M7z9N0SMl +KOp5ezR42yEAkC02hHVt76gkco9zZKu6myWBKf5kjQrApHQqSzv4JHzbBtrmyRuiPDr sZ93xyZbs40TvuFPUgOKUNlUClcRiw4e5TRMv9POqHicoPxb7HQfeJhJLCPc3hQ5ApNr TIMrR1IGf/+a0Ug2UABe3nHJc1XWfl79/k4zVgvpScqndzZi2bQsGvqNgx8QECdP9r/s hGcQ==
MIME-Version: 1.0
Received: by 10.220.149.69 with SMTP id s5mr9502374vcv.23.1355495446361; Fri, 14 Dec 2012 06:30:46 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Fri, 14 Dec 2012 06:30:45 -0800 (PST)
In-Reply-To: <20121213222237.C5069B1E006@rfc-editor.org>
References: <20121213222237.C5069B1E006@rfc-editor.org>
Date: Fri, 14 Dec 2012 09:30:45 -0500
X-Google-Sender-Auth: GdIV1B3ifwc582HBnovuUM9pLHM
Message-ID: <CALaySJK6YimPpKK6bbnAZBwNyqhjD2zNCJFSQFbQSx_40nQv1Q@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: text/plain; charset=ISO-8859-1
Cc: http-state@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, zhong.j.yu@gmail.com, abarth@eecs.berkeley.edu
Subject: Re: [http-state] [Technical Errata Reported] RFC6265 (3430)
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: Fri, 14 Dec 2012 14:30:48 -0000

> The following errata report has been submitted for RFC6265,
> "HTTP State Management Mechanism".
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=6265&eid=3430
> --------------------------------------
> Type: Technical
> Reported by: Zhong Yu <zhong.j.yu@gmail.com>
>
> Section: 4.1.1
>
> Original Text
> -------------
>  max-age-av        = "Max-Age=" non-zero-digit *DIGIT
>                        ; In practice, both expires-av and max-age-av
>                        ; are limited to dates representable by the
>                        ; user agent.
>  non-zero-digit    = %x31-39
>                        ; digits 1 through 9
>
>
> Corrected Text
> --------------
>  max-age-av        = "Max-Age=" 1*DIGIT
>                        ; In practice, both expires-av and max-age-av
>                        ; are limited to dates representable by the
>                        ; user agent.
>
>
> Notes
> -----
> The current text forbids a server to send Max-Age=0.

Actually, it's much worse than that: the ABNF for max-age-av does not
match the text in Section 5.2.2 at all (5.2.2 allows a "-" as well,
and values less than or equal to zero).  Before verifying this, we
need to check whether things like "-1" were meant to be valid --
whether the error is only in the ABNF, or whether 5.2.2 is (also)
wrong.

The easiest fix is to make the ABNF match Section 5.2.2, which could
be done this way:

Original Text
-------------
   max-age-av        = "Max-Age=" non-zero-digit *DIGIT

Corrected Text
-------------
  max-age-av        = "Max-Age=" (DIGIT / ("-" non-zero-digit)) *DIGIT

If Section 5.2.2 correctly expresses the intent, then this seems the
right erratum.  Otherwise, there is an erratum in 5.2.2.

Adam, Jeff (and others): comments?  What was the intent when the text
was written?

Barry

From dan.winship@gmail.com  Mon Dec 17 07:59:48 2012
Return-Path: <dan.winship@gmail.com>
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 480AB21F8B27 for <http-state@ietfa.amsl.com>; Mon, 17 Dec 2012 07:59:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level: 
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 X1y8G-dMr2TE for <http-state@ietfa.amsl.com>; Mon, 17 Dec 2012 07:59:47 -0800 (PST)
Received: from mail-ye0-f172.google.com (mail-ye0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id ADBF021F8B16 for <http-state@ietf.org>; Mon, 17 Dec 2012 07:59:47 -0800 (PST)
Received: by mail-ye0-f172.google.com with SMTP id m10so652475yen.31 for <http-state@ietf.org>; Mon, 17 Dec 2012 07:59:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=OWNV5hmVp07Pk5LpC9rB+u5ORwNybTvrQkTlrcVk5YI=; b=skRFb5nS3GEjpVy8qSLqW8sHHNocKR99SVR7QPlCA8wTd3tW/SrlG1gFhZVFWqxT3c hegNR9QuVb/LuQNHJJ3VMaf0t+QkrXn5NkM9XEusJnxPJySkIYzBB2zTtpqIcNJH0RhT HahIwhdhWYG1tz0nWRjPGUtWrprSo50JHh79qNCSxOfM8nUsCm6erJ1Hny5yiGbx8DlW J+3FvxwXvfr8YwGfqzQvI0TGbl46f+lZgeDlLdLUuG16J2yp5audIdZGvaO2boRzKA30 eK9R8fuB4p77pRwkvOdbCAeEXbqkg8zyDsMoLqaIALh2/Rkegf9OxsosnlJcFHhjIQK/ NqBw==
Received: by 10.52.23.37 with SMTP id j5mr3413580vdf.56.1355759987130; Mon, 17 Dec 2012 07:59:47 -0800 (PST)
Received: from laptop.home.mysterion.org (c-76-17-119-23.hsd1.ga.comcast.net. [76.17.119.23]) by mx.google.com with ESMTPS id vl8sm11556138veb.9.2012.12.17.07.59.45 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Dec 2012 07:59:46 -0800 (PST)
Message-ID: <50CF4129.9080705@gmail.com>
Date: Mon, 17 Dec 2012 10:58:33 -0500
From: Dan Winship <dan.winship@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>
References: <20121213222237.C5069B1E006@rfc-editor.org> <CALaySJK6YimPpKK6bbnAZBwNyqhjD2zNCJFSQFbQSx_40nQv1Q@mail.gmail.com>
In-Reply-To: <CALaySJK6YimPpKK6bbnAZBwNyqhjD2zNCJFSQFbQSx_40nQv1Q@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: abarth@eecs.berkeley.edu, Pete Resnick <presnick@qti.qualcomm.com>, http-state@ietf.org, zhong.j.yu@gmail.com, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [http-state] [Technical Errata Reported] RFC6265 (3430)
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: Mon, 17 Dec 2012 15:59:48 -0000

On 12/14/2012 09:30 AM, Barry Leiba wrote:
> Actually, it's much worse than that: the ABNF for max-age-av does not
> match the text in Section 5.2.2 at all

Yes, that's intentional, and explained in the introduction:

>    To maximize interoperability with user agents, servers SHOULD limit
>    themselves to the well-behaved profile defined in Section 4 when
>    generating cookies.
> 
>    User agents MUST implement the more liberal processing rules defined
>    in Section 5, in order to maximize interoperability with existing
>    servers that do not conform to the well-behaved profile defined in
>    Section 4.

The prohibition against "Max-Age=0" is probably because IE still doesn't
support Max-Age, so any cookie that has Max-Age but not Expires is a
session cookie in IE. That's annoying for non-zero Max-Age values (and
the spec warns about this), but Max-Age=0 would end up meaning "delete
the cookie unless the user is using IE", which is almost certainly not
what you want.

-- Dan


From barryleiba@gmail.com  Mon Dec 17 08:17:29 2012
Return-Path: <barryleiba@gmail.com>
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 17E0521F8B35 for <http-state@ietfa.amsl.com>; Mon, 17 Dec 2012 08:17:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.042
X-Spam-Level: 
X-Spam-Status: No, score=-103.042 tagged_above=-999 required=5 tests=[AWL=-0.065, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, 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 w0t6PlIHB9mG for <http-state@ietfa.amsl.com>; Mon, 17 Dec 2012 08:17:28 -0800 (PST)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id A372A21F8B64 for <http-state@ietf.org>; Mon, 17 Dec 2012 08:17:19 -0800 (PST)
Received: by mail-vc0-f172.google.com with SMTP id fw7so7398004vcb.31 for <http-state@ietf.org>; Mon, 17 Dec 2012 08:17:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=gXxGjwQy8Xq+fXlYQEiPnO0kr1MDxdugQetXU/sNsF0=; b=z2GLG3ptl5n7GjquRRGkA2VXhJ2yfgVGMX9OpooL9qAb81CbKch96sAqDlfxQ6FmjB blOki54s4ZIAD/Mh6lo8mZ0XYeu2vSxl/90SCLIgPwsR3gwzpuzvSVIbXhC/eBXqDYfe u/boYmguWQlMLnSM+GQc83eUPB/Casbc40470b8AHhzk8935Zccp38N2gTeIivEnVu8M 8V9fl8aMVJ5ifg9k3MlNUtllYkykMPh+GEY6GX6jKA5rC8Fwzr4pHISmdwW5n1L+zdXY M6MWnvdf8cdtvypYBqxhygZDF43Ic8xzAfbNqOzKl2fBxPgd39rBwGj2SY/AMju2RRZt X3QA==
MIME-Version: 1.0
Received: by 10.52.69.201 with SMTP id g9mr20663586vdu.98.1355761039079; Mon, 17 Dec 2012 08:17:19 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.58.28.231 with HTTP; Mon, 17 Dec 2012 08:17:18 -0800 (PST)
In-Reply-To: <50CF4129.9080705@gmail.com>
References: <20121213222237.C5069B1E006@rfc-editor.org> <CALaySJK6YimPpKK6bbnAZBwNyqhjD2zNCJFSQFbQSx_40nQv1Q@mail.gmail.com> <50CF4129.9080705@gmail.com>
Date: Mon, 17 Dec 2012 11:17:18 -0500
X-Google-Sender-Auth: PFgjKgVKxu6Kd8_shxHNbRmHGfw
Message-ID: <CALaySJ+R_88OOG=Z1qRo+xECN7ubi6C2-AdFetYpwodBema6zw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Dan Winship <dan.winship@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: abarth@eecs.berkeley.edu, Pete Resnick <presnick@qti.qualcomm.com>, http-state@ietf.org, zhong.j.yu@gmail.com, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [http-state] [Technical Errata Reported] RFC6265 (3430)
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: Mon, 17 Dec 2012 16:17:29 -0000

Hi, Dan.

>> Actually, it's much worse than that: the ABNF for max-age-av does not
>> match the text in Section 5.2.2 at all
>
> Yes, that's intentional, and explained in the introduction:
>
>>    To maximize interoperability with user agents, servers SHOULD limit
>>    themselves to the well-behaved profile defined in Section 4 when
>>    generating cookies.
>>
>>    User agents MUST implement the more liberal processing rules defined
>>    in Section 5, in order to maximize interoperability with existing
>>    servers that do not conform to the well-behaved profile defined in
>>    Section 4.

Oy.  Yes, as I read more, I see the various bits of this.  I wish the
document had said all this in a different way, making it clearer that
the ABNF is not normative in the way it usually is.

Anyway, what this tells me is that this erratum should be "Rejected",
with an explanation related to what you sent in your message. Thanks.

Barry

From zhong.j.yu@gmail.com  Mon Dec 17 08:24:51 2012
Return-Path: <zhong.j.yu@gmail.com>
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 0049D21F8B35 for <http-state@ietfa.amsl.com>; Mon, 17 Dec 2012 08:24:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.814
X-Spam-Level: 
X-Spam-Status: No, score=-6.814 tagged_above=-999 required=5 tests=[AWL=-3.215, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 7KuBnLoe4TSp for <http-state@ietfa.amsl.com>; Mon, 17 Dec 2012 08:24:50 -0800 (PST)
Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id D33A621F8B2F for <http-state@ietf.org>; Mon, 17 Dec 2012 08:24:49 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id za17so5880639obc.31 for <http-state@ietf.org>; Mon, 17 Dec 2012 08:24:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=knxBfGZ87OPHIVsLNsbDOrxYUL5ErdECG+e83sR6jR0=; b=MnxlgwTQJ30+4Snr0FNhlFNDPgT775wLgKWt/zeT/3Sow8kQLgqaDEl7Hek9din/2s WK85NPZzpXh8szuichD/ju7JIx6/tQDS5D17DuqLifdfIm15Rlpk2o9PALtPPiMuN5IZ P46+z2XM9BfwPvnFzR7WkonrDQWpyZ6sze0cKDX06E72UPC1Fu/EvisINfFiEong7CEo T5ySWSBb57ZkqZwt1q+DCNqZhMaFKgMnmX016/nG7wZrQ0pGd3WYjzSMjwt3fywRSh2+ h4zHT+nzn0kinnXZ63HXKoDn18xDgV3rk9QwjGO+lPHJeOSJ/Q/V3NvHNyHbkYAcQkAT 1rSQ==
MIME-Version: 1.0
Received: by 10.182.2.169 with SMTP id 9mr12190085obv.66.1355761489132; Mon, 17 Dec 2012 08:24:49 -0800 (PST)
Received: by 10.76.12.227 with HTTP; Mon, 17 Dec 2012 08:24:48 -0800 (PST)
In-Reply-To: <50CF4129.9080705@gmail.com>
References: <20121213222237.C5069B1E006@rfc-editor.org> <CALaySJK6YimPpKK6bbnAZBwNyqhjD2zNCJFSQFbQSx_40nQv1Q@mail.gmail.com> <50CF4129.9080705@gmail.com>
Date: Mon, 17 Dec 2012 10:24:48 -0600
Message-ID: <CACuKZqFkVDG5Si_psL39_c1jCrnEU+hP-nNQcTwCL6=woMpgnA@mail.gmail.com>
From: Zhong Yu <zhong.j.yu@gmail.com>
To: Dan Winship <dan.winship@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Mon, 17 Dec 2012 13:51:13 -0800
Cc: http-state@ietf.org, Pete Resnick <presnick@qti.qualcomm.com>, Barry Leiba <barryleiba@computer.org>, abarth@eecs.berkeley.edu, RFC Errata System <rfc-editor@rfc-editor.org>
Subject: Re: [http-state] [Technical Errata Reported] RFC6265 (3430)
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: Mon, 17 Dec 2012 16:24:51 -0000

On Mon, Dec 17, 2012 at 9:58 AM, Dan Winship <dan.winship@gmail.com> wrote:
> On 12/14/2012 09:30 AM, Barry Leiba wrote:
>> Actually, it's much worse than that: the ABNF for max-age-av does not
>> match the text in Section 5.2.2 at all
>
> Yes, that's intentional, and explained in the introduction:
>
>>    To maximize interoperability with user agents, servers SHOULD limit
>>    themselves to the well-behaved profile defined in Section 4 when
>>    generating cookies.
>>
>>    User agents MUST implement the more liberal processing rules defined
>>    in Section 5, in order to maximize interoperability with existing
>>    servers that do not conform to the well-behaved profile defined in
>>    Section 4.
>
> The prohibition against "Max-Age=0" is probably because IE still doesn't
> support Max-Age, so any cookie that has Max-Age but not Expires is a
> session cookie in IE. That's annoying for non-zero Max-Age values (and
> the spec warns about this), but Max-Age=0 would end up meaning "delete
> the cookie unless the user is using IE", which is almost certainly not
> what you want.

Thanks Dan, so a server should avoid Max-Age all together. If a server
sets Max-Age=a few seconds, it won't be honored by IE either.

Zhong
