I support early code point assignment. It’s been suggested that as long as the CFRG signature curves document is not finalized, we should wait with the eddsa_* ones. I don’t believe so. Anything in any draft is subject to change up to the time it’s published and people who implement internet draft should make allowances for such a risk. I see no problem with assigning numbers now. It does not make sense to ship a version of a product that you’ll have to support backwards compatibility with forever. But it is up to implementers to be smart enough about this.
Yoav > On 23 Nov 2015, at 4:21 PM, Sean Turner <s...@sn3rd.com> wrote: > > All, > > We’ve received an early code point assignment for the following 4 (four) > elliptic curve points that will go in the "Supported Groups" Registry: > > // ECDH functions. > ecdh_x25519 > ecdh_x448 > > // Signature curves. > eddsa_ed25519 > eddsa_ed448 > > These points will be included in the following 2 (two) drafts: > draft-ietf-tls-tls13 > draft-ietf-tls-rfc4492bis. > > Early code points are permitted in the “Supported Groups” registry and the > chairs (that’s us) need to determine whether there is support for these > assignments. Some input has already been received and those people do not > need to respond again to this call, but we’d like to hear from others whether > they support early code point assignment for these curves. If you do not > please state why. We’re looking for input by November 30th. > > J&S > _______________________________________________ > TLS mailing list > TLS@ietf.org > https://www.ietf.org/mailman/listinfo/tls _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
