Arguably, "national" crypto specifications garnish more stature if these
are made available to the pubic by that standard-setting body itself
(who, thereby, acts as its authoritative source), without deference to a
third party (that may, independently from the originator, enforce
document control [e.g., by effectuating technical changes or enforcing
controlled dissemination]).
Since your draft introducing SM cipher suites with TLS1.3 appeals to the
authority of a standard-setting authority, easy availability of the full
and accredited technical documentation to the IETF community helps in
scrutiny and, e.g., evaluating claims in the security considerations
section.
On 8/16/2019 3:06 AM, Kepeng Li wrote:
Hi Rene and all,
> Since the ISO documents are not available to the general > public without payment, it would be helpful to have a freely
available > document (in English) from an authoritative source. Having
such a > reference available would be helpful to the IETF community
(and > researchers).
About the references to ISO documens, I think it is a general issue
for IETF drafts.
How does the other IETF drafts make the references to ISO documents?
ISO documents are often referenced by IETF drafts.
Thanks,
Kind Regards
Kepeng
——————————————————————————————————————————————————————————————————
Re: [TLS] Draft for SM cipher suites used in TLS1.3
Rene Struik <[email protected] <mailto:[email protected]>>Thu,
15 August 2019 15:34 UTCShow header
<https://mailarchive.ietf.org/arch/browse/tls/?index=NHbHOGtsR1S5cCr9nWN9_sdyTgg&gbt=1#>
Hi Paul:
I tried and look up the documents GMT.0009-2012 and GBT.32918.5-2016 on
the (non-secured) websites you referenced, but only found Chinese
versions (and Chinese website navigation panels [pardon my poor language
skills here]). Since the ISO documents are not available to the general
public without payment, it would be helpful to have a freely available
document (in English) from an authoritative source. Having such a
reference available would be helpful to the IETF community (and
researchers). Please note that BSI provides its specifications in German
and English, so as to foster use/study by the community. If the Chinese
national algorithms would be available in similar form, this would serve
a similar purpose.
FYI - I am interested in full details and some time last year I tried to
download specs, but only Parts 2, 4, and 5 were available [1], [2], [3],
not Parts 1 and 3.
Best regards, Rene
[1] China ECC - Public Key Cryptographic Algorithm SM2 Based on ECC -
Part 5 - Parameter Definition (SEMB, July 24, 2018)
[2] China ECC - Public Key Cryptographic Algorithm SM2 Based on ECC -
Part 2 - Digital Signature Algorithm (SEMB, July 24, 2018)
[3] China ECC - Public Key Cryptographic Algorithm SM2 Based on ECC -
Part 4 - Public Key Encryption Algorithm (SEMB, July 24, 2018)
On 8/15/2019 10:16 AM, Paul Yang wrote:
> Hi all,
>
> I have submitted a new internet draft to introduce the SM cipher
> suites into TLS 1.3 protocol.
>
> https://tools.ietf.org/html/draft-yang-tls-tls13-sm-suites-00
>
> SM cryptographic algorithms are originally a set of Chinese national
> algorithms and now have been (or being) accepted by ISO as
> international standards, including SM2 signature algorithm, SM3 hash
> function and SM4 block cipher. These algorithms have already been
> supported some time ago by several widely used open source
> cryptographic libraries including OpenSSL, BouncyCastle, Botan, etc.
>
> Considering TLS1.3 is being gradually adopted in China's internet
> industry, it's important to have a normative definition on how to use
> the SM algorithms with TLS1.3, especially for the mobile internet
> scenario. Ant Financial is the company who develops the market leading
> mobile app 'Alipay' and supports payment services for Alibaba
> e-commerce business. We highly are depending on the new TLS1.3
> protocol for both performance and security purposes. We expect to have
> more deployment of TLS1.3 capable applications in China's internet
> industry by this standardization attempts.
>
> It's very appreciated to have comments from the IETF TLS list :-)
>
> Many thanks!
>
> _______________________________________________
> TLS mailing list
> [email protected] <mailto:[email protected]>
> https://www.ietf.org/mailman/listinfo/tls
--
email: [email protected] | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363
_______________________________________________
TLS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tls
