OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

pkcs11 message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [pkcs11] Russian algorithms question on the mailing list


The mailing this is open for all discussion between TC members so you should feel free to email on topics.
For outsiders (non-TC members) who want to contribute - they have to send their emails via the pkcs11-comments list - to cover off on the OASIS IPR requirements.

Ultimately, the TC has to vote to include the material, and that generally means at least one member is interested in it in my experience.

In an OpenSSL context, you should look atÂhttps://github.com/gost-engine/engine which will also point you atÂhttps://www.altlinux.org/OSS-GOST-Crypto for reference information.

Tim.


On Wed, Oct 3, 2018 at 10:40 PM Johnson Darren <darren.johnson@gemalto.com> wrote:

Hi,

Iâm sure everyone noticed the question and proposal for GOST R 34.10.2012 and GOST R 34.11.2012. Normally we discuss new comments on the mailing list before replying. ÂIs that the preferred/required process? Discuss the comments internally as a TC first before replying? Or is the mailing list more of an open forum and we can reply as we see fit?

Â

What is the process for handling external proposals? Can they champion their own proposal and we provide feedback via email or the list? Or does a TC member need to support them?

Â

Does anyone on the TC have any experience with the newer GOST algorithms? Â

Â

Finally I recall that we discussed some new requirements about how proposals should be written up, to make the editors job easier. Did we finalize on that topic? With that in mind, should we ask Ivan to modify his proposal so that it is in a format more consistent with the current standard, so that it is easier to review and incorporate?

Â

Thanks

Darren


This message and any attachments are intended solely for the addressees and may contain confidential information. Any unauthorized use or disclosure, either whole or partial, is prohibited.
E-mails are susceptible to alteration. Our company shall not be liable for the message if altered, changed or falsified. If you are not the intended recipient of this message, please delete it and notify the sender.
Although all reasonable efforts have been made to keep this transmission free from viruses, the sender will not be liable for damages caused by a transmitted virus.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]