Re: comedia-tls iana considerations (was Re: [MMUSIC] Re: Progressing/Resolving the IESG Review of the BFCP specs)

Russ Housley <housley@vigilsec.com> Tue, 13 December 2005 16:18 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 1EmCrc-0007C1-KN; Tue, 13 Dec 2005 11:18:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmCrZ-0007Bh-SW for mmusic@megatron.ietf.org; Tue, 13 Dec 2005 11:18:50 -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 LAA15842 for <mmusic@ietf.org>; Tue, 13 Dec 2005 11:17:48 -0500 (EST)
Received: from woodstock.binhost.com ([144.202.243.4]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1EmCsX-0006Qc-Ao for mmusic@ietf.org; Tue, 13 Dec 2005 11:19:50 -0500
Received: (qmail 25365 invoked by uid 0); 13 Dec 2005 16:18:40 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (70.21.115.66) by woodstock.binhost.com with SMTP; 13 Dec 2005 16:18:40 -0000
Message-Id: <7.0.0.10.2.20051213111809.063106e0@vigilsec.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.0.10 (Beta)
Date: Tue, 13 Dec 2005 11:18:21 -0500
To: Colin Perkins <csp@csperkins.org>, Allison Mankin <mankin@psg.com>, Jonathan Lennox <lennox@cs.columbia.edu>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: comedia-tls iana considerations (was Re: [MMUSIC] Re: Progressing/Resolving the IESG Review of the BFCP specs)
In-Reply-To: <BE29243C-5C78-4520-B279-B90A90FD7DD4@csperkins.org>
References: <200512122048.PAA24927@ietf.org> <BE29243C-5C78-4520-B279-B90A90FD7DD4@csperkins.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: "'hardie@qualcomm.com' Hardie" <hardie@qualcomm.com>, Sam Hartman <hartmans-ietf@mit.edu>, IETF MMUSIC working group <mmusic@ietf.org>, Jon Peterson <jon.peterson@neustar.biz>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Sender: mmusic-bounces@ietf.org
Errors-To: mmusic-bounces@ietf.org

Correct.

At 11:02 AM 12/13/2005, Colin Perkins wrote:
>Allison,
>
>[cc'ing Jonathan Lennox, to ensure this doesn't get lost]
>
>To confirm: you're proposing an update to comedia-tls IANA
>considerations, not to sdp-bfcp?
>
>Colin
>
>
>
>
>On 12 Dec 2005, at 20:49, Allison Mankin wrote:
>>Thanks to Russ and Ted for the prompt re-review of the BFCP documents.
>>
>>Russ wrote:
>>>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?
>>
>>Good point.  I'll note to the WG that Russ also sent this to the IESG
>>as a Last Call comment on the document.
>>
>>There are some instances when attribute values are registered in IANA,
>>not just the att-field.  One that is comparable is the key management
>>protocol identifier from draft-ietf-mmusic-kmgmt-ext.
>>
>>So a suggestion is to add to the IANA Considerations a crisp new
>>sub-registry for the hash-func values in the fingerprint attribute.
>>Its rules for registration can be that new identifiers are
>>permitted only for hash functions found in RFC 3279 or updates
>>of RFC 3279.
>>
>>Does the editor want to propose some IANA Considerations text?
>>
>>Allison (wearing the hat of an AD shepherd for comedia-tls)
>>
>>
>>
>>_______________________________________________
>>mmusic mailing list
>>mmusic@ietf.org
>>https://www1.ietf.org/mailman/listinfo/mmusic
>


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