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

[Nick Sullivan <[e-mail]>]

Looks good to me too.

On Mon, Apr 15, 2019 at 2:08 PM Yoav Nir <[e-mail]> wrote:

> Looks good to me.
>
> Yoav
>
> On 15 Apr 2019, at 4:26, Wang Haiguang <[e-mail]>
> 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:[e-mail] <[e-mail]>]
> *Sent:* Friday, April 12, 2019 5:58 PM
> *To:* Wang Haiguang <[e-mail]>
> *Cc:* [e-mail]; Sean Turner <[e-mail]>
> *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-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 <
> [e-mail]> 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.
>
> 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 <[e-mail]>
> *Cc:* [e-mail]; Sean Turner <[e-mail]>
> *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 [[e-mail]]
> *Sent:* Thursday, 28 March, 2019 1:03:32 PM
> *To:* Wang Haiguang
> *Cc:* [e-mail]; 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:
>
>    1. 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.
>    2. 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).
>    3. 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 <[e-mail]>
> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tls-reg-review
>
>
> <draft-wang-tls-raw-public-key-with-ibc-10.pdf>
>
>
> _______________________________________________
> tls-reg-review mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/tls-reg-review
>