Re: [saag] Input for conflict review of draft-secure-cookie-session-protocol

=JeffH <Jeff.Hodges@KingsMountain.com> Mon, 22 October 2012 17:48 UTC

Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04BAD11E80E8 for <saag@ietfa.amsl.com>; Mon, 22 Oct 2012 10:48:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.442
X-Spam-Level:
X-Spam-Status: No, score=-101.442 tagged_above=-999 required=5 tests=[AWL=1.157, BAYES_00=-2.599, 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 Uam77CSQPseb for <saag@ietfa.amsl.com>; Mon, 22 Oct 2012 10:48:02 -0700 (PDT)
Received: from oproxy11-pub.bluehost.com (oproxy11-pub.bluehost.com [173.254.64.10]) by ietfa.amsl.com (Postfix) with SMTP id 0E4FB11E80A4 for <saag@ietf.org>; Mon, 22 Oct 2012 10:48:01 -0700 (PDT)
Received: (qmail 12769 invoked by uid 0); 22 Oct 2012 17:47:38 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by oproxy11.bluehost.com with SMTP; 22 Oct 2012 17:47:38 -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=Plg3HgzOBPvVmJojIP3j+1taeSX9Y3djfU0FenjdYqg=; b=W6x3gT+udPUNzVG1MbvXLX2WDjrgVcw7mqgPyK3hzAe0oTjv5tiY/DK5tsHvv8tYurCFEahm/FDEo5IgdlTcxP+BAwS/YuCzst6nb5fHUkeHsMopuuz4hhE7pBvku1XA;
Received: from [216.113.168.128] (port=7599 helo=[10.244.137.141]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1TQM6D-0003EM-0l; Mon, 22 Oct 2012 11:47:37 -0600
Message-ID: <508586B8.5030302@KingsMountain.com>
Date: Mon, 22 Oct 2012 10:47:36 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: IETF Security Area Advisory Group <saag@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}
Cc: draft-secure-cookie-session-protocol@tools.ietf.org, Nevil Brownlee <rfc-ise@rfc-editor.org>
Subject: Re: [saag] Input for conflict review of draft-secure-cookie-session-protocol
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 17:48:03 -0000

stephen.farrell@cs.tcd.ie suggested..
 >
 > If it were called "KoanLogic's Secure cookie Sessions
 > for HTTP" would that then be ok? IMO, it ought. That way,
 > the independent-stream RFC won't confuse anyone into
 > thinking that the IETF as a whole has developed this, but
 > if some IETF WG wants to do similar work, this could be
 > useful input. (And adding one word seems likely quicker
 > than organising and coming to IETF rough consensus;-)
 >
 > What do folks (incl. authors) think of that?
 >

+1

this has been done with e.g. various of Microsoft's work...


5385 Version 2.0 Microsoft Word Template for Creating Internet Drafts
      and RFCs. J. Touch. February 2010. (Format: TXT=38421 bytes)
      (Obsoletes RFC3285) (Status: INFORMATIONAL)


4757 The RC4-HMAC Kerberos Encryption Types Used by Microsoft Windows.
      K. Jaganathan, L. Zhu, J. Brezak. December 2006. (Format: TXT=36562
      bytes) (Updated by RFC6649) (Status: INFORMATIONAL)

4559 SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft
      Windows. K. Jaganathan, L. Zhu, J. Brezak. June 2006. (Format:
      TXT=16088 bytes) (Status: INFORMATIONAL)


etc.



HTH,

=JeffH