Re: [TLS] Next steps for draft-ietf-tls-ecc-XX.txt

On Tue, Nov 02, 2004 at 04:48:02PM -0800, Eric Rescorla wrote:
> Vipul Gupta <Vipul.Gupta@Sun.COM> writes:

>> In fact, at least one of the authors of that draft didn't realize that
>> the sentence would preclude Informational/Experimental
>> RFCs from defining new TLS extensions. So I'd also favor changing
>> the wording in RFC 3546.
>>
>> Who needs to approve such a change and if they do would you want
>> us to remove the extensions in the ECC draft until the change is made
>> or could it proceed to last call in parallel with the change to RFC
>> 3546?

> You'd need to create a new document to revise 3546 and get WG
> consensus behind it. The documents should proceed in parallel.

Hi Eric,

I believe we are now ready for Last Call for both specifications:

1. draft-ietf-tls-rfc3546bis-00.txt (TLS Extensions)
2. draft-ietf-tls-ecc-09.txt (ECC Cipher Suites for TLS).

The former is for Standards Track; the latter would be Informational.

1. Since November, we have draft-ietf-tls-rfc3546bis-00.txt by the
   same authors as RFC 3546, with the change described above.
   Core sentence:

       "ExtensionType values are to be assigned via IETF Consensus as
       defined in RFC 2434"

   Otherwise, the ID just clarifies the handling of TLS extensions
   with session resumption (now stating that "In general the
   specification of each extension type must include a discussion of
   the effect of the extension both during new sessions and during
   resumed sessions" instead of trying to give a general rule for all
   extensions).

2. The latest revision of the TLS-ECC draft is at

       http://www.ietf.org/internet-drafts/draft-ietf-tls-ecc-09.txt

   The draft uses extension to ensure that interoperability can be
   achieved (point compression can be used if desired, e.g. to
   accomodate fielded certificates that rely on point compression, but
   is forbidden if either party does not support it; the server may
   not pick an ECC ciphersuite unless the client's ECC capabilities
   as specified in the extensions are sufficient to successfully
   finish the handshake).

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