Re: [jose] Proposed resolution of header criticality issue
"Manger, James H" <James.H.Manger@team.telstra.com> Tue, 12 March 2013 02:48 UTC
Return-Path: <James.H.Manger@team.telstra.com>
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 E960C21F88E8 for <jose@ietfa.amsl.com>; Mon, 11 Mar 2013 19:48:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.9
X-Spam-Level:
X-Spam-Status: No, score=-0.9 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, HTML_MESSAGE=0.001, RELAY_IS_203=0.994]
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 d9cqAtwOITff for <jose@ietfa.amsl.com>; Mon, 11 Mar 2013 19:48:13 -0700 (PDT)
Received: from ipxbno.tcif.telstra.com.au (ipxbno.tcif.telstra.com.au [203.35.82.204]) by ietfa.amsl.com (Postfix) with ESMTP id 30C8F21F87B1 for <jose@ietf.org>; Mon, 11 Mar 2013 19:48:10 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="4.84,827,1355058000"; d="scan'208,217"; a="118584610"
Received: from unknown (HELO ipccni.tcif.telstra.com.au) ([10.97.216.208]) by ipobni.tcif.telstra.com.au with ESMTP; 12 Mar 2013 13:48:08 +1100
X-IronPort-AV: E=McAfee;i="5400,1158,7011"; a="120270219"
Received: from wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) by ipccni.tcif.telstra.com.au with ESMTP; 12 Mar 2013 13:48:09 +1100
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by wsmsg3707.srv.dir.telstra.com ([172.49.40.81]) with mapi; Tue, 12 Mar 2013 13:48:08 +1100
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Tim Bray <tbray@textuality.com>, Karen ODonoghue <odonoghue@isoc.org>
Date: Tue, 12 Mar 2013 13:48:07 +1100
Thread-Topic: [jose] Proposed resolution of header criticality issue
Thread-Index: Ac4ewu3OxYs3UBa/Rsup629DaiYmfwABuoEA
Message-ID: <255B9BB34FB7D647A506DC292726F6E1150B786643@WSMSG3153V.srv.dir.telstra.com>
References: <513E6A73.1090403@isoc.org> <513E774C.6090605@isoc.org> <CAHBU6ivLV+D3g-gLgBNXkkj3cSPLXkh1KXcN83ewR0Hd6a4YtA@mail.gmail.com>
In-Reply-To: <CAHBU6ivLV+D3g-gLgBNXkkj3cSPLXkh1KXcN83ewR0Hd6a4YtA@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: multipart/alternative; boundary="_000_255B9BB34FB7D647A506DC292726F6E1150B786643WSMSG3153Vsrv_"
MIME-Version: 1.0
Cc: jose <jose@ietf.org>
Subject: Re: [jose] Proposed resolution of header criticality issue
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 12 Mar 2013 02:48:14 -0000
I’ll add some cheers — this does look like substantial progress. I assume the fields such as “epk”, “apu” etc that sometimes must be understood, and at other times must be ignored (depending on “alg” or “enc” value) would NOT be listed in the “crit” field as they are defined in the “base specs”. Being in the “base specs” is the right criteria for whether a field should be listed in “crit” as long as “base specs” means: “base specifications for the particular “alg”/”enc” values”. It shouldn’t mean (and doesn’t have to mean) the base spec for the whole JOSE system. P.S. “meta” might be a nicer label than “asd”. -- James Manger From: jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] On Behalf Of Tim Bray Sent: Tuesday, 12 March 2013 12:43 PM To: Karen ODonoghue Cc: jose Subject: Re: [jose] Proposed resolution of header criticality issue Cue wild cheers from the peanut gallery where non-cryptographers sit. MustIgnore is infinitely more robust and open-ended than MustUnderstand. -T On Mon, Mar 11, 2013 at 5:31 PM, Karen O'Donoghue <odonoghue@isoc.org<mailto:odonoghue@isoc.org>> wrote: Folks, A side meeting was held Sunday with a number of jose working group participants to try to resolve the open issue related to header criticality. The following are the proposed resolutions from the meeting. Point 5 of the proposed resolution below is actually independent of the other 4 points, and could be considered separately. This will all be discussed in Wednesday's meeting. In addition to the text below, there was some agreement to replace the "understand" text with something a bit more explicit like "must process". However, that text has not been rolled into the summary text below yet. Thank you to Jim Schaad, Mike Jones, John Bradley, Nat Sakimura, Martin Thomas, Eric Rescorla, Matt Miller, and Richard Barnes for your efforts (and my apologies if I missed someone). Regards, Karen 1: Change the language “Additional members MAY be present in the JWK. If present, they MUST be understood by implementations using them.” to “Additional members MAY be present in the JWK. If not understood by implementations encountering them, they MUST be ignored.” (And make the same change for JWK Set as well.) 2: Characterize all existing JWS and JWE header fields as either must be understood or may be ignored. “alg”, “enc”, and “zip” must be understood. “kid”, “x5u”, “x5c”, “x5t”, “jwk”, “jku”, “typ”, and “cty” can be ignored because while not using them may result in the inability to process some signatures or encrypted content, this will not result in a security violation – just degraded functionality. Other fields such as “epk”, “apu”, “apv”, “epu”, and “epv” must be understood and used when “alg” or “enc” values requiring them are used, and otherwise they may be ignored. 3. Define a new header field that lists which additional fields not defined in the base specifications must be understood and acted upon when present. For instance, an expiration-time extension field could be marked as must-be-understood-and-acted-upon. One possible name for this would be “crit” (critical). An example use, along with a hypothetical “exp” (expiration-time) field is: {"alg":"ES256", "crit":["exp"], "exp”:1363284000 } 4. All additional header fields not defined in the base specifications and not contained in the “crit” list MUST be ignored if not understood. 5. Define a new header field “asd” (application-specific data) whose value is a JSON structure whose contents are opaque to and ignored by JWS and JWE implementations but for which its contents MUST be provided to applications using JWS or JWE, provided that the signature/MAC validation or decryption operation succeeds. The intended use of this field is to have a standard place to provide application-specific metadata about the payload or plaintext. _______________________________________________ jose mailing list jose@ietf.org<mailto:jose@ietf.org> https://www.ietf.org/mailman/listinfo/jose
- [jose] Proposed resolution of header criticality … Karen O'Donoghue
- Re: [jose] Proposed resolution of header critical… Tim Bray
- Re: [jose] Proposed resolution of header critical… Manger, James H
- Re: [jose] Proposed resolution of header critical… John Bradley
- Re: [jose] Proposed resolution of header critical… Richard Barnes
- Re: [jose] Proposed resolution of header critical… Dick Hardt
- Re: [jose] Proposed resolution of header critical… Manger, James H
- Re: [jose] Proposed resolution of header critical… Dick Hardt
- Re: [jose] Proposed resolution of header critical… Vladimir Dzhuvinov / NimbusDS
- Re: [jose] Proposed resolution of header critical… Dirkjan Ochtman
- Re: [jose] Proposed resolution of header critical… Richard Barnes
- Re: [jose] Proposed resolution of header critical… Manger, James H
- Re: [jose] Proposed resolution of header critical… Vladimir Dzhuvinov / NimbusDS
- Re: [jose] Proposed resolution of header critical… Richard Barnes
- Re: [jose] Proposed resolution of header critical… Mike Jones
- Re: [jose] Proposed resolution of header critical… Mike Jones
- Re: [jose] Proposed resolution of header critical… Brian Campbell
- Re: [jose] Proposed resolution of header critical… John Bradley
- Re: [jose] Proposed resolution of header critical… Richard Barnes
- Re: [jose] Proposed resolution of header critical… Richard Barnes
- Re: [jose] Proposed resolution of header critical… Matt Miller (mamille2)
- Re: [jose] Proposed resolution of header critical… Jim Schaad
- Re: [jose] Proposed resolution of header critical… Richard Barnes
- Re: [jose] Proposed resolution of header critical… Anthony Nadalin
- Re: [jose] Proposed resolution of header critical… Mike Jones
- Re: [jose] Proposed resolution of header critical… Anthony Nadalin
- Re: [jose] Proposed resolution of header critical… Dick Hardt
- Re: [jose] Proposed resolution of header critical… Richard Barnes
- Re: [jose] Proposed resolution of header critical… Dick Hardt
- Re: [jose] Proposed resolution of header critical… John Bradley
- Re: [jose] Proposed resolution of header critical… Dick Hardt
- Re: [jose] Proposed resolution of header critical… John Bradley
- Re: [jose] Proposed resolution of header critical… Dick Hardt
- Re: [jose] Proposed resolution of header critical… Brian Campbell
- [jose] "crit" strings don't have to be field names Manger, James H
- Re: [jose] "crit" strings don't have to be field … Richard Barnes
- Re: [jose] "crit" strings don't have to be field … Manger, James H
- Re: [jose] "crit" strings don't have to be field … Manger, James H
- Re: [jose] Proposed resolution of header critical… Jim Schaad
- Re: [jose] Proposed resolution of header critical… Richard Barnes
- Re: [jose] Proposed resolution of header critical… John Bradley