[prev in list] [next in list] [prev in thread] [next in thread]
List: ietf-tls
Subject: [TLS] =?utf-8?q?Re=EF=BC=9A_=28offline=29_Re=3A__Draft_for_SM_ci?= =?utf-8?q?pher_suites_used_in_TLS
From: "Kepeng Li" <kepeng.lkp () alibaba-inc ! com>
Date: 2019-08-19 11:51:31
Message-ID: 20a27f61-98cf-4b2c-b6a8-e25aabd56099.kepeng.lkp () alibaba-inc ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
[Attachment #4 (text/plain)]
Currently, we uploaded some of the referenced documents here:
https://github.com/alipay/tls13-sm-spec
@Rene, Parts 1 and 3 can be found in the link above.
Hope it helps.
Thanks,
Kind Regards
Kepeng
------------------------------------------------------------------
发件人：李克鹏(易深) <kepeng.lkp@antfin.com>
发送时间：2019年8月19日(星期一) 17:38
收件人：sean+ietf <sean+ietf@sn3rd.com>; joe <joe@salowey.net>; caw \
<caw@heapingbits.net> 抄 送：tls@ietf.org <tls@ietf.org>; "Blumenthal, Uri - \
0553 - MITLL" <uri@ll.mit.edu>; Paul Yang <kaishen.yy=40alipay.com@dmarc.ietf.org> \
主 题：Re: [TLS] (offline) Re: Draft for SM cipher suites used in TLS1.3
Hi WG chairs,
Can we place the referenced documents in the TLS WG GitHub?
https://github.com/tlswg
According to the discussion below, this can help people to read and understand the \
referenced specifications.
Thanks,
Kind Regards
Kepeng
发件人: TLS <tls-bounces@ietf.org> 代表 "Blumenthal, Uri - 0553 - MITLL" \
<uri@ll.mit.edu> 日期: 2019年8月18日 星期日 22:08
收件人: Paul Yang <kaishen.yy=40alipay.com@dmarc.ietf.org>
抄送: "tls@ietf.org" <tls@ietf.org>
主题: Re: [TLS] (offline) Re: Draft for SM cipher suites used in TLS1.3
IMHO, placing the documents on GitHub would be perfect, and quite sufficient.
Please make sure to post the name of the repo here. ;/)
I leave it to others to decide whether they'd want copies of today PDF files sent to \
the mailing list directly. Regards,
Uri
Sent from my iPhone
On Aug 17, 2019, at 01:03, Paul Yang <kaishen.yy=40alipay.com@dmarc.ietf.org> wrote:
Good points.
The good news is that we have found some English PDFs of SM2, including the missing \
part 1 and part 3. Will continue to find English translations of other SM standards \
mentioned in the draft. So, if we host a free website, say on Github or so, to \
provide those docs, is it convenient for you guys? Or should we just drop the PDF \
files to this mailing list as attachments?
On Aug 16, 2019, at 10:58 PM, Rene Struik <rstruik.ext@gmail.com> wrote:
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 <rstruik.ext@gmail.com> Thu, 15 August 2019 15:34 UTCShow header
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
> TLS@ietf.org
> https://www.ietf.org/mailman/listinfo/tls
--
email: rstruik.ext@gmail.com | Skype: rstruik
cell: +1 (647) 867-5658 | US: +1 (415) 690-7363
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
Regards,
Paul Yang
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
_______________________________________________ TLS mailing list TLS@ietf.org \
https://www.ietf.org/mailman/listinfo/tls
[Attachment #5 (text/html)]
<div class="__aliyun_email_body_block"><div style="clear:both;"><span \
style="color:#000000;font-size:16.0px;font-family:arial;">Currently, we uploaded some \
of the referenced documents here:</span></div><div style="clear:both;"><span \
style="color:#000000;font-size:16.0px;font-family:arial;"><a \
href="https://github.com/alipay/tls13-sm-spec">https://github.com/alipay/tls13-sm-spec</a></span></div><div \
style="clear:both;"><br ></div><div style="clear:both;"><span \
style="font-size:16.0px;font-family:arial;">@Rene, <span \
style="color:#212529;font-family:arial;font-size:16.0px;">Parts 1 and 3 can be found \
in the link above.</span></span></div><div style="clear:both;"><span \
style="color:#000000;font-size:16.0px;font-family:arial;"><br ></span></div><div \
style="clear:both;"><span style="font-size:16.0px;font-family:arial;">Hope it \
helps.</span></div><div style="clear:both;"><br ></div><div \
style="clear:both;"><span \
style="font-size:16.0px;font-family:arial;">Thanks,</span></div><div \
style="clear:both;"><br ></div><div style="clear:both;"><span \
style="font-size:16.0px;font-family:arial;">Kind Regards</span></div><div \
style="clear:both;"><span \
style="font-size:16.0px;font-family:arial;">Kepeng</span></div><div \
style="clear:both;"><span \
style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;"><br \
></span></div><blockquote \
> style="margin-right:.0px;margin-top:.0px;margin-bottom:.0px;"><div \
> style="clear:both;"><span \
> style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">------------------------------------------------------------------</span></div><div \
> style="clear:both;"><span \
> style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">发件人：李克鹏(易深) \
> <kepeng.lkp@antfin.com></span></div><div style="clear:both;"><span \
> style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">发送时间：2019年8月19日(星期一) \
> 17:38</span></div><div style="clear:both;"><span \
> style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">收件人：sean+ietf \
> <sean+ietf@sn3rd.com>; joe <joe@salowey.net>; caw \
> <caw@heapingbits.net></span></div><div style="clear:both;"><span \
> style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">抄 送：tls@ietf.org \
> <tls@ietf.org>; "Blumenthal, Uri - 0553 - MITLL" <uri@ll.mit.edu>; Paul \
> Yang <kaishen.yy=40alipay.com@dmarc.ietf.org></span></div><div \
> style="clear:both;"><span \
> style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;">主 题：Re: \
> [TLS] (offline) Re: Draft for SM cipher suites used in TLS1.3</span></div><div \
> style="clear:both;"><span \
> style="font-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000;"><br \
> ></span></div><style >!-- @font-face{font-family:Helvetica;panose-1:0 0 0 0 0 0 0 \
> > 0 0 0;}{font-family:宋体;panose-1:2 1 6 0 3 1 1 1 1 1;}{font-family:Cambria \
> > Math;panose-1:2 4 5 3 5 4 6 3 2 4;}{font-family:DengXian;panose-1:2 1 6 0 3 1 1 1 \
> > 1 1;}{font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 \
> > 4;}{font-family:Tahoma;panose-1:2 11 6 4 3 5 4 4 2 4;}{font-family:lucida \
> > Grande;panose-1:2 11 6 0 4 5 2 2 2 4;}{font-family:Menlo;panose-1:2 11 6 9 3 8 4 \
> > 2 2 4;}{font-family:\@等线;panose-1:2 1 6 0 3 1 1 1 1 \
> > 1;}{font-family:\@宋体;panose-1:2 1 6 0 3 1 1 1 1 1;}p.MsoNormal, li.MsoNormal, \
> > div.MsoNormal{margin:.0cm;margin-bottom:.0pt;font-size:12.0pt;font-family:宋体;}h3{mso-style-priority:9;mso-style-link: \
> > 题 3 字符;mso-margin-top-alt:auto;margin-right:.0cm;mso-margin-bottom-alt:auto;margin-left:.0cm;font-size:13.5pt;font-family:宋体;}a:link, \
> > span.MsoHyperlink{mso-style-priority:99;color:blue;text-decoration:underline;}a:visited, \
> > span.MsoHyperlinkFollowed{mso-style-priority:99;color:purple;text-decoration:underline;}pre{mso-style-priority:99;mso-style-link:HTML \
> > 预设 式 字符;margin:.0cm;margin-bottom:.0pt;font-size:12.0pt;font-family:宋体;}p.msonormal0, \
> > li.msonormal0, div.msonormal0{mso-style-name:msonormal;mso-margin-top-alt:auto;mar \
> > gin-right:.0cm;mso-margin-bottom-alt:auto;margin-left:.0cm;font-size:12.0pt;font-family:宋体;}span.HTML{mso-style-name:HTML \
> > 预设 式 字符;mso-style-priority:99;mso-style-link:HTML 预设 \
> > 式;font-family:Courier New;}span.3{mso-style-name: 题 3 \
> > 字符;mso-style-priority:9;mso-style-link: 题 \
> > 3;font-family:宋体;font-weight:bold;}p.msg-header, li.msg-header, \
> > div.msg-header{mso-style-name:msg-header;mso-margin-top-alt:auto;margin-right:.0cm \
> > ;mso-margin-bottom-alt:auto;margin-left:.0cm;font-size:12.0pt;font-family:宋体;} \
> > span.pipe{mso-style-name:pipe;}span.EmailStyle23{mso-style-type:personal-reply;fon \
> > t-family:DengXian;color:windowtext;}.MsoChpDefault{mso-style-type:export-only;font-size:10.0pt;}@page \
> > WordSection1{size:612.0pt 792.0pt;margin:72.0pt 90.0pt 72.0pt \
> > 90.0pt;}div.WordSection1{page:WordSection1;}--></style><div \
> > class="WordSection1"><p class="MsoNormal"><span \
> > style="font-size:19.0px;font-family:DengXian;">Hi WG chairs,</span></p><p \
> > class="MsoNormal"><span \
> > style="font-size:19.0px;font-family:DengXian;"> </span></p><p \
> > class="MsoNormal"><span style="font-size:19.0px;font-family:DengXian;">Can we \
> > place the referenced documents in the TLS WG GitHub?</span></p><p \
> > class="MsoNormal"><span style="font-size:19.0px;font-family:DengXian;"><a \
> > href="https://github.com/tlswg" \
> > target="_blank">https://github.com/tlswg</a></span></p><p \
> > class="MsoNormal"><span \
> > style="font-size:19.0px;font-family:DengXian;"> </span></p><p \
> > class="MsoNormal"><span style="font-size:19.0px;font-family:DengXian;">According \
> > to the discussion below, this can help people to read and understand the \
> > referenced specifications.</span></p><p class="MsoNormal"><span \
> > style="font-size:19.0px;font-family:DengXian;"> </span></p><p \
> > class="MsoNormal"><span \
> > style="font-size:19.0px;font-family:DengXian;">Thanks,</span></p><p \
> > class="MsoNormal"><span \
> > style="font-size:19.0px;font-family:DengXian;"> </span></p><p \
> > class="MsoNormal"><span style="font-size:19.0px;font-family:DengXian;">Kind \
> > Regards</span></p><p class="MsoNormal"><span \
> > style="font-size:19.0px;font-family:DengXian;">Kepeng </span></p><p \
> > class="MsoNormal"><span \
> > style="font-size:14.0px;font-family:DengXian;"> </span></p><div \
> > style="border-right:none;border-bottom:none;border-left:none;border-image:initial;border-top:1.0px \
> > solid #b5c4df;padding:.0px .0cm .0cm;"><p class="MsoNormal"><b ><span \
> > style="color:black;">发件人</span></b><b ><span \
> > style="font-family:Calibri,sans-serif;color:black;">: </span></b><span \
> > style="font-family:Calibri,sans-serif;color:black;">TLS \
> > <tls-bounces@ietf.org> </span><span \
> > style="color:black;">代表</span><span \
> > style="font-family:Calibri,sans-serif;color:black;"> "Blumenthal, Uri - 0553 - \
> > MITLL" <uri@ll.mit.edu><br ></span><b ><span \
> > style="color:black;">日期</span></b><b ><span \
> > style="font-family:Calibri,sans-serif;color:black;">: </span></b><span \
> > style="font-family:Calibri,sans-serif;color:black;">2019</span><span \
> > style="color:black;">年</span><span \
> > style="font-family:Calibri,sans-serif;color:black;">8</span><span \
> > style="color:black;">月</span><span \
> > style="font-family:Calibri,sans-serif;color:black;">18</span><span \
> > style="color:black;">日</span><span \
> > style="font-family:Calibri,sans-serif;color:black;"> </span><span \
> > style="color:black;">星期日</span><span \
> > style="font-family:Calibri,sans-serif;color:black;"> 22:08<br ></span><b ><span \
> > style="color:black;">收件人</span></b><b ><span \
> > style="font-family:Calibri,sans-serif;color:black;">: </span></b><span \
> > style="font-family:Calibri,sans-serif;color:black;">Paul Yang \
> > <kaishen.yy=40alipay.com@dmarc.ietf.org><br ></span><b ><span \
> > style="color:black;">抄送</span></b><b ><span \
> > style="font-family:Calibri,sans-serif;color:black;">: </span></b><span \
> > style="font-family:Calibri,sans-serif;color:black;">"tls@ietf.org" \
> > <tls@ietf.org><br ></span><b ><span \
> > style="color:black;">主题</span></b><b ><span \
> > style="font-family:Calibri,sans-serif;color:black;">: </span></b><span \
> > style="font-family:Calibri,sans-serif;color:black;">Re: [TLS] (offline) Re: Draft \
> > for SM cipher suites used in TLS1.3</span></p></div><div ><p \
> > class="MsoNormal"> </p></div><p class="MsoNormal">IMHO, placing the \
> > documents on GitHub would be perfect, and quite sufficient. </p><div ><p \
> > class="MsoNormal"> </p></div><div ><p class="MsoNormal">Please make sure to \
> > post the name of the repo here. ;/)</p><div ><p \
> > class="MsoNormal"> </p></div><div ><p class="MsoNormal" \
> > style="margin-bottom:16.0px;">I leave it to others to decide whether they'd want \
> > copies of today PDF files sent to the mailing list directly.</p><div \
> > id="AppleMailSignature"><p class="MsoNormal">Regards,</p><div ><p \
> > class="MsoNormal">Uri</p></div><div ><p class="MsoNormal"> </p></div><div \
> > ><p class="MsoNormal">Sent from my iPhone</p></div></div><div ><p \
> > > class="MsoNormal" style="margin-bottom:16.0px;"><br >On Aug 17, 2019, at 01:03, \
> > > Paul Yang <<a href="mailto:kaishen.yy=40alipay.com@dmarc.ietf.org" \
> > > target="_blank">kaishen.yy=40alipay.com@dmarc.ietf.org</a>> \
> > > wrote:</p></div><div ><p class="MsoNormal">Good points.</p><div ><p \
> > > class="MsoNormal"> </p></div><div ><p class="MsoNormal">The good news is \
> > > that we have found some English PDFs of SM2, including the missing part 1 and \
> > > part 3. Will continue to find English translations of other SM standards \
> > > mentioned in the draft.</p></div><div ><p \
> > > class="MsoNormal"> </p></div><div ><p class="MsoNormal">So, if we host a \
> > > free website, say on Github or so, to provide those docs, is it convenient for \
> > > you guys? Or should we just drop the PDF files to this mailing list as \
> > > attachments?</p><div ><p class="MsoNormal"><br ><br ></p><div ><p \
> > > class="MsoNormal">On Aug 16, 2019, at 10:58 PM, Rene Struik <<a \
> > > href="mailto:rstruik.ext@gmail.com" \
> > > target="_blank">rstruik.ext@gmail.com</a>> wrote:</p></div><p \
> > > class="MsoNormal"> </p><div ><div ><div ><p class="MsoNormal">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]). \
> > > </p></div><div ><p class="MsoNormal"> </p></div><div ><p \
> > > class="MsoNormal">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.</p></div><div ><p class="MsoNormal"> </p></div><div ><p \
> > > class="MsoNormal">On 8/16/2019 3:06 AM, Kepeng Li wrote:</p></div><div ><div \
> > > ><div ><p class="MsoNormal" style="background:white;"><span \
> > > > style="font-size:14.0px;font-family:Arial,sans-serif;">Hi Rene and \
> > > > all,</span></p></div></div><div ><div ><p class="MsoNormal" \
> > > > style="background:white;"> </p></div></div><div ><div ><pre \
> > > > style="line-height:21.0px;background:white;"><span \
> > > > style="font-size:14.0px;font-family:Arial,sans-serif;color:#212529;">> \
> > > > Since the ISO documents are not available to the general </span></pre><pre \
> > > > style="line-height:21.0px;background:white;"><span \
> > > > style="font-size:14.0px;font-family:Arial,sans-serif;color:#212529;">> \
> > > > public without payment, it would be helpful to have a freely available \
> > > > </span></pre><pre style="line-height:21.0px;background:white;"><span \
> > > > style="font-size:14.0px;font-family:Arial,sans-serif;color:#212529;">> \
> > > > document (in English) from an authoritative source. Having such a \
> > > > </span></pre><pre style="line-height:21.0px;background:white;"><span \
> > > > style="font-size:14.0px;font-family:Arial,sans-serif;color:#212529;">> \
> > > > reference available would be helpful to the IETF community (and \
> > > > </span></pre><pre style="line-height:21.0px;background:white;"><span \
> > > > style="font-size:14.0px;font-family:Arial,sans-serif;color:#212529;">> \
> > > > researchers).</span></pre></div><div ><p class="MsoNormal" \
> > > > style="background:white;"><span \
> > > > style="font-size:14.0px;font-family:Arial,sans-serif;">About the references \
> > > > to ISO documens, I think it is a general issue for IETF \
> > > > drafts.</span></p></div></div><div ><div ><p class="MsoNormal" \
> > > > style="background:white;"> </p></div></div><div ><div ><p \
> > > > class="MsoNormal" style="background:white;"><span \
> > > > style="font-size:14.0px;font-family:Arial,sans-serif;">How does the other \
> > > > IETF drafts make the references to ISO documents? ISO documents are often \
> > > > referenced by IETF drafts.</span></p></div></div><div ><div ><p \
> > > > class="MsoNormal" style="background:white;"> </p></div></div><div ><div \
> > > > ><p class="MsoNormal" style="background:white;"><span \
> > > > > style="font-size:14.0px;font-family:Arial,sans-serif;">Thanks,</span></p></div></div><div \
> > > > > ><div ><p class="MsoNormal" \
> > > > > > style="background:white;"> </p></div></div><div ><div ><p \
> > > > > > class="MsoNormal" style="background:white;"><span \
> > > > > > style="font-size:14.0px;font-family:Arial,sans-serif;">Kind \
> > > > > > Regards</span></p></div><div ><p class="MsoNormal" \
> > > > > > style="background:white;"><span \
> > > > > > style="font-size:14.0px;font-family:Arial,sans-serif;">Kepeng</span></p></div><div \
> > > > > > ><p class="MsoNormal" style="background:white;"><span \
> > > > > > > style="font-size:14.0px;font-family:Tahoma,sans-serif;">————— \
> > > > > > > ——————————————————————— \
> > > > > > > ————————————————————————————————————</span></p></div><div \
> > > > > > > ><h3 style="background:white;"><span style="font-family:lucida \
_______________________________________________
TLS mailing list
TLS@ietf.org
https://www.ietf.org/mailman/listinfo/tls
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic