[CFRG] Re: [IANA #1410706] Progressing draft-irtf-cfrg-kangarootwelve-16

[Colin Perkins <[e-mail]>]

Thanks, Amanda!
Colin


On 15 Jan 2025, at 2:11, Amanda Baber via RT wrote:

> Hi all,
>
> We're asking the COSE Algorithm reviewers if it's possible to make 
> assignments before the end of the IESG review.
>
> thanks,
>
> Amanda Baber
> IANA Operations Manager
>
> On Tue Jan 14 12:29:30 2025, [e-mail] wrote:
>> Hi,
>>
>> I’ve seen no objections, so I suggest we move forward with this 
>> draft
>> to the IESG conflict review. Starting the conflict review will also
>> trigger IANA to look at the draft, so we can get the parameter values
>> assigned by the expert in parallel to the IESG review.
>>
>> Colin
>>
>>
>>
>>
>> On 10 Jan 2025, at 0:00, Nick Sullivan wrote:
>>
>>> As the shepherd, I'm bumping this up in case anyone else on the list
>>> has
>>> comments. If there are no comments by tomorrow, I recommend 
>>> requesting
>>> codepoints for the IANA experts so they can be included in the RFC
>>> editor
>>> copy.
>>>
>>> Nick
>>>
>>> On Mon, Dec 30, 2024 at 4:47 AM Colin Perkins <[e-mail]>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> Thanks! The change also looks reasonable to me, but I’d like to
>>>> give the
>>>> CFRG time to review before sending this draft to the IESG for
>>>> conflict
>>>> review.
>>>>
>>>> CFRG – please review the IANA considerations section in
>>>> draft-irtf-cfrg-kangarootwelve-16
>>>> <https://datatracker.ietf.org/doc/draft-irtf-cfrg-kangarootwelve/16/>
>>>> and
>>>> comment by 10 January if you have any concerns.
>>>>
>>>> Thanks,
>>>> Colin
>>>>
>>>> On 12 Dec 2024, at 11:30, Ari Keränen wrote:
>>>>
>>>> Thanks! Looks good to me.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Ari
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Gilles VAN ASSCHE <[e-mail]>
>>>> *Date:* Thursday, 12. December 2024 at 11.41
>>>> *To:* Ari Keränen <[e-mail]>
>>>> *Cc:* Maximilian Lorlacks <[e-mail]>, The IRSG <
>>>> [e-mail]>, Colin Perkins <[e-mail]>,
>>>> [e-mail] <
>>>> [e-mail]>, [e-mail] <
>>>> [e-mail]>, [e-mail] <[e-mail]>, Nick Sullivan 
>>>> <
>>>> [e-mail]>
>>>> *Subject:* RE: [irsg] [CFRG] Ari Keränen's No Objection on
>>>> draft-irtf-cfrg-kangarootwelve-15: (with COMMENT)
>>>>
>>>> Dear Ari,
>>>>
>>>>
>>>>
>>>> We agree with your suggestion. Please find below the updated text.
>>>>
>>>>
>>>>
>>>> Kind regards,
>>>>
>>>> Gilles
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> *IANA Considerations*
>>>>
>>>> IANA has allocated entries k12-256 and k12-512 in the Named
>>>> Information
>>>> Hash Algorithm Registry. IANA is requested to update the references
>>>> to
>>>> refer to the final version of this document.
>>>>
>>>>
>>>>
>>>> The rest of this paragraph should be kept in the final document: In
>>>> the
>>>> Named Information Hash Algorithm Registry, k12-256 refers to the 
>>>> hash
>>>> function obtained by evaluating KT128 on the input message with
>>>> default C
>>>> (the empty string) and L = 32 bytes (256 bits). Similarly, k12-512
>>>> refers
>>>> to the hash function obtained by evaluating KT256 on the input
>>>> message with
>>>> default C (the empty string) and L = 64 bytes (512 bits).
>>>>
>>>>
>>>> IANA is requested to update the COSE Algorithms registry by adding
>>>> the
>>>> following entries:
>>>>
>>>> +===============+=======+===================+
>>>> | Name          | Value | Description       |
>>>> +===============+=======+===================+
>>>> | TurboSHAKE128 |       | TurboSHAKE128 XOF |
>>>> +---------------+-------+-------------------+
>>>> | TurboSHAKE256 |       | TurboSHAKE256 XOF |
>>>> +---------------+-------+-------------------+
>>>> | KT128         |       | KT128 XOF         |
>>>> +---------------+-------+-------------------+
>>>> | KT256         |       | KT256 XOF         |
>>>> +---------------+-------+-------------------+
>>>>
>>>> The Value is left to be assigned by the IANA expert. The other 
>>>> fields
>>>> (Capabilities, Change Controller, Reference and Recommended) are 
>>>> left
>>>> at
>>>> the discretion of the IANA expert.
>>>> ------------------------------
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Ari Keränen <[e-mail]>
>>>> *Sent:* mercredi 11 décembre 2024 12:27
>>>> *To:* Gilles VAN ASSCHE <[e-mail]>
>>>> *Cc:* Maximilian Lorlacks <[e-mail]>; The IRSG <
>>>> [e-mail]>; Colin Perkins <[e-mail]>;
>>>> [e-mail]; [e-mail];
>>>> [e-mail]; Nick Sullivan <[e-mail]>
>>>> *Subject:* Re: [irsg] [CFRG] Ari Keränen's No Objection on
>>>> draft-irtf-cfrg-kangarootwelve-15: (with COMMENT)
>>>>
>>>>
>>>>
>>>> Thank you, Gilles!
>>>>
>>>>
>>>>
>>>> I was still wondering is it necessary to change the names of the
>>>> allocations or would it be better just to document the existing
>>>> allocations
>>>> as such (i.e., write in the IANA considerations section “IANA has
>>>> allocated
>>>> […] IANA is requested to update the references […]”) ? Again,
>>>> thinking of
>>>> those who might be already using those values as registered.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Ari
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Gilles VAN ASSCHE <[e-mail]>
>>>> *Date:* Wednesday, 11. December 2024 at 12.16
>>>> *To:* Colin Perkins <[e-mail]>, Ari Keränen <
>>>> [e-mail]>
>>>> *Cc:* Maximilian Lorlacks <[e-mail]>, The IRSG <
>>>> [e-mail]>, [e-mail] <
>>>> [e-mail]>, [e-mail] <
>>>> [e-mail]>, [e-mail] <[e-mail]>, Nick Sullivan 
>>>> <
>>>> [e-mail]>
>>>> *Subject:* RE: [irsg] [CFRG] Ari Keränen's No Objection on
>>>> draft-irtf-cfrg-kangarootwelve-15: (with COMMENT)
>>>>
>>>> You don't often get email from [e-mail]. Learn why
>>>> this is
>>>> important <https://aka.ms/LearnAboutSenderIdentification>
>>>>
>>>> Dear all,
>>>>
>>>>
>>>>
>>>> After discussions among the authors, please find below our proposal
>>>> for
>>>> the IANA Considerations section.
>>>>
>>>>
>>>>
>>>> We welcome your feedback. We will then release a new version of the
>>>> draft
>>>> with this section added.
>>>>
>>>>
>>>>
>>>> Kind regards,
>>>>
>>>> Gilles
>>>>
>>>>
>>>> ------------------------------
>>>>
>>>> *IANA Considerations*
>>>>
>>>> IANA is requested to update the Named Information Hash Algorithm
>>>> Registry
>>>> by
>>>> - renaming k12-256 into kt128-256;
>>>> - renaming k12-512 into kt256-512;
>>>> - updating the reference of these entries to refer to the final
>>>> version of
>>>> this document.
>>>>
>>>> kt128-256 refers to the hash function obtained by evaluating KT128 
>>>> on
>>>> the
>>>> input message with default C (the empty string) and L = 32 bytes 
>>>> (256
>>>> bits). Similarly, kt256-512 refers to the hash function obtained by
>>>> evaluating KT256 on the input message with default C (the empty
>>>> string) and
>>>> L = 64 bytes (512 bits).
>>>>
>>>> The ID value is left blank or to be assigned by the IANA expert.
>>>>
>>>> +====+==================+==============+
>>>> | ID | Hash Name String | Value Length |
>>>> +====+==================+==============+
>>>> |    | kt128-256        | 256 bits     |
>>>> +----+------------------+--------------+
>>>> |    | kt256-512        | 512 bits     |
>>>> +----+------------------+--------------+
>>>>
>>>> IANA is requested to update the COSE Algorithms registry by adding
>>>> the
>>>> following entries:
>>>>
>>>> +===============+=======+===================+
>>>> | Name          | Value | Description       |
>>>> +===============+=======+===================+
>>>> | TurboSHAKE128 |       | TurboSHAKE128 XOF |
>>>> +---------------+-------+-------------------+
>>>> | TurboSHAKE256 |       | TurboSHAKE256 XOF |
>>>> +---------------+-------+-------------------+
>>>> | KT128         |       | KT128 XOF         |
>>>> +---------------+-------+-------------------+
>>>> | KT256         |       | KT256 XOF         |
>>>> +---------------+-------+-------------------+
>>>>
>>>> The Value is left to be assigned by the IANA expert. The other 
>>>> fields
>>>> (Capabilities, Change Controller, Reference and Recommended) are 
>>>> left
>>>> at
>>>> the discretion of the IANA expert.
>>>> ------------------------------
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Gilles VAN ASSCHE <[e-mail]>
>>>> *Sent:* vendredi 29 novembre 2024 17:58
>>>> *To:* Colin Perkins <[e-mail]>; Ari Keränen <
>>>> [e-mail]>
>>>> *Cc:* Maximilian Lorlacks <[e-mail]>; The IRSG <
>>>> [e-mail]>; [e-mail];
>>>> [e-mail]; [e-mail]; Nick Sullivan <
>>>> [e-mail]>
>>>> *Subject:* RE: [irsg] [CFRG] Ari Keränen's No Objection on
>>>> draft-irtf-cfrg-kangarootwelve-15: (with COMMENT)
>>>>
>>>>
>>>>
>>>> Dear Ari, Carsten, Colin, Max, all,
>>>>
>>>>
>>>>
>>>> Many thanks for your feedback on this matter. We will work on the
>>>> IANA
>>>> considerations and make a concrete proposal.
>>>>
>>>>
>>>>
>>>> Kind regards,
>>>>
>>>> Gilles
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ST Restricted
>>>>
>>>> *From:* Colin Perkins <[e-mail]>
>>>> *Sent:* vendredi 29 novembre 2024 16:16
>>>> *To:* Ari Keränen <[e-mail]>
>>>> *Cc:* Gilles VAN ASSCHE <[e-mail]>; Maximilian
>>>> Lorlacks <
>>>> [e-mail]>; The IRSG <[e-mail]>;
>>>> [e-mail]; [e-mail];
>>>> [e-mail]; Nick Sullivan <[e-mail]>
>>>> *Subject:* Re: [irsg] [CFRG] Ari Keränen's No Objection on
>>>> draft-irtf-cfrg-kangarootwelve-15: (with COMMENT)
>>>>
>>>>
>>>>
>>>> Hi,
>>>>
>>>> That’s a good point.
>>>> Colin
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> ST Restricted
>>>>
>>>> On 27 Nov 2024, at 7:27, Ari Keränen wrote:
>>>>
>>>> Hi,
>>>>
>>>>
>>>>
>>>> Given the registration has already been done and someone might be
>>>> using
>>>> these, removing them now sounds sub-optimal to me. I’d rather
>>>> suggest just
>>>> documenting in the IANA section that these were allocated with a 
>>>> note
>>>> that
>>>> future allocations would be handled differently. Perhaps adding a 
>>>> few
>>>> words
>>>> on why the two entries were (originally?) considered important 
>>>> enough
>>>> to
>>>> register (e.g., that have typically used parameter values).
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Cheers,
>>>>
>>>> Ari
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *From:* Colin Perkins <[e-mail]>
>>>> *Date:* Wednesday, 27. November 2024 at 1.13
>>>> *To:* Gilles VAN ASSCHE <[e-mail]>
>>>> *Cc:* Maximilian Lorlacks <[e-mail]>, Ari Keränen 
>>>> <
>>>> [e-mail]>, The IRSG <[e-mail]>,
>>>> [e-mail] <
>>>> [e-mail]>, [e-mail] <
>>>> [e-mail]>, [e-mail] <[e-mail]>, Nick Sullivan 
>>>> <
>>>> [e-mail]>
>>>> *Subject:* Re: [irsg] [CFRG] Ari Keränen's No Objection on
>>>> draft-irtf-cfrg-kangarootwelve-15: (with COMMENT)
>>>>
>>>> Hi,
>>>>
>>>> That’s fine from my part – but you will need to add an IANA
>>>> Considerations
>>>> section to the draft to request IANA do so.
>>>>
>>>> Colin
>>>>
>>>>
>>>>
>>>> On 25 Nov 2024, at 10:58, Gilles VAN ASSCHE wrote:
>>>>
>>>> Hi Colin,
>>>>
>>>>
>>>>
>>>> Good point. After discussions among the authors, we suggest 
>>>> removing
>>>> the
>>>> k12-256 and k12-512 entries from the registry.
>>>>
>>>>
>>>>
>>>> Kind regards,
>>>>
>>>> Gilles
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *ST Restricted*
>>>>
>>>> *From:* Colin Perkins <[e-mail]>
>>>> *Sent:* jeudi 21 novembre 2024 14:43
>>>> *To:* Gilles VAN ASSCHE <[e-mail]>
>>>> *Cc:* Maximilian Lorlacks <[e-mail]>; Ari Keränen 
>>>> <
>>>> [e-mail]>; The IRSG <[e-mail]>;
>>>> [e-mail]; [e-mail];
>>>> [e-mail]; Nick Sullivan <[e-mail]>
>>>> *Subject:* Re: [irsg] [CFRG] Ari Keränen's No Objection on
>>>> draft-irtf-cfrg-kangarootwelve-15: (with COMMENT)
>>>>
>>>>
>>>>
>>>> Hi,
>>>>
>>>> The existing registry (
>>>> https://www.iana.org/assignments/named-information/named-information.xml)
>>>> points to an old version (-06) of this draft. Is that still
>>>> appropriate, or
>>>> should the registry be updated to either remove these entries or to
>>>> point
>>>> to the RFC number assigned to this draft once published?
>>>>
>>>> Colin
>>>>
>>>> On 19 Nov 2024, at 12:13, Gilles VAN ASSCHE wrote:
>>>>
>>>> Dear Ari, dear Max,
>>>>
>>>> In the past, we discussed internally about the Named Information 
>>>> Hash
>>>> Algorithm Registry, and we decided that no IANA actions were 
>>>> needed.
>>>> The
>>>> reason is that the registry contains fixed-output length hash
>>>> functions,
>>>> whereas our draft proposes extendable output functions (XOFs) that
>>>> have no
>>>> defined output length. As for the two existing entries, I would not
>>>> go
>>>> further adding (XOF, output length) pairs as hash functions, 
>>>> because
>>>> the
>>>> list is potentially infinite.
>>>>
>>>> Instead, in the long run, it may be interesting to create a 
>>>> registry
>>>> dedicated to XOFs, but at this moment, I would just leave it as it
>>>> is.
>>>>
>>>> Kind regards,
>>>> Gilles
>>>>
>>>> ST Restricted
>>>> -----Original Message-----
>>>> From: Maximilian Lorlacks [e-mail]
>>>> Sent: vendredi 15 novembre 2024 18:40
>>>> To: Ari Keränen [e-mail]
>>>> Cc: The IRSG [e-mail]; 
>>>> [e-mail];
>>>> [e-mail]; [e-mail]; Nick Sullivan
>>>> [e-mail]
>>>> Subject: Re: [CFRG] Ari Keränen's No Objection on
>>>> draft-irtf-cfrg-kangarootwelve-15: (with COMMENT)
>>>>
>>>> Hi all,
>>>>
>>>> Looking at the NIH entry, I couldn't help but notice that it 
>>>> predates
>>>> TurboSHAKE. If an IANA considerations section is introduced, would
>>>> the
>>>> authors feel like it would be helpful to include a TurboSHAKE 
>>>> profile
>>>> for
>>>> NIH as well?
>>>>
>>>> Cheers,
>>>>
>>>> Max
>>>>
>>>> Sent with Proton Mail secure email.
>>>>
>>>> On Friday, November 15th, 2024 at 1:39 PM, Ari Keränen via
>>>> Datatracker
>>>> [e-mail] wrote:
>>>>
>>>> Ari Keränen has entered the following ballot position for
>>>> draft-irtf-cfrg-kangarootwelve-15: No Objection
>>>>
>>>> When responding, please keep the subject line intact and reply to 
>>>> all
>>>> email addresses included in the To and CC lines. (Feel free to cut
>>>> this introductory paragraph, however.)
>>>>
>>>> The document, along with other ballot positions, can be found here:
>>>> https://datatracker.ietf.org/doc/draft-irtf-cfrg-kangarootwelve/
>>>> ------------------------------
>>>> COMMENT:
>>>>
>>>> Given there are two registrations of Hash Name Strings for this 
>>>> draft
>>>> in the Named Information IANA registry
>>>> (https://www.iana.org/assignments/named-information/named-information.
>>>> xhtml), this would be useful to be noted in the IANA Considerations
>>>> section.
>>>> ------------------------------
>>>>
>>>> CFRG mailing list -- [e-mail]
>>>> To unsubscribe send an email to [e-mail]
>>>>
>>>>