Re: [jose] Ted Lemon's No Objection on draft-ietf-jose-json-web-key-33: (with COMMENT)

Ted, this resolution has been incorporated into the -40 documents.  Thanks again for your useful review!

				-- Mike

-----Original Message-----
From: jose [mailto:jose-bounces@ietf.org] On Behalf Of Mike Jones
Sent: Saturday, January 10, 2015 2:04 PM
To: Ted Lemon
Cc: Kathleen Moriarty; jose-chairs@tools.ietf.org; draft-ietf-jose-json-web-key@tools.ietf.org; iesg@ietf.org; jose@ietf.org
Subject: Re: [jose] Ted Lemon's No Objection on draft-ietf-jose-json-web-key-33: (with COMMENT)

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:Ted.Lemon@nominum.com] 
Sent: Saturday, January 10, 2015 5:09 AM
To: Mike Jones
Cc: iesg@ietf.org; jose-chairs@tools.ietf.org; Kathleen Moriarty; draft-ietf-jose-json-web-key@tools.ietf.org; jose@ietf.org
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 <Michael.Jones@microsoft.com> 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
jose@ietf.org
https://www.ietf.org/mailman/listinfo/jose