On Fri, 19 Dec 2014, Nico Williams wrote:
One thing I just noticed is that you allow Unicode. You might want to
reference RFC3987 (IRIs), for, e.g., advice as to normalization.
hi Nico, that's a good point. I've added a note there (plus
an entry to the References section):
--- draft-pechanec-pkcs11uri-17-v5.txt 2014-12-29 21:46:05.000000000 -0800
+++ draft-pechanec-pkcs11uri-17-v6.txt 2014-12-29 22:32:16.000000000 -0800
@@ -193,10 +193,13 @@
characters in the unreserved set or to permitted characters from the
reserved set should be percent-encoded. This specification suggests
one allowable exception to that rule for the "id" attribute, as
- stated later in this section. Grammar rules "unreserved" and "pct-
- encoded" in the PKCS#11 URI specification below are imported from
- [RFC3986]. As a special case, note that according to Appendix A of
- [RFC3986], a space must be percent-encoded.
+ stated later in this section. Note that if a URI does carry
+ characters outside of the ASCII character set a conversion to an
+ Internationalized Resource Identifier (IRI) defined in [RFC3987] may
+ be considered. Grammar rules "unreserved" and "pct-encoded" in the
+ PKCS#11 URI specification below are imported from [RFC3986]. As a
+ special case, note that according to Appendix A of [RFC3986], a space
+ must be percent-encoded.
The PKCS#11 specification imposes various limitations on the value of
attributes, be it a more restrictive character set for the "serial"
latest working version of draft 17 (v6) is attached.
thank you, Jan.
--
Jan Pechanec <jan(_dot_)pechanec(_at_)oracle(_dot_)com>
draft-pechanec-pkcs11uri-17-v6.txt
Description: Text document