Re: [TLS] Brief Cross-WG review - draft-ietf-mmusic-comedia-tls

Eric Rescorla <ekr@networkresonance.com> Tue, 03 January 2006 19: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 1EtrRW-0007H2-VX; Tue, 03 Jan 2006 14:03:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EtrRU-0007Gu-Vf; Tue, 03 Jan 2006 14:03:33 -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 OAA13063; Tue, 3 Jan 2006 14:02:18 -0500 (EST)
Received: from raman.networkresonance.com ([198.144.196.3]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EtrWo-0007MX-Qv; Tue, 03 Jan 2006 14:09:04 -0500
Received: by raman.networkresonance.com (Postfix, from userid 1001) id 55EA31E8C4C; Tue, 3 Jan 2006 11:03:20 -0800 (PST)
To: Allison Mankin <mankin@psg.com>
Subject: Re: [TLS] Brief Cross-WG review - draft-ietf-mmusic-comedia-tls
References: <20060103174729.5D0CF222418@laser.networkresonance.com>
From: Eric Rescorla <ekr@networkresonance.com>
Date: Tue, 03 Jan 2006 11:03:20 -0800
In-Reply-To: <20060103174729.5D0CF222418@laser.networkresonance.com> (Allison Mankin's message of "Tue, 03 Jan 2006 09:45:54 -0800")
Message-ID: <86hd8l877r.fsf@raman.networkresonance.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.18 (berkeley-unix)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: Jonathan Lennox <lennox@cs.columbia.edu>, hartmans+ietf@mit.edu, tls@ietf.org, jon.peterson@neustar.biz, mmusic@ietf.org
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: EKR <ekr@networkresonance.com>
List-Id: "This is the mailing list for the Transport Layer Security working group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>, <mailto:tls-request@lists.ietf.org?subject=subscribe>
Sender: tls-bounces@lists.ietf.org
Errors-To: tls-bounces@lists.ietf.org

Allison Mankin <mankin@psg.com> writes:

>> 
>> > One other question -- in the IESG review, the issue was raised that
>> > there's not currently an IANA registry for textual names of hash
>> > functions.  I agreed to add an IANA considerations section for this
>> > purpose, but I was wondering if there's interest in having this
>> > registry be more broadly scoped than just for comedia-tls?
>> 
>> Well, as far as TLS goes, we only use integer code points, so this
>> wouldn't buy us anything, but speaking personally I think this
>> would be a good idea.
>
> Ekr,
>
> I somehow missed Jonathan's original question about this.  I'll support
> making this registry broad-based as long as we don't have to troubleshoot
> it a lot from the security side.  Essentially this is going to be
> an IANA space for SDP-folk determined names of the algorithms
> from RFCs 3280 and 4055 (and later, any RFCs which update 4055).
>
> The reason I don't want to use the broad registry if it entails
> debugging is that it's not very likely to be in the consciousness of 
> future security developers, not being integrated into a reference
> security RFC, and there's not much precedent (if any) for using
> the same registry for multiple protocols.  

OK, well I don't have a strong feeling either way, so this is
probably a question for SAAG or the SEC ADs.

-Ekr


_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls