W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2012

Re: [OAUTH-WG] fyi: IETF conflict review results for draft-secure-cookie-session-protocol

From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 6 Dec 2012 14:34:48 -0500
Message-ID: <CAC4RtVAOCyn2Zzj96U0+Vxw4QOU_GvvJ+Q8XTQs1eKgD=gpTqw@mail.gmail.com>
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Cc: 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>
> [ 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
Received on Thursday, 6 December 2012 19:35:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 6 December 2012 19:35:20 GMT