All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taehee Yoo <ap420073@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH 0/2] crypto: Introduce ARIA symmetric cipher algorithm
Date: Thu, 30 Jun 2022 16:13:19 +0900	[thread overview]
Message-ID: <50203730-35f1-4bf9-3f3a-ca6cd3b01d4a@gmail.com> (raw)
In-Reply-To: <Yr1FBOC8Zi1ltlBi@gondor.apana.org.au>

On 6/30/22 15:39, Herbert Xu wrote:

Hi Herbert,
Thank you so much for your review!

 > Taehee Yoo <ap420073@gmail.com> wrote:
 >> This patchset adds a new ARIA(RFC 5794) symmetric cipher algorithm.
 >>
 >> Like SEED, the ARIA is a standard cipher algorithm in South Korea.
 >> Especially Government and Banking industry have been using this 
algorithm.
 >> So the implementation of ARIA will be useful for them and network 
vendors.
 >>
 >> Usecases of this algorithm are TLS[1], and IPSec.
 >> It would be very useful for them if it implements kTLS for ARIA.
 >
 > You haven't added any glue to use this for IPsec.  Unless there is
 > an in-kernel user we won't add any new algorithms.
 >
 > Thanks,

Unfortunately, IPsec draft[1] is expired so I think adding the 
aria-IPsec feature is not our rule as far as I know even if there are 
already  users in South Korea.
So, my plan is to add the kTLS feature because aria-TLS[2] is now standard.
So, Is it okay to add the aria-kTLS feature into the v2 patch, instead 
of aria-IPsec?

[1] https://datatracker.ietf.org/doc/draft-nsri-ipsecme-aria-ipsec/
[2] https://datatracker.ietf.org/doc/html/rfc6209

Thanks,
Taehee Yoo

  reply	other threads:[~2022-06-30  7:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20 16:41 [PATCH 0/2] crypto: Introduce ARIA symmetric cipher algorithm Taehee Yoo
2022-06-20 16:41 ` [PATCH 1/2] crypto: Implement " Taehee Yoo
2022-06-20 16:41 ` [PATCH 2/2] crypto: add ARIA testmgr tests Taehee Yoo
2022-06-30  6:39 ` [PATCH 0/2] crypto: Introduce ARIA symmetric cipher algorithm Herbert Xu
2022-06-30  7:13   ` Taehee Yoo [this message]
2022-06-30  7:16     ` Herbert Xu
2022-06-30  7:22       ` Taehee Yoo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50203730-35f1-4bf9-3f3a-ca6cd3b01d4a@gmail.com \
    --to=ap420073@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.