On Fri, Mar 16, 2018 at 02:01:48PM +0000, Sean Turner wrote: > During Adam Roach’s AD review of draft-ietf-tls-tls13, he noted something > about the HashAlgorithm and that made me go look at what was said in > draft-ietf-tls-iana-registry-updates. Turns out that 4492bis assigned some > values draft-ietf-tls-iana-registry-updates was marking as reserved. I have > fixed that up in: > https://github.com/tlswg/draft-ietf-tls-iana-registry-updates/pull/65 > > One further point brought out in discussions with Adam was that if we’re > really closing the HashAlgorithm and SignatureAlgorithms registry we need to > also mark 224-255 as deprecated. Currently these are marked as Reserved for > Private Use. So the question is should we mark 224-255 as deprecated in > these two registries?
With no hats, yes, we should mark those ranges as deprecated, since there is no warning about them in the SignatureScheme registry and the latter is the way of the future. -Ben _______________________________________________ TLS mailing list TLS@ietf.org https://www.ietf.org/mailman/listinfo/tls
