IETF Logo Mail Archive

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

Ted Lemon <Ted.Lemon@nominum.com> Sat, 10 January 2015 13:09 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 521091A876B; Sat, 10 Jan 2015 05:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lg7ledA-HDSq; Sat, 10 Jan 2015 05:09:23 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30D771A876A; Sat, 10 Jan 2015 05:09:23 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id BD273DA0270; Sat, 10 Jan 2015 13:09:22 +0000 (UTC)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 3341853E08E; Sat, 10 Jan 2015 05:09:22 -0800 (PST)
Received: from [10.0.20.107] (71.233.43.215) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.195.1; Sat, 10 Jan 2015 05:09:21 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739439BC633F2@TK5EX14MBXC287.redmond.corp.microsoft.com>
Date: Sat, 10 Jan 2015 08:09:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <B0DAC27C-B311-4E4E-A27F-FCF8427974F7@nominum.com>
References: <4E1F6AAD24975D4BA5B16804296739439BC633F2@TK5EX14MBXC287.redmond.corp.microsoft.com>
To: Mike Jones <Michael.Jones@microsoft.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/pkkgRnr86aNP7ELQ9PXfiiOOl7M>
Cc: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, "draft-ietf-jose-json-web-key@tools.ietf.org" <draft-ietf-jose-json-web-key@tools.ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Ted Lemon's No Objection on draft-ietf-jose-json-web-key-33: (with COMMENT)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jose/>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 10 Jan 2015 13:09:25 -0000

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!

v2.23.0 | Report a Bug | By Email