Re: [Tls-reg-review] [IANA #1152216] Request for Assignment (tls-parameters, draft-yang-tls-tls13-sm-suites)

Yoav Nir <ynir.ietf@gmail.com> Thu, 19 September 2019 03:48 UTC

Return-Path: <ynir.ietf@gmail.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 9A45112006F for <tls-reg-review@ietfa.amsl.com>; Wed, 18 Sep 2019 20:48:37 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 sWqZneOPfAj7 for <tls-reg-review@ietfa.amsl.com>; Wed, 18 Sep 2019 20:48:35 -0700 (PDT)
Received: from mail-wm1-x344.google.com (mail-wm1-x344.google.com [IPv6:2a00:1450:4864:20::344]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 282B6120026 for <tls-reg-review@ietf.org>; Wed, 18 Sep 2019 20:48:35 -0700 (PDT)
Received: by mail-wm1-x344.google.com with SMTP id f16so2204886wmb.2 for <tls-reg-review@ietf.org>; Wed, 18 Sep 2019 20:48:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=R7q/UBpjM2jK5NpjHkwCRTGGCPRHTV7rYxHD47p3hzw=; b=kI4cHzbD0BsDSAqA2Cf4yFXPviTPfwHBXyKc5z3IsQJPFbbqv+/P7I0QxgvyfN6sD2 4rldnT4jL8d6OAGAz1/vqyH6IA1bWWd2acAZw6x1webQTlmRaUFVKstsNIRBIeEVLJ/l O70lYrIhUPTo2PBPjZ8DXkAEq94azKdUtcxMAWuO7KK0h/SeNvjLcIlxSO7GZsoOk5er 3FQhRszgAqaYn3ysoTLwnM6PnY9436jV+93Yg2L4wBak5H/lM6S1NyCBtSTBcdxFWcbF uFcv/wlwfJShsMGRCgb7nUl/+lXfVA9ie8rpgWAvcqPi3dWhm+wwUAPD88ad2e3a71sl GMTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=R7q/UBpjM2jK5NpjHkwCRTGGCPRHTV7rYxHD47p3hzw=; b=QVDgnRYXF3B/zC44zPNc24LEs4d+u3u3YaZUbZHbda4H60mz54bzc4NjoufPtumzaH jsh82GlhKhA8m7yvzcZWfdqLQOcS/Apv75LHDCXW5M/U99gOvdaBAJ1r5gFhjAzTdmfu /uPO3qPC2/WvOkQ/5k8MC7WA1yMRD0H67OUBV6tRVkT6MurhCy9r3A+yPMpe1mpqeFN4 VEqRt26G6GT5Kelty0PxsfdM3CKQjvR7ioCeKrAGKAia9PuYMIckz/2eP0GGLVwolBVY T/QcDFVJOrLRCnJOS3INC0BsZV6PztHkQE0aAvVYKCQBLxLbvemOLXoWMyn2InUYdQrL jABA==
X-Gm-Message-State: APjAAAWmXl2lTokt66qu5WFLI5Nf8LWMcCxs6lgdFPhP5LCHtID0pn2F nP+2qnw6vaTJPHuMOMQpYNo=
X-Google-Smtp-Source: APXvYqwt8XFNJpSarcxfMEH59FYbiJVBAZv8ZKrVAuPslva4ntePokWEW6ozLy5+YY7LhB8tmqxfPA==
X-Received: by 2002:a1c:9cd0:: with SMTP id f199mr800998wme.111.1568864913548; Wed, 18 Sep 2019 20:48:33 -0700 (PDT)
Received: from [192.168.1.12] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id u10sm14568679wrg.55.2019.09.18.20.48.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Sep 2019 20:48:32 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <271DDA0F-5EFF-4574-869B-09158CC6F3C5@akamai.com>
Date: Thu, 19 Sep 2019 06:48:27 +0300
Cc: "iana-prot-param-comment@iana.org" <iana-prot-param-comment@iana.org>, "nick@cloudflare.com" <nick@cloudflare.com>, "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D4D9B243-DC1D-4905-989C-F227A8DD2DF6@gmail.com>
References: <RT-Ticket-1152216@icann.org> <2v3cxr80dc-1@ppa4.dc.icann.org> <rt-4.4.3-23168-1568845104-1675.1152216-9-0@icann.org> <271DDA0F-5EFF-4574-869B-09158CC6F3C5@akamai.com>
To: Rich Salz <rsalz@akamai.com>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/5nwDMc5Oik4TqqqmS6lGOgna-zo>
Subject: Re: [Tls-reg-review] [IANA #1152216] Request for Assignment (tls-parameters, draft-yang-tls-tls13-sm-suites)
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: Thu, 19 Sep 2019 03:48:38 -0000

Looks good to me

> On 19 Sep 2019, at 4:10, Salz, Rich <rsalz@akamai.com> wrote:
> 
> I am okay with this, of course :)  I'd like Yoav (or Nick) to sanity-check.
> 
> On 9/18/19, 6:18 PM, "Amanda Baber via RT" <iana-prot-param-comment@iana.org> wrote:
> 
>    Hi Rich, all,
> 
>    As it appears that Yoav and Rich have both approved these registrations on the mailing list, should we move ahead with these registrations, with the additional information proposed by Rich? Specifically:
> 
>    =====
> 
>    Looking at https://tools.ietf.org/html/draft-yang-tls-tls13-sm-suites-00, the IANA considerations in particular, I suggest the following:
> 
>                 +-------+-----------------+---------+-----------+
>                 | Value | Description     | DTLS-OK | Reference |
>                 +-------+-----------------+---------+-----------+
>                 |  TBD1 | TLS_SM4_GCM_SM3 | No      | this RFC  |
>                 |       |                 |         |           |
>                 |  TBD2 | TLS_SM4_CCM_SM3 | No      | this RFC  |
>                 +-------+-----------------+---------+-----------+
>    Update the TLS Cipher Suites table to include
>    TBD1 is 0x00,0xC6
>    TBD2 is 0x00,0xC7
>    Note to the draft authors: This table is missing the “Recommended” column.  It should be filled in with “N”
> 
> 
>                   +-------+-------------+---------+-----------+
>                   | Value | Description | DTLS-OK | Reference |
>                   +-------+-------------+---------+-----------+
>                   |  TBD3 | sm2sig_sm3  | No      | this RFC  |
>                   +-------+-------------+---------+-----------+
>    TBD3 is 0x0708
>    Note to the draft authors: This table is missing the “Recommended” column. It should be filled in with “N”
> 
> 
>            +-------+-------------+---------+-------------+-----------+
>            | Value | Description | DTLS-OK | Recommended | Reference |
>            +-------+-------------+---------+-------------+-----------+
>            |  TBD4 | curveSM2    | No      | No          | this RFC  |
>            +-------+-------------+---------+-------------+-----------+
>    TBD4 is 224
>    Note to the draft authors: This table should NOT have the “Recommended” column.
> 
>    =====
> 
>    I saw that the requester was asked to contact us, but our understanding from RFC 8447 is that registration requests should actually be sent to us by the reviewers (upon approval) rather than the requesters. We do need to contact the list when a draft is up for IESG Approval, if the registrations in the document are still pending expert approval.
> 
>    thanks,
>    Amanda
> 
>    On Wed Sep 18 05:12:47 2019, kaishen.yy@antfin.com wrote:
>> 
>> Contact Name:
>> Paul Yang
>> 
>> Contact Email:
>> kaishen.yy@antfin.com
>> 
>> Type of Assignment:
>> I request to assign a set of TLS parameters including two TLS cipher
>> suites, one signature scheme and one supported group entry.
>> 
>> Registry:
>> Those numbers are assigned in "TLS Cipher Suites", "TLS Supported
>> Groups" and "TLS SignatureScheme" registries.
>> 
>> Description:
>> We are trying to standardize the use of Chinese SM algorithms into
>> TLSv1.3 and we also need to have an early implementation of the draft
>> for a validation purpose, so we need to get those numbers assigned by
>> IANA.
>> 
>> Additional Info:
>> The I-D has been submitted to: https://tools.ietf.org/html/draft-yang-
>> tls-tls13-sm-suites-00
> 
> 
>