Re: [COSE] Assigning CBOR tags to key structures
Jim Schaad <ietf@augustcellars.com> Fri, 07 April 2017 16:05 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 73B8C129400 for <cose@ietfa.amsl.com>; Fri, 7 Apr 2017 09:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=augustcellars.com
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 pUNK_TQVZj6P for <cose@ietfa.amsl.com>; Fri, 7 Apr 2017 09:05:08 -0700 (PDT)
Received: from mail4.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 9B177127863 for <cose@ietf.org>; Fri, 7 Apr 2017 09:05:08 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-us
DKIM-Signature: v=1; a=rsa-sha256; d=augustcellars.com; s=winery; c=simple/simple; t=1491581092; h=from:subject:to:date:message-id; bh=NPR4M6PO5TIrjDCP8kl/AjpDmLEjesb8PltMeoDYYfg=; b=JeZmzvX8i71thHFhha6yefB3ZiwyjZBkTf6jmzdxVbVMVeQO6r9q5HHKZZ5yyaS7PccRAUA4fhE h8vTw0kWTaBeWHoOp9JA/fR4tH5leNbi09tH931tBz4gXeCnhdTyWqc3+qrMZZLYFwUC7xc57TEjq WBR91dmWALN5L4Bv0T2vvcMSyJxzcHbhNlfoB9zpNBdHK/JaY673LtFKhi+rEVfLWPsKz9LR3c2p+ EQbrVTtHAgVVkvVch+M0ChMXGhCDFMX4fSQBzpXNKRKr3Sta6KA7G3EODZiwDok4syrgcSSQLBMAH BT5oK76wRN5D0PU3a6yHqOSp2JAC66rNTIrA==
Received: from mail2.augustcellars.com (192.168.1.201) by mail4.augustcellars.com (192.168.1.153) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 7 Apr 2017 09:04:51 -0700
Received: from hebrews (192.168.0.98) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 7 Apr 2017 09:04:49 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Renzo Navas' <renzoefra@gmail.com>, 'cose' <cose@ietf.org>
CC: 'Carsten Bormann' <cabo@tzi.org>
References: <08eb01d103c8$3deade00$b9c09a00$@augustcellars.com> <561A2C9B.5060104@tzi.org> <094001d10451$cccec4e0$666c4ea0$@augustcellars.com> <CAD2CPUGTgSiNBVkrvYLnk6=OmwNwQu-z=mSwo_r=j8RHVtX2VQ@mail.gmail.com>
In-Reply-To: <CAD2CPUGTgSiNBVkrvYLnk6=OmwNwQu-z=mSwo_r=j8RHVtX2VQ@mail.gmail.com>
Date: Fri, 07 Apr 2017 09:04:47 -0700
Message-ID: <028601d2afb8$afa316f0$0ee944d0$@augustcellars.com>
MIME-Version: 1.0
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQGex/CO2QN+9BtqSk7SR9o8Xg6cPgIFoq+pArZgrAsCiFAtDqHnogQw
X-Originating-IP: [192.168.0.98]
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/CmKZN93mefuPf8wHElzZuDdh0D4>
Subject: Re: [COSE] Assigning CBOR tags to key structures
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 07 Apr 2017 16:05:11 -0000
There is a content type that was defined. This can be used for the same purpose by including a content type in the protected properties. This allows for identification of the content before doing the decryption. jim > -----Original Message----- > From: Renzo Navas [mailto:renzoefra@gmail.com] > Sent: Friday, April 7, 2017 1:34 AM > To: cose <cose@ietf.org> > Cc: Carsten Bormann <cabo@tzi.org>; Jim Schaad <ietf@augustcellars.com> > Subject: Re: [COSE] Assigning CBOR tags to key structures > > Hi all! > Sorry to revive this 1 and half year old topic. > > In the end we finally have no CBOR Tag for COSE_Key and COSE_KeySet, I > could not find at IANA (nor on the cose rev 24 document) :( Was it discarded > at the end, why? or there is a chance to still get the tag at IANA? > > Regards ! > > Renzo > > > ------------ > > PS: some more details of why this can be useful follow: > > More details on the Use Case: transporting a symmetric key with COSE_Key , it > has to be protected, so wrapped on an Encrypt0 message (Tag 16); Would be > nice have a tag to identify that the payload is a Cose_key object; it is true at > the moment I can design the app to always expect a keyobjet as the payload of > an encrypt0 ... ; but I'm cutting flexibility, or we can design a custom cbor > structure, but we are loosing on interoperability. > I have a coap server, with limited ram, and I have actually size only for for two > coap resources, so I can see I will have to overload some functionality of this > resource, particularly this is a sort of "/authz-info" ace resource, that I will use > to do authenticated key establishment (oauth pop token provisioning), and > other stuff, so probably quite overloaded. > > > > > On Sun, Oct 11, 2015 at 8:22 PM, Jim Schaad <ietf@augustcellars.com> > wrote: > > As a general rule, this makes sense to me. > > > > Jim > > > > > >> -----Original Message----- > >> From: Carsten Bormann [mailto:cabo@tzi.org] > >> Sent: Sunday, October 11, 2015 2:32 AM > >> To: Jim Schaad <ietf@augustcellars.com> > >> Cc: cose@ietf.org > >> Subject: Re: [COSE] Assigning CBOR tags to key structures > >> > >> I'd propose this rule: > >> If there is a media type, there should be a CBOR tag for those > >> environments that don't benefit from media types. > >> (And generally vice versa, unless we are using CBOR tags in other > >> than top-level > >> positions.) > >> > >> Grüße, Carsten > >> > >> > >> Jim Schaad wrote: > >> > I am currently working on the IANA text for doing assignment of > >> > CBOR tags in COSE. > >> > > >> > There is a possibility to request tags for the KEY and KEY_SET maps > >> > in the document. At the present time I have not done this. Can > >> > anybody see a reason for asking for tags on these two elements > >> > other than > >> completeness? > >> > I.e. does anybody have a place where it would make sense to use the > >> > pre-defined tags rather than knowing either a key or key set is in > >> > this location (it is possible to distinguish between the two items > >> > based on the an array vs map tag.) > >> > > >> > > >> > Jim > >> > > >> > > >> > _______________________________________________ > >> > COSE mailing list > >> > COSE@ietf.org > >> > https://www.ietf.org/mailman/listinfo/cose > >> > > > > > _______________________________________________ > > COSE mailing list > > COSE@ietf.org > > https://www.ietf.org/mailman/listinfo/cose
- Re: [COSE] Assigning CBOR tags to key structures Renzo Navas
- Re: [COSE] Assigning CBOR tags to key structures Renzo Navas
- [COSE] Assigning CBOR tags to key structures Jim Schaad
- Re: [COSE] Assigning CBOR tags to key structures Carsten Bormann
- Re: [COSE] Assigning CBOR tags to key structures Mike Jones
- Re: [COSE] Assigning CBOR tags to key structures Jim Schaad
- Re: [COSE] Assigning CBOR tags to key structures Renzo Navas
- Re: [COSE] Assigning CBOR tags to key structures Jim Schaad
- Re: [COSE] Assigning CBOR tags to key structures Carsten Bormann