Re: [Uri-review] The registration request for “cstr” URI scheme

Ted Hardie <ted.ietf@gmail.com> Fri, 06 May 2022 09:38 UTC

MIME-Version: 1.0
References: <2022042617064765004922@cnic.cn> <CA+9kkMA4JZw6cBDUzJQsvgOfveKYkw8u3P1hm60_pDkfQP1MtQ@mail.gmail.com> <202205061436003998902@cnic.cn> <CA+9kkMAq2pLWAc0-W+msaJ69HG=0+PuSVz-_k-yy0pk02tBohQ@mail.gmail.com> <562e51d2-43ef-2b1a-c9a1-e57a4d30cb65@it.aoyama.ac.jp>
In-Reply-To: <562e51d2-43ef-2b1a-c9a1-e57a4d30cb65@it.aoyama.ac.jp>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Fri, 06 May 2022 10:38:00 +0100
Message-ID: <CA+9kkMD184YaGX=PH7QyWbH5C_f-TB3R04OL8fg6tJJpezt+jw@mail.gmail.com>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Cc: uri-review <uri-review@ietf.org>, wangshu@cnic.cn, liujia <liujia@cnic.cn>
Content-Type: multipart/alternative; boundary="000000000000d3c4d405de549eb8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/uri-review/pmYWx3IIMc5-0NNoSGtjlC0pTkA>
Subject: Re: [Uri-review] The registration request for “cstr” URI scheme
Precedence: list

Hi Martin,

Thanks for your comments.  I think the simplest thing here would be for the
registration to simply confirm that they are using the characters as
specified in RFC 3986.  After all, the ":" as a delimiter MUST be the
originally specified character; you aren't allowed to percent-encode an
alternative at all.

regards,

Ted Hardie


On Fri, May 6, 2022 at 10:21 AM Martin J. Dürst <duerst@it.aoyama.ac.jp>
wrote:

> Hello Ted, others,
>
> On 2022-05-06 17:18, Ted Hardie wrote:
> > Dear Wang Shu,
> >
> > Thank you for this update.  I have now reviewed the specification at
> > https://cstr.cn/doc/specification/ .  I have a small number of follow-up
> > questions. First, the specification notes that the internal identifier
> does
> > not have a fixed length, but it does not note how it is composed.  Is it
> > composed of digits as are the agency code and type code, or of alphabetic
> > characters, or a mix of the two?
> >
> > Second, the specification notes that the separators are "half-width
> > characters".  RFC 3986 sets out the syntax of URIs with reference to the
> > ASCII character set (See section 2.2 for the reserved characters, which
> > include ":", and section 2.3 for the unreserved characters, which include
> > ".").  Can you clarify that you are using these characters, rather than
> > those drawn from Unicode Halfwidth and Fullwidth range ( U+FF1A and
> U+FF0E
> > from https://www.unicode.org/charts/PDF/UFF00.pdf)?
>
> I can only guess, but the half-width character in that range are for
> Japanese and Korean, and I don't think there's a high probability that
> the Chinese Academy of Sciences would use them.
>
> I think it would be better to change "half-width characters" to
> something like "code points in the range of ..." or so, to be more
> explicit.
>
> Regards,   Martin.
>
> > For the security considerations, section 3.7 of RFC 7595 gives
> guidelines (
> > https://datatracker.ietf.org/doc/html/rfc7595#section-3.7).  In a case
> like
> > yours might make reference to Section 7 of RFC 3986 and then go on to say
> > whether you know of any other issues.  If the internal identifier
> encodes a
> > specific individual, for example, you might note that.  If there are no
> > other considerations, something like this:
> >
> > The general security considerations from Section 7 of RFC 3986
> > apply, but no other security considerations have been identified at the
> > time of registration.
> >
> > Thanks again for the opportunity to review the update,
> >
> > regards,
> >
> > Ted Hardie
> >
> > On Fri, May 6, 2022 at 7:36 AM wangshu@cnic.cn <wangshu@cnic.cn> wrote:
> >
> >> Dear Ted Hardie,
> >>
> >> Thank you for your reply, we have already updated the security
> >> considerations and references including the cstr specification.The
> "cstr"
> >> scheme is specified as follows:
> >>
> >>
> >>
> >> Scheme name: cstr
> >>
> >>
> >>
> >> Status: Provisional
> >>
> >>
> >>
> >> Applications/protocols that use this scheme name:
> >>
> >> A "cstr" URI is used to express an identifier that is for common science
> >> and technology resources.
> >>
> >> Applications that use this scheme name provide services for the
> >> persistent identification, inluding citation, statistics and
> traceability
> >> of science and technology resources.
> >>
> >>
> >>
> >> Security considerations:
> >>
> >>     Unknown, use with care.
> >>
> >>
> >>
> >>
> >>
> >> Contact: Wang Shu (wangshu@cnic.cn)
> >>
> >>
> >>
> >> Change controllers:
> >>
> >>    - Wang Shu (wangshu@cnic.cn)
> >>
> >>    - Computer Network Information Center,Chinese Academy of Sciences
> >>
> >>
> >>
> >> References:
> >>
> >> [1] *https://www.cstr.cn/en/* <https://www.cstr.cn/en/>
> >>
> >> [2] *https://cstr.cn/doc/specification/*
> >> <https://cstr.cn/doc/specification/>
> >>
> >>
> >>
> >> Please let me know if you have any questions about cstr.
> >>
> >> Looking forward to your reply.
> >>
> >> Best wishes.
> >>
> >> Shu
> >>
> >> ------------------------------
> >> wangshu@cnic.cn
> >>
>

[Uri-review] The registration request for “cstr” … wangshu@cnic.cn
Re: [Uri-review] The registration request for “cs… Ted Hardie
Re: [Uri-review] The registration request for “cs… wangshu@cnic.cn
Re: [Uri-review] The registration request for “cs… Ted Hardie
Re: [Uri-review] The registration request for “cs… Martin J. Dürst
Re: [Uri-review] The registration request for “cs… Ted Hardie
Re: [Uri-review] The registration request for “cs… wangshu@cnic.cn
Re: [Uri-review] The registration request for “cs… wangshu@cnic.cn
Re: [Uri-review] The registration request for “cs… Ted Hardie
Re: [Uri-review] The registration request for “cs… wangshu@cnic.cn
Re: [Uri-review] The registration request for “cs… Ted Hardie
Re: [Uri-review] The registration request for “cs… wangshu@cnic.cn
Re: [Uri-review] The registration request for “cs… Graham Klyne
Re: [Uri-review] The registration request for “cs… wangshu@cnic.cn