Re: [Cfrg] RFC 5742 conflict review for draft-dolmatov-kuznyechik

Dear colleagues,

in my opinion,
- no strong arguments against Kuznyechik's security have been proposed;
- this RFC draft has nothing in common with concrete proposals of algorithm
usage in cryptographic protocols, so anyway we don't have potential
security risks that can immediately follow from adoption of this draft;
- a strong need of RFC with Kuznyechik exists due to the fact that in
several years it will become a №1 cipher in Russia and a reference problem
will be important for multi-algorithm cryptographic software development
and usage;
- the RFC draft itself is well-structured and complete.

I think the draft can be adopted in the current form.

Best regards,
Stanislav Smyshlyaev, Ph.D.,
Head of Information Security Department,
CryptoPro LLC

Alexey Melnikov <alexey.melnikov@isode.com> writes:

> Dear CFRG participants,
>
> On February 4th the IESG will be doing the conflict review for a draft
> [1] that describes GOST R 34.12-2015: Block Cipher
> "Kuznyechik". Stephen Farrell is handling this document on behalf of
> IESG. Stephen asked for feedback from CFRG.
>
> Since national algorithms are typically documented as independent
> submission stream RFCs, I think this one does not represent a conflict
> with ongoing IETF work or process. If you disagree, please let Stephen
> and CFRG chairs know.
>
> Should someone want code points for using this algorithm in IETF
> protocols, that would of course go through the normal IETF consensus
> process. See RFC 5742 [2] for details of what this bit of process is
> about.
>
> If you have comments on the draft content then please send those to
> the authors and cc the independent submissions editor, Nevil Brownlee
> (rfc-ise@rfc-editor.org).
>
> Best Regards,
> Alexey, on behalf of CFRG chairs.
>
> [1] https://datatracker.ietf.org/doc/draft-dolmatov-kuznyechik/
> [2] https://tools.ietf.org/html/rfc5742
> _______________________________________________
> Cfrg mailing list
> Cfrg@irtf.org
> https://www.irtf.org/mailman/listinfo/cfrg
>