Re: [openpgp] [IANA #1291713] Ballot issued: <draft-ietf-openpgp-crypto-refresh-12.txt> to Proposed Standard

[Stephen Farrell <[e-mail]>]

Hi Amanda,

(Cc'ing the WG just in case.)

I can't think of any reason why changing the names of the registries
would be a problem, and as you say, that could help with clarity for
future discussions related to these and similar registries for other
protocols.

So, my take is that that's a fine change. If anyone on the list has
a reason to not like that change, please say. (This does not affect
the actual protocol, just the registry names. I guess there's a very
small chance someone has tooling that depends on those names, but I'd
be surprised if that were the case.)

For clarity: the current set of registries can be seen here. [1]
The change suggested here is just to prepend "OpenPGP" to the names of
the various registries at the same time as making other changes from
crypto-refresh.

Cheers,
S.

[1] https://www.iana.org/assignments/pgp-parameters/pgp-parameters.xhtml

On 13/12/2023 01:00, Amanda Baber via RT wrote:
> Hi all,
> 
> Resending this IANA question.
> 
> thanks,
> 
> Amanda Baber
> IANA Operations Manager
> 
> On Thu Dec 07 20:34:34 2023, amanda.baber wrote:
>> Dear Authors,
>>
>> Would it be possible/appropriate to prepend "OpenPGP" to the registry
>> names in this document? The TLS WG did something similar for their
>> registries:
>>
>> https://www.iana.org/assignments/tls-parameters
>>
>> I ask because several registry names are common to other registry
>> groups. For example, there are 14 occurrences of "Hash Algorithms" in
>> the list of registries maintained by IANA:
>>
>> https://www.iana.org/protocols
>>
>> And there's an "AEAD Algorithms" at
>>
>> https://www.iana.org/assignments/aead-parameters
>>
>> thanks,
>>
>> Amanda Baber
>> IANA Operations Manager
>