IETF Logo Mail Archive

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

=JeffH <Jeff.Hodges@KingsMountain.com> Thu, 06 December 2012 18:23 UTC

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

v2.23.0 | Report a Bug | By Email