[saag] Re: draft-paulwh-crypto-components-02
Christian Huitema <[email protected]>
| Newsgroups | gmane.ietf.saag |
|---|---|
| Message-ID | <[email protected]> |
Your version 2 draft revises the 6th paragraph in section 3.4 to say: 'Working groups setting up such registries should strongly consider mandating that decisions on setting the values in these columns to anything other than "MAY" require a standards track RFC. That is, Independent Stream and IRTF RFCs would not be able to set or change the values in such a table in an IANA registry.' I am not sure I understand the paragraph. Did you mean that the WG should think twice before asking the IANA to only update the registry if the changed is detailed in a standard track RFC? That WG that define a registry with options such as "may implement, should implement, must implement" should not require a standard track RFC if developers are not required to implement the algorithm (i.e., "may implement")? Or that WG should absolutely ask the IANA to require a standard track RFC before describing an algorithm as "mandatory to implement"? Or some combination? By the way, I would suggest sticking to terms like optional and mandatory instead of using circumlocution such as `other than MAY`. I understand that using MAY and MUST as nouns is common jargon in the IETF, but it is rather puzzling for outsiders. -- Christian Huitema On 2/11/2025 1:33 PM, Paul Hoffman wrote: > Greetings again. Thanks for the reviews of draft-paulwh-crypto-components-01. PaulW and I have made some small but significant updates based on those reviews to clarify the role of working groups for registries. The diffs are at: > https://author-tools.ietf.org/iddiff?url2=draft-paulwh-crypto-components-02 > > More reviews are welcome. We may be heading toward SAAG consensus, at which point we can take it to the wider IETF community. > > --Paul Hoffman > > _______________________________________________ > saag mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ saag mailing list -- [email protected] To unsubscribe send an email to [email protected]