IETF Logo Mail Archive

[XCON] Re: [MMUSIC] Re: Progressing/Resolving the IESG Review of the BFCP specs

Jonathan Lennox <lennox@cs.columbia.edu> Tue, 13 December 2005 18:33 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmExn-0002dC-Cf; Tue, 13 Dec 2005 13:33:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmExd-0002br-H5; Tue, 13 Dec 2005 13:33:21 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03717; Tue, 13 Dec 2005 13:32:04 -0500 (EST)
Received: from cs.columbia.edu ([128.59.16.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmEyU-0003Ca-Ad; Tue, 13 Dec 2005 13:34:08 -0500
Received: from cnr.cs.columbia.edu (cnr.cs.columbia.edu [128.59.19.133]) by cs.columbia.edu (8.12.10/8.12.10) with ESMTP id jBDIWpQw001230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 13 Dec 2005 13:32:51 -0500 (EST)
Received: from cnr.cs.columbia.edu (localhost [127.0.0.1]) by cnr.cs.columbia.edu (8.13.3/8.13.3) with ESMTP id jBDIWoG2089570; Tue, 13 Dec 2005 13:32:50 -0500 (EST) (envelope-from lennox@cnr.cs.columbia.edu)
Received: (from lennox@localhost) by cnr.cs.columbia.edu (8.13.3/8.13.3/Submit) id jBDIWkxr089567; Tue, 13 Dec 2005 13:32:46 -0500 (EST) (envelope-from lennox)
From: Jonathan Lennox <lennox@cs.columbia.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17311.5070.589311.939533@cnr.cs.columbia.edu>
Date: Tue, 13 Dec 2005 13:32:46 -0500
To: Russ Housley <housley@vigilsec.com>
In-Reply-To: <7.0.0.10.2.20051212142348.0369a800@vigilsec.com>
References: <7.0.0.10.2.20051212142348.0369a800@vigilsec.com>
X-Mailer: VM 7.19 under Emacs 21.3.1
X-PerlMx-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __HAS_X_MAILER 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0'
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
Cc: hardie@qualcomm.com, mmusic@ietf.org, jon.peterson@neustar.biz, hartmans-ietf@mit.edu, xcon@ietf.org, gonzalo.camarillo@ericsson.com
Subject: [XCON] Re: [MMUSIC] Re: Progressing/Resolving the IESG Review of the BFCP specs
X-BeenThere: xcon@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Centralized Conferencing <xcon.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:xcon@ietf.org>
List-Help: <mailto:xcon-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/xcon>, <mailto:xcon-request@ietf.org?subject=subscribe>
Sender: xcon-bounces@ietf.org
Errors-To: xcon-bounces@ietf.org

On Monday, December 12 2005, "Russ Housley" wrote to "mankin@psg.com, hartmans-ietf@mit.edu, hardie@qualcomm.com, mmusic@ietf.org, xcon@ietf.org, gonzalo.camarillo@ericsson.com, jon.peterson@neustar.biz, mankin@psg.com" saying:

> This document depends on the fingerprint Attribute definition in 
> [10], which is draft-ietf-mmusic-comedia-tls-05.  The definition of 
> the fingerprint attribute includes:
> 
>     hash-func              =  "sha-1" / "sha-224" / "sha-256" /
>                               "sha-384" / "sha-512" /
>                               "md5" / "md2" / token
>                               ; Additional hash functions can only come
>                               ; from updates to RFC 3279
> 
> RFC 3279 does not define the short strings used here.  RFC 3279 
> provides ASN.1 object identifiers, which are not suitable 
> here.  draft-ietf-mmusic-comedia-tls needs to say how these 
> identifiers will be assigned.  Will IANA maintain a registry?

It could be an IANA registry; I can write an IANA considerations section.

A registry of hash function names seems like something that's useful more
broadly than just for the TLS Comedia fingerprint, though.  For instance, at
some point RFC 2617 is going to need new hash functions.  Should this
problem be solved in more generality?

-- 
Jonathan Lennox
lennox@cs.columbia.edu

_______________________________________________
XCON mailing list
XCON@ietf.org
https://www1.ietf.org/mailman/listinfo/xcon

v2.23.0 | Report a Bug | By Email