Re: [jose] #169: Section 4.1.1 "alg" (Algorithm) Header Parameter
"jose issue tracker" <trac+jose@trac.tools.ietf.org> Thu, 03 October 2013 19:34 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 6EBD521E805D for <jose@ietfa.amsl.com>; Thu, 3 Oct 2013 12:34:30 -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=[AWL=0.000, 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 TxjnOtStBHVr for <jose@ietfa.amsl.com>; Thu, 3 Oct 2013 12:34:23 -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 8A31621E80AF for <jose@ietf.org>; Thu, 3 Oct 2013 12:16:53 -0700 (PDT)
Received: from localhost ([127.0.0.1]:37129 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 1VRoOF-0003XK-BF; Thu, 03 Oct 2013 21:16:47 +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-encryption@tools.ietf.org, ietf@augustcellars.com
X-Trac-Project: jose
Date: Thu, 03 Oct 2013 19:16:47 -0000
X-URL: http://tools.ietf.org/jose/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/jose/trac/ticket/169#comment:2
Message-ID: <076.d349050b448551406387316b55da8913@trac.tools.ietf.org>
References: <061.6f0b49c8aa8f7366110b9cfa3a738ab7@trac.tools.ietf.org>
X-Trac-Ticket-ID: 169
In-Reply-To: <061.6f0b49c8aa8f7366110b9cfa3a738ab7@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-jose-json-web-encryption@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: ekr@rtfm.com, jhildebr@cisco.com, mbj@microsoft.com
Resent-Message-Id: <20131003191653.8A31621E80AF@ietfa.amsl.com>
Resent-Date: Thu, 03 Oct 2013 12:16:53 -0700
Resent-From: trac+jose@trac.tools.ietf.org
Cc: jose@ietf.org
Subject: Re: [jose] #169: Section 4.1.1 "alg" (Algorithm) Header Parameter
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: Thu, 03 Oct 2013 19:34:30 -0000
#169: Section 4.1.1 "alg" (Algorithm) Header Parameter Description changed by ietf@augustcellars.com: Old description: > A. See comments for JWS > > B. para 1 - s/identifies a/identifies the/ > > * FIXED > > C. Text does not recognize the multiple recipient case in rejecting the > JWE > > * FIXED > > D. SHOULD seems to not be 2119 - also what are the conditions where the > SHOULD can be violated. > > E. I need to find where it was the case (think it was implicit direct) > but there were some cases where I thought that the alg could be omitted > based on emails. > > F. Kill reference on the registry - The initial population is ok for > that. > > * probably is WON'T FIX New description: A. See comments for JWS (Issue #102) B. para 1 - s/identifies a/identifies the/ * FIXED C. Text does not recognize the multiple recipient case in rejecting the JWE * FIXED D. SHOULD seems to not be 2119 - also what are the conditions where the SHOULD can be violated. E. I need to find where it was the case (think it was implicit direct) but there were some cases where I thought that the alg could be omitted based on emails. * WONT FIX - the documents do not allow this, there was a thread which has since been repudiated that said it was allowed. F. Kill reference on the registry - The initial population is ok for that. * probably is WON'T FIX -- -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-jose-json-web- ietf@augustcellars.com | encryption@tools.ietf.org Type: defect | Status: new Priority: Editorial | Milestone: Component: json-web- | Version: encryption | Resolution: Severity: - | Keywords: | -------------------------+------------------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/jose/trac/ticket/169#comment:2> jose <http://tools.ietf.org/jose/>
- [jose] #169: Section 4.1.1 "alg" (Algorithm) Head… jose issue tracker
- Re: [jose] #169: Section 4.1.1 "alg" (Algorithm) … jose issue tracker
- Re: [jose] #169: Section 4.1.1 "alg" (Algorithm) … jose issue tracker
- Re: [jose] #169: Section 4.1.1 "alg" (Algorithm) … jose issue tracker