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

Paul Yang <kaishen.yy@alipay.com> Fri, 16 August 2019 05:14 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 F3BA412001B for <tls-reg-review@ietfa.amsl.com>; Thu, 15 Aug 2019 22:14:13 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 IOML21YNfEYu for <tls-reg-review@ietfa.amsl.com>; Thu, 15 Aug 2019 22:14:11 -0700 (PDT)
Received: from out0-154.mail.aliyun.com (out0-154.mail.aliyun.com [140.205.0.154]) (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 9DB54120013 for <tls-reg-review@ietf.org>; Thu, 15 Aug 2019 22:14:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alipay.com; s=default; t=1565932444; h=From:Content-Type:Mime-Version:Subject:Message-Id:Date:To; bh=Zm8P7f1voUqtgndw/w7OUCMGU8CaS1hcV99jax+A1Iw=; b=TIcN4kRxCtGH7sUx/1Nr3dWdsLtZGC20cBcgreN2NR+QAygznayzKdkvYhMXXlIMWExSDEUbKbDj/3abFZyvq8rdAfe+BKrr3c5/oejjIgjlfHFmcUnxH5l514g8BeZGVXwhzqfWxoJxiJFzEJ2HK3kTR4xZxmn0vvFhRTIXcEs=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R151e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03302; MF=kaishen.yy@alipay.com; NM=1; PH=DS; RN=1; SR=0; TI=SMTPD_---.FD0Hju7_1565932440;
Received: from 10.15.232.47(mailfrom:kaishen.yy@alipay.com fp:SMTPD_---.FD0Hju7_1565932440) by smtp.aliyun-inc.com(127.0.0.1); Fri, 16 Aug 2019 13:14:00 +0800
From: Paul Yang <kaishen.yy@alipay.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_82C7B934-FB11-4010-921C-50F0E60219C1"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Message-Id: <EF11BCB9-024B-49BC-8279-AF575C250E54@alipay.com>
Date: Fri, 16 Aug 2019 13:13:59 +0800
To: tls-reg-review@ietf.org
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/N8DZlkatg8H64hisVQpWeobFSNM>
X-Mailman-Approved-At: Mon, 19 Aug 2019 06:24:52 -0700
Subject: [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: Fri, 16 Aug 2019 05:14:14 -0000

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