Re: [COSE] Assigning CBOR tags to key structures
Renzo Navas <renzoefra@gmail.com> Fri, 07 April 2017 08:34 UTC
Return-Path: <renzoefra@gmail.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 D425F129646 for <cose@ietfa.amsl.com>; Fri, 7 Apr 2017 01:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, 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=gmail.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 qwXV7CxMAfxT for <cose@ietfa.amsl.com>; Fri, 7 Apr 2017 01:34:06 -0700 (PDT)
Received: from mail-qk0-x22a.google.com (mail-qk0-x22a.google.com [IPv6:2607:f8b0:400d:c09::22a]) (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 68882128CD5 for <cose@ietf.org>; Fri, 7 Apr 2017 01:34:06 -0700 (PDT)
Received: by mail-qk0-x22a.google.com with SMTP id f133so40028120qke.2 for <cose@ietf.org>; Fri, 07 Apr 2017 01:34:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=rt0OznU+VEoi+q5tx7l5quRbiA9fsTNT1ImlZ1yJJOY=; b=XkH1v8ywt+M+6ZSa+oXB07TJsBdWbn2Db7JGA86UJ1+qlGUMrlF6phvAcBQxFJSpAA qEiUs0z9QGaG2qew+9lKjJZNCDpLPwCGwZVJpCrUR4+hVFjDxwJgElbgyMXaH9PfeDhL S/g+9SahJQiKvWH0wJ5iImFUV2++Z0RXFEm4Zu8F+JTEetub+dlNR4BHanK42GgC3lQB 7xfqIOFm2xJnSwYyeloWSP1q06Ibg8qoU9TgZqLitQnlqdvxTOQm1OswRef0sjKZarKv X3ytVBWox7UaTplvfW0hBD6oMGQr1rrtg91eOFFaxp9iziwaEc0DYXkjlFjcL53nIsQu 9Yew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=rt0OznU+VEoi+q5tx7l5quRbiA9fsTNT1ImlZ1yJJOY=; b=LNt33pQRX0FARnS8ZOBaMkWt6sRxEx59RCWi6CRMD+nM11VIGk0zI3/06iya425Q9k dzXoqD8V35NfdFsxzdYsABGHbp+KvC3qTsu+058uW2kM9y+J7Nwhj2lHtxcym99UEKkz ZdRgU/rvxOToFlxQ1DexB+fWLJZpvTzA/VzeuEqXD6bO62C324wwU1jVZqNcx9fBOrkV LmcINHLMVkXgMeCd1xmud36RFqPPbPbr1FOCP/HF8RRr1OGLTO5nqRACOqENtCm4K+yM jot02Xk7dy0LYYChrDjO7lWcJElq7TE6DDkfP0JnEh3JIVJtUS89rD3tL1Xz0RaWbzRS Lz6w==
X-Gm-Message-State: AFeK/H11v5v2QEOloeU1izw1LtntzD2ixTSgeShXg7J0SyEYBZAUF8hz7bcRfbYI2G4eN55ssS2LBfRfGl1BaQ==
X-Received: by 10.55.182.193 with SMTP id g184mr22962895qkf.20.1491554045531; Fri, 07 Apr 2017 01:34:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.36.21 with HTTP; Fri, 7 Apr 2017 01:33:45 -0700 (PDT)
In-Reply-To: <094001d10451$cccec4e0$666c4ea0$@augustcellars.com>
References: <08eb01d103c8$3deade00$b9c09a00$@augustcellars.com> <561A2C9B.5060104@tzi.org> <094001d10451$cccec4e0$666c4ea0$@augustcellars.com>
From: Renzo Navas <renzoefra@gmail.com>
Date: Fri, 07 Apr 2017 10:33:45 +0200
Message-ID: <CAD2CPUGTgSiNBVkrvYLnk6=OmwNwQu-z=mSwo_r=j8RHVtX2VQ@mail.gmail.com>
To: cose <cose@ietf.org>
Cc: Carsten Bormann <cabo@tzi.org>, Jim Schaad <ietf@augustcellars.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/4zu4_na5spPgsyh64uwNDyPOckc>
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 08:34:09 -0000
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