Re: [Tls-reg-review] Application for the TLS code points

Yoav Nir <ynir.ietf@gmail.com> Fri, 12 April 2019 09:58 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 CD8CB12019E for <tls-reg-review@ietfa.amsl.com>; Fri, 12 Apr 2019 02:58:32 -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 beSLkAoxHth9 for <tls-reg-review@ietfa.amsl.com>; Fri, 12 Apr 2019 02:58:30 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 DCBD3120273 for <tls-reg-review@ietf.org>; Fri, 12 Apr 2019 02:58:29 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id o25so10438436wmf.5 for <tls-reg-review@ietf.org>; Fri, 12 Apr 2019 02:58:29 -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=YEHvlt9fKQew9S3/oduHt+casoYYD0nKIUlAU4ziP3I=; b=tB32dOW0rnZne8ALilP9Vk5uamgZ+sjnSmbyzGt05vozbi3GOXw+vui5Bk2Kite0Tg Hllvddnm7htRf4/p/nQbtprCFoW5ZcUw/2dG2Pr8npZcqYaLqUo0+kwXDzMY8W/vaY8/ jZ29LXF4pr5mTzDokwDrLdXqpAt1Ef05VRvycn9m+fGE361WCu9N+cJ4HI2HmqRQZHHk 5f/EA4OOtoleSdzz92a7iPLAkkob5GUs5VnVTIlw+FbKqqN1QKykX3JGR7O09GNcvVkS +lY/f3+nBZyUTmppqH71jGKiMVUtJZGKHcWX4OVc3/TMbemJrN1D5kwdMrD++w9ffJIg kVeg==
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=YEHvlt9fKQew9S3/oduHt+casoYYD0nKIUlAU4ziP3I=; b=JsWre45ptfE4xmFtpC+nK48JQ+lQdozgCKxru2kfM/i0x3tm1wZeFoHt96EMtQd+pE QDI4qYes4tebQWdfOrnHyYabz4/jwFQiTDGi2qANHSoV+J63W6Tn4vpMjihbBhK723IO mOeHiEQRptX4m3hWx6kP41Ixn0mHfh5HkTz9PX/GIPp8fiU9he4q1a/GUT+oF1rsxWyT 7yW10UaA1TLqe4Df1ufkiIINdqVsxhY0ghjUesYiWFvL1JDrHoKGKRiZ73NSGr8rNv82 keYY+ctRqMaLXN69QXPwm/seOcrKwJ4ui4H9m8IZevg7IoiDLdtEr3hPAxkvac3aCIop xh9w==
X-Gm-Message-State: APjAAAVl1SyVJWs7arKLaFRbj2d0o7GKRhKHPcI+3SwlV17Bps9fWDZE c9VBZAuBG9s5KZC0+gVu83w/bDwhQSg=
X-Google-Smtp-Source: APXvYqxYRM6nmDg2St9dFdHJ4ycursbfy3a+r0Vo0Kl+r0ouAUWFbbn+2c/PfAuRFzFaN4hDwF6Jyw==
X-Received: by 2002:a1c:5f06:: with SMTP id t6mr10726321wmb.7.1555063108382; Fri, 12 Apr 2019 02:58:28 -0700 (PDT)
Received: from [192.168.1.13] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id x5sm6179110wmi.37.2019.04.12.02.58.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 12 Apr 2019 02:58:27 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <027C8CFE-3314-4B63-8C34-6355E995D845@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_0BC16023-5193-47C8-9BA5-0984A9A490F8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Date: Fri, 12 Apr 2019 12:58:20 +0300
In-Reply-To: <0AE05CBFB1A6A0468C8581DAE58A31309E3A8CFB@SINEML521-MBX.china.huawei.com>
Cc: "tls-reg-review@ietf.org" <tls-reg-review@ietf.org>, Sean Turner <sean@sn3rd.com>
To: Wang Haiguang <wang.haiguang.shieldlab@huawei.com>
References: <0AE05CBFB1A6A0468C8581DAE58A31309E345DA7@SINEML521-MBS.china.huawei.com> <11052966-A4BF-4BD2-A51B-29CF89BBE965@gmail.com> <0AE05CBFB1A6A0468C8581DAE58A31309E35C40C@SINEML521-MBX.china.huawei.com> <0AE05CBFB1A6A0468C8581DAE58A31309E3A8CFB@SINEML521-MBX.china.huawei.com>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tls-reg-review/j0rgiPZe8ga_ible2o0VqyLs3aM>
Subject: Re: [Tls-reg-review] Application for the TLS code points
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, 12 Apr 2019 09:58:33 -0000

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-parameters.xml#tls-signaturescheme <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> 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>.
>  
> 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>
> Cc: tls-reg-review@ietf.org; Sean Turner <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]
> Sent: Thursday, 28 March, 2019 1:03:32 PM
> To: Wang Haiguang
> Cc: 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>> 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>
> https://www.ietf.org/mailman/listinfo/tls-reg-review <https://www.ietf.org/mailman/listinfo/tls-reg-review>