Hi Ted,
Rather than adding a clarification/disclaimer clause, how about this wording,
which keeps things simple and inline?
UTF8(STRING) denotes the octets of the UTF-8 [RFC3629] representation of
STRING, where STRING is a sequence of zero or more Unicode characters.
ASCII(STRING) denotes the octets of the ASCII [RFC20] representation of
STRING, where STRING is a sequence of zero or more ASCII characters.
In particular, I'd rather avoid the description "unspecified" in the specs,
which could raise more questions than it answers for implementers. Also, I
believe that the new clauses accomplish the constraining of the character sets
that your wording included.
Does that work for you?
Thanks again,
-- Mike
-----Original Message-----
From: Ted Lemon [mailto:[email protected]]
Sent: Saturday, January 10, 2015 5:09 AM
To: Mike Jones
Cc: [email protected]; [email protected]; Kathleen Moriarty;
[email protected]; [email protected]
Subject: Re: Ted Lemon's No Objection on draft-ietf-jose-json-web-key-33: (with
COMMENT)
On Jan 9, 2015, at 11:52 PM, Mike Jones <[email protected]> wrote:
> If you think that the current notation is unclear, we should sort out how to
> clarify it. The best I've come up with is to add the phrase ", where STRING
> is a sequence of zero or more Unicode characters" to these definitions. (The
> language "sequence of zero or more Unicode characters" comes from the
> introduction to RFC 7159.) Do you think that would address your questions,
> or do you have an alternate suggestion?
You could add a note that says something like this:
The specific encoding, ASCII(string) or UTF8(string) specifies how string is
encoded as a sequence of octets. The original encoding of string is
unspecified, although the specific encoding does also constrain the set of
characters that can appear in string.
> Sorry again for you not receiving a reply to this until now!
I thought you had, but it's no problem either way. Thanks for checking back
on it!
_______________________________________________
jose mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/jose
