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

Colin Perkins <csp@csperkins.org> Tue, 13 December 2005 16:03 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 1EmCcZ-0003Tw-Vq; Tue, 13 Dec 2005 11:03:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmCcO-0003St-IN for mmusic@megatron.ietf.org; Tue, 13 Dec 2005 11:03:19 -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 LAA13620 for <mmusic@ietf.org>; Tue, 13 Dec 2005 11:01:46 -0500 (EST)
Received: from mr1.dcs.gla.ac.uk ([130.209.249.184]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmCcz-0005ke-5d for mmusic@ietf.org; Tue, 13 Dec 2005 11:03:47 -0500
Received: from alor.dcs.gla.ac.uk ([130.209.247.84]:64509) by mr1.dcs.gla.ac.uk with esmtpsa (TLSv1:RC4-SHA:128) (Exim 4.42) id 1EmCbf-0002qR-7H; Tue, 13 Dec 2005 16:02:23 +0000
In-Reply-To: <200512122048.PAA24927@ietf.org>
References: <200512122048.PAA24927@ietf.org>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <BE29243C-5C78-4520-B279-B90A90FD7DD4@csperkins.org>
Content-Transfer-Encoding: 7bit
From: Colin Perkins <csp@csperkins.org>
Subject: comedia-tls iana considerations (was Re: [MMUSIC] Re: Progressing/Resolving the IESG Review of the BFCP specs)
Date: Tue, 13 Dec 2005 16:02:22 +0000
To: Allison Mankin <mankin@psg.com>, Jonathan Lennox <lennox@cs.columbia.edu>
X-Mailer: Apple Mail (2.746.2)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
Cc: "'hardie@qualcomm.com' Hardie" <hardie@qualcomm.com>, IETF MMUSIC working group <mmusic@ietf.org>, Jon Peterson <jon.peterson@neustar.biz>, Sam Hartman <hartmans-ietf@mit.edu>, Russ Housley <housley@vigilsec.com>, 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

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