Re: [jose] Feedback request on jose tracker issue #15: Should at least on key indicator be mandatory
Richard Barnes <rlb@ipv.sx> Mon, 15 April 2013 15:40 UTC
Return-Path: <rlb@ipv.sx>
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 AD02821F9404 for <jose@ietfa.amsl.com>; Mon, 15 Apr 2013 08:40:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.063
X-Spam-Level:
X-Spam-Status: No, score=-1.063 tagged_above=-999 required=5 tests=[AWL=-0.638, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RDNS_NONE=0.1]
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 JUFa6OoR49Xb for <jose@ietfa.amsl.com>; Mon, 15 Apr 2013 08:40:43 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id CC97521F9401 for <jose@ietf.org>; Mon, 15 Apr 2013 08:40:42 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id va7so4188306obc.6 for <jose@ietf.org>; Mon, 15 Apr 2013 08:40:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:x-originating-ip:in-reply-to:references :date:message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=eYVbsb8z9rtHiQWbJ+yLXziBkoOjS970euOPlh3YXt0=; b=W3EOjrQGUmvqPFgtYsPUDFEPyzbcC55/WOy3FawJziYEFqanlyfZJbG/oJh6Cda7RH G9mQx1CiHhGzV+HxYJWr/dcjOm/AkhN/p26UCjrMxiB942ij2Ntn2fT7CUgunwIsvt3p Ab5T/osdQmuAUFxk05ost8d9URHTZcbFKI9pkucIhf/fmzOnL+8uLxsrYZmUB0mbJEN2 49PkJZN3dB+20SKARA3cGzxPoG3OPknaaidBP9vBCvXsFgTs56N7abjONr8tK6efDRvi Cu1ASmPDze3wcwkePyy9udjZD+JWnR8ntaOkJUPCAC6q9HZ2/q+mgpZ2UVOwlC3hAj8W BoEA==
MIME-Version: 1.0
X-Received: by 10.182.129.101 with SMTP id nv5mr3607360obb.56.1366040442255; Mon, 15 Apr 2013 08:40:42 -0700 (PDT)
Received: by 10.60.25.196 with HTTP; Mon, 15 Apr 2013 08:40:42 -0700 (PDT)
X-Originating-IP: [66.207.95.33]
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394367615F37@TK5EX14MBXC283.redmond.corp.microsoft.com>
References: <51674E63.3050809@isoc.org> <4E1F6AAD24975D4BA5B168042967394367615F37@TK5EX14MBXC283.redmond.corp.microsoft.com>
Date: Mon, 15 Apr 2013 11:40:42 -0400
Message-ID: <CAL02cgQ5OOwkTRNsSypq+y6+z3_cqAxDvkNo+HvC0m44oNf-fA@mail.gmail.com>
From: Richard Barnes <rlb@ipv.sx>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary="e89a8fb1ebe44f4d8004da6813f4"
X-Gm-Message-State: ALoCoQkXpLoAqH5KTdaxryBILmqtcbMHos+mTdd2YM0XmSXE8hUCfqCu8trxFijiDfNzXHofR18/
Cc: "jose@ietf.org" <jose@ietf.org>, "odonoghue@isoc.org" <odonoghue@isoc.org>
Subject: Re: [jose] Feedback request on jose tracker issue #15: Should at least on key indicator be mandatory
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: Mon, 15 Apr 2013 15:40:43 -0000
Nice straw man, Mike :) Nobody is arguing that cases with out-of-band negotiation are not important. The question is how they should be supported. What ISSUE-9 and ISSUE-15 are about is saying that the default assumption should be that all communication is via JW* headers. Otherwise, we're not designing a stand-alone protocol, we're designing an adjunct to something else, and we should do it in that WG. That default assumption means that you have to have certain contraints, like a key indicator being REQUIRED. The SPI header is then the "get out of jail free card", releasing you from those constraints. Let's design a real protocol first, then let people cheat. --Richard On Fri, Apr 12, 2013 at 1:25 AM, Mike Jones <Michael.Jones@microsoft.com>wrote: > Reading this question, I believe that there’s a possibility for the > question to be misinterpreted, since the sense of the question in the > subject is opposite of the sense of the question in the body. I believe > that the intent of 1 and 2 were as follows:**** > > ** ** > > 1. Yes – Use cases where key information is exchanged by means other than > the JWS and JWE headers ARE important.**** > > 2. No – Use cases where key information is exchanged by means other than > the JWS and JWE headers ARE NOT important.**** > > ** ** > > Maybe people could reply with 1 and 2 as above, so that their answers to > the question of whether these use cases are important are not are > unambiguous.**** > > ** ** > > -- Mike**** > > ** ** > > *From:* jose-bounces@ietf.org [mailto:jose-bounces@ietf.org] *On Behalf > Of *Karen O'Donoghue > *Sent:* Thursday, April 11, 2013 5:00 PM > > *To:* jose@ietf.org > *Subject:* [jose] Feedback request on jose tracker issue #15: Should at > least on key indicator be mandatory**** > > ** ** > > Issue #15 http://trac.tools.ietf.org/wg/jose/trac/ticket/15. suggests > requiring that a key indicator, such as a “kid” field, be required in all > JWS and JWE headers. Are use cases where key information is exchanged by > means other than the JWS or JWE headers important? **** > > Which of these best describes your preferences on this issue?**** > > 1. Yes.**** > > 2. No. **** > > 0. I need more information to decide.**** > > **** > > Your reply is requested by Friday, April 19th (or earlier). **** > > _______________________________________________ > jose mailing list > jose@ietf.org > https://www.ietf.org/mailman/listinfo/jose > >
- [jose] Feedback request on jose tracker issue #15… Karen O'Donoghue
- Re: [jose] Feedback request on jose tracker issue… Dick Hardt
- Re: [jose] Feedback request on jose tracker issue… Manger, James H
- Re: [jose] Feedback request on jose tracker issue… Mike Jones
- Re: [jose] Feedback request on jose tracker issue… Axel.Nennker
- Re: [jose] Feedback request on jose tracker issue… Roland Hedberg
- Re: [jose] Feedback request on jose tracker issue… hideki nara
- Re: [jose] Feedback request on jose tracker issue… Mike Jones
- Re: [jose] Feedback request on jose tracker issue… Richard Barnes
- Re: [jose] Feedback request on jose tracker issue… Richard Barnes
- Re: [jose] Feedback request on jose tracker issue… Mike Jones
- Re: [jose] Feedback request on jose tracker issue… nov matake
- Re: [jose] Feedback request on jose tracker issue… Anthony Nadalin
- Re: [jose] Feedback request on jose tracker issue… Matias Woloski
- Re: [jose] Feedback request on jose tracker issue… Breno de Medeiros
- Re: [jose] Feedback request on jose tracker issue… Richard Barnes
- Re: [jose] Feedback request on jose tracker issue… Mike Jones
- Re: [jose] Feedback request on jose tracker issue… Edmund Jay
- Re: [jose] Feedback request on jose tracker issue… Richard Barnes
- Re: [jose] Feedback request on jose tracker issue… charles.marais@orange.com
- Re: [jose] Feedback request on jose tracker issue… Sascha Preibisch
- Re: [jose] Feedback request on jose tracker issue… John Bradley
- Re: [jose] Feedback request on jose tracker issue… Javier Rojas Blum
- Re: [jose] Feedback request on jose tracker issue… Vladimir Dzhuvinov / NimbusDS
- Re: [jose] Feedback request on jose tracker issue… Matt Miller
- Re: [jose] Feedback request on jose tracker issue… Nat Sakimura
- Re: [jose] Feedback request on jose tracker issue… Russ Housley
- Re: [jose] Feedback request on jose tracker issue… Richard Barnes
- Re: [jose] Feedback request on jose tracker issue… Salvatore D'Agostino