[jose] #84: Section 7.1 JSON Web Key Parameters Registry
"jose issue tracker" <trac+jose@trac.tools.ietf.org> Sun, 18 August 2013 19:59 UTC
Return-Path: <trac+jose@trac.tools.ietf.org>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6D8821F9EA9 for <jose@ietfa.amsl.com>; Sun, 18 Aug 2013 12:59:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s+0QL15ozYgG for <jose@ietfa.amsl.com>; Sun, 18 Aug 2013 12:59:10 -0700 (PDT)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 54E6621F9E21 for <jose@ietf.org>; Sun, 18 Aug 2013 12:59:10 -0700 (PDT)
Received: from localhost ([127.0.0.1]:41747 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+jose@trac.tools.ietf.org>) id 1VB97z-0002hx-VG; Sun, 18 Aug 2013 21:59:07 +0200
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>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-jose-json-web-key@tools.ietf.org, ietf@augustcellars.com
X-Trac-Project: jose
Date: Sun, 18 Aug 2013 19:59:07 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: https://grenache.tools.ietf.org/wg/jose/trac/ticket/84
Message-ID: <061.2c8e43041b4a771491d9dbf782ad3a03@trac.tools.ietf.org>
X-Trac-Ticket-ID: 84
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-key@tools.ietf.org, ietf@augustcellars.com, jose@ietf.org
X-SA-Exim-Mail-From: trac+jose@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: mbj@microsoft.com
Resent-Message-Id: <20130818195910.54E6621F9E21@ietfa.amsl.com>
Resent-Date: Sun, 18 Aug 2013 12:59:10 -0700
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: [jose] #84: Section 7.1 JSON Web Key Parameters Registry
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 19 Aug 2013 23:23:12 -0000
#84: Section 7.1 JSON Web Key Parameters Registry 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. -- -------------------------+------------------------------------------------- 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 | Keywords: Severity: - | -------------------------+------------------------------------------------- Ticket URL: <https://grenache.tools.ietf.org/wg/jose/trac/ticket/84> 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