RE: [TLS] Re: Cipher-suite specific extensions

"Simon Blake-Wilson" <sblakewilson@bcisse.com> Wed, 24 August 2005 17:31 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7z6C-0001ux-Lc; Wed, 24 Aug 2005 13:31:40 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E7z6B-0001up-0D for tls@megatron.ietf.org; Wed, 24 Aug 2005 13:31:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06985 for <tls@ietf.org>; Wed, 24 Aug 2005 13:31:36 -0400 (EDT)
Received: from 209-204-118-122.sniparpa.net ([209.204.118.122] helo=bcisse.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E7z6W-0000cG-9T for tls@ietf.org; Wed, 24 Aug 2005 13:32:01 -0400
Received: from simon (dns2.ccnwired.com [216.13.13.68]) by bcisse.com; Wed, 24 Aug 2005 13:28:44 -0400
From: Simon Blake-Wilson <sblakewilson@bcisse.com>
To: tls@ietf.org
Subject: RE: [TLS] Re: Cipher-suite specific extensions
Date: Wed, 24 Aug 2005 13:28:43 -0400
Message-ID: <03d701c5a8d1$4737fd10$af00a8c0@simon>
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
MIME-Version: 1.0
In-Reply-To: <873bp1sdn9.fsf@scholes.stanford.edu>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 2.0 (++)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
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>
Content-Type: multipart/mixed; boundary="===============2129321832=="
Sender: tls-bounces@lists.ietf.org
Errors-To: tls-bounces@lists.ietf.org

Hi folks,

By my count the results of my informal poll on whether people support
adding cipher-suite specific extensions to the TLS extensions and ECC in
TLS docs are currently 1-1.

I don't think that shows sufficient support for making the changes to add
cipher-suite specific support so unless more people speak up I suggest we
move forward with the two documents without cipher-suite specific
extension support.

Note that this certainly does not exclude someone putting out a new I-D
specifying syntax for cipher-suite specific extensions to use to populate
extension data, as well as new extension types for cipher-suite specific
versions of existing extensions and/or new cipher-suite specific
extensions.

Any comments?

Best regards. Simon 

> -----Original Message-----
> From: tls-bounces@lists.ietf.org 
> [mailto:tls-bounces@lists.ietf.org] On Behalf Of Hovav Shacham
> Sent: Monday, August 22, 2005 8:25 PM
> To: tls@ietf.org
> Subject: [TLS] Re: Cipher-suite specific extensions
> 
> 
> "Simon Blake-Wilson" <sblakewilson@bcisse.com> writes:
> 
> > Can I take this as meaning that not many people care and we 
> can move 
> > forward with the TLS extensions and ECC documents as they are, 
> > deferring this issue to future I-Ds?
> 
> Yes.  I support leaving the extensions document as is, 
> without adding ciphersuite-specific extension support.
> 
> -- 
> Hovav Shacham                                  hovav@hovav.net
> "Rightly looked at there is no laughable thing under the sun."
> 
> _______________________________________________
> TLS mailing list
> TLS@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/tls
> 
_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls