Re: [COSE] New Version Notification for draft-schaad-cose-x509-00.txt
Jim Schaad <ietf@augustcellars.com> Tue, 06 December 2016 04:16 UTC
Return-Path: <ietf@augustcellars.com>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59CFC129695 for <cose@ietfa.amsl.com>; Mon, 5 Dec 2016 20:16:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.796
X-Spam-Level:
X-Spam-Status: No, score=-4.796 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-2.896, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 F4xf7fpsycY0 for <cose@ietfa.amsl.com>; Mon, 5 Dec 2016 20:16:49 -0800 (PST)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7C501296A9 for <cose@ietf.org>; Mon, 5 Dec 2016 20:16:48 -0800 (PST)
Received: from hebrews (24.21.96.37) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 5 Dec 2016 20:36:27 -0800
From: Jim Schaad <ietf@augustcellars.com>
To: "'Lundblade, Laurence'" <llundbla@qti.qualcomm.com>, 'Samuel Erdtman' <samuel@erdtman.se>
References: <147987163959.30322.14158962529156430503.idtracker@ietfa.amsl.com> <004901d24546$8e76bfe0$ab643fa0$@augustcellars.com> <CAF2hCbZK4+mSHTqvZQnzFD+7F8PDkP0q3JNFYp=dOMRkE+Vh=w@mail.gmail.com> <9CE238FE-6AF0-458D-A1C7-B790870323D3@qti.qualcomm.com>
In-Reply-To: <9CE238FE-6AF0-458D-A1C7-B790870323D3@qti.qualcomm.com>
Date: Mon, 05 Dec 2016 20:16:40 -0800
Message-ID: <06e701d24f77$8d438280$a7ca8780$@augustcellars.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_06E8_01D24F34.7F265D00"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGas+U5hOX2ZwwTfdISQ4lSrZ9yRQGKptd0AmvDM5wAeJK3gqFGCfeA
Content-Language: en-us
X-Originating-IP: [24.21.96.37]
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/5A67oKZruqDoQ7cOXu3pKOfsGJ0>
Cc: 'cose' <cose@ietf.org>
Subject: Re: [COSE] New Version Notification for draft-schaad-cose-x509-00.txt
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>, <mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>, <mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Dec 2016 04:16:52 -0000
Thanks for input, it is something that nobody else has actually given yet. I could easily get behind the idea of moving to two different headers, one for ordered and one for a bag. I don't think that there would be a huge problem with assigning the multiple code points. I don't know how common/uncommon it is for fields to allow multiple types. I do know that the COSE spec does it in a couple of places, although most of them can be ignored at this point in time. Personally, I don't find the code to support that feature to be very difficult and argued that as part of the JOSE effort when the same topic was discussed. While it does not explicitly say that in COSE, my assumption was always that 'kid' only identified COSE based keys. I think that is probably an invalid assumption. I would however expect that if an explicit key is given in the form a certificate then a kid would not need to be present. An application however could state that a kid could be the spki value from a certificate so that it could be used to find certificates if desired. I'll make a comment to myself on that. More comments from everybody about what is good and bad are wanted. Jim From: Lundblade, Laurence [mailto:llundbla@qti.qualcomm.com] Sent: Monday, December 05, 2016 6:21 PM To: Samuel Erdtman <samuel@erdtman.se> Cc: Jim Schaad <ietf@augustcellars.com>; cose <cose@ietf.org> Subject: Re: [COSE] New Version Notification for draft-schaad-cose-x509-00.txt Sorry for the delayed response and thanks for the draft. The order definitive chain option for x5c looks pretty good. How does the kid parameter come into play? Is x5c in lieu of kid? Seems like it would be. Is it usual to have the data type / semantics vary for some CBOR like x5c? Haven't run into any CBOR like that before. Would it be better to have an x5cb (b for bag) and an x5co (o for ordered). Thanks! LL On Nov 23, 2016, at 10:43 PM, Samuel Erdtman <samuel@erdtman.se <mailto:samuel@erdtman.se> > wrote: Looks like a good start to me. Laurence what do you think? //Samuel On Wed, Nov 23, 2016 at 6:00 AM, Jim Schaad <ietf@augustcellars.com <mailto:ietf@augustcellars.com> > wrote: This is a rough draft of what a set of X.509 headers could look like. There is lots of things that are incomplete or missing, but I said I would write up a fast version for people to look at so here it is. If you are interested, please comment on the headers. The pointer to the github repository is in the document. Jim > -----Original Message----- > From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org <mailto:internet-drafts@ietf.org> ] > Sent: Tuesday, November 22, 2016 7:27 PM > To: Jim Schaad <ietf@augustcellars.com <mailto:ietf@augustcellars.com> > > Subject: New Version Notification for draft-schaad-cose-x509-00.txt > > > A new version of I-D, draft-schaad-cose-x509-00.txt has been successfully > submitted by Jim Schaad and posted to the IETF repository. > > Name: draft-schaad-cose-x509 > Revision: 00 > Title: CBOR Encoded Message Syntax (COSE): Headers for carrying > and referencing X.509 certificates > Document date: 2016-11-22 > Group: Individual Submission > Pages: 6 > URL: https://www.ietf.org/internet-drafts/draft-schaad-cose-x509-00.txt > Status: https://datatracker.ietf.org/doc/draft-schaad-cose-x509/ > Htmlized: https://tools.ietf.org/html/draft-schaad-cose-x509-00 > > > Abstract: > This document defines the headers and usage for referring to and > transporting X.509 certificates in the CBOR Encoded Message (COSE) > Syntax. > > Contributing to this document > > The source for this draft is being maintained in GitHub. Suggested > changes should be submitted as pull requests at <https://github.com/ > cose-wg/X509>. Instructions are on that page as well. Editorial > changes can be managed in GitHub, but any substantial issues need to > be discussed on the COSE mailing list. > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org/> . > > The IETF Secretariat _______________________________________________ COSE mailing list COSE@ietf.org <mailto:COSE@ietf.org> https://www.ietf.org/mailman/listinfo/cose
- Re: [COSE] New Version Notification for draft-sch… Laurence Lundblade
- Re: [COSE] New Version Notification for draft-sch… Laurence Lundblade
- Re: [COSE] New Version Notification for draft-sch… Jim Schaad
- [COSE] FW: New Version Notification for draft-sch… Jim Schaad
- Re: [COSE] FW: New Version Notification for draft… Samuel Erdtman
- Re: [COSE] FW: New Version Notification for draft… Kumar, Sandeep
- Re: [COSE] FW: New Version Notification for draft… Ludwig Seitz
- Re: [COSE] FW: New Version Notification for draft… Kathleen Moriarty
- Re: [COSE] FW: New Version Notification for draft… Kumar, Sandeep
- Re: [COSE] FW: New Version Notification for draft… Jim Schaad
- Re: [COSE] FW: New Version Notification for draft… Justin Richer
- Re: [COSE] New Version Notification for draft-sch… Lundblade, Laurence
- Re: [COSE] New Version Notification for draft-sch… Jim Schaad
- Re: [COSE] New Version Notification for draft-sch… Samuel Erdtman