Re: [Tls-reg-review] [IANA #1140715] Fwd: Application for the TLS code points (draft-wang-tls-raw-public-key-with-ibc)
Wang Haiguang <wang.haiguang.shieldlab@huawei.com> Tue, 23 April 2019 07:13 UTC
Return-Path: <wang.haiguang.shieldlab@huawei.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 D5BF8120227 for <tls-reg-review@ietfa.amsl.com>; Tue, 23 Apr 2019 00:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 q6Mi54sx1CFL for <tls-reg-review@ietfa.amsl.com>; Tue, 23 Apr 2019 00:13:18 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 29498120091 for <tls-reg-review@ietf.org>; Tue, 23 Apr 2019 00:13:18 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 22D47F070163CAB33946 for <tls-reg-review@ietf.org>; Tue, 23 Apr 2019 08:13:16 +0100 (IST)
Received: from SINEML705-CAH.china.huawei.com (10.223.161.55) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 23 Apr 2019 08:13:15 +0100
Received: from SINEML521-MBX.china.huawei.com ([169.254.1.204]) by SINEML705-CAH.china.huawei.com ([10.223.161.55]) with mapi id 14.03.0415.000; Tue, 23 Apr 2019 15:13:10 +0800
From: Wang Haiguang <wang.haiguang.shieldlab@huawei.com>
To: "iana-prot-param@iana.org" <iana-prot-param@iana.org>, "ynir.ietf@gmail.com" <ynir.ietf@gmail.com>
CC: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, "sean@sn3rd.com" <sean@sn3rd.com>
Thread-Topic: [IANA #1140715] Fwd: [Tls-reg-review] Application for the TLS code points (draft-wang-tls-raw-public-key-with-ibc)
Thread-Index: AQHU9LEXFh3QC0NC+EqNhHQFz15NTqZJXiUQ
Date: Tue, 23 Apr 2019 07:13:09 +0000
Message-ID: <0AE05CBFB1A6A0468C8581DAE58A31309E3C9289@SINEML521-MBX.china.huawei.com>
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> <DBCD233C-FF5E-46B6-B4EA-771174CEB131@gmail.com> <rt-4.4.3-1957-1555451465-1491.1140715-37-0@icann.org> <rt-4.4.3-22099-1555459439-106.1140715-37-0@icann.org>
In-Reply-To: <rt-4.4.3-22099-1555459439-106.1140715-37-0@icann.org>
Accept-Language: en-SG, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.215.37.82]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/5vlu9MQ7rry13hry2F1zICQPnas>
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, 23 Apr 2019 07:13:22 -0000
Dear all Thanks very much to help provided in assigning the code points for signature algorithms included in the TLS-IBC draft. Have a nice day. Haiguang -----Original Message----- From: Amanda Baber via RT [mailto:iana-prot-param@iana.org] Sent: Wednesday, April 17, 2019 8:04 AM To: ynir.ietf@gmail.com Cc: tls-reg-review@ietf.org; Wang Haiguang <wang.haiguang.shieldlab@huawei.com>; sean@sn3rd.com Subject: [IANA #1140715] Fwd: [Tls-reg-review] Application for the TLS code points (draft-wang-tls-raw-public-key-with-ibc) Hi all, We've added the following entries to the TLS SignatureScheme registry: Value: 0x0704 Description: eccsi_sha256 Recommended: N Reference: [draft-wang-tls-raw-public-key-with-ibc] Value: 0x0705 Description: iso_ibs1 Recommended: N Reference: [draft-wang-tls-raw-public-key-with-ibc] Value: 0x0706 Description: iso_ibs2 Recommended: N Reference: [draft-wang-tls-raw-public-key-with-ibc] Value: 0x0707 Description: iso_chinese_ibs Recommended: N Reference: [draft-wang-tls-raw-public-key-with-ibc] Please see https://www.iana.org/assignments/tls-parameters thanks, Amanda On Tue Apr 16 21:51:05 2019, ynir.ietf@gmail.com wrote: > 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>>
- Re: [Tls-reg-review] Application for the TLS code… Wang Haiguang
- Re: [Tls-reg-review] Application for the TLS code… Yoav Nir
- [Tls-reg-review] Application for the TLS code poi… Wang Haiguang
- Re: [Tls-reg-review] Application for the TLS code… Yoav Nir
- Re: [Tls-reg-review] Application for the TLS code… Salz, Rich
- Re: [Tls-reg-review] Application for the TLS code… Nick Sullivan
- Re: [Tls-reg-review] Application for the TLS code… Wang Haiguang
- Re: [Tls-reg-review] Application for the TLS code… Yoav Nir
- Re: [Tls-reg-review] Application for the TLS code… Wang Haiguang
- Re: [Tls-reg-review] Application for the TLS code… Yoav Nir
- Re: [Tls-reg-review] Application for the TLS code… Nick Sullivan
- Re: [Tls-reg-review] Application for the TLS code… Wang Haiguang
- [Tls-reg-review] Fwd: Application for the TLS cod… Yoav Nir
- Re: [Tls-reg-review] [IANA #1140715] Fwd: Applica… Yoav Nir
- Re: [Tls-reg-review] [IANA #1140715] Fwd: Applica… Wang Haiguang