Re: [jose] #84: Section 7.1 JSON Web Key Parameters Registry

"jose issue tracker" <trac+jose@trac.tools.ietf.org> Wed, 02 October 2013 02:19 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: jose issue tracker <trac+jose@trac.tools.ietf.org>
Precedence: bulk
Auto-Submitted: auto-generated
To: draft-ietf-jose-json-web-key@tools.ietf.org, ietf@augustcellars.com
Date: Wed, 02 Oct 2013 02:19:07 -0000
Message-ID: <076.ed067bc44c481a0d914982a76840332b@trac.tools.ietf.org>
References: <061.2c8e43041b4a771491d9dbf782ad3a03@trac.tools.ietf.org>
In-Reply-To: <061.2c8e43041b4a771491d9dbf782ad3a03@trac.tools.ietf.org>
Resent-To: mbj@microsoft.com
Resent-Message-Id: <20131002021913.98F9621F9C88@ietfa.amsl.com>
Resent-Date: Tue, 01 Oct 2013 19:19:13 -0700
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #84: Section 7.1 JSON Web Key Parameters Registry

#84: Section 7.1 JSON Web Key Parameters Registry

Description changed by ietf@augustcellars.com:

Old description:

> A. This section is missing any mention of criteria by which an expert is
> to determine if the registration makes any sense.
>
> B. I have a problem with the word reserved.  To me this is not the same
> as "reserved word" used in computer languages.  To me this implies
> something that is set aside for future use.  This is not consistent with
> how the word is used in this content.  In the case of the first sentence
> it can just be deleted.  You have a registry for JWK parameter names.
>
> C. Is it permissible for a "private" field to be registered without a
> public specification attached to it?  It would appear not, but this may
> be desirable behavior in the future.

New description:

 A. This section is missing any mention of criteria by which an expert is
 to determine if the registration makes any sense.

 B. I have a problem with the word reserved.  To me this is not the same as
 "reserved word" used in computer languages.  To me this implies something
 that is set aside for future use.  This is not consistent with how the
 word is used in this content.  In the case of the first sentence it can
 just be deleted.  You have a registry for JWK parameter names.

 * FIXED

 C. Is it permissible for a "private" field to be registered without a
 public specification attached to it?  It would appear not, but this may be
 desirable behavior in the future.

--

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-jose-json-web-
  ietf@augustcellars.com |  key@tools.ietf.org
     Type:  defect       |      Status:  new
 Priority:  major        |   Milestone:
Component:  json-web-    |     Version:
  key                    |  Resolution:
 Severity:  -            |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/84#comment:1>
jose <http://tools.ietf.org/jose/>

[jose] #84: Section 7.1 JSON Web Key Parameters R… jose issue tracker
Re: [jose] #84: Section 7.1 JSON Web Key Paramete… jose issue tracker
Re: [jose] #84: Section 7.1 JSON Web Key Paramete… jose issue tracker