Re: [Tls-reg-review] [IANA #1140715] Fwd: Application for the TLS code points (draft-wang-tls-raw-public-key-with-ibc)

Yoav Nir <ynir.ietf@gmail.com> Tue, 16 April 2019 21:50 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 DD2201203A5 for <tls-reg-review@ietfa.amsl.com>; Tue, 16 Apr 2019 14:50:54 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 N2OlC2gkLAWs for <tls-reg-review@ietfa.amsl.com>; Tue, 16 Apr 2019 14:50:51 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 121141203C8 for <tls-reg-review@ietf.org>; Tue, 16 Apr 2019 14:50:48 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id j9so29108035wrn.6 for <tls-reg-review@ietf.org>; Tue, 16 Apr 2019 14:50:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=pruU3zhR6uiRp3Rc/QTN4H0w8uz9OahI8Uv6I7hAM/I=; b=lx0TTavTc80Q9YXkKdNhZ8+covIAo7Xx0giFtczilgR0sbUvNlJiL1G/pToNFliLNk K/zZqFvPe3EWZ05am5ItcCUUMCeUu8ETVLCq8ISKtPspYoOv8Q79h9tau62b9yWry4lx r9mJF6X+Mn/zSIZ1NvYsHp8wSr42VBPUQU5yhDciwi7HdZViE0oHi/iajOTApzopE5IZ dGlwMKvNCn/H5V+avBRVluqUUov/v2NR5sR5jQg7v0+3qLq1rjlN3X9nDNdkt762Jx6Y U4cjNbq+LcwDyL91BWk07OupuxCbvuRLXoTK1HvyeJdQxubU12dCoWa4xU+sSB+7n1qg rBFg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=pruU3zhR6uiRp3Rc/QTN4H0w8uz9OahI8Uv6I7hAM/I=; b=QpY8hOP4uQ/FP1WwYAlHJOoxhuXjpBOzI61GGw66GbbJY4L8lb1YYbw+6MejJQc1WJ x3Mi+AdA29F/7q8tetNagzMH6BUJX111lXyndv1Xdj9jkzh3C+Cv9atisohPHEafQLru b0Kenq90I3igQ0siseaV3G+TzpXnS+tFnfyw1aQol9xpEkCyxzmq/7Gtj7d1vT4Lhnhl MHiySH/gSudOYHZF3+fuUwzhqyO56Q0CcD0NeEZdusNqkGaMCSKGZKTTSG3mgtpmwtky CjXeBfe3F7DLDB9AG7llMGzcseISd+sNxyd9aQ9U9BwmA2ui0pR0FNvkp/xW0cIBAWgp 8cDg==
X-Gm-Message-State: APjAAAWXhlmivyJmN9K5EPu2JamlNICSLG9zshjWCIjtSiCHJN3clqjX vTwe3ZBiWVtmGCxkXOi8rBo=
X-Google-Smtp-Source: APXvYqwaFCCyEBNB2gmS2fhcVT4TNeBZG15C/e4imDfWV/5yJ6nTN7k3YLCaplTVOKNZH3ff5ImOng==
X-Received: by 2002:adf:fa86:: with SMTP id h6mr51958496wrr.67.1555451446587; Tue, 16 Apr 2019 14:50:46 -0700 (PDT)
Received: from [192.168.1.13] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id c10sm63506843wru.83.2019.04.16.14.50.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 16 Apr 2019 14:50:45 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <DBCD233C-FF5E-46B6-B4EA-771174CEB131@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_9141CBE4-63C8-4A67-A534-BC302279537C"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Wed, 17 Apr 2019 00:50:43 +0300
In-Reply-To: <rt-4.4.3-1957-1555449700-724.1140715-37-0@icann.org>
Cc: tls-reg-review@ietf.org
To: iana-prot-param@iana.org
References: <RT-Ticket-1140715@icann.org> <0AE05CBFB1A6A0468C8581DAE58A31309E3B9ADC@SINEML521-MBX.china.huawei.com> <F2E8CA68-890E-4E80-A8B0-0FCF0CB4C5EB@gmail.com> <rt-4.4.3-1957-1555449700-724.1140715-37-0@icann.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/EiRan3NtyEIgA_6oh6I_rSnCuis>
Subject: Re: [Tls-reg-review] [IANA #1140715] Fwd: Application for the TLS code points (draft-wang-tls-raw-public-key-with-ibc)
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: Tue, 16 Apr 2019 21:50:55 -0000

Hi, Amanda.

I don’t see much difference there, so I think starting with 0x0704 should be fine.

> On 17 Apr 2019, at 0:21, Amanda Baber via RT <iana-prot-param@iana.org> wrote:
> 
> Hi Yoav,
> 
> Which values should we assign for these four registrations? There are several separate ranges of available values:
> 
> https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-signaturescheme <https://www.iana.org/assignments/tls-parameters/tls-parameters.xhtml#tls-signaturescheme>
> 
> Best regards,
> 
> Amanda Baber
> Lead IANA Services Specialist
> 
> On Tue Apr 16 19:36:57 2019, ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com> wrote:
>> Hi,
>> 
>> Rich, Nick and I have discussed this, and we approve this request.
>> 
>> https://tools.ietf.org/html/draft-wang-tls-raw-public-key-with-ibc-10 <https://tools.ietf.org/html/draft-wang-tls-raw-public-key-with-ibc-10>
>> <https://tools.ietf.org/html/draft-wang-tls-raw-public-key-with-ibc- <https://tools.ietf.org/html/draft-wang-tls-raw-public-key-with-ibc->
>> 10>
>> 
>> Please let us know if there are any problems with it.
>> 
>> Thanks
>> 
>> Yoav
>> (on behalf of the TLS registry review team)
>> 
>>> Begin forwarded message:
>>> 
>>> From: Wang Haiguang <wang.haiguang.shieldlab@huawei.com>
>>> Subject: RE: [Tls-reg-review] Application for the TLS code points
>>> Date: 16 April 2019 at 12:44:43 GMT+3
>>> To: Nick Sullivan <nick@cloudflare.com>, Yoav Nir
>>> <ynir.ietf@gmail.com>
>>> Cc: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, Sean Turner
>>> <sean@sn3rd.com>
>>> 
>>> Dear Yoav and Sullivan
>>> 
>>> I have uploaded the version of TLS-IBC draft version 10 to the IETF
>>> data tracker for code points application. The version is the same as
>>> the one attached in the previous email.
>>> 
>>> Following is link to the uploaded draft:
>>> https://www.ietf.org/id/draft-wang-tls-raw-public-key-with-ibc-10.pdf
>>> <https://www.ietf.org/id/draft-wang-tls-raw-public-key-with-ibc- <https://www.ietf.org/id/draft-wang-tls-raw-public-key-with-ibc->
>>> 10.pdf>
>>> 
>>> May I know what other procedure I should do for the application the
>>> code points as required in the draft?
>>> 
>>> Thanks very for the help.
>>> 
>>> Regards.
>>> 
>>> Haiguang
>>> 
>>> From: Nick Sullivan [mailto:nick@cloudflare.com]
>>> Sent: Tuesday, April 16, 2019 8:24 AM
>>> To: Yoav Nir <ynir.ietf@gmail.com>
>>> Cc: Wang Haiguang <wang.haiguang.shieldlab@huawei.com>; tls-reg-
>>> review@ietf.org; Sean Turner <sean@sn3rd.com>
>>> Subject: Re: [Tls-reg-review] Application for the TLS code points
>>> 
>>> Looks good to me too.
>>> 
>>> On Mon, Apr 15, 2019 at 2:08 PM Yoav Nir <ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>
>>> <mailto:ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>>> wrote:
>>> Looks good to me.
>>> 
>>> Yoav
>>> 
>>> 
>>> On 15 Apr 2019, at 4:26, Wang Haiguang
>>> <wang.haiguang.shieldlab@huawei.com <mailto:wang.haiguang.shieldlab@huawei.com>
>>> <mailto:wang.haiguang.shieldlab@huawei.com <mailto:wang.haiguang.shieldlab@huawei.com>>> wrote:
>>> 
>>> Dear Yoav
>>> 
>>> Thanks very much for your kindness.
>>> 
>>> I have updated the draft by copying the text you provided in the last
>>> email  into the IANA section.
>>> Please help to check whether the content in the IANA section is
>>> appropriate or not.
>>> 
>>> If it is okay, I will upload this version as a version 10 to the IETF
>>> data tracker.
>>> 
>>> Best regards.
>>> 
>>> Haiguang
>>> 
>>> From: Yoav Nir [mailto:ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>
>>> <mailto:ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>>]
>>> Sent: Friday, April 12, 2019 5:58 PM
>>> To: Wang Haiguang <wang.haiguang.shieldlab@huawei.com <mailto:wang.haiguang.shieldlab@huawei.com>
>>> <mailto:wang.haiguang.shieldlab@huawei.com <mailto:wang.haiguang.shieldlab@huawei.com>>>
>>> Cc: tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org> <mailto:tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>>; Sean
>>> Turner <sean@sn3rd.com <mailto:sean@sn3rd.com> <mailto:sean@sn3rd.com <mailto:sean@sn3rd.com>>>
>>> Subject: Re: [Tls-reg-review] Application for the TLS code points
>>> 
>>> Hi, Haiguang.
>>> 
>>> This is still not right. The word “reserved” in IANA registries means
>>> code points that are not to be assigned. For example, in this
>>> registry a lot of ranges are reserved for backward compatibility..
>>> 
>>> https://www.iana.org/assignments/tls-parameters/tls- <https://www.iana.org/assignments/tls-parameters/tls->
>>> parameters.xml#tls-signaturescheme
>>> <https://www.iana.org/assignments/tls-parameters/tls- <https://www.iana.org/assignments/tls-parameters/tls->
>>> parameters.xml#tls-parameters-16>
>>> 
>>> The way such IANA Considerations sections are usually phrased are
>>> something like the following:
>>> 
>>> IANA is requested to assign 4 code points from the TLS
>>> SignatureScheme registry with the following descriptions:
>>> eccsi_sha256
>>> iso_ibs1
>>> iso_ibs2
>>> iso_chinese_ibs
>>> 
>>> For all of these entries the Recommended field should be N, and the
>>> Reference field should be this document.
>>> 
>>> Feel free to copy the above text.
>>> 
>>> Yoav
>>> 
>>> 
>>> On 12 Apr 2019, at 11:05, Wang Haiguang
>>> <wang.haiguang.shieldlab@huawei.com <mailto:wang.haiguang.shieldlab@huawei.com>
>>> <mailto:wang.haiguang.shieldlab@huawei.com <mailto:wang.haiguang.shieldlab@huawei.com>>> wrote:
>>> 
>>> Dear Yoav,
>>> 
>>> I have updated the TLS-IBC draft, which is version -09, and has been
>>> uploaded to the data tracker.
>>> Following is the link to the updated draft:
>>> https://www.ietf.org/id/draft-wang-tls-raw-public-key-with-ibc-09.txt <https://www.ietf.org/id/draft-wang-tls-raw-public-key-with-ibc-09.txt>
>>> <https://www.ietf.org/id/draft-wang-tls-raw-public-key-with-ibc- <https://www.ietf.org/id/draft-wang-tls-raw-public-key-with-ibc->
>>> 09.txt>.
>>> 
>>> In the IANA section, I have removed the request for ECCSI OID as it
>>> has already been assigned.
>>> For the code point, I added following content:
>>> 
>>> The following TLS code points are required to be assigned:
>>> 
>>> - Signature Scheme Registry: signature algorithm for
>>> eccsi_with_sha256, iso_ibs1, iso_ibs2, iso_chinese_ibs are required
>>> to be reserved.
>>> 
>>> Please let me know your comments.
>>> 
>>> Best regards.
>>> 
>>> Haiguang
>>> 
>>> 
>>> From: Wang Haiguang
>>> Sent: Thursday, March 28, 2019 4:34 PM
>>> To: Yoav Nir <ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com> <mailto:ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>>>
>>> Cc: tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org> <mailto:tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>>; Sean
>>> Turner <sean@sn3rd.com <mailto:sean@sn3rd.com> <mailto:sean@sn3rd.com <mailto:sean@sn3rd.com>>>
>>> Subject: RE: [Tls-reg-review] Application for the TLS code points
>>> 
>>> Dear Yoav,
>>> 
>>> Thanks very much for the comments.
>>> 
>>> We will update the draft according to your suggestion and will upload
>>> the IETF data tracker soon.
>>> 
>>> Previously we have submit a version 9, but it seems that version is
>>> not the data tracker, so I am going to change the version number to 9
>>> for next submission instead of a 10.
>>> 
>>> Best regards.
>>> 
>>> Haiguang
>>> From: Yoav Nir [ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com> <mailto:ynir.ietf@gmail.com <mailto:ynir.ietf@gmail.com>>]
>>> Sent: Thursday, 28 March, 2019 1:03:32 PM
>>> To: Wang Haiguang
>>> Cc: tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org> <mailto:tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>>; Sean
>>> Turner
>>> Subject: Re: [Tls-reg-review] Application for the TLS code points
>>> 
>>> Hi, Haiguang
>>> 
>>> We’ve discussed it, and you can get your code points.  However, there
>>> are a few things you need to do first:
>>> The current draft in the datatracker is version -08, not -10. That
>>> version requests just one code point assignment, not 4.  Please
>>> submit the updated draft.
>>> Even in the PDF version of the draft, the four code points appear in
>>> section 4, but they do not appear in section 8 (IANA Considerations).
>>> The IANA considerations section is confusing.  It states that IANA is
>>> asked to assign an OID, and in the next bullet point says that this
>>> OID has already been assigned.  It’s not clear to me, and it won’t be
>>> clear to IANA what you want them to do.
>>> 
>>> So please get back to us after you submit a revised draft with a
>>> fixed section 8, and we will instruct IANA to make the assignment.
>>> 
>>> Hope this helps.
>>> 
>>> Yoav
>>> (on behalf of the TLS review team)
>>> 
>>> 
>>> 
>>> On 26 Mar 2019, at 9:58, Wang Haiguang
>>> <wang.haiguang.shieldlab@huawei.com <mailto:wang.haiguang.shieldlab@huawei.com>
>>> <mailto:wang.haiguang.shieldlab@huawei.com <mailto:wang.haiguang.shieldlab@huawei.com>>> wrote:
>>> 
>>> Dear Rich, Yoav and Nick
>>> 
>>> This is Haiguang Wang from Huawei.
>>> 
>>> Currently we are working on a personal draft named as draft-wang-tls-
>>> raw-public-key-with-ibc-10.
>>> We have made a presentation in IETF 104 yesterday. Attached is the
>>> our presentation slides and the draft that will be upload to the IETF
>>> meeting.
>>> 
>>> We need 4 code points for four IBS signature algorithms, so please
>>> review and let us know whether we can get the four code points for
>>> implementation and testing of the protocol.
>>> 
>>> enum {
>>> ...
>>> /* IBS ECCSI signature algorithm */
>>> eccsi_sha256 (TBD),
>>> iso_ibs1 (TBD),
>>> iso_ibs2 (TBD),
>>> iso_chinese_ibs (TBD),
>>> /* Reserved Code Points */
>>> private_use (0xFE00..0xFFFF),
>>> (0xFFFF)
>>> } SignatureScheme;
>>> 
>>> 
>>> Best regards.
>>> 
>>> Haiguang
>>> <draft-wang-tls-raw-public-key-with-ibc-10.pdf><slides-104-TLS-raw-
>>> public-key-IBC-10.pdf>_______________________________________________
>>> tls-reg-review mailing list
>>> tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org> <mailto:tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>>
>>> https://www.ietf.org/mailman/listinfo/tls-reg-review <https://www.ietf.org/mailman/listinfo/tls-reg-review>
>>> <https://www.ietf.org/mailman/listinfo/tls-reg-review <https://www.ietf.org/mailman/listinfo/tls-reg-review>>
>>> 
>>> <draft-wang-tls-raw-public-key-with-ibc-10.pdf>
>>> 
>>> _______________________________________________
>>> tls-reg-review mailing list
>>> tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org> <mailto:tls-reg-review@ietf.org <mailto:tls-reg-review@ietf.org>>
>>> https://www.ietf.org/mailman/listinfo/tls-reg-review <https://www.ietf.org/mailman/listinfo/tls-reg-review>
>>> <https://www.ietf.org/mailman/listinfo/tls-reg-review <https://www.ietf.org/mailman/listinfo/tls-reg-review>>