On 7/19/2021 10:16 AM, Salz, Rich wrote:
I support publication.
https://datatracker.ietf.org/doc/draft-ietf-tls-cross-sni-resumption/
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
Nit - which also applies to draft-ietf-tls-flags: In the IANA
considerations section, the Value field is expressed as 0x8 - a hex
value - rather than 8 a decimal value. Given that the registry uses
decimal bit number positions, and that a hex value might be confused
with a mask (e.g. 0x8 might be confused with bit 5), I'd suggest
dropping the "0x". Or, to keep this more in keeping with normal
practice, specify Value as "TBD" and have the IANA do the actual
assignment consistent with policy - it's a good way to ensure the WG and
the IANA are on the same page. If that change is made, add a "to be
removed before publication" note to the IANA indicating that you want
the assignment to be made out of the 8-31 range. Section 3 would also
need to change to remove "(8)";
Nit: Section 4 - it's not clear that "Section 4.6.1" refers to RFC8846
(at least in the text version) as opposed to a mis-numbered section -
instead I suggest: "Section 4.6.1 of that document"
Mike
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
