[art] Re: AD Evaluation: draft-barnes-sframe-iana-256-00

[Martin Thomson <[e-mail]>]

On Sat, Jan 17, 2026, at 03:41, Aron Rosenberg wrote:
> We changed the Change Controller portion of the registry because it was 
> not actually the original intent of the original authors to require a 
> new RFC for introducing a new cipher suite definition. 

That's a misunderstanding of what the change controller is for.

If the IETF is responsible for maintaining an entry, then it is the change controller.

But if an independent entity (Apple as an organization or just the individual Richard Barnes) wants to register an entry, they can become the change controller.  The question the field answers is "who does IANA ask to approve a change to that entry?"  That's an important field for maintaining the registry.

The registry operates under "specification required", which is the same "expert review" plus a requirement to have a specification.  If you think a specification is too onerous, I'd like to understand why.  You have defined the three new entries in this document in a single small paragraph, meeting the requirement easily.  I don't think that it could be made much easier without compromising the openness of the protocol.