Re: [Tls-reg-review] Request to code point on new drafts

Paul Yang <kaishen.yy@alipay.com> Mon, 19 August 2019 15:56 UTC

Return-Path: <kaishen.yy@alipay.com>
X-Original-To: tls-reg-review@ietfa.amsl.com
Delivered-To: tls-reg-review@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55E43120817 for <tls-reg-review@ietfa.amsl.com>; Mon, 19 Aug 2019 08:56:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alipay.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jlAOGqKdwXPe for <tls-reg-review@ietfa.amsl.com>; Mon, 19 Aug 2019 08:56:54 -0700 (PDT)
Received: from out0-129.mail.aliyun.com (out0-129.mail.aliyun.com [140.205.0.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DB7C120818 for <tls-reg-review@ietf.org>; Mon, 19 Aug 2019 08:56:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alipay.com; s=default; t=1566230209; h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:To; bh=np2/Jx3NM8PC5A4Jrt4svIno/hhQFkYKIy8BJ7H+eS0=; b=fOXaqT4VnqwZoiEV/u4g+1Pko96buErKjefBfwyJqP95KhMqwjKUJSC0rVVuRSDcJIIOwQg3KTfwnJRhgH1zZA0CxyXCuHaSNvVsMqf6fxHhVeyX2Hu38gntRI+Vm35nLQvLxN4fvGdpSz3VAydjRyM/4D6mRt5MamPjakC3ZfI=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R171e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03303; MF=kaishen.yy@alipay.com; NM=1; PH=DS; RN=2; SR=0; TI=SMTPD_---.FEcqNYT_1566230208;
Received: from 30.39.143.227(mailfrom:kaishen.yy@alipay.com fp:SMTPD_---.FEcqNYT_1566230208) by smtp.aliyun-inc.com(127.0.0.1); Mon, 19 Aug 2019 23:56:48 +0800
From: Paul Yang <kaishen.yy@alipay.com>
Message-Id: <21DAA117-C545-485F-9FBE-879437D52F84@alipay.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_2FBE9F2F-9396-4407-A0BC-8DD2998D4EA1"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Mon, 19 Aug 2019 23:56:47 +0800
In-Reply-To: <54CFCCD3-4173-4052-B3DE-E5880BD59120@akamai.com>
Cc: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>
To: Rich Salz <rsalz@akamai.com>
References: <EF11BCB9-024B-49BC-8279-AF575C250E54@alipay.com> <54CFCCD3-4173-4052-B3DE-E5880BD59120@akamai.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/IET09N7ugr5l_wEFrjwAc-qDQK4>
Subject: Re: [Tls-reg-review] Request to code point on new drafts
X-BeenThere: tls-reg-review@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TLS REVIEW <tls-reg-review.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tls-reg-review/>
List-Post: <mailto:tls-reg-review@ietf.org>
List-Help: <mailto:tls-reg-review-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tls-reg-review>, <mailto:tls-reg-review-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Aug 2019 15:56:56 -0000

TBH, I don’t know the difference between an early assignment and a late one (And how will it affect the final publication).

But from the implementation point of view, I think the earlier the better. Since lots of companies/organizations in China are waiting for the IANA code-points then they can implement this in their services and products.

This can definitely bring TLSv1.3 online and can make their business complied to the SCA’s requirements at the same time. Would this make a bit of sense I think...

> On Aug 19, 2019, at 11:51 PM, Salz, Rich <rsalz@akamai.com> wrote:
> 
> Are you asking for an early code-point assignment, or do you want to wait / can you wait until the document is closer to publication?
> 
> On 8/19/19, 9:25 AM, "Paul Yang" <kaishen.yy=40alipay.com@dmarc.ietf.org> wrote:
> 
>    Hi there,
> 
>    A new draft has submitted by me yesterday: https://tools.ietf.org/html/draft-yang-tls-tls13-sm-suites-00
> 
>    It describes how new SM cipher suites are used in TLS1.3. There are several code points we would like to request IANA to assign. An IANA consideration section has been included in this draft. I list the detail as follow as well.
>    There are 4 TBD values in this draft:
> 
>    CipherSuite TLS_SM4_GCM_SM3 = { TBD1, TBD1 };
>    CipherSuite TLS_SM4_CCM_SM3 = { TBD2, TBD2 };
> 
>    SignatureScheme sm2sig_sm3 = { TBD3 };
> 
>    NamedGroup curveSM2 = { TBD4 };
> 
>    Note: typos found in original draft, for TBD4 should be in registry “TLS Supported Groups” instead of “TLS HashAlgorithm”. Will fix this in next version of the draft.
> 
>    Please review this request, thanks.
> 
>    Regards,
> 
>    Paul Yang
> 
> 
> 


Regards,

Paul Yang