Re: [TLS] Re: WGLC: draft-ietf-tls-srp-13

Mike <mike-list@pobox.com> Tue, 26 December 2006 18:35 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GzH9A-0001Ab-BN; Tue, 26 Dec 2006 13:35:32 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GzH98-0001AV-UV for tls@ietf.org; Tue, 26 Dec 2006 13:35:30 -0500
Received: from proof.pobox.com ([207.106.133.28]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GzH96-0008VF-Nt for tls@ietf.org; Tue, 26 Dec 2006 13:35:30 -0500
Received: from proof (localhost [127.0.0.1]) by proof.pobox.com (Postfix) with ESMTP id BE42E29D52 for <tls@ietf.org>; Tue, 26 Dec 2006 13:35:45 -0500 (EST)
Received: from [192.168.1.8] (wsip-24-234-114-35.lv.lv.cox.net [24.234.114.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by proof.sasl.smtp.pobox.com (Postfix) with ESMTP id 83652A5F56 for <tls@ietf.org>; Tue, 26 Dec 2006 13:35:45 -0500 (EST)
Message-ID: <45916B59.2030600@pobox.com>
Date: Tue, 26 Dec 2006 10:35:05 -0800
From: Mike <mike-list@pobox.com>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: tls@ietf.org
Subject: Re: [TLS] Re: WGLC: draft-ietf-tls-srp-13
References: <20061221154549.0A8941CC6B@delta.rtfm.com> <878xguzzv0.fsf@latte.josefsson.org>
In-Reply-To: <878xguzzv0.fsf@latte.josefsson.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Cc:
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
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>
Errors-To: tls-bounces@lists.ietf.org

> I suggest that for future TLS revisions, it should be considered
> whether to remove the distinction of standards-track numbers and
> non-standards track number, and that it becomes easier to have IANA
> perform early allocation of TLS ciphersuite numbers to help
> implementers test new TLS draft.

I can see that it may be a good idea to remove the distinction
between standard track and non-standard track ciphersuite numbers,
but I'd like to see the private range retained.  I am actually
planning to use some private ciphersuites soon in an experiment.

Mike

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