> On Oct 25, 2024, at 10:52, Salz, Rich <rs...@akamai.com> wrote: > > I mean "IANA cannot have designated..." > > I blame auto-correct. Or outlook. Anyone other than me. > > On 10/25/24, 10:50 AM, "Salz, Rich" wrote: > >> The following PR creates the TLS Flags sub-registry where we can manage the >> actual flags. I asserted that the chairs control adding values, which won’t >> be true once (and if) the registry goes to IANA (it’ll be the DEs: Rich, >> Nick, and Yoav), and populated the 1st value from the draft: >> resumption_across_names. Assuming this is good, I will merge the PR. > > > Apparently IANA can have designated experts control things until the RFC is > published.
Oh, if DEs can (or are willing) to do it then I am all about having you manage it! PR updated: https://github.com/tlswg/wg-materials/pull/22/files > Does this mean we'll need a new RFC to switch things? Or can it be done by > IESG telling IANA? If the latter, than maybe we do a little dance to say IESG > designated control to the TLS WG Chairs and then IESG designates control to > the regular TLS designated experts? But if the proposal you're saying works, > great. I'm just interested in trying to avoid administrivia while we wait to > get this new sub-registry into our hot little hands :) My thinking is that the repo is just going to get PRed to just refer to the IANA sub-registry when it is created ;) spt _______________________________________________ TLS mailing list -- tls@ietf.org To unsubscribe send an email to tls-le...@ietf.org
