Re: [jose] way forward for two remaining drafts

"HAYASHI, Tatsuya" <lef.mutualauth@gmail.com> Thu, 16 July 2015 10:28 UTC

Return-Path: <lef.mutualauth@gmail.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 3B00A1B393B for <jose@ietfa.amsl.com>; Thu, 16 Jul 2015 03:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 1lS-PAC6q39a for <jose@ietfa.amsl.com>; Thu, 16 Jul 2015 03:28:26 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (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 64AAA1B3942 for <jose@ietf.org>; Thu, 16 Jul 2015 03:26:42 -0700 (PDT)
Received: by iebmu5 with SMTP id mu5so52442473ieb.1 for <jose@ietf.org>; Thu, 16 Jul 2015 03:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=mBvrtSnzpnxHm2cEoZTUv2d8C5cgTkALb3ssdfQCrw8=; b=MpOfW3WuO+/g3kMU5wAUVcfX8h0ymxPfv4A6FzKD75IcAswNrhyhs6y2cGjmqnz4l2 rU+TqVvBDdNer3MlrZWHr821jz5U4fu8x4NvQuc1HWJuCkoIeWtx0QrWU2mOIsUa3Ea9 tt2DM7jIe2ibdPp45CsA7tlQAAORiVYPRj/R5l25+sVkuvhMxSsUi3tMqc0xx4qF4xjM wNegR7zQvDplnAGXr+9gRVIVzOShY11lu+YGRv3c+YBjGE1f9bO1wK6v+C0hHmIfYTxy rH0Xi1qkU2+NY/CkhbfzG8rHDadcJS8PLZLPYSWik/0nXnZNw2jZ+OKlcJtY9jp4UFpm JUzg==
X-Received: by 10.50.143.101 with SMTP id sd5mr3412670igb.44.1437042401858; Thu, 16 Jul 2015 03:26:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.30 with HTTP; Thu, 16 Jul 2015 03:26:22 -0700 (PDT)
In-Reply-To: <CAAAkSUFNsogUgbKq3LOz4SPAr41AsKtzSLXHYJKNonWSycCR1g@mail.gmail.com>
References: <8FF9C9E8-7259-4818-ADC2-8D70E4FBB9E9@isoc.org> <BY2PR03MB4424F0C2B5D8839444DD44CF5900@BY2PR03MB442.namprd03.prod.outlook.com> <0B8C5F38-DE8A-474B-B8DC-8B53B824C5BD@gmail.com> <CABzCy2A_yxx+WFSLJiw5ZBPfGaR5de5Lf0uaPFbaMGOnzWSnpg@mail.gmail.com> <CAAAkSUFNsogUgbKq3LOz4SPAr41AsKtzSLXHYJKNonWSycCR1g@mail.gmail.com>
From: "HAYASHI, Tatsuya" <lef.mutualauth@gmail.com>
Date: Thu, 16 Jul 2015 19:26:22 +0900
Message-ID: <CAGipQF=Y9BmKnOWezx96jnMa4MYS-jGRi9cj7r=cMW-WsbN=Rg@mail.gmail.com>
To: hideki nara <hdknr@ic-tact.co.jp>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <http://mailarchive.ietf.org/arch/msg/jose/gZJ6bVh1Y12PBHvcfhRL7bhfYik>
Cc: Karen O'Donoghue <odonoghue@isoc.org>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Nat Sakimura <sakimura@gmail.com>, Mike Jones <Michael.Jones@microsoft.com>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] way forward for two remaining drafts
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: Thu, 16 Jul 2015 10:28:28 -0000

+1

I think it's good.

On Thu, Jul 16, 2015 at 6:49 PM, hideki nara <hdknr@ic-tact.co.jp> wrote:
> +1
> ---
> hideki
>
> 2015-07-13 2:32 GMT+09:00 Nat Sakimura <sakimura@gmail.com>:
>>
>> Sorry to chime in so late. I have been completely under water for sometime
>> now.
>>
>> Like Phil, I do see that draft-jones-jose-jws-signing-input-options sort
>> of thing can be very useful, though I may want to have slightly different
>> way of encoding the things. Being able to do detached signature is quite
>> attractive.
>>
>> Best,
>>
>> Nat
>>
>> 2015-07-10 2:37 GMT+09:00 Kathleen Moriarty
>> <kathleen.moriarty.ietf@gmail.com>:
>>>
>>> Hi,
>>>
>>> Sent from my iPhone
>>>
>>> On Jul 9, 2015, at 1:16 PM, Mike Jones <Michael.Jones@microsoft.com>
>>> wrote:
>>>
>>> About
>>> https://tools.ietf.org/html/draft-jones-jose-jws-signing-input-options-00,
>>> I’ll add that this addresses the requests make by Jim Schaad and Richard
>>> Barnes in JOSE Issues #26 “Allow for signature payload to not be base64
>>> encoded” and #23 http://trac.tools.ietf.org/wg/jose/trac/ticket/23 “Make
>>> crypto independent of binary encoding (base64)”.
>>>
>>>
>>>
>>> About
>>> https://tools.ietf.org/html/draft-jones-jose-key-managed-json-web-signature-01,
>>> I’ll add that this addresses the request made by Jim Schaad in JOSE Issue #2
>>> http://trac.tools.ietf.org/wg/jose/trac/ticket/2 “No key management for
>>> MAC”.
>>>
>>>
>>>
>>> Also, there’s a highly relevant discussion about key management for MACs
>>> going on in the COSE working group.  See the thread “[Cose] Key management
>>> for MACs (was Re: Review of draft-schaad-cose-msg-01)” – especially
>>> https://mailarchive.ietf.org/arch/msg/cose/aUehU6O7Ui8CXcGxy3TquZOxWH4 and
>>> https://mailarchive.ietf.org/arch/msg/cose/ouOIdAOe2P-W8BjGLJ7BNvvRr10.
>>>
>>>
>>>
>>> One could take the view that our decision on the JOSE key management
>>> draft should be informed by the related decision in COSE.  Specifically,
>>> that if COSE decides to support key management for MACs, the same reasoning
>>> likely should apply to our decision on whether to define a standard
>>> mechanism for supporting key management for MACs in JOSE.
>>>
>>>
>>>
>>> Key management is explicitly out-of-scope for COSE as stated in the
>>> charter.  The discussion referenced had this point at the close of that
>>> discussion.
>>>
>>> I'm not seeing much support for these drafts moving forward in JOSE.  I'm
>>> also not seeing enough to justify standards track and AD sponsored.  If you
>>> think these are important to have move forward in the WG or as standards
>>> track, please say so soon.  They can still go forward through the
>>> Independent submission process through the ISE.
>>>
>>> Thank you,
>>> Kathleen
>>>
>>>                                                             -- Mike
>>>
>>>
>>>
>>> From: jose [mailto:jose-bounces@ietf.org] On Behalf Of Karen O'Donoghue
>>> Sent: Wednesday, July 01, 2015 8:38 AM
>>> To: jose@ietf.org
>>> Subject: [jose] way forward for two remaining drafts
>>>
>>>
>>>
>>> Folks,
>>>
>>>
>>>
>>> With the thumbprint draft progressing through the process, we have two
>>> remaining individual drafts to decide what to do with. The options include:
>>> 1) adopt as working group drafts; 2) ask for AD sponsorship of individual
>>> drafts; or 3) recommend that they not be published. Please express your
>>> thoughts on what we should do with these drafts. Jim, Kathleen, and I would
>>> like to make a decision in the Prague timeframe, so please respond by 15
>>> July.
>>>
>>>
>>>
>>>
>>> https://tools.ietf.org/id/draft-jones-jose-jws-signing-input-options-00.txt
>>>
>>>
>>>
>>>
>>> https://tools.ietf.org/id/draft-jones-jose-key-managed-json-web-signature-01.txt
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Karen
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>>>
>>>
>>> _______________________________________________
>>> jose mailing list
>>> jose@ietf.org
>>> https://www.ietf.org/mailman/listinfo/jose
>>>
>>
>>
>>
>> --
>> Nat Sakimura (=nat)
>> Chairman, OpenID Foundation
>> http://nat.sakimura.org/
>> @_nat_en
>>
>> _______________________________________________
>> jose mailing list
>> jose@ietf.org
>> https://www.ietf.org/mailman/listinfo/jose
>>
>
>
> _______________________________________________
> jose mailing list
> jose@ietf.org
> https://www.ietf.org/mailman/listinfo/jose
>



-- 
HAYASHI, Tatsuya
Lepidum Co. Ltd.