[jose] Possible (minor) Errata for JWS / RFC7515

Brian Campbell <bcampbell@pingidentity.com> Mon, 21 December 2015 23:12 UTC

Return-Path: <bcampbell@pingidentity.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 22AEF1ACE66 for <jose@ietfa.amsl.com>; Mon, 21 Dec 2015 15:12:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 fkglYs6QsK4a for <jose@ietfa.amsl.com>; Mon, 21 Dec 2015 15:12:05 -0800 (PST)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CEC0E1ACE54 for <jose@ietf.org>; Mon, 21 Dec 2015 15:12:05 -0800 (PST)
Received: by mail-io0-x22c.google.com with SMTP id q126so169775128iof.2 for <jose@ietf.org>; Mon, 21 Dec 2015 15:12:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:from:date:message-id:subject:to:content-type; bh=3umhGVjJxDhN7XJmBeEuQK3TPLcjjGaGq9d3dBhZh+E=; b=IoWdMfRDCmAwpib6CJkmyLR3SLL4OttThhrN7HI66gfTmalq5kc/Or9qUJ0dgnr8o5 zBuh15pXd1PXerasZQ6qN2B/H2b2K5hUzYyO94HHcKVGNAiZcxdJBd+oTlHP/pG8i2bC n2t8++h/iRplqOpKtchcswGYuzr25avQcd/Hc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=3umhGVjJxDhN7XJmBeEuQK3TPLcjjGaGq9d3dBhZh+E=; b=LWczId0kE1TZs0PpjUrX7l04UWolSFOmyKyxSDCIC3hAbSmX99IZ4fsBJRhfnlO5t+ DXiMclVWFik5meWm2DthvfWUwbsO47eaKXEdPylrI+XxbMHqYcnoT1ErAjkw0UhXLwZJ 0yAxCEpScSfe0pER0QDnLYrtwpZL6gvvTthkwvHX0RKyogSeN5JYI759L0JeOxzqFo9G Y497/Ejo3f8cPhTPLnfaVv98h5PDypZDEG0y8Nl5p7n51FPPFpCqwdQwCH4rkmVYHiDp s0NzbevJM/skc4y81qVxX5YVQHUb2NIAgVIcpVmw7LtwHKKul8daxujzXdHtG7HlfbJY hVMw==
X-Gm-Message-State: ALoCoQn0h6BcK8ZD8tgz1gRquAIvHfIkpB1vD99iG0dCpjQXh7SAIUY9EAiVJEbKpPjw9LUP+STeCSmiZNCkaOmpnlwkH18w3z7VRSHrUynTJ2LHbtHYEb4=
X-Received: by 10.107.33.12 with SMTP id h12mr24382038ioh.48.1450739525073; Mon, 21 Dec 2015 15:12:05 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.23.133 with HTTP; Mon, 21 Dec 2015 15:11:35 -0800 (PST)
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 21 Dec 2015 16:11:35 -0700
Message-ID: <CA+k3eCR+S9tPCfuTWyFhg+9MHJ27rbhme6J6V7sUw0bwOBqg3g@mail.gmail.com>
To: "jose@ietf.org" <jose@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140c20c0ddce20527709ed1"
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/lZfTHfsNe9iO5oHylNy9Wr-L0CM>
Subject: [jose] Possible (minor) Errata for JWS / RFC7515
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: <https://mailarchive.ietf.org/arch/browse/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, 21 Dec 2015 23:12:07 -0000

The recent discussion about whether or not to mandate using "crit" with the
"b64" header
<http://www.ietf.org/mail-archive/web/jose/current/msg05427.html> inspired
me to look at the support for "crit" in my own implementation (which was,
ahem, somewhat lacking). In doing so I went to add the "Negative Test Case
for "crit" Header Parameter" from Appendix E
<http://tools.ietf.org/html/rfc7515#appendix-E> and I noticed that the
header name used in the text and the unencoded header is different than
what's in the encoded JWS. It's "http://example.invalid/UNDEFINED" in the
former and "http://example.com/UNDEFINED" in the latter. The intent of the
test case is pretty clear but it's still inconsistent. Is this the kind of
thing that should be an errata?






<http://tools.ietf.org/html/rfc7515#appendix-E>