Re: [jose] POLL(s): header criticality

Stephen Kent <kent@bbn.com> Thu, 07 February 2013 16:11 UTC

Return-Path: <kent@bbn.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 D855421F86EF for <jose@ietfa.amsl.com>; Thu, 7 Feb 2013 08:11:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UIYqAFuLQh78 for <jose@ietfa.amsl.com>; Thu, 7 Feb 2013 08:11:43 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 3C30C21F86DC for <jose@ietf.org>; Thu, 7 Feb 2013 08:11:43 -0800 (PST)
Received: from dhcp89-089-208.bbn.com ([128.89.89.208]:54071) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1U3U4b-000K6k-JV; Thu, 07 Feb 2013 11:11:41 -0500
Message-ID: <5113D23D.4040407@bbn.com>
Date: Thu, 07 Feb 2013 11:11:41 -0500
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: jose@ietf.org, Hannes.Tschofenig@gmx.net
References: <510FCA42.5000704@isoc.org> <51134A69.5020704@gmx.net> <4E1F6AAD24975D4BA5B1680429673943674194D4@TK5EX14MBXC284.redmond.corp.microsoft.com> <20130207085054.180050@gmx.net>
In-Reply-To: <20130207085054.180050@gmx.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [jose] POLL(s): header criticality
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: Thu, 07 Feb 2013 16:11:44 -0000

Hannes,

I share your concern. If JOSE is to be used more widely than in the 
OpenID context, then it
probably is not a good idea to rely on constructs/conventions from that 
context re extensions.

Steve

On 2/7/13 3:50 AM, Hannes Tschofenig wrote:
> Hi Mike,
>
> whatever story the group comes up with I believe it would be important to describe this in the document since other specifications have followed a different approach.
>
> Knowing you guys I had already expected that you try to solve this extensibility issue using additional OpenID Connect specifications.
>
> I am wondering what approach other specifications have used in the past. My understanding is that XML, CMS, and PSKC follow a model where the mandatory to implement functionality is defined in the specification and additional specifications indicate what additional extensions have to be used. Is my understanding correct?
>
> Ciao
> Hannes
>