> On Mar 12, 2018, at 19:58, Adam Roach <a...@nostrum.com> wrote: > > On 3/7/18 12:58 PM, Eric Rescorla wrote: >> > > - TLS SignatureScheme Registry: Values with the first byte in the >> > > range 0-253 (decimal) are assigned via Specification Required >> > > [RFC8126]. Values with the first byte 254 or 255 (decimal) are >> > > reserved for Private Use [RFC8126]. Values with the first byte in >> > > the range 0-6 or with the second byte in the range 0-3 that are >> > > not currently allocated are reserved for backwards compatibility. >> > >> > Unless I misunderstand the compatibility mechanisms here, the reservation >> > of >> > first byte=0-6 seems to assume that no further assignments will be made >> > from >> > the "TLS HashAlgorithm Registry" (after 4492bis lands). If this is the >> > case, I >> > would expect the IANA considerations section to include a request that the >> > IANA >> > close the table to further registrations. The same comment applies to TLS >> > SignatureAlgorithm Registry. >> >> Agreed, but I'd like to hear from the chairs. > > > I think we're still waiting to hear from the chairs on this topic. > > /a
I think this got lost somewhere in the flurry of emails: See s17 of https://datatracker.ietf.org/doc/draft-ietf-tls-iana-registry-updates/ We don’t close the registry because technically, if somebody really, really wanted to they could register values for earlier versions. spt _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
