From nobody Tue Jul 2 08:24:09 2019 Return-Path: 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 14A0D1202D0; Tue, 2 Jul 2019 08:24:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 OCoXOX0RQAnI; Tue, 2 Jul 2019 08:23:57 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2C7B1202AF; Tue, 2 Jul 2019 08:22:51 -0700 (PDT) Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 2E102380BE; Tue, 2 Jul 2019 11:20:57 -0400 (EDT) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 3BD50BE6; Tue, 2 Jul 2019 11:22:49 -0400 (EDT) From: Michael Richardson To: Derek Atkins , cose@ietf.org cc: "suit\@ietf.org" In-Reply-To: References: X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Subject: Re: [COSE] [Suit] draft-atkins-suit-cose-walnutdsa X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2019 15:24:01 -0000 --=-=-= Content-Type: text/plain Derek, looking at the IANA Considerations of draft-atkins-suit-cose-walnutdsa, it seems that you need a number in: 1) COSE Algorithms -- registry 2) COSE Key Types -- registry and several in the 3) COSE Key Type Parameters -- registry https://www.iana.org/assignments/cose/cose.xhtml#algorithms For the first, you can have: Integer values greater than 65535 Expert Review And the other two are Expert Review anyway, no specification required! You are even listed as one of the experts for COSE Key Types :-) {If my reading is correct, you can also use strings longer than 2-bytes without registration with IANA, but that has an operational (maintaining legacy code) and bytes-on-the-wire impact should you be allocated a shorter code later on} You could also ask for early allocation via the COSE WG, but that probably requires the document to be adopted first! That's what I would do: just ask for the values via Expert Review, and live for now, with the a five-bye (encoded) COSE Algorithm code, if your market need is urgent. Derek Atkins wrote: > We have customers who are looking to use this technology today, so we > would like to do it in a standard way that others could understand. > Personally, I'm fine with an Informational (instead of Standards-track) > publication if that would make people happier. Even so, the RFC Editor > would still require approval from this WG as it is within their (the > WG's) area. yes, if you went ISE, which would still take awhile. -- Michael Richardson , Sandelman Software Works -= IPv6 IoT consulting =- --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl0bdsgACgkQgItw+93Q 3WUTgAf9HYHgpEvhnT8vMBzP9YVoR44j0KFMH51o0vjCSKaCzGij0/z/xt0FnkeJ 9RzclmRFpMUEQcKJX5KCorFzgzujlcQyJfAEaCc91x17SoOjHRp/i2O9T/ya3X0S iCnL01ZoT8FiP5sR0dA3LBSiDx2EHrpa3AJjQUCcwYsMgRbZmNOm6kZuSCvcTfPh 4F0a1cJ9smMkWn6OgHYSLdTEjbxih+Ary9qi4StWZW2BnX50mKfP5+YmEAuuGbI7 dWJdC0sqvV0+7Z5UGG4nrQOxiUjL5MbnKETtgioXTOBRRC4DmWy5yqurC0LRaxA1 mbd0OavKyfHvopG630G960KWadNZ3g== =DtOF -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Jul 3 01:20:01 2019 Return-Path: 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 2F1B61207AD; Wed, 3 Jul 2019 01:19:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.198 X-Spam-Level: X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=unavailable 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 e5tujRalLeCV; Wed, 3 Jul 2019 01:19:31 -0700 (PDT) Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 220BD120784; Wed, 3 Jul 2019 01:19:31 -0700 (PDT) Received: from [192.168.217.110] (p548DC676.dip0.t-ipconnect.de [84.141.198.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 45dvCj0bQjzyXp; Wed, 3 Jul 2019 10:19:29 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mao-Original-Outgoing-Id: 583834767.013062-bdf4889171780bfa535d450990982355 Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Wed, 3 Jul 2019 10:19:28 +0200 Message-Id: To: Ace Wg , core , cose , cbor@ietf.org, t2trg@irtf.org X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [COSE] Constrained Node/Network Cluster @ IETF105: FINAL AGENDA X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jul 2019 08:19:40 -0000 From nobody Wed Jul 3 01:39:33 2019 Return-Path: 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 7E51B120691; Wed, 3 Jul 2019 01:39:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.197 X-Spam-Level: X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 NxBvF5fFf-i6; Wed, 3 Jul 2019 01:39:07 -0700 (PDT) Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87B851202E3; Wed, 3 Jul 2019 01:39:07 -0700 (PDT) Received: from [192.168.217.110] (p548DC676.dip0.t-ipconnect.de [84.141.198.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 45dvDl2NLzzyTX; Wed, 3 Jul 2019 10:20:23 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 X-Mao-Original-Outgoing-Id: 583834821.1630419-43cd4d155cf509da54f578df08c885de Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: Date: Wed, 3 Jul 2019 10:20:23 +0200 To: Ace Wg , core , cose , cbor@ietf.org, t2trg@irtf.org X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [COSE] Constrained Node/Network Cluster @ IETF105: FINAL AGENDA X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Jul 2019 08:39:11 -0000 Here is my usual eclectic condensed agenda based on the FINAL AGENDA for IETF105. Remember that, even though this will now go to the printers, there is still some potential for changes. Conflicts that meet the eye: COSE/TEEP stays; ROLL/SUIT/DINRG and 6TISCH/ACE are maybe slightly less annoying. LAKE and LOOPS have been disentangled, thank you. I have put in some side meetings, but that picture may still change (and I don't understand the timezone logic of that system, so it may be all wrong). All times are EDT (Eastern Daylight Time) =3D=3D UTC -4 hours. (Pure UTC times at https://datatracker.ietf.org/meeting/agenda-utc are useful for those who want to listen from remote.) Gr=C3=BC=C3=9Fe, Carsten FRIDAY, July 19, 2019 -- OMA/T2TRG Work Meeting - @ Ericsson Montreal Office (St-Laurent) SATURDAY/SUNDAY, July 20/21, 2019 -- Hackathon (including various interops) - Centre Ville SUNDAY, July 21, 2019 -- Sun 1700-1900 Welcome Reception - Place du Canada -- Sun 1800-2000 Hot RFC Lightning Talks - Viger MONDAY, July 22, 2019 1000-1200 Morning Session I Van Horne SEC acme Automated Certificate Management = Environment WG St-Catherine SEC *** teep Trusted Execution Environment = Provisioning WG Laurier TSV loops Local Optimizations on Path Segments BOF 1330-1530 Afternoon Session I St-Catherine INT *** 6lo IPv6 over Networks of = Resource-constrained Nodes WG Place du Canada SEC secdispatch Security Dispatch WG Van Horne TSV taps Transport Services WG 1550-1750 Afternoon Session II Laurier ART httpbis Hypertext Transfer Protocol WG St-Catherine OPS v6ops IPv6 Operations WG Van Horne SEC *** lake Lightweight Authenticated Key Exchange = BOF 1810-1910 Afternoon Session III Laurier ART dispatch Dispatch WG - Joint with ARTAREA TUESDAY, July 23, 2019 0830-0945 Side Meetings / Open Time C2 (21st Floor) IoT Onboarding and MUD (0900..1030?) Place du Canada IETF tdd Technology Deep Dive - How NICs Work = Today 1000-1200 Morning Session I St-Catherine ART *** cbor Concise Binary Object Representation = Maintenance and Extensions WG - 1000-1130 St-Catherine INT ipwave IP Wireless Access in Vehicular = Environments WG - 1130-1200 Notre Dame IRTF icnrg Information-Centric Networking Duluth OPS anima Autonomic Networking Integrated Model = and Approach WG Van Horne SEC cacao Collaborative Automated Course of Action = Operations for Cyber Security BOF Place du Canada TSV quic QUIC WG 1330-1500 Afternoon Session I Centre Ville OPS anima Autonomic Networking Integrated Model = and Approach WG 1520-1650 Afternoon Session II Duluth INT intarea Internet Area Working Group WG Place du Canada IRTF irtfopen IRTF Open Meeting Van Horne SEC oauth Web Authorization Protocol WG Collier CoRAL side meeting (1500..1700?) 1710-1810 Afternoon Session III Duluth ART *** core Constrained RESTful Environments WG Laurier INT 6man IPv6 Maintenance WG Place du Canada SEC tls Transport Layer Security WG WEDNESDAY, July 24, 2019 1000-1200 Morning Session I Van Horne IRTF*** dinrg Decentralized Internet Infrastructure St-Catherine RTG *** roll Routing Over Low power and Lossy = networks WG Viger SEC *** suit Software Updates for Internet of Things = WG Place du Canada TSV quic QUIC WG 1330-1530 Afternoon Session I Place du Canada GEN netrqmts IETF Meeting Network = Requirements BOF Laurier IRTF pearg Privacy Enhancements and Assessments = Research Group Viger IRTF*** t2trg Thing-to-Thing St-Catherine RTG bier Bit Indexed Explicit Replication WG Centre Ville RTG detnet Deterministic Networking WG 1550-1650 Afternoon Session II St-Catherine RTG babel Babel routing protocol WG Centre Ville RTG detnet Deterministic Networking WG Van Horne SEC *** rats Remote ATtestation ProcedureS WG THURSDAY, July 25, 2019 1000-1200 Morning Session I Duluth ART *** core Constrained RESTful Environments WG Place du Canada SEC tls Transport Layer Security WG Laurier TSV tsvwg Transport Area Working Group WG 1330-1530 Afternoon Session I Duluth INT dnssd Extensions for Scalable DNS Service = Discovery WG Viger IRTF coinrg Computing in the Network Proposed = Research Group Laurier IRTF panrg Path Aware Networking RG Place du Canada SEC saag Security Area Open Meeting 1550-1720 Afternoon Session II Laurier ART httpbis Hypertext Transfer Protocol WG Duluth INT 6man IPv6 Maintenance WG Place du Canada IRTF cfrg Crypto Forum Van Horne RTG rift Routing In Fat Trees WG St-Catherine SEC *** rats Remote ATtestation ProcedureS WG Centre Ville TSV tsvarea Transport Area Open Meeting 1740-1910 Afternoon Session III Duluth INT *** 6tisch IPv6 over the TSCH mode of IEEE = 802.15.4e WG Centre Ville SEC *** ace Authentication and Authorization for = Constrained Environments WG Place du Canada SEC mls Messaging Layer Security WG St-Catherine TSV rmcat RTP Media Congestion Avoidance = Techniques WG FRIDAY, July 26, 2019 1000-1200 Morning Session I Notre Dame ART ice Interactive Connectivity Establishment = WG Centre Ville INT *** lpwan IPv6 over Low Power Wide-Area Networks = WG Place du Canada IRTF maprg Measurement and Analysis for Protocols Laurier SEC mls Messaging Layer Security WG Duluth SEC oauth Web Authorization Protocol WG 1220-1350 Afternoon Session I Van Horne SEC *** cose CBOR Object Signing and Encryption WG St-Catherine SEC *** teep Trusted Execution Environment = Provisioning WG Place du Canada TSV tsvwg Transport Area Working Group WG From nobody Mon Jul 8 07:44:21 2019 Return-Path: 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 B53A81201EC for ; Mon, 8 Jul 2019 07:44:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.603 X-Spam-Level: X-Spam-Status: No, score=-0.603 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, PDS_NO_HELO_DNS=1.295, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ackl-io.20150623.gappssmtp.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 4Wz_hl0Lrkcu for ; Mon, 8 Jul 2019 07:44:18 -0700 (PDT) Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 D12771201E6 for ; Mon, 8 Jul 2019 07:44:17 -0700 (PDT) Received: by mail-wr1-x429.google.com with SMTP id g17so7294847wrr.5 for ; Mon, 08 Jul 2019 07:44:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackl-io.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=FPn3m4JJM+/WNgfGxH43u+NM9o6Y26vNZOGPMajsNv4=; b=qfnOHqX+LkG81AJRAzR/BnqEotdO/wmxg5DrRYjhZMBVzbry8AxB0mNMYPLmOtTxII PA6D6jN+Yq3v+4MMFjYsSEEUoAT5fXMmNaFR6Fyx7b5IMo7fiqGFQFSGVhxZudQA3fRm 8cDku034XmX7tXWrZFhWC+YGpKwsZPEbmKof/5zaJKsVrAERv/+bdgQ1gnHRTcIc5i13 7QAXxVGlzaANKLuSvQ5N+zo+e18RaGwHQlGgsEhTmOYRQHV4BuKjkE7ir+AunIZ5H04B XXKKcl6CnJP7q2c7gzBHG5xOXsRhJ804Z2YMZIbU869y2NypjzPjUMU8txOdOIfVtfhT /guw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=FPn3m4JJM+/WNgfGxH43u+NM9o6Y26vNZOGPMajsNv4=; b=k1e7UlIzypi/o4/9xTn+kmHgmFmCAZ8NmV2XzYmLAn0I8GHIT7quoaEXU3aBPbd1Gx fJlFPro5oairnBkoxyHQQedkEM9aoaWREoOBR4eD7/oVWJ789CK8c8BiAcROV3h0sLR8 Ec13/167rQrh7Y3XPu1NtuxRXvJkDEw0v+OHjKT7S9IQJw29ktFn+FL3QK0LsJTEoAas 8+mJsyMAZvl5bgK5RKZQC4wigsWa9zzhYefk1XQ+FOebblWsC3X5UMnSY8EG766JFQKP L0YKdxa7S/kb8wXRiTfF/DXga3yCAwLqyj4I+FvMP2SnKAOp4jl2AvdwFSgVcX26GYSy xv1A== X-Gm-Message-State: APjAAAX8fDRmzU4MfFJ9+wMilrV1fhmj1nJM4lZ+6GGZT705JvoQsbFO qKGDY0c4IHX+QoAGvGfyGoDvLbqW/ou+OvTRLSd0RoAN5x4= X-Google-Smtp-Source: APXvYqyJsaHcJSL+9JAYrkCvu7zU4ULCSvQwER86QA4ysWR4M5wGD7Pr4+hbtee5trBfkZDnBmw8yEn3ZBLco+jiKIs= X-Received: by 2002:adf:f6d2:: with SMTP id y18mr18898952wrp.102.1562597055987; Mon, 08 Jul 2019 07:44:15 -0700 (PDT) MIME-Version: 1.0 From: ivaylo petrov Date: Mon, 8 Jul 2019 16:43:50 +0200 Message-ID: To: cose Cc: cose-chairs@ietf.org Content-Type: multipart/alternative; boundary="000000000000731664058d2c7af6" Archived-At: Subject: [COSE] Call for agenda items IETF 105 X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jul 2019 14:44:20 -0000 --000000000000731664058d2c7af6 Content-Type: text/plain; charset="UTF-8" Dear all, The final agenda for IETF 105 has been published at: https://datatracker.ietf.org/meeting/105/agenda.html and as you could see there, COSE will be meeting on Friday July 26th from 12:20 to 13:50, during Afternoon session I in room Van Horne. If you'd like a slot to present a draft, please send a request to the chairs (cc) by Friday July 12th. Please provide the following information: Draft name Presenter name Remote vs. Local presentation Expected duration Objective of the discussion Any WG draft not being discussed/presented needs a status update sent to the list before the meeting as well. As always - we would appreciate your help in taking notes and jabber, so please do volunteer! Looking forward to seeing you all in Montreal, Best regards, - Matthew and Ivaylo COSE Chairs --000000000000731664058d2c7af6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Dear all,

The final agenda for IETF 105 ha= s been published at: https://datatracker.ietf.org/meeting/105/agenda.html and as = you could see there, COSE=C2=A0will be meeting on Friday July 26th from 12:= 20 to 13:50, during Afternoon session I in room Van Horne.=C2=A0

If = you'd like a slot to present a draft, please send a request to the chai= rs (cc) by Friday July 12th.=C2=A0Please provide the following information:=

Draft name
Presenter name
Remote vs. Local presentation
Ex= pected duration
Objective of the discussion

Any WG draft not bein= g discussed/presented needs a status update sent to the list before the mee= ting as well.

As always - we would appreciate your help in taking no= tes and jabber, so please do volunteer!

Looking forward to seeing yo= u all in Montreal,

Best regards,=C2=A0
- Matthew and Ivaylo
CO= SE Chairs

=
--000000000000731664058d2c7af6-- From nobody Mon Jul 8 12:51:44 2019 Return-Path: X-Original-To: cose@ietf.org Delivered-To: cose@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D7C361200B2; Mon, 8 Jul 2019 12:51:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: cose@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.98.3 Auto-Submitted: auto-generated Precedence: bulk Reply-To: cose@ietf.org Message-ID: <156261549484.745.3515846621909370100@ietfa.amsl.com> Date: Mon, 08 Jul 2019 12:51:34 -0700 Archived-At: Subject: [COSE] I-D Action: draft-ietf-cose-webauthn-algorithms-01.txt X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Jul 2019 19:51:36 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the CBOR Object Signing and Encryption WG of the IETF. Title : COSE and JOSE Registrations for WebAuthn Algorithms Author : Michael B. Jones Filename : draft-ietf-cose-webauthn-algorithms-01.txt Pages : 10 Date : 2019-07-08 Abstract: The W3C Web Authentication (WebAuthn) specification and the FIDO2 Client to Authenticator Protocol (CTAP) specification use COSE algorithm identifiers. This specification registers algorithms in the IANA "COSE Algorithms" registry that are used by WebAuthn and CTAP implementations that are not already registered. Also, they are registered in the IANA "JSON Web Signature and Encryption Algorithms" registry, when not already registered there. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-cose-webauthn-algorithms/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-cose-webauthn-algorithms-01 https://datatracker.ietf.org/doc/html/draft-ietf-cose-webauthn-algorithms-01 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-cose-webauthn-algorithms-01 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Jul 8 18:00:51 2019 Return-Path: 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 D3E5E12024E for ; Mon, 8 Jul 2019 18:00:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.74 X-Spam-Level: X-Spam-Status: No, score=-1.74 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 s1CdZjFgh2P3 for ; Mon, 8 Jul 2019 18:00:46 -0700 (PDT) Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-bl2nam06on0731.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe55::731]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABBD3120090 for ; Mon, 8 Jul 2019 18:00:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=A02sO2Qr8LNwQjioZ159tSkTJRKNcva7pKMPFFavcDmAP4cKJGIDcLJKtb6U8G1GsNs4LhQVxhAI2KACrfn8p1SI370YWkzTGHc2Y5uqaABHbNSKZEuauk/SiCweec2HV6JMHI4h/DBgqcLwcBCAdIS9Y2Ik9RCvQku4y/ArfPSS5ztQs3nrTJzm0ssNAy5wkjD66pojV/Nh4yyyq0aDFU2zBg3/LGrah+Ig5NJ6/B8c1+GBLO5Q2Q+xZsdgEpmvVYXyBAvmMe+vrbbzHNOgetK3b8YeDgn7C0/J2x8VLw/DlY/EFvu+PRsW41jGCpr5G6cfkm+Air6icEwVT1Sl/g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vlxaupeb6fACrCpETJZjC5jh1T7TdhDjL+4+cbYTRvg=; b=JUOMYyh7aFdVKOAGJzzSet1UkmlQmL038KkcwZ5MxmI0SiSsfhILqqcDOI2nUaM04YYFKkEi4L0p+ac2UrnNuwHVkAL8qRMxkdhdUSl1Irh+AnDY2xhyeNWyYLE7+uguvykHTJICSQlz4yw0yd7bPLu7Fxfn+s0wI+wbpw2EGR5YRu0dsD3Xs6l6IWyRs6yqVkU+eFtqKoLLmhg/Hi8QA6tE8t+YbuTe044nkGnD3pklcc6isZxbyuiEHKYTZJz3N+AngElshETlTa3OO+wkPMP7IwpWkfM/IFsaIcfIQC1O1KFTQ/0VajeyzNctAxTVdIaVxdDLMUlGzn0+apCWHA== ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=microsoft.com;dmarc=pass action=none header.from=microsoft.com;dkim=pass header.d=microsoft.com;arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vlxaupeb6fACrCpETJZjC5jh1T7TdhDjL+4+cbYTRvg=; b=cRRk3sH++pvhRO1iXfDWb7gUbEwOaTgFE0D9QjlkH+R49iU+RFvQDjFl+SbFClqbTrLxWorkfH1++3/dea0gfWBw+7CRCBoIKT+jDxG3CiK7FMR6zeZRiVWryeKadKxXfYdAewcHbGPpLN2mcgCHLfGPg+utkoD1LnMLWqCkhvw= Received: from SN6PR00MB0301.namprd00.prod.outlook.com (52.132.117.155) by SN6PR00MB0335.namprd00.prod.outlook.com (52.132.118.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2106.0; Tue, 9 Jul 2019 01:00:43 +0000 Received: from SN6PR00MB0301.namprd00.prod.outlook.com ([fe80::35ef:5419:5d79:8d42]) by SN6PR00MB0301.namprd00.prod.outlook.com ([fe80::35ef:5419:5d79:8d42%3]) with mapi id 15.20.2106.000; Tue, 9 Jul 2019 01:00:43 +0000 From: Mike Jones To: "cose@ietf.org" Thread-Topic: Refinements to COSE and JOSE Registrations for WebAuthn Algorithms Thread-Index: AdU17zg5W2KLcrvbQTWqKrR8Ec2fqA== Date: Tue, 9 Jul 2019 01:00:43 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=ad36b730-8142-4171-bc83-0000f6ed6c9f; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2019-07-09T00:42:41-0800; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michael.Jones@microsoft.com; x-originating-ip: [2001:4898:80e8:3:a253:b1b0:93bf:f325] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 5bd11579-4a23-498e-9acd-08d70408de5a x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(4618075)(2017052603328)(7193020); SRVR:SN6PR00MB0335; x-ms-traffictypediagnostic: SN6PR00MB0335: x-ms-exchange-purlcount: 4 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8273; x-forefront-prvs: 0093C80C01 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(39860400002)(136003)(366004)(396003)(376002)(209900001)(189003)(199004)(68736007)(10090500001)(8990500004)(606006)(14454004)(966005)(5660300002)(7696005)(186003)(6506007)(2351001)(99286004)(102836004)(71200400001)(6116002)(6916009)(790700001)(8676002)(81156014)(53376002)(71190400001)(22452003)(86362001)(316002)(8936002)(1730700003)(72206003)(256004)(14444005)(66446008)(7736002)(476003)(73956011)(64756008)(66556008)(66476007)(76116006)(2906002)(486006)(74316002)(66946007)(21615005)(5640700003)(55016002)(6306002)(54896002)(236005)(25786009)(9686003)(33656002)(53936002)(6436002)(10290500003)(81166006)(52536014)(46003)(4744005)(2501003)(478600001)(6606295002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR00MB0335; H:SN6PR00MB0301.namprd00.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: G/kWiRCqZrkzrl45CP6eNCs+KQZ+aGMNqubn1Pzg2KH6Hs9F0fCmsfTgnuyxQmOEyYXrQd11rLPaTNfUX2iRnECgixi2gIqdRmLag5c1iWK0XsgGt8KiH/4PBqFRcNMRTnfyQy5A8LpJTo8qXNsK+Bule1ohXdu2IGYqhPhfwCAbO2ERzhS14vbgE+4emZN8SxhgcBiFSQGTOX7UP4c1f7YC9EiPgESfuAIK6MHhvihZYT/MebVqfnITk12xw7WrjOF1Jnd+OC8qX+5AeXoHL6TlTN6IddbdYfTz7B2mSRginS6V+Zd6VsiuTwQNCf2fI7R/Mpj+rfo0m98Z1BuQ8cZkthbHVGCbHDyqzJa1l1bDjAxS+Xs6EPmhiB6dwZ4E5k8DRj5iuq2sZX7cxQPkX8jVbIyEB0Z1H9MXTrude5Q= x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_SN6PR00MB0301C86E256CD5DB59E9B192F5F10SN6PR00MB0301namp_" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-Network-Message-Id: 5bd11579-4a23-498e-9acd-08d70408de5a X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2019 01:00:43.1354 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: mbj@microsoft.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR00MB0335 Archived-At: Subject: [COSE] Refinements to COSE and JOSE Registrations for WebAuthn Algorithms X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Jul 2019 01:00:50 -0000 --_000_SN6PR00MB0301C86E256CD5DB59E9B192F5F10SN6PR00MB0301namp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable The "COSE and JOSE Registrations for WebAuthn Algorithms" specification has= been updated to address feedback received since working group adoption. T= he one breaking change is changing the secp256k1 curve identifier for JOSE = from "P-256K" to "secp256k1", for reasons described by John Mattsson. The = draft now also specifies that the SHA-256 hash function is to be used with = "ES256K" signatures - a clarification due to Matt Palmer. The specification is available at: * https://tools.ietf.org/html/draft-ietf-cose-webauthn-algorithms-01 An HTML-formatted version is also available at: * http://self-issued.info/docs/draft-ietf-cose-webauthn-algorithms-01.h= tml -- Mike P.S. This notice was also posted at http://self-issued.info/?p=3D1986 and = as @selfissued. --_000_SN6PR00MB0301C86E256CD5DB59E9B192F5F10SN6PR00MB0301namp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

The “COSE and JOSE Registrations for WebAuthn = Algorithms” specification has been updated to address feedback receiv= ed since working group adoption.  The one breaking change is changing = the secp256k1 curve identifier for JOSE from “P-256K” to “secp256k1”, for reasons described by John Mattsson.  The draft now al= so specifies that the SHA-256 hash function is to be used with “ES256K” signatu= res - a clarification due to Matt Palmer.

 

The specification is available at:

 

An HTML-formatted version is also available at:=

 

        &nbs= p;            &= nbsp;           &nbs= p;            &= nbsp;           &nbs= p;     -- Mike

 

P.S.  This notice was also posted at http://self-issued.info/?p=3D1986 and as @selfissued.

 

--_000_SN6PR00MB0301C86E256CD5DB59E9B192F5F10SN6PR00MB0301namp_-- From nobody Mon Jul 15 17:10:13 2019 Return-Path: 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 4737012014A for ; Mon, 15 Jul 2019 17:10:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 QRYYhxLSJCO5 for ; Mon, 15 Jul 2019 17:10:09 -0700 (PDT) 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 9D77F120148 for ; Mon, 15 Jul 2019 17:10:08 -0700 (PDT) Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 15 Jul 2019 17:10:01 -0700 From: Jim Schaad To: 'ivaylo petrov' CC: References: In-Reply-To: Date: Mon, 15 Jul 2019 17:10:01 -0700 Message-ID: <01c901d53b6a$d18eda70$74ac8f50$@augustcellars.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01CA_01D53B30.25300270" X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AQJneSEMY9wkQIgCpAGCd7m4SP3hpqWn3ipQ X-Originating-IP: [73.180.8.170] Archived-At: Subject: Re: [COSE] Comments on the draft-ietf-cose-hash-algs X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2019 00:10:11 -0000 ------=_NextPart_000_01CA_01D53B30.25300270 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ivaylo, =20 I can see why you have that comment. I have modified the document to = read =20 The standard "Collision Attack" is one where an attacker can = find two different messages that have the same hash value. If a collision attack exists which is insufficiently difficult, = then the function SHOULD NOT be used for a cryptographic purpose. =20 I briefly thought about talking about what difficult means, but I = don=E2=80=99t know of a really good way to do that. =20 =20 Jim =20 =20 From: ivaylo petrov =20 Sent: Monday, July 15, 2019 12:44 AM To: Jim Schaad Subject: Comments on the draft-ietf-cose-hash-algs =20 Hi, Jim, =20 The new version of the draft seems rather good to me. I have a comment = about a statement in section 2. =20 > The standard "Collision Attack" is one where an attacker can find two = different messages that=20 > have the same hash value. If a collision attack exists, then the = function SHOULD NOT be used for a cryptographic purpose. I might be misinterpreting the therm cryptographic purposes, but it = seems to me that this phrasing is not precise enough as every hash = function can be brute-forced to find two different inputs that yield the = same output value. The real issue is when this is not as difficult as = expected. Cheers, Ivaylo =09 =09 =20 ------=_NextPart_000_01CA_01D53B30.25300270 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Ivaylo,

 

I can see = why you have that comment.=C2=A0=C2=A0 I have modified the document to = read

 

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The = standard "Collision Attack" is one where an attacker can find = two different messages that have the same hash value.

=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 If a = collision attack exists which is insufficiently difficult, then the = function SHOULD NOT be used for a cryptographic = purpose.

 

I briefly thought about talking about what difficult = means, but I don=E2=80=99t know of a really good way to do that.=C2=A0 =

 

Jim

 

 

From: = ivaylo petrov <ivaylo@ackl.io>
Sent: Monday, July 15, = 2019 12:44 AM
To: Jim Schaad = <ietf@augustcellars.com>
Subject: Comments on the = draft-ietf-cose-hash-algs

 

Hi, = Jim,

 

The new version = of the draft seems rather good to me. I have a comment about a statement = in section 2.

 

> The standard "Collision Attack" = is one where an attacker can find two different messages that
> = have the same hash value. If a collision attack exists, then the = function SHOULD NOT be used for a cryptographic = purpose.


I might be misinterpreting the therm = cryptographic purposes, but it seems to me that this phrasing is not = precise enough as every hash function can be brute-forced to find two = different inputs that yield the same output value. The real issue is = when this is not as difficult as = expected.

Cheers,
Ivaylo

 

------=_NextPart_000_01CA_01D53B30.25300270-- From nobody Fri Jul 19 10:42:38 2019 Return-Path: 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 2D3E2120128 for ; Fri, 19 Jul 2019 10:42:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=myidemia.onmicrosoft.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 d2y9jrRqFgZ9 for ; Fri, 19 Jul 2019 10:42:34 -0700 (PDT) Received: from mx08-0018b601.pphosted.com (mx08-0018b601.pphosted.com [91.207.212.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C65F1200BA for ; Fri, 19 Jul 2019 10:42:34 -0700 (PDT) Received: from pps.filterd (m0136512.ppops.net [127.0.0.1]) by mx08-0018b601.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x6JHfY1Y032381 for ; Fri, 19 Jul 2019 17:42:31 GMT Received: from eur01-ve1-obe.outbound.protection.outlook.com (mail-ve1eur01lp2056.outbound.protection.outlook.com [104.47.1.56]) by mx08-0018b601.pphosted.com with ESMTP id 2tt56hwa3q-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for ; Fri, 19 Jul 2019 17:42:31 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=i8g/PyId9C908kq4CEIp6aeysQjD0C5WaG/tk+V1tcRGmqyWDPn9QAqul62oKmIQ4LvCxGeiKwFY+mgF+fKeowTkjCa6TIEb7Zr7s2HUxbtX0Pwxt3ghrFiRmtRNa1AqnRkanTLqFrQwASpBRL+906faCARsky3n4a66qO8cO5Xvo+dEcNXnKkc2M10d/UJZHPT/hCFp9wC+lGBjmfxXzuDztjgNjdfOjpqjcLZIME/puaOHN1nskLM3LHdzKLXGEZDf7WPy7PeLltt+jC6xoKzWdpgTa1VKRTtQ80ezx5y7Nbq0RedRQ1EVMPIa5kZ5N3TgsFrjhbQkF5y7QjEBaA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KZLLQ+ocNjOTP6/uxZd1QtN1MaH4U0RKbtfDUKaoOhY=; b=SKy9JWzz5TKhtESnYOewRYvfYUKJTGU0456MJ78HUM5V42MZd+CxzIiAXJMZRzFDAEsGCC7SDIoEz7BzXmt2+5MGy/9rLQSa9SrNFq0qh8oFumw1MwhrNz/9Q/SdcqmhsLy8PL06cSbmsKFvyJOyQVS7SrNRUFxztZE75v4Uq7g/6dw29JTJrF8HUcJwWXtUNQ4a1C0YOE4ohDAU3feScwmsAjeyHuwNt6j9BDMs/GfSo5/1wgFuMtHw0SRDF9/k8bnUDiyYIQqvdr/U+9hJm9+EJ3fqmHz8UH/D6rDfzaBBbYgo+bLdkocC3hwDtRlYFnXQ0OPsSAOPXpc3/yNXOw== ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=idemia.com;dmarc=pass action=none header.from=idemia.com;dkim=pass header.d=idemia.com;arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=myidemia.onmicrosoft.com; s=selector2-myidemia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=KZLLQ+ocNjOTP6/uxZd1QtN1MaH4U0RKbtfDUKaoOhY=; b=AgopbFokbUtcFBeXjdtkHveIqZLOARsu19s14OM2ZGDCtD4lwXR5py20ckaN8iES2kk6k54Vx5SvPUUqmx220+hgqDA97kQ3SptFzOPyoqqn/qC0xIGhoVFq226ncyb8TN2ThTFW9EpGHxJ7N7nQYcwVaUPmM7vqo38q5ggdDUc= Received: from VI1P189MB0319.EURP189.PROD.OUTLOOK.COM (10.165.195.140) by VI1P189MB0382.EURP189.PROD.OUTLOOK.COM (10.165.195.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2094.14; Fri, 19 Jul 2019 17:42:29 +0000 Received: from VI1P189MB0319.EURP189.PROD.OUTLOOK.COM ([fe80::8520:9acb:bfec:e6cf]) by VI1P189MB0319.EURP189.PROD.OUTLOOK.COM ([fe80::8520:9acb:bfec:e6cf%6]) with mapi id 15.20.2094.013; Fri, 19 Jul 2019 17:42:29 +0000 From: DESPERRIER Jean-Marc To: "cose@ietf.org" Thread-Topic: [COSE] I-D Action: draft-ietf-cose-x509-02.txt Thread-Index: AQHVJ3Z32Dm2xIFTEk6GtpEoh2xhKqbSXzTA Date: Fri, 19 Jul 2019 17:42:29 +0000 Message-ID: References: <156104177627.2962.16582348312117462911@ietfa.amsl.com> In-Reply-To: <156104177627.2962.16582348312117462911@ietfa.amsl.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [165.225.76.89] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 56681ce0-6e5a-4557-0afd-08d70c7078cb x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:VI1P189MB0382; x-ms-traffictypediagnostic: VI1P189MB0382: x-ms-exchange-purlcount: 6 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:3276; x-forefront-prvs: 01039C93E4 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(346002)(136003)(366004)(396003)(376002)(39860400002)(199004)(189003)(6246003)(33656002)(86362001)(486006)(68736007)(66574012)(25786009)(66066001)(6116002)(3846002)(5640700003)(8936002)(6436002)(229853002)(71190400001)(71200400001)(2906002)(53936002)(6916009)(2501003)(9686003)(6306002)(256004)(55016002)(14444005)(478600001)(186003)(74316002)(14454004)(66946007)(8676002)(76116006)(7696005)(7736002)(305945005)(66476007)(99286004)(476003)(446003)(11346002)(76176011)(2351001)(52536014)(55236004)(6506007)(5660300002)(316002)(966005)(66446008)(64756008)(66556008)(26005)(1730700003)(81156014)(81166006)(102836004); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1P189MB0382; H:VI1P189MB0319.EURP189.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: idemia.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: 0bJU6Fv6cioMZRwWEZYF230bcLPJIVw5Msh7nU1mfO8beepkgyHA8YY3W2wJOXH7iFqFcoqvEXnTGRferdJbJHZ+yqfH/07TqwjlrvVfTBRvvMsi5e/MUTSZKgttTl6yJGLnEYratoCQGgIBsFiTh8uRI+Uv2YI/56G/padLOEP9svpiZCGUIJ/bLJV4j1Zz/mORmj2JdSIUi3OCnOV4VBfnn7/x+oV7wClR5Y2g/TEmI987Us+bGm263I05Req8H1ldeBvXOfxYQzdTaoUifqz+o/+r+S+2LeZdmJxX6F0n/iaOdk1XaTbGb36TjH3spqsa1NjH9nqEz7sOfVM242R6G/Of5If8IPEtUteJpKL/kYkixOts4QaBVBvH1vTJ0kMAMpc11fD8HUoDHXLfHo/npIfkMJPgGDtCOR/jFKw= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: idemia.com X-MS-Exchange-CrossTenant-Network-Message-Id: 56681ce0-6e5a-4557-0afd-08d70c7078cb X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2019 17:42:29.7408 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 7694d41c-5504-43d9-9e40-cb254ad755ec X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: g578695@mph.morpho.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1P189MB0382 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9323 signatures=668688 X-Proofpoint-Spam-Details: rule=outbound_idemia_notspam policy=outbound_idemia score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1907190189 Archived-At: Subject: Re: [COSE] I-D Action: draft-ietf-cose-x509-02.txt X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2019 17:42:37 -0000 Hi,=20 I unfortunately didn't find the time to engage the group further about this= document after my comments at the start of the year. The ISO SC17/WG10 will run a test event in the middle of august for the cur= rent specification of the ISO 18013-5 draft This draft integrates a COSE_Sign1 element using a x5chain header to refere= nce a X509 certificate. It would be very helpful if we could have a temporarily register value to u= se for that, instead of the TBD3 that's currently in table 1. If it can't be done in time, we'll have to use some value reserved for priv= ate use, as per the COSE Header Parameters register, so below -65536, but i= t will be cool if we can do better. Unfortunately we have very little time available, if we want to give suffic= iently in advance the information to implementers about what they should us= e. Best regards, Jean-Marc -----Message d'origine----- De=A0: COSE De la part de internet-drafts@ietf.org Envoy=E9=A0: jeudi 20 juin 2019 16:43 =C0=A0: i-d-announce@ietf.org Cc=A0: cose@ietf.org Objet=A0: [COSE] I-D Action: draft-ietf-cose-x509-02.txt A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the CBOR Object Signing and Encryption WG of t= he IETF. Title : CBOR Object Signing and Encryption (COSE): Header= s for carrying and referencing X.509 certificates Author : Jim Schaad Filename : draft-ietf-cose-x509-02.txt Pages : 10 Date : 2019-06-20 Abstract: The CBOR Signing And Encrypted Message (COSE) structure uses references to keys in general. For some algorithms, additional properties are defined which carry parts of keys as needed. The COSE Key structure is used for transporting keys outside of COSE messages. This document extends the way that keys can be identified and transported by providing attributes that refer to or contain X.509 certificates. The IETF datatracker status page for this draft is: https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf.org= _doc_draft-2Dietf-2Dcose-2Dx509_&d=3DDwICAg&c=3DznOEDNGT1crOtqImlna_pg&r=3D= PnzBO7W9avH7TwSoGwQ1PkCbALuNs4S26POtm0vaNjs&m=3D0IVrrRQgxotsWeYuLusfPGh5-lp= r5atX6jkVWxX5B84&s=3DFx_c7_IQIjKgwgegOeTk_fUtQyjNyjHFMAvQZALGxCw&e=3D=20 There are also htmlized versions available at: https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_= draft-2Dietf-2Dcose-2Dx509-2D02&d=3DDwICAg&c=3DznOEDNGT1crOtqImlna_pg&r=3DP= nzBO7W9avH7TwSoGwQ1PkCbALuNs4S26POtm0vaNjs&m=3D0IVrrRQgxotsWeYuLusfPGh5-lpr= 5atX6jkVWxX5B84&s=3D4K3pQop6df6Vz3JsV_3GVSB80-oUhu_AJwuQMMr2khM&e=3D https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__datatracker.ietf.org= _doc_html_draft-2Dietf-2Dcose-2Dx509-2D02&d=3DDwICAg&c=3DznOEDNGT1crOtqImln= a_pg&r=3DPnzBO7W9avH7TwSoGwQ1PkCbALuNs4S26POtm0vaNjs&m=3D0IVrrRQgxotsWeYuLu= sfPGh5-lpr5atX6jkVWxX5B84&s=3D60Iddoll2X79MSc3Hg_umNUGPUIexHbLjBCb-0WrNY4&e= =3D=20 A diff from the previous version is available at: https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_rfcdiff= -3Furl2-3Ddraft-2Dietf-2Dcose-2Dx509-2D02&d=3DDwICAg&c=3DznOEDNGT1crOtqImln= a_pg&r=3DPnzBO7W9avH7TwSoGwQ1PkCbALuNs4S26POtm0vaNjs&m=3D0IVrrRQgxotsWeYuLu= sfPGh5-lpr5atX6jkVWxX5B84&s=3DSxmgZ7t2BnYZ9jUQgHUMQNJ28lD4TUzpKoUELZqtqfo&e= =3D=20 Please note that it may take a couple of minutes from the time of submissio= n until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: https://urldefense.proofpoint.com/v2/url?u=3Dftp-3A__ftp.ietf.org_internet-= 2Ddrafts_&d=3DDwICAg&c=3DznOEDNGT1crOtqImlna_pg&r=3DPnzBO7W9avH7TwSoGwQ1PkC= bALuNs4S26POtm0vaNjs&m=3D0IVrrRQgxotsWeYuLusfPGh5-lpr5atX6jkVWxX5B84&s=3DTI= MdjEqpl-6RjI8hPHFK4RG3FDTMrSsIYbQ6A4I0hM4&e=3D=20 _______________________________________________ COSE mailing list COSE@ietf.org https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__www.ietf.org_mailman= _listinfo_cose&d=3DDwICAg&c=3DznOEDNGT1crOtqImlna_pg&r=3DPnzBO7W9avH7TwSoGw= Q1PkCbALuNs4S26POtm0vaNjs&m=3D0IVrrRQgxotsWeYuLusfPGh5-lpr5atX6jkVWxX5B84&s= =3Du3h7Ue9WBz8NToDxSg-yzjYjkUgq2IitoNV6ceGSoeE&e=3D=20 From nobody Mon Jul 29 07:51:27 2019 Return-Path: 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 8C6D8120127; Mon, 29 Jul 2019 07:51:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 po9bw5r7juLN; Mon, 29 Jul 2019 07:51:24 -0700 (PDT) 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 A2726120136; Mon, 29 Jul 2019 07:51:23 -0700 (PDT) Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 29 Jul 2019 07:51:17 -0700 From: Jim Schaad To: CC: , 'IANA' Date: Mon, 29 Jul 2019 07:51:15 -0700 Message-ID: <005001d5461d$149a4c70$3dcee550$@augustcellars.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AdVGG7/zFE5AfdzPQJi7oNvF59n5nQ== X-Originating-IP: [73.180.8.170] Archived-At: Subject: [COSE] Early Code Point Assignments X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2019 14:51:26 -0000 Following the meeting in Montreal where I asked for the ability to do early point assignment for documents in the working group and got permission, these are the code points that I am assigning. I am only assigning points that I know people are asking for now, some points will be setup later. For draft-ietf-cose-x509 (https://tools.ietf.org/html/draft-ietf-cose-x509): Table COSE Header Parameters https://www.iana.org/assignments/cose/cose.xhtml#header-parameters Name Value x5bag 32 x5chain 33 x5t 34 x5u 35 For draft-ietf-cose-hash-algs (https://tools.ietf.org/html/draft-ietf-cose-hash-algs): Table COSE Algorithms https://www.iana.org/assignments/cose/cose.xhtml#algorithms Name Value SHA-1 -14 SHA-256/64 -15 SHA-256 -16 SHA-384 -43 SHA-512 -44 SHA-512/256 -17 SHAKE128 -18 SHAKE256 -45 Jim From nobody Mon Jul 29 08:21:52 2019 Return-Path: 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 4DE49120144 for ; Mon, 29 Jul 2019 08:21:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.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 vfPBhwn4b0eK for ; Mon, 29 Jul 2019 08:21:48 -0700 (PDT) Received: from mail-io1-xd2b.google.com (mail-io1-xd2b.google.com [IPv6:2607:f8b0:4864:20::d2b]) (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 9EFDE120124 for ; Mon, 29 Jul 2019 08:21:48 -0700 (PDT) Received: by mail-io1-xd2b.google.com with SMTP id f4so120885089ioh.6 for ; Mon, 29 Jul 2019 08:21:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:to:from:subject:openpgp:autocrypt:message-id:date:user-agent :mime-version:content-language:content-transfer-encoding; bh=Omcrh2/Lvm3g6VhPJqqmd/c8eY/SnxsMZE0ufteDT1o=; b=ScimT3EOxOx1IOblsqpS9zdMSQAEvGZN9+M94jVMemiZUArqtBa6WkDgDDkdBN42mB Mj78LhI+WDbZT2+VUEpgr/shtFD0Z4AdQlj52h8iPJqFaFVIxe1+9+qDK1xf3PzXTDux 0fa68OHqhWsJnXebk1sEpHyFluiZ+pUgQcYKWGUeBeEqX+sUBYeEQTsCDGDY4fd0xgr4 VkRVslg3wtpogyFV0Hglr5+8yAhFE/EwRawIZMtPxlvJ4C7ylYmK8FbfDKeHUM4yK6Mr foXqHnWqya9+9snOWl3/DH49nvkwM04uIvYVC6OGcYoT3lYpN1ZQUgaAIvLlHHH2AHmf 2aOA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:to:from:subject:openpgp:autocrypt :message-id:date:user-agent:mime-version:content-language :content-transfer-encoding; bh=Omcrh2/Lvm3g6VhPJqqmd/c8eY/SnxsMZE0ufteDT1o=; b=mbXyn87IcVtVqHB46dfsPuVf1kw9mZ8JFRzQ1CB+Et0qPKO44tl+w/WxXvVrqQ0qDX pGnkyYMRbnLa4HireSb5kVpljoxz4F9OwWYYlGozNKgk/rFIPwLWcoiVxw1MJ92PT5HC FnB8YnlanaCWq89kipSUG/V4igYAJ+8wwTbYfe9UEk2iQNSe6SnYficyRSLVRuaVL89J RmQiDgwvKYYqiD4shJt7JurQd3XJ3B/bYzzu4qo1Q3soB2NOeUhn4dhLo/h/2YZkwheD v6DhBkGiU5P+owy0cP0ktvyfFqdF8wTgEdjfO4oYrQ7WCmPP2T7IIjd/Xb/JUlNILQ7Q X6Zw== X-Gm-Message-State: APjAAAW6Wv1umE4CFJJRIrx3wmPdluFXn/Btxs+031MR8c+1H4Pcktn9 NChAGi64Nd7Drf68k2oL1ICvlVzhhBU= X-Google-Smtp-Source: APXvYqxA5pMKJDfECA/55fgFKxfpZoZF7E5noFtiWngDpiXfnOZS0WFbjYnLjsiW+02Jw+3klzHmbQ== X-Received: by 2002:a5e:8e42:: with SMTP id r2mr19900633ioo.305.1564413707580; Mon, 29 Jul 2019 08:21:47 -0700 (PDT) Received: from mmiller-44677.local (c-24-8-164-51.hsd1.co.comcast.net. [24.8.164.51]) by smtp.gmail.com with ESMTPSA id z26sm61431117ioi.85.2019.07.29.08.21.46 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 29 Jul 2019 08:21:47 -0700 (PDT) Sender: Matthew Miller To: cose From: "Matthew A. Miller" Openpgp: preference=signencrypt Autocrypt: addr=linuxwolf+ietf@outer-planes.net; prefer-encrypt=mutual; keydata= mQENBFJoAooBCADQmEtpbpY/4wTeKgZIuyG7HkxIFgiUeqOvtiBKj/pCA73d7Q5hCvQdGcKJ 6uZsYz3Il9oKoKFxVt90iEXspbE39g6ek19e6RsB4j0Q10l4QvH+EqeD760gs0H2yf/eYj9i uk9/VY6axdQlPsmid1zoQgCNjSM7X4/K26WGMs03sbXJpKdoonelzIlJSNfzi0q546iplo72 D2cCm9BriMkQvcGnsm4B9eBIBn3GKmVx1tsmPNeNTyun2DvaLnrYxbA0Ivo1DzZReds9NZ25 uROI/+b+lcg9/kmHzhK+q8NMQCFWmqpS/lZRKxVBSijKGpGr5h8VLVf5iURHtwG+B/QxABEB AAG0M01hdHRoZXcgQS4gTWlsbGVyIDxsaW51eHdvbGYraWV0ZkBvdXRlci1wbGFuZXMubmV0 PokBPQQTAQoAJwUCWKsJ1AIbAwUJC8ckMQULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRDs 9HJOEJ4Fu1iBCADAcW06d/7GTlBjTlYuMGgjzDBoWeQ9/zxgMnSrgNb6yO7wHzE65CeFs6OI 6LQ4A34CNM3hhcWDIzlqrV25fVyy7qCh6bCNMs1pOT63+Od4kcjHtUnGGTONT5fXSGY7mCtl XJFjb3TwyLUZXQCifhCIaUdF/4SVoGk96W9ssbDKN+5xq7B7gyVkwB0WM67zxt/kC6TPcXXL 5m7jsNRpRmFQqOlIF+HrQAcSr1lKRWgetb1VHfXCgcmDaTKn1QC7s0Ml+27dc0SoIkBI8cnv inJ4oFYWrvnTlOvv+v8AFXZnPrxZ/JYvnVD/y5PX7v08Z8RFXm1AmVxIWjXPI6TySkGvuQEN BFJoAooBCADA/ruHwYlQ7pdjJY6twkZcMmedkQNL6r5tNBeQkwVrvitUjHTKKipjxB2kEkUZ oxPgMI1h7/enDrVlMMMqq6RIJ86H+yx13zNIZNBlJfmVHgHj7TT8spa6A/qIccdiIRNsFVvl vFxpH8sTjVbHfPYexbdOR5kHpZWTzYxNyVLXMK5jen0B4K+vjbgFJAvsoLfzLZ5Bz3kb6dpu xUNzqhDyhk5/UPaCIFvZWBtiRKmkqPwEq8G2aMJq5Z4Sr8CRkpoMB25rxCPS8R+ByiHxpq+U 8mKuqPVg1LJzcA7hHmms8aBN6lxSlbyKnzEg8AWgld+6+xlJXu5U/fqDAClTj5mfABEBAAGJ ATwEGAEKACYCGwwWIQQx11iN7JBpDWvMmODs9HJOEJ4FuwUCWm+kiwUJC8tagQAKCRDs9HJO EJ4Fu40cB/9xyEnuQegivmL6OBVG5HvUAaXGUxtWiWdLm3NrduL0h7rctF060xQTekNRCjbl xZ1w/unPDBEEIMPYbF8i7IwJZoRLTG1B1MjI04AUU60G0IU6uw0ST6IsC7oYGvhDNJApbVBb j9u9x+kzaktCftl3qdpSKgRh9McIyZgevuFBdo80RDtX8niktUA3xsfJWBD1yJA33UNSzqOe 54wFRbsM2+4erREPMD659h2lACPCXjPW/6ucnv0/cdPF8V2JNMCT0yPJVCSUfFLTrtyYtiRI 6S52cI4eEOZIXCQp30TA4E27O2mMLOYzlKA5P5T+Icf4gz8e/puNUKIBDlY6KF7p Message-ID: <133c6b7d-3946-1899-3194-3f77eabf1e7e@outer-planes.net> Date: Mon, 29 Jul 2019 09:21:46 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [COSE] =?utf-8?q?=F0=9F=94=94_WGLC_of_rfc8152bis_drafts_=28-stru?= =?utf-8?q?ct_and_-algs=29?= X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2019 15:21:50 -0000 This message starts the Working Group Last Call on the two 8152bis drafts: * draft-ietf-cose-rfc8152bis-struct [COSE-STRUCT] (Structures and Processes) * draft-ietf-cose-rfc8152bis-algs [COSE-ALGS] (Algorithms) The working group last call with run for **four weeks**, ending on August 26, 2019. Please review and send any comments or feedback to the working group. Even if your feedback is "this is ready", please let us know. Thank you, - Ivaylo and Matthew COSE Chairs [COSE-STRUCT]: < https://datatracker.ietf.org/doc/draft-ietf-cose-rfc8152bis-struct/ > [COSE-ALGS]: < https://datatracker.ietf.org/doc/draft-ietf-cose-rfc8152bis-algs/ > From nobody Mon Jul 29 08:56:02 2019 Return-Path: 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 D6C771201CA; Mon, 29 Jul 2019 08:55:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.6 X-Spam-Level: X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=myidemia.onmicrosoft.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 UPih4jzljznr; Mon, 29 Jul 2019 08:55:56 -0700 (PDT) Received: from mx07-0018b601.pphosted.com (mx07-0018b601.pphosted.com [185.132.180.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 747181201D1; Mon, 29 Jul 2019 08:55:52 -0700 (PDT) Received: from pps.filterd (m0136514.ppops.net [127.0.0.1]) by mx08-0018b601.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x6TFk6tx031754; Mon, 29 Jul 2019 15:55:45 GMT Received: from eur02-am5-obe.outbound.protection.outlook.com (mail-am5eur02lp2052.outbound.protection.outlook.com [104.47.4.52]) by mx08-0018b601.pphosted.com with ESMTP id 2u0epa42r1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 29 Jul 2019 15:55:45 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=b3GmG7H0d8WJi9c24uW8+tl+KbEKKE7UNY4kBCSOkHc7ZkE/3PjmHSm12zrj4uT+4hLjlc6ipQg0W3p0qbZMmC87FAnQ/ZfugIX+L04ioQAzhhBSLh0b79xAGnIRRtl0KITzVjhpaKoaW5l2tqlArtl7Qg4JJ7hOIO1SUB9h6n77BtMWNg7yMzMrupnyYuUl9v69ihnFvaottaFkscXxNtQm5Oty2h/8KjyNTqWQZU0t+xlFTRhyp3myxFb7/zUh+UV1p2/Vv3ygn5EwmxnYtCF9wO7Utv+YBzOZPff0TNFUxmeUNgFkkI1J07h08yNkK2AGMdeJp4kL3ZLFg25evQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NrJbD0cdF4980B1o0JdnkkbLBMZDm68Y+ltrUNPLrjM=; b=B84k4QUGBuCFZnkUjRk+qIIMIjQaFvt/GmPAW7Yg+OazCPkWlO0IvPDQTb9qTHpA+iqjuDfAM9RjPa3/HH0Skm2mkx3bravQyDqGXwn++iRUcFO334MPyGrZg+4yoog5omQfRwz7YkPqxxB0yFy+/61caUPB6pZxJRnqKwidAM68iYxNTOI9K2x9qh/sT0VFc6FfAGOoM7CCVfwKDYM3lUQDza9FlQmI76G0DeebicLOYWHKu0cktPfof20BvImLtA5SCYArVF8gXFkfevHgKXbFofOJgWrY7ttoD3lrA7hO4us2S7cDg0bF+SFuqkAWWMDW3U+ltZMdIG6NxHK1pw== ARC-Authentication-Results: i=1; mx.microsoft.com 1;spf=pass smtp.mailfrom=idemia.com;dmarc=pass action=none header.from=idemia.com;dkim=pass header.d=idemia.com;arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=myidemia.onmicrosoft.com; s=selector2-myidemia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NrJbD0cdF4980B1o0JdnkkbLBMZDm68Y+ltrUNPLrjM=; b=hMQsz7tznXXKgY/SE2P+9edF/1wixwkrGFNWW3W5X+rdIohPO9e6mu/10Pt8JCo1SvyYg9Ohny0nIlO6lWOjEBGsXh/X4ld92BupduuNYhNzEN64LqHgcSprC/o8gSE6adMLBXizOjNPiVIZ7uJY8SDc/s9Hb/Yj666K1sCp1y8= Received: from VI1P189MB0319.EURP189.PROD.OUTLOOK.COM (10.165.195.140) by VI1P189MB0542.EURP189.PROD.OUTLOOK.COM (10.165.196.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2115.10; Mon, 29 Jul 2019 15:55:43 +0000 Received: from VI1P189MB0319.EURP189.PROD.OUTLOOK.COM ([fe80::dc8:81fa:2b25:907]) by VI1P189MB0319.EURP189.PROD.OUTLOOK.COM ([fe80::dc8:81fa:2b25:907%3]) with mapi id 15.20.2115.005; Mon, 29 Jul 2019 15:55:43 +0000 From: DESPERRIER Jean-Marc To: Jim Schaad , "cose@ietf.org" CC: "cose-ads@ietf.org" Thread-Topic: [COSE] Early Code Point Assignments Thread-Index: AdVGG7/zFE5AfdzPQJi7oNvF59n5nQACUn4Q Date: Mon, 29 Jul 2019 15:55:43 +0000 Message-ID: References: <005001d5461d$149a4c70$3dcee550$@augustcellars.com> In-Reply-To: <005001d5461d$149a4c70$3dcee550$@augustcellars.com> Accept-Language: fr-FR, en-US Content-Language: fr-FR X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [165.225.76.89] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 09738c87-43d8-4055-0e4e-08d7143d36b4 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(7168020)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:VI1P189MB0542; x-ms-traffictypediagnostic: VI1P189MB0542: x-ms-exchange-purlcount: 5 x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:8882; x-forefront-prvs: 01136D2D90 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(39860400002)(136003)(396003)(376002)(346002)(366004)(189003)(199004)(7696005)(256004)(6306002)(305945005)(446003)(4326008)(76176011)(66066001)(99286004)(8936002)(102836004)(33656002)(55016002)(9686003)(2906002)(186003)(478600001)(6506007)(229853002)(11346002)(486006)(55236004)(53936002)(476003)(81156014)(81166006)(3846002)(8676002)(6246003)(74316002)(68736007)(966005)(52536014)(66946007)(6116002)(14454004)(26005)(2501003)(64756008)(66446008)(25786009)(66476007)(66556008)(7736002)(316002)(71190400001)(71200400001)(5660300002)(76116006)(6436002)(86362001)(110136005); DIR:OUT; SFP:1102; SCL:1; SRVR:VI1P189MB0542; H:VI1P189MB0319.EURP189.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: idemia.com does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: XN45hwVk9rkkwAFQSKXJH8ASrjn6hCx9lT4q8QWEBwC0C4lRYwU9PMh9vTud/VN2o/SRBys5itft2pdXC1Mjjq57bzQovo27yNWHjarwYe+7MwvrQNZmd1scpfHQK97wrw9hVYVcsH2Tv9447X0zK91Es50fMU926Ml4LXe98oF7F85SHY1vVrCYhD/Vz3WAJN5FcGotwZXuwG9otiaVtzED/tR1mnPGBmF9ZywFIBOm4ZDRgc+DAeB2lMrhggcg5gJnvFwetC43K27TuHGFzSoBjXN1mMKnSYtL2MrkLK0UbvdgKqlylk3rLojhRfyNZgT26QN55OUMYpiD6ppqSR4mB3cpTu/Hxl4GdyJpTV/4uRUuHWCphfmq56uULIo15c5c/pht/WWmCOX14SvowvuYJi+fUvRrSV/tzbMC7jA= Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: idemia.com X-MS-Exchange-CrossTenant-Network-Message-Id: 09738c87-43d8-4055-0e4e-08d7143d36b4 X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jul 2019 15:55:43.8515 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 7694d41c-5504-43d9-9e40-cb254ad755ec X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: g578695@mph.morpho.com X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1P189MB0542 X-Proofpoint-Virus-Version: vendor=nai engine=6000 definitions=9333 signatures=668685 X-Proofpoint-Spam-Details: rule=outbound_idemia_notspam policy=outbound_idemia score=0 lowpriorityscore=0 suspectscore=0 adultscore=0 mlxlogscore=999 priorityscore=1501 spamscore=0 mlxscore=0 malwarescore=0 bulkscore=0 clxscore=1011 phishscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1907290178 Archived-At: Subject: Re: [COSE] Early Code Point Assignments X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2019 15:56:00 -0000 Thanks a lot Jim ! How long do you expect for it to take until the IANA registry is updated wi= th this ? Will there be new drafts with just that change, or will it wait until more = changes are incorporated in the drafts ? Br, Jean-Marc -----Message d'origine----- De=A0: COSE De la part de Jim Schaad Envoy=E9=A0: lundi 29 juillet 2019 16:51 =C0=A0: cose@ietf.org Cc=A0: cose-ads@ietf.org; 'IANA' Objet=A0: [COSE] Early Code Point Assignments Following the meeting in Montreal where I asked for the ability to do early= point assignment for documents in the working group and got permission, these are the code points that I am assigning. I am only assigning points that I know people are asking for now, some points will be setup later. For draft-ietf-cose-x509 (https://urldefense.com/v3/__https://tools.ietf.or= g/html/draft-ietf-cose-x509__;!U11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3ga= zlI9OafG6C5RwG9UoYC41y6o_LFH8jxhW5xlqvW6$ ): Table COSE Header Parameters https://urldefense.com/v3/__https://www.iana.org/assignments/cose/cose.xhtm= l*header-parameters__;Iw!U11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9Oa= fG6C5RwG9UoYC41y6o_LFH8jxhWzvsQNq0$=20 Name Value x5bag 32 x5chain 33 x5t 34 x5u 35 For draft-ietf-cose-hash-algs (https://urldefense.com/v3/__https://tools.ietf.org/html/draft-ietf-cose-ha= sh-algs__;!U11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9OafG6C5RwG9UoYC4= 1y6o_LFH8jxhW41rdV3W$ ): Table COSE Algorithms https://urldefense.com/v3/__https://www.iana.org/assignments/cose/cose.xhtm= l*algorithms__;Iw!U11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9OafG6C5Rw= G9UoYC41y6o_LFH8jxhW-CPXFvk$=20 Name Value SHA-1 -14 SHA-256/64 -15 SHA-256 -16 SHA-384 -43 SHA-512 -44 SHA-512/256 -17 SHAKE128 -18 SHAKE256 -45 Jim _______________________________________________ COSE mailing list COSE@ietf.org https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/cose__;!U= 11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9OafG6C5RwG9UoYC41y6o_LFH8jxh= W7sLk-TT$=20 From nobody Mon Jul 29 09:27:43 2019 Return-Path: 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 DF56B120293 for ; Mon, 29 Jul 2019 09:27:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 9l8FgFD-L6-2 for ; Mon, 29 Jul 2019 09:27:32 -0700 (PDT) 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 7E5551202CF for ; Mon, 29 Jul 2019 09:27:32 -0700 (PDT) Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 29 Jul 2019 09:27:27 -0700 From: Jim Schaad To: 'DESPERRIER Jean-Marc' , References: <005001d5461d$149a4c70$3dcee550$@augustcellars.com> In-Reply-To: Date: Mon, 29 Jul 2019 09:27:24 -0700 Message-ID: <007601d5462a$82ea1f90$88be5eb0$@augustcellars.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AQGVzQ9rd57TtEKLbhe0ZKWAeJRxLwHdz7yap1HMHtA= X-Originating-IP: [73.180.8.170] Archived-At: Subject: Re: [COSE] Early Code Point Assignments X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jul 2019 16:27:41 -0000 I expect that it might take as long as week for the numbers to get into = the registry. I will be rolling the numbers into the drafts either just = before or after the WGLC depending on what other feedback I get. Jim -----Original Message----- From: COSE On Behalf Of DESPERRIER Jean-Marc Sent: Monday, July 29, 2019 8:56 AM To: Jim Schaad ; cose@ietf.org Cc: cose-ads@ietf.org Subject: Re: [COSE] Early Code Point Assignments Thanks a lot Jim ! How long do you expect for it to take until the IANA registry is updated with this ? Will there be new drafts with just that change, or will it wait until = more changes are incorporated in the drafts ? Br, Jean-Marc -----Message d'origine----- De=A0: COSE De la part de Jim Schaad = Envoy=E9=A0: lundi 29 juillet 2019 16:51 =C0=A0: cose@ietf.org Cc=A0: cose-ads@ietf.org; = 'IANA' Objet=A0: [COSE] Early Code Point Assignments Following the meeting in Montreal where I asked for the ability to do = early point assignment for documents in the working group and got permission, these are the code points that I am assigning. I am only assigning = points that I know people are asking for now, some points will be setup later. For draft-ietf-cose-x509 (https://urldefense.com/v3/__https://tools.ietf.org/html/draft-ietf-cose-= x50 9__;!U11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9OafG6C5RwG9UoYC41y6o= _LF H8jxhW5xlqvW6$ ): Table COSE Header Parameters https://urldefense.com/v3/__https://www.iana.org/assignments/cose/cose.xh= tml *header-parameters__;Iw!U11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9O= afG 6C5RwG9UoYC41y6o_LFH8jxhWzvsQNq0$=20 Name Value x5bag 32 x5chain 33 x5t 34 x5u 35 For draft-ietf-cose-hash-algs (https://urldefense.com/v3/__https://tools.ietf.org/html/draft-ietf-cose-= has h-algs__;!U11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9OafG6C5RwG9UoYC= 41y 6o_LFH8jxhW41rdV3W$ ): Table COSE Algorithms https://urldefense.com/v3/__https://www.iana.org/assignments/cose/cose.xh= tml *algorithms__;Iw!U11cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9OafG6C5R= wG9 UoYC41y6o_LFH8jxhW-CPXFvk$=20 Name Value SHA-1 -14 SHA-256/64 -15 SHA-256 -16 SHA-384 -43 SHA-512 -44 SHA-512/256 -17 SHAKE128 -18 SHAKE256 -45 Jim _______________________________________________ COSE mailing list COSE@ietf.org https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/cose__;= !U1 1cABxz5NU!gJwmhNTLylLQEZXMb9CfEJJ-5C-6A3gazlI9OafG6C5RwG9UoYC41y6o_LFH8jx= hW7 sLk-TT$=20 _______________________________________________ COSE mailing list COSE@ietf.org https://www.ietf.org/mailman/listinfo/cose From nobody Tue Jul 30 09:16:46 2019 Return-Path: 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 032E712016F for ; Tue, 30 Jul 2019 09:16:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=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=outer-planes-net.20150623.gappssmtp.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 VZ2lDirPzFrG for ; Tue, 30 Jul 2019 09:16:43 -0700 (PDT) Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 E934512015C for ; Tue, 30 Jul 2019 09:16:42 -0700 (PDT) Received: by mail-io1-xd34.google.com with SMTP id i10so16089111iol.13 for ; Tue, 30 Jul 2019 09:16:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:from:subject:to:references:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=n0yHfkuEqBashF7KiUWfXV9eq6LuSIbfT0PIdGUOeCI=; b=kA+tVytXcgfkXq69WRToh07S/siEfB5Jxk4wp5x/dlEFLaKnVQpATUvcbwYNo2oRhA UWFOy0N3tZ4mxgEOLknWpu252Cp3J7eIft+jLfP9ooUiGPlnROJuFfW1W+2u8uj1MBM7 L2urTpwKDNmiJbkexbhClYaQK0//l2X/JJO6jHFcGciiUN2c1y+ZHchDEvej9szmaogp ix3jeqQXPDUDlzlwTvgk7T9XkceXLLRgWzLsSIA7FJim0i8ggCXUY6VYacOAo1rMtFTO stTUIdlWK/D5OC+FzJm52M4ulRXCWgFRFgfvK/XrAeBo8ko/MeOc+x2QX4k8/4K68Sey nycw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:subject:to:references:openpgp :autocrypt:message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=n0yHfkuEqBashF7KiUWfXV9eq6LuSIbfT0PIdGUOeCI=; b=IsvuIRAimAUslSV0pVbok17YjL/30CLRmQ5uWpmodXBzWYarMa+RGGKXE2wN4mOl1W JGbn89PEB0j5s1vq3ZIr5vCUEiftE3lJSvLVJPZwj7FqcrEiRuoZ1gNWW2Q2ptKz8ozY nP1u/BE4d7rbQl4algEBSFfrl2r47evcWiKv5fmsjfr5lN/IZqcQ5m+T7wlKsu9B/UJD IVlI6MpfxK/huFvBG4nk+O+mRJ3+mg2tYKbpds4urXu52vNmNEDGP8XCTJu5rsG3eOFh 0lugsJDtPnF11YzMKcjEgXx6YjjJ9U22yJWtsY+WwW6uaOWZjXqexL046dTF4GmUM9eL tEKQ== X-Gm-Message-State: APjAAAVurHTZl8thvAtWJxerLVN25a1qjsUUPrF1/n9z0V9SMqPKPOtY 3IJHrUa8chcNxLdBptO4G76szaTqaeo= X-Google-Smtp-Source: APXvYqxHr6lSGhi+ZaM1sjHpBhwtA+v4gGzT30gg6Xyl1aCFHMmCC3Zv1E4PsXvub2fuVIfqEglkzA== X-Received: by 2002:a02:aa1d:: with SMTP id r29mr49212580jam.127.1564503401786; Tue, 30 Jul 2019 09:16:41 -0700 (PDT) Received: from mmiller-44677.local ([207.126.127.114]) by smtp.gmail.com with ESMTPSA id o7sm55001751ioo.81.2019.07.30.09.16.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jul 2019 09:16:41 -0700 (PDT) Sender: Matthew Miller From: "Matthew A. Miller" To: cose References: <133c6b7d-3946-1899-3194-3f77eabf1e7e@outer-planes.net> Openpgp: preference=signencrypt Autocrypt: addr=linuxwolf+ietf@outer-planes.net; prefer-encrypt=mutual; keydata= mQENBFJoAooBCADQmEtpbpY/4wTeKgZIuyG7HkxIFgiUeqOvtiBKj/pCA73d7Q5hCvQdGcKJ 6uZsYz3Il9oKoKFxVt90iEXspbE39g6ek19e6RsB4j0Q10l4QvH+EqeD760gs0H2yf/eYj9i uk9/VY6axdQlPsmid1zoQgCNjSM7X4/K26WGMs03sbXJpKdoonelzIlJSNfzi0q546iplo72 D2cCm9BriMkQvcGnsm4B9eBIBn3GKmVx1tsmPNeNTyun2DvaLnrYxbA0Ivo1DzZReds9NZ25 uROI/+b+lcg9/kmHzhK+q8NMQCFWmqpS/lZRKxVBSijKGpGr5h8VLVf5iURHtwG+B/QxABEB AAG0M01hdHRoZXcgQS4gTWlsbGVyIDxsaW51eHdvbGYraWV0ZkBvdXRlci1wbGFuZXMubmV0 PokBPQQTAQoAJwUCWKsJ1AIbAwUJC8ckMQULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRDs 9HJOEJ4Fu1iBCADAcW06d/7GTlBjTlYuMGgjzDBoWeQ9/zxgMnSrgNb6yO7wHzE65CeFs6OI 6LQ4A34CNM3hhcWDIzlqrV25fVyy7qCh6bCNMs1pOT63+Od4kcjHtUnGGTONT5fXSGY7mCtl XJFjb3TwyLUZXQCifhCIaUdF/4SVoGk96W9ssbDKN+5xq7B7gyVkwB0WM67zxt/kC6TPcXXL 5m7jsNRpRmFQqOlIF+HrQAcSr1lKRWgetb1VHfXCgcmDaTKn1QC7s0Ml+27dc0SoIkBI8cnv inJ4oFYWrvnTlOvv+v8AFXZnPrxZ/JYvnVD/y5PX7v08Z8RFXm1AmVxIWjXPI6TySkGvuQEN BFJoAooBCADA/ruHwYlQ7pdjJY6twkZcMmedkQNL6r5tNBeQkwVrvitUjHTKKipjxB2kEkUZ oxPgMI1h7/enDrVlMMMqq6RIJ86H+yx13zNIZNBlJfmVHgHj7TT8spa6A/qIccdiIRNsFVvl vFxpH8sTjVbHfPYexbdOR5kHpZWTzYxNyVLXMK5jen0B4K+vjbgFJAvsoLfzLZ5Bz3kb6dpu xUNzqhDyhk5/UPaCIFvZWBtiRKmkqPwEq8G2aMJq5Z4Sr8CRkpoMB25rxCPS8R+ByiHxpq+U 8mKuqPVg1LJzcA7hHmms8aBN6lxSlbyKnzEg8AWgld+6+xlJXu5U/fqDAClTj5mfABEBAAGJ ATwEGAEKACYCGwwWIQQx11iN7JBpDWvMmODs9HJOEJ4FuwUCWm+kiwUJC8tagQAKCRDs9HJO EJ4Fu40cB/9xyEnuQegivmL6OBVG5HvUAaXGUxtWiWdLm3NrduL0h7rctF060xQTekNRCjbl xZ1w/unPDBEEIMPYbF8i7IwJZoRLTG1B1MjI04AUU60G0IU6uw0ST6IsC7oYGvhDNJApbVBb j9u9x+kzaktCftl3qdpSKgRh9McIyZgevuFBdo80RDtX8niktUA3xsfJWBD1yJA33UNSzqOe 54wFRbsM2+4erREPMD659h2lACPCXjPW/6ucnv0/cdPF8V2JNMCT0yPJVCSUfFLTrtyYtiRI 6S52cI4eEOZIXCQp30TA4E27O2mMLOYzlKA5P5T+Icf4gz8e/puNUKIBDlY6KF7p Message-ID: Date: Tue, 30 Jul 2019 10:16:40 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <133c6b7d-3946-1899-3194-3f77eabf1e7e@outer-planes.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [COSE] =?utf-8?q?Review_of_draft-ietf-cose-rfc8152bis-struct_for?= =?utf-8?q?_=F0=9F=94=94_WGLC_of_rfc8152bis_drafts?= X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Jul 2019 16:16:45 -0000 [ Posting as an individual ] This is my review of draft-ietf-cose-rfc8152bis-struct. Overall I think the document is nearly ready, with what I consider editorial issues (some larger than others) that ought to be addressed one way or another. I note that I have not tried to verify the examples in -rfc8152bis-struct, though the diagnostic values all seem correct to me (where a visual inspection is possible). Thank you again, Jim, for undertaking this document. ## Minor Questions/Concerns ## * The term "context" is used throughout as an information set and/or configuration not discretely encoded in the protocol, but is never explicitly defined. I think it important to define, especially as abbreviated counter signatures wholly depend on inferred parameters. * Further with abbreviated counter signatures, I think the original text in RFC 8152 Appendix A.2 did a bit better to be explicit on what was implicit, and that CounterSignature0 applied to more than encrypted data. I suggest rewording the first paragraph to something like the following: """ Abbreviated countersignatures were designed primarily to deal with the problem of having group encrypted messaging, but still needing to know who originated the message. The object was to keep the countersignature as small as possible while still providing the needed security. For abbreviated countersignatures, there is no provision for any protected attributes related to the signing operation. Instead, the parameters for computing or verifying the abbreviated countersignature are inferred from the same context used to describe the encryption, signature, or MAC processing. """ * The sections that describe generically describe algorithm classes (Sections 9 through 13), to me, break with the flow of the document and can seem to imply the actual algorithms are still defined herein. I think it would be worth making them all subsections under a "Algorithm Classes in Use" (or a better title), with a short paragraph stating the following describe categories of algorithms and the requirements or restrictions placed on algorithms that apply. ## Nits ## * The reference to I-D.ietf-cbor-cddl should be updated to RFC 8610. * In Section 1.2 "Changes from RFC8152", "standalong" should be "standalone". * Table 2 ought to be explicitly changed to`[[ this document ]]` to aid the RFC Editor. * In Section 4.4 "Signing and Verification Process", the CDDL for `Sig_structure` is missing "CounterSignature0" as an option for `context`. * In Section 5 "Counter Signatures", paragraph 2, the word "oppose" should be "opposed" in the sentence "It should be noted as oppose to attesting to the unencrypted data." * In Section 5.2 "Abbreviated Countersignatures", first paragraph, "orginated" should be "originated". * In Section 6.1.1 "Content Key Distribution Methods", the "key transport" and "passwords" entries have a note on "[no] algorithms are defined in this document". I think it enough to strike this last sentence completely from each, but can see a case for saying "[no] algorithms are defined in [I-D.ietf-cose-rfc8152bis-algs]" instead. * In Section 10 "Message Authentication Code (MAC) Algorithms", the penultimate paragraph should have "this document" replaced with a reference to draft-ietf-cose-rfc8152bis-algs. * In Section 14 "CBOR Encoding Restrictions", the second bullet's first sentence seems to be missing a word or two; suggest changing to something like: """ Encoding MUST be done using definite lengths and values MUST be encoded using the minimum possible length. """ * In Section 15 "Application Profiling Considerations", the word "profiles" should be "profile" in second paragraph ("... where a profiles was developed for ..."). * In Section 17 "Security Considerations", the third bulleted item should have a reference to draft-ietf-cose-rfc8152bis-algs instead of this document ("Several algorithms in this document ..."). * Also in Section 17 "Security Considerations", the penultimate paragraph mentions that "algorithms presented in this document"; "this document" should be replaced with a reference to draft-ietf-cose-rfc8152bis-algs. * In Section 18.1 "Author's Versions", "THe" should be "The". * The title for Section 18.2 should be "JavaScript Version". * In Appendix A "Guidelines for External Data Authentication of Algorithms", the second bulleted item should have "algorithms in this document" changed to reference draft-ietf-cose-rfc8152bis-algs. - m&m Matthew A. Miller On 19/07/29 11:21, Matthew A. Miller wrote: > This message starts the Working Group Last Call on the two 8152bis drafts: > > * draft-ietf-cose-rfc8152bis-struct [COSE-STRUCT] (Structures and Processes) > * draft-ietf-cose-rfc8152bis-algs [COSE-ALGS] (Algorithms) > > The working group last call with run for **four weeks**, ending on > August 26, 2019. > > Please review and send any comments or feedback to the working group. > Even if your feedback is "this is ready", please let us know. > > > Thank you, > > - Ivaylo and Matthew > COSE Chairs > > [COSE-STRUCT]: < > https://datatracker.ietf.org/doc/draft-ietf-cose-rfc8152bis-struct/ > > [COSE-ALGS]: < > https://datatracker.ietf.org/doc/draft-ietf-cose-rfc8152bis-algs/ > > From nobody Wed Jul 31 08:12:37 2019 Return-Path: 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 0601212006D; Wed, 31 Jul 2019 08:12:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.989 X-Spam-Level: X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ihtfp.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 qYBwy8qiP7lP; Wed, 31 Jul 2019 08:12:34 -0700 (PDT) Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB4B412004F; Wed, 31 Jul 2019 08:12:33 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 85570E2044; Wed, 31 Jul 2019 11:12:32 -0400 (EDT) Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 24378-01; Wed, 31 Jul 2019 11:12:26 -0400 (EDT) Received: from securerf.ihtfp.org (99-46-190-172.lightspeed.tukrga.sbcglobal.net [99.46.190.172]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mocana.ihtfp.org", Issuer "IHTFP Consulting Certification Authority" (not verified)) by mail2.ihtfp.org (Postfix) with ESMTPS id 66969E2040; Wed, 31 Jul 2019 11:12:26 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1564585946; bh=GsOlVcbMjQpRtrpnT7KlkNLRq8lETed1zOmUf5cND0A=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=JUUc3yal8byLa38LSNRD4869qHimZ0g7+zk1IAn4jvy1qlePolXMNfWbHY8g+0w6r fjL7ubA4fvrBRIUdsopuEfBXZ4h+scGI9gLv+cAbAo99CXw5jsz5e5EihrXLgTKnWN YfYNQhq8bJoz8pDnywPu/KuhRcUmykuip6Shr8jY= Received: (from warlord@localhost) by securerf.ihtfp.org (8.15.2/8.15.2/Submit) id x6VFCK40022565; Wed, 31 Jul 2019 11:12:20 -0400 From: Derek Atkins To: Michael Richardson Cc: cose@ietf.org, "suit\@ietf.org" References: <835.1562080969@localhost> Date: Wed, 31 Jul 2019 11:12:19 -0400 In-Reply-To: <835.1562080969@localhost> (Michael Richardson's message of "Tue, 02 Jul 2019 11:22:49 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Virus-Scanned: Maia Mailguard 1.0.2a Archived-At: Subject: Re: [COSE] [Suit] draft-atkins-suit-cose-walnutdsa X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2019 15:12:36 -0000 Michael, Again, sorry for the delay in responding. I've had a lot of $DAYJOB deadlines which have taken over and some things have fallen through the cracks. Too many balls in the air, so to speak. Comments are inline below.. Michael Richardson writes: > Derek, looking at the IANA Considerations of > draft-atkins-suit-cose-walnutdsa, it seems that you need a number in: > > 1) COSE Algorithms -- registry > 2) COSE Key Types -- registry > > and several in the > 3) COSE Key Type Parameters -- registry Correct. > https://www.iana.org/assignments/cose/cose.xhtml#algorithms > > For the first, you can have: > Integer values greater than 65535 Expert Review > > And the other two are Expert Review anyway, no specification required! > You are even listed as one of the experts for COSE Key Types :-) Yes, I know I am one of the experts for these registries. However, I feel I must recuse myself from approval of these. > {If my reading is correct, you can also use strings longer than 2-bytes > without registration with IANA, but that has an operational (maintaining > legacy code) and bytes-on-the-wire impact should you be allocated a shorter > code later on} Yes, which is another reason I'd rather get something right. > You could also ask for early allocation via the COSE WG, but that probably > requires the document to be adopted first! Does it? Or does the WG just need to approve of the document going through any of the publication processes? > That's what I would do: just ask for the values via Expert Review, and live > for now, with the a five-bye (encoded) COSE Algorithm code, if your market > need is urgent. Yes, I could just request the entries in the registry. However, I am trying to be a good netizen; I want to have a document that people can look at to understand what the registry items mean. > Derek Atkins wrote: > > We have customers who are looking to use this technology today, so we > > would like to do it in a standard way that others could understand. > > Personally, I'm fine with an Informational (instead of Standards-track) > > publication if that would make people happier. Even so, the RFC Editor > > would still require approval from this WG as it is within their (the > > WG's) area. > > yes, if you went ISE, which would still take awhile. I am fine going through the ISE, however I suspect that the IESG in their conflict review would then go and ask this WG about it. So I wanted to bring it up here, first. What is your definition of "awhile"? Thanks, > Michael Richardson , Sandelman Software Works > -= IPv6 IoT consulting =- -derek -- Derek Atkins 617-623-3745 derek@ihtfp.com www.ihtfp.com Computer and Internet Security Consultant From nobody Wed Jul 31 08:51:55 2019 Return-Path: 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 ECAA112037E; Wed, 31 Jul 2019 08:51:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.651 X-Spam-Level: X-Spam-Status: No, score=-1.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 oDjPkxQ24llG; Wed, 31 Jul 2019 08:51:51 -0700 (PDT) Received: from smtp01.icann.org (smtp01.icann.org [192.0.33.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 07F8712037A; Wed, 31 Jul 2019 08:51:51 -0700 (PDT) Received: from request4.lax.icann.org (request1.lax.icann.org [10.32.11.221]) by smtp01.icann.org (Postfix) with ESMTP id BA4CEE06FF; Wed, 31 Jul 2019 15:51:50 +0000 (UTC) Received: by request4.lax.icann.org (Postfix, from userid 48) id B7A8A20620; Wed, 31 Jul 2019 15:51:50 +0000 (UTC) RT-Owner: sabrina.tanamal From: "Sabrina Tanamal via RT" Reply-To: iana-prot-param@iana.org In-Reply-To: <005001d5461d$149a4c70$3dcee550$@augustcellars.com> References: <005001d5461d$149a4c70$3dcee550$@augustcellars.com> Message-ID: X-RT-Loop-Prevention: IANA X-RT-Ticket: IANA #1148103 X-Managed-BY: RT 4.4.3 (http://www.bestpractical.com/rt/) X-RT-Originator: sabrina.tanamal@icann.org To: ietf@augustcellars.com CC: cose@ietf.org, cose-ads@ietf.org, ivaylo@ackl.io, linuxwolf+ietf@outer-planes.net, kaduk@mit.edu Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Precedence: bulk Date: Wed, 31 Jul 2019 15:51:50 +0000 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Archived-At: Subject: [COSE] [IANA #1148103] Early Code Point Assignments X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2019 15:51:53 -0000 Hi Jim, all, Before we can make RFC 7120 early allocations for the registrations listed below, we need approval from a chair and an AD. Because these are Standards Action with Expert Review registries, we'll have to ask the designated experts for approval as well. Best regards, Sabrina Tanamal Senior IANA Services Specialist On Mon Jul 29 14:52:02 2019, ietf@augustcellars.com wrote: > Following the meeting in Montreal where I asked for the ability to do early > point assignment for documents in the working group and got permission, > these are the code points that I am assigning. I am only assigning points > that I know people are asking for now, some points will be setup later. > > For draft-ietf-cose-x509 (https://tools.ietf.org/html/draft-ietf-cose-x509): > > Table COSE Header Parameters > https://www.iana.org/assignments/cose/cose.xhtml#header-parameters > > Name Value > x5bag 32 > x5chain 33 > x5t 34 > x5u 35 > > For draft-ietf-cose-hash-algs > (https://tools.ietf.org/html/draft-ietf-cose-hash-algs): > > Table COSE Algorithms > https://www.iana.org/assignments/cose/cose.xhtml#algorithms > > Name Value > > SHA-1 -14 > SHA-256/64 -15 > SHA-256 -16 > SHA-384 -43 > SHA-512 -44 > SHA-512/256 -17 > SHAKE128 -18 > SHAKE256 -45 > > > Jim > > From nobody Wed Jul 31 09:30:10 2019 Return-Path: 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 748FE12013C for ; Wed, 31 Jul 2019 09:30:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-net.20150623.gappssmtp.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 hj0ADVJqPpKo for ; Wed, 31 Jul 2019 09:30:06 -0700 (PDT) Received: from mail-io1-xd43.google.com (mail-io1-xd43.google.com [IPv6:2607:f8b0:4864:20::d43]) (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 7CD70120158 for ; Wed, 31 Jul 2019 09:30:06 -0700 (PDT) Received: by mail-io1-xd43.google.com with SMTP id q22so17825731iog.4 for ; Wed, 31 Jul 2019 09:30:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:cc:references:from:openpgp:autocrypt:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=NxSTFAKpixMqZYwpx5Ju+mfSXog8sxEIiBG2g2C9YKU=; b=X9NLJ0n9mOtR8Fyvj57dv2jhp3UpsthR0CgGcOhLD4+whPg8bIpnf+lDkC1H0ncruD 0NxkrP4TFkGeJJLWRDDZYZAQcIBmSku5ryHwbbeB3qXr7xYf1saZOcyWuXBW/NN0qHKj aYHdd6veDXf88dsbMJBi5oC0bHA4zwbNfQDK770XbK/hK47KMOxCgu6SME/3qRBW7PqT ylyoxNCfCD5gLQ7m3/pK9caWdWWdteHaTkux6SYg7OvtN3Y/OrtOqwGdKcKhCEpfqi67 DeWwPFn4//lNsU5507YjReRI6rNYN6TzeCu0fuFDb/SjT2wAn9bhDWoEwNMvDEu1mZfe MzrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:openpgp :autocrypt:message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=NxSTFAKpixMqZYwpx5Ju+mfSXog8sxEIiBG2g2C9YKU=; b=pt2eANUpofcidv7zs+s9zuNkfuvayetTdRe07KWWym/08xFWhaZ06dEO+tf+kyRxNa aY8dOk+lcxb9MXnyiKtJWIe94QFH6UgtEeuwrkPJp2NDGnfS0wUzuL+0BojRSe60YZVH mkSfPfPuKxni5LkO52A7bX0YJ0/n9yBuUIA9OROHK40CxVZb4ntRzXusdYizKV2ry2Io Y/p3XS4SE5y7ty/gHJlqBfmZb/6LPINX6/soyvId3NIF3WqbcuBVSl/H7+Nk5kZx4fY0 5lT201wd75mFpa4YEWIm0Z7CkyhY6Hy+/7JnMJjwbJkFNYnrSqFKe8xIcZJdlZdAnFZU ER2g== X-Gm-Message-State: APjAAAXGSd6ecV9myJk+TMDWraNZcSOEgqWFlsc35xUCLLKxkbM3KHAF hs6QtoH3qCADYxBLgwQc1lc= X-Google-Smtp-Source: APXvYqyh/A+5Wnitz/XkFrH+TVnUycH1YMM8Mw+Pp7MQq1ImAcI7u0Hd7TceLr+HFh0JxFwT5mCyzA== X-Received: by 2002:a6b:ed02:: with SMTP id n2mr5650245iog.131.1564590605591; Wed, 31 Jul 2019 09:30:05 -0700 (PDT) Received: from mmiller-44677.local ([207.126.127.114]) by smtp.gmail.com with ESMTPSA id q13sm61348193ioh.36.2019.07.31.09.30.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jul 2019 09:30:04 -0700 (PDT) Sender: Matthew Miller To: iana-prot-param@iana.org, ietf@augustcellars.com Cc: cose@ietf.org, cose-ads@ietf.org, ivaylo@ackl.io, kaduk@mit.edu References: <005001d5461d$149a4c70$3dcee550$@augustcellars.com> From: "Matthew A. Miller" Openpgp: preference=signencrypt Autocrypt: addr=linuxwolf+ietf@outer-planes.net; prefer-encrypt=mutual; keydata= mQENBFJoAooBCADQmEtpbpY/4wTeKgZIuyG7HkxIFgiUeqOvtiBKj/pCA73d7Q5hCvQdGcKJ 6uZsYz3Il9oKoKFxVt90iEXspbE39g6ek19e6RsB4j0Q10l4QvH+EqeD760gs0H2yf/eYj9i uk9/VY6axdQlPsmid1zoQgCNjSM7X4/K26WGMs03sbXJpKdoonelzIlJSNfzi0q546iplo72 D2cCm9BriMkQvcGnsm4B9eBIBn3GKmVx1tsmPNeNTyun2DvaLnrYxbA0Ivo1DzZReds9NZ25 uROI/+b+lcg9/kmHzhK+q8NMQCFWmqpS/lZRKxVBSijKGpGr5h8VLVf5iURHtwG+B/QxABEB AAG0M01hdHRoZXcgQS4gTWlsbGVyIDxsaW51eHdvbGYraWV0ZkBvdXRlci1wbGFuZXMubmV0 PokBPQQTAQoAJwUCWKsJ1AIbAwUJC8ckMQULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRDs 9HJOEJ4Fu1iBCADAcW06d/7GTlBjTlYuMGgjzDBoWeQ9/zxgMnSrgNb6yO7wHzE65CeFs6OI 6LQ4A34CNM3hhcWDIzlqrV25fVyy7qCh6bCNMs1pOT63+Od4kcjHtUnGGTONT5fXSGY7mCtl XJFjb3TwyLUZXQCifhCIaUdF/4SVoGk96W9ssbDKN+5xq7B7gyVkwB0WM67zxt/kC6TPcXXL 5m7jsNRpRmFQqOlIF+HrQAcSr1lKRWgetb1VHfXCgcmDaTKn1QC7s0Ml+27dc0SoIkBI8cnv inJ4oFYWrvnTlOvv+v8AFXZnPrxZ/JYvnVD/y5PX7v08Z8RFXm1AmVxIWjXPI6TySkGvuQEN BFJoAooBCADA/ruHwYlQ7pdjJY6twkZcMmedkQNL6r5tNBeQkwVrvitUjHTKKipjxB2kEkUZ oxPgMI1h7/enDrVlMMMqq6RIJ86H+yx13zNIZNBlJfmVHgHj7TT8spa6A/qIccdiIRNsFVvl vFxpH8sTjVbHfPYexbdOR5kHpZWTzYxNyVLXMK5jen0B4K+vjbgFJAvsoLfzLZ5Bz3kb6dpu xUNzqhDyhk5/UPaCIFvZWBtiRKmkqPwEq8G2aMJq5Z4Sr8CRkpoMB25rxCPS8R+ByiHxpq+U 8mKuqPVg1LJzcA7hHmms8aBN6lxSlbyKnzEg8AWgld+6+xlJXu5U/fqDAClTj5mfABEBAAGJ ATwEGAEKACYCGwwWIQQx11iN7JBpDWvMmODs9HJOEJ4FuwUCWm+kiwUJC8tagQAKCRDs9HJO EJ4Fu40cB/9xyEnuQegivmL6OBVG5HvUAaXGUxtWiWdLm3NrduL0h7rctF060xQTekNRCjbl xZ1w/unPDBEEIMPYbF8i7IwJZoRLTG1B1MjI04AUU60G0IU6uw0ST6IsC7oYGvhDNJApbVBb j9u9x+kzaktCftl3qdpSKgRh9McIyZgevuFBdo80RDtX8niktUA3xsfJWBD1yJA33UNSzqOe 54wFRbsM2+4erREPMD659h2lACPCXjPW/6ucnv0/cdPF8V2JNMCT0yPJVCSUfFLTrtyYtiRI 6S52cI4eEOZIXCQp30TA4E27O2mMLOYzlKA5P5T+Icf4gz8e/puNUKIBDlY6KF7p Message-ID: <508a414d-6397-9d77-caac-d2371a2f9e05@outer-planes.net> Date: Wed, 31 Jul 2019 10:30:04 -0600 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [COSE] [IANA #1148103] Early Code Point Assignments X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2019 16:30:09 -0000 As a Chair, I approve of this early assignment. - m&m Matthew A. Miller On 19/07/31 09:51, Sabrina Tanamal via RT wrote: > Hi Jim, all, > > Before we can make RFC 7120 early allocations for the registrations listed below, we need approval from a chair and an AD. > > Because these are Standards Action with Expert Review registries, we'll have to ask the designated experts for approval as well. > > Best regards, > > Sabrina Tanamal > Senior IANA Services Specialist > > On Mon Jul 29 14:52:02 2019, ietf@augustcellars.com wrote: >> Following the meeting in Montreal where I asked for the ability to do early >> point assignment for documents in the working group and got permission, >> these are the code points that I am assigning. I am only assigning points >> that I know people are asking for now, some points will be setup later. >> >> For draft-ietf-cose-x509 (https://tools.ietf.org/html/draft-ietf-cose-x509): >> >> Table COSE Header Parameters >> https://www.iana.org/assignments/cose/cose.xhtml#header-parameters >> >> Name Value >> x5bag 32 >> x5chain 33 >> x5t 34 >> x5u 35 >> >> For draft-ietf-cose-hash-algs >> (https://tools.ietf.org/html/draft-ietf-cose-hash-algs): >> >> Table COSE Algorithms >> https://www.iana.org/assignments/cose/cose.xhtml#algorithms >> >> Name Value >> >> SHA-1 -14 >> SHA-256/64 -15 >> SHA-256 -16 >> SHA-384 -43 >> SHA-512 -44 >> SHA-512/256 -17 >> SHAKE128 -18 >> SHAKE256 -45 >> >> >> Jim >> >> > From nobody Wed Jul 31 11:03:09 2019 Return-Path: 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 D0D9D120671 for ; Wed, 31 Jul 2019 11:03:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 1wF-oOKiZ5W0 for ; Wed, 31 Jul 2019 11:02:58 -0700 (PDT) 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 3F606120680 for ; Wed, 31 Jul 2019 11:02:58 -0700 (PDT) Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 31 Jul 2019 11:02:51 -0700 From: Jim Schaad To: "'Matthew A. Miller'" , 'cose' References: <133c6b7d-3946-1899-3194-3f77eabf1e7e@outer-planes.net> In-Reply-To: Date: Wed, 31 Jul 2019 11:02:49 -0700 Message-ID: <01b301d547ca$2c0e2cb0$842a8610$@augustcellars.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Content-Language: en-us Thread-Index: AQHyB9FWkBfNzju4o5H6lRZB1jFIfQLJf+AeppP8NLA= X-Originating-IP: [73.180.8.170] Archived-At: Subject: Re: [COSE] =?utf-8?q?Review_of_draft-ietf-cose-rfc8152bis-struct_for?= =?utf-8?q?_=F0=9F=94=94_WGLC_of_rfc8152bis_drafts?= X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2019 18:03:08 -0000 Comments inline. -----Original Message----- From: COSE On Behalf Of Matthew A. Miller Sent: Tuesday, July 30, 2019 9:17 AM To: cose Subject: [COSE] Review of draft-ietf-cose-rfc8152bis-struct for = =F0=9F=94=94 WGLC of rfc8152bis drafts [ Posting as an individual ] This is my review of draft-ietf-cose-rfc8152bis-struct. Overall I think = the document is nearly ready, with what I consider editorial issues = (some larger than others) that ought to be addressed one way or another. I note that I have not tried to verify the examples in = -rfc8152bis-struct, though the diagnostic values all seem correct to me = (where a visual inspection is possible). [JLS] The good news is that as long as I do not touch them, the examples = were pulled directly from the examples website as they were = automatically generated for RFC 8152. Thank you again, Jim, for undertaking this document. ## Minor Questions/Concerns ## * The term "context" is used throughout as an information set and/or = configuration not discretely encoded in the protocol, but is never = explicitly defined. I think it important to define, especially as = abbreviated counter signatures wholly depend on inferred parameters. [JLS] Proposed text: Context is used throughout the document to represent = information that is not part of the COSE message. Information which is part of the context can come from several = different sources including: Protocol interactions, associated key structures and program = configuration. Context should generally be included in the cryptographic = configuration, for more details see . * Further with abbreviated counter signatures, I think the original text = in RFC 8152 Appendix A.2 did a bit better to be explicit on what was = implicit, and that CounterSignature0 applied to more than encrypted = data. I suggest rewording the first paragraph to something like the following: """ Abbreviated countersignatures were designed primarily to deal with the problem of having group encrypted messaging, but still needing to know who originated the message. The object was to keep the countersignature as small as possible while still providing the needed security. For abbreviated countersignatures, there is no provision for any protected attributes related to the signing operation. Instead, the parameters for computing or verifying the abbreviated countersignature are inferred from the same context used to describe the encryption, signature, or MAC processing. """ [JLS] Looks good - done. * The sections that describe generically describe algorithm classes = (Sections 9 through 13), to me, break with the flow of the document and = can seem to imply the actual algorithms are still defined herein. I = think it would be worth making them all subsections under a "Algorithm = Classes in Use" (or a better title), with a short paragraph stating the = following describe categories of algorithms and the requirements or = restrictions placed on algorithms that apply. [JLS] This makes a good deal of sense to me. Even if it means that I = need to go and refresh all of the references in other documents. For = now I have used the section title "Taxonomy of Algorithms used by COSE" = although Classification might be a less esoteric term. Text for the = section is currently In this section, a taxonomy of the different algorithm types = that can be used in COSE is laid out. This taxonomy should not be considered to be exhaustive as there = are new algorithm structures that could be found or are not known to the = author. ## Nits ## * The reference to I-D.ietf-cbor-cddl should be updated to RFC 8610. [JLS] Done * In Section 1.2 "Changes from RFC8152", "standalong" should be = "standalone". [JLS] Done. * Table 2 ought to be explicitly changed to`[[ this document ]]` to aid = the RFC Editor. [JLS] Done. * In Section 4.4 "Signing and Verification Process", the CDDL for = `Sig_structure` is missing "CounterSignature0" as an option for = `context`. [JLS] Done. * In Section 5 "Counter Signatures", paragraph 2, the word "oppose" should be "opposed" in the sentence "It should be noted as oppose to = attesting to the unencrypted data." [JLS] Done. * In Section 5.2 "Abbreviated Countersignatures", first paragraph, = "orginated" should be "originated". [JLS} Done * In Section 6.1.1 "Content Key Distribution Methods", the "key = transport" and "passwords" entries have a note on "[no] algorithms are = defined in this document". I think it enough to strike this last = sentence completely from each, but can see a case for saying "[no] = algorithms are defined in [I-D.ietf-cose-rfc8152bis-algs]" instead. [JLS] Eliminated for key transport, since RSA algorithms now exist. = Changed the language on passwords to " As of when this document was = published, no password algorithms have been defined." * In Section 10 "Message Authentication Code (MAC) Algorithms", the = penultimate paragraph should have "this document" replaced with a = reference to draft-ietf-cose-rfc8152bis-algs. [JLS] Done * In Section 14 "CBOR Encoding Restrictions", the second bullet's first = sentence seems to be missing a word or two; suggest changing to = something like: """ Encoding MUST be done using definite lengths and values MUST be = encoded using the minimum possible length. """ [JLS] Done * In Section 15 "Application Profiling Considerations", the word = "profiles" should be "profile" in second paragraph ("... where a = profiles was developed for ..."). [JLS] Switched /a profiles/one/ * In Section 17 "Security Considerations", the third bulleted item = should have a reference to draft-ietf-cose-rfc8152bis-algs instead of = this document ("Several algorithms in this document ..."). [JLS] Done * Also in Section 17 "Security Considerations", the penultimate = paragraph mentions that "algorithms presented in this document"; "this = document" should be replaced with a reference to = draft-ietf-cose-rfc8152bis-algs. [JLS] Done. This has been frequently enough in the review that I did a = scan for the phrase "this document" and fixed a couple of other cases. * In Section 18.1 "Author's Versions", "THe" should be "The". [JLS] This section disappears before publication, but fixed it anyway. * The title for Section 18.2 should be "JavaScript Version". [JLS] Done * In Appendix A "Guidelines for External Data Authentication of = Algorithms", the second bulleted item should have "algorithms in this = document" changed to reference draft-ietf-cose-rfc8152bis-algs. [JLS] - m&m Matthew A. Miller On 19/07/29 11:21, Matthew A. Miller wrote: > This message starts the Working Group Last Call on the two 8152bis = drafts: >=20 > * draft-ietf-cose-rfc8152bis-struct [COSE-STRUCT] (Structures and=20 > Processes) > * draft-ietf-cose-rfc8152bis-algs [COSE-ALGS] (Algorithms) >=20 > The working group last call with run for **four weeks**, ending on=20 > August 26, 2019. >=20 > Please review and send any comments or feedback to the working group. > Even if your feedback is "this is ready", please let us know. >=20 >=20 > Thank you, >=20 > - Ivaylo and Matthew > COSE Chairs >=20 > [COSE-STRUCT]: < > https://datatracker.ietf.org/doc/draft-ietf-cose-rfc8152bis-struct/ > > [COSE-ALGS]: < > https://datatracker.ietf.org/doc/draft-ietf-cose-rfc8152bis-algs/ > >=20 _______________________________________________ COSE mailing list COSE@ietf.org https://www.ietf.org/mailman/listinfo/cose From nobody Wed Jul 31 12:38:12 2019 Return-Path: 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 EC73E120077; Wed, 31 Jul 2019 12:38:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 L70PDDT6tZB4; Wed, 31 Jul 2019 12:38:08 -0700 (PDT) Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CD6112008D; Wed, 31 Jul 2019 12:38:07 -0700 (PDT) Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id B1BD2380BE; Wed, 31 Jul 2019 15:37:39 -0400 (EDT) Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D7781205; Wed, 31 Jul 2019 15:38:05 -0400 (EDT) From: Michael Richardson To: Derek Atkins cc: "suit\@ietf.org" , cose@ietf.org In-Reply-To: References: <835.1562080969@localhost> X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Archived-At: Subject: Re: [COSE] [Suit] draft-atkins-suit-cose-walnutdsa X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jul 2019 19:38:11 -0000 --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Derek Atkins wrote: >> And the other two are Expert Review anyway, no specification require= d! >> You are even listed as one of the experts for COSE Key Types :-) > Yes, I know I am one of the experts for these registries. However, I > feel I must recuse myself from approval of these. Yes, obviously, but the point is that you will know how to ask nicely :-) >> You could also ask for early allocation via the COSE WG, but that >> probably requires the document to be adopted first! > Does it? Or does the WG just need to approve of the document going > through any of the publication processes? If the document isn't adopted, then I don't think the WG chairs can ask the AD to approve. I think that adoption is the only required step; your document could take awhile to progress. IANA will check back on progress f= or the early allocation, to make sure the document is still of interest. >> That's what I would do: just ask for the values via Expert Review, a= nd >> live for now, with the a five-bye (encoded) COSE Algorithm code, if >> your market need is urgent. > Yes, I could just request the entries in the registry. However, I am > trying to be a good netizen; I want to have a document that people can > look at to understand what the registry items mean. While you don't have to provide a specification for Expert Review, I think that if you *do* that it will get recorded. If you later on get a 1-byte code allocated then, it's code complexity, but it's not too terrible, I thi= nk. At some point, your constrained devices will only use the 1-byte code, and your non-constrained devices will continue to be tolerant of both. >> Derek Atkins wrote: > We have customers who are >> looking to use this technology today, so we > would like to do it in= a >> standard way that others could understand. > Personally, I'm fine >> with an Informational (instead of Standards-track) > publication if >> that would make people happier. Even so, the RFC Editor > would sti= ll >> require approval from this WG as it is within their (the > WG's) are= a. >>=20 >> yes, if you went ISE, which would still take awhile. > I am fine going through the ISE, however I suspect that the IESG in > their conflict review would then go and ask this WG about it. So I > wanted to bring it up here, first. What is your definition of > "awhile"? Given the conflict review and the typical length of the RFC editor Producti= on queue, I would say you are looking at a year before AUTH48, but the early allocation could occur much sooner. =2D-=20 ] Never tell me the odds! | ipv6 mesh network= s [ ] Michael Richardson, Sandelman Software Works | IoT architect = [ ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails = [ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl1B7h0ACgkQgItw+93Q 3WW3tgf9FuNUNIdWx/IUWiCxn32wSF8aRELCxYKKepNvF3Gdcypd+JYxbeUtOIAP NfabCEKBpcY0DpUcYIGRwMDq2OQMQya8nZVpQBCcNFIIVUFTOqJXTR0C4+l/D4+q F3rnt5nqbkGUDh1ceV58ixItb+e1xEWyABO8xs/SIalKIGWFXfN/77Ol+Q5SoK5M wJhFE1CXl8DuW2Dvrbff/SzJ3rXqSDLJEDKHCf6atKoc4m4h6fD4REbYTKMReRhM 048piKfpw+vj1GIYEYh5wGKiXw8Pmid+NcT6DVIbNCe6jqxRxDvmcR21RSdqamVd 2QF1eRRp+2fKkMQttCNtF45k2FJvHw== =oBly -----END PGP SIGNATURE----- --=-=-=-- From nobody Wed Jul 31 17:11:18 2019 Return-Path: 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 DE4311200FF; Wed, 31 Jul 2019 17:11:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.2 X-Spam-Level: X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 DOLNT8zxN2-A; Wed, 31 Jul 2019 17:11:08 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D69E2120043; Wed, 31 Jul 2019 17:11:07 -0700 (PDT) Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x710B3BF009876 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 31 Jul 2019 20:11:05 -0400 Date: Wed, 31 Jul 2019 19:11:02 -0500 From: Benjamin Kaduk To: Michael Richardson Cc: Derek Atkins , "suit@ietf.org" , cose@ietf.org Message-ID: <20190801001102.GS1006@kduck.mit.edu> References: <835.1562080969@localhost> <28628.1564601885@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <28628.1564601885@localhost> User-Agent: Mutt/1.10.1 (2018-07-13) Archived-At: Subject: Re: [COSE] [Suit] draft-atkins-suit-cose-walnutdsa X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2019 00:11:10 -0000 On Wed, Jul 31, 2019 at 03:38:05PM -0400, Michael Richardson wrote: > > Derek Atkins wrote: > >> And the other two are Expert Review anyway, no specification required! > >> You are even listed as one of the experts for COSE Key Types :-) > > > Yes, I know I am one of the experts for these registries. However, I > > feel I must recuse myself from approval of these. > > Yes, obviously, but the point is that you will know how to ask nicely :-) > > >> You could also ask for early allocation via the COSE WG, but that > >> probably requires the document to be adopted first! > > > Does it? Or does the WG just need to approve of the document going > > through any of the publication processes? > > If the document isn't adopted, then I don't think the WG chairs can ask the > AD to approve. I think that adoption is the only required step; your > document could take awhile to progress. IANA will check back on progress for I think so, too. > the early allocation, to make sure the document is still of interest. Yes, a one-year extension with just the chairs' approval and subsequent ones with the IESG's approval. > >> That's what I would do: just ask for the values via Expert Review, and > >> live for now, with the a five-bye (encoded) COSE Algorithm code, if > >> your market need is urgent. > > > Yes, I could just request the entries in the registry. However, I am > > trying to be a good netizen; I want to have a document that people can > > look at to understand what the registry items mean. > > While you don't have to provide a specification for Expert Review, I think > that if you *do* that it will get recorded. If you later on get a 1-byte I think so, too. > code allocated then, it's code complexity, but it's not too terrible, I think. > At some point, your constrained devices will only use the 1-byte code, > and your non-constrained devices will continue to be tolerant of both. > > >> Derek Atkins wrote: > We have customers who are > >> looking to use this technology today, so we > would like to do it in a > >> standard way that others could understand. > Personally, I'm fine > >> with an Informational (instead of Standards-track) > publication if > >> that would make people happier. Even so, the RFC Editor > would still > >> require approval from this WG as it is within their (the > WG's) area. > >> > >> yes, if you went ISE, which would still take awhile. > > > I am fine going through the ISE, however I suspect that the IESG in > > their conflict review would then go and ask this WG about it. So I My understanding is that Adrian will be asking that even before the document gets far enough to need an IESG conflict review. > > wanted to bring it up here, first. What is your definition of > > "awhile"? > > Given the conflict review and the typical length of the RFC editor Production > queue, I would say you are looking at a year before AUTH48, but the early > allocation could occur much sooner. Adrian has been pressing the IESG to adhere better to the 4-week timeline for conflict review responses (modulo IETF meetings, etc.), but given the xmlv3 cutover and C238 breaking loose, it does seem reasonable to expect things to get backed up a bit. -Ben From nobody Wed Jul 31 17:15:29 2019 Return-Path: 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 7C933120110; Wed, 31 Jul 2019 17:15:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 3bXJLSNH8Tmc; Wed, 31 Jul 2019 17:15:25 -0700 (PDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A6E0120121; Wed, 31 Jul 2019 17:15:25 -0700 (PDT) Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id x710FEgk010996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 31 Jul 2019 20:15:17 -0400 Date: Wed, 31 Jul 2019 19:15:14 -0500 From: Benjamin Kaduk To: "Matthew A. Miller" Cc: iana-prot-param@iana.org, ietf@augustcellars.com, cose@ietf.org, cose-ads@ietf.org, ivaylo@ackl.io Message-ID: <20190801001513.GT1006@kduck.mit.edu> References: <005001d5461d$149a4c70$3dcee550$@augustcellars.com> <508a414d-6397-9d77-caac-d2371a2f9e05@outer-planes.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <508a414d-6397-9d77-caac-d2371a2f9e05@outer-planes.net> User-Agent: Mutt/1.10.1 (2018-07-13) Archived-At: Subject: Re: [COSE] [IANA #1148103] Early Code Point Assignments X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2019 00:15:28 -0000 As AD, I approve of the request (but defer to the Experts for what range from which to assign the values). -Ben On Wed, Jul 31, 2019 at 10:30:04AM -0600, Matthew A. Miller wrote: > As a Chair, I approve of this early assignment. > > > - m&m > > Matthew A. Miller > > On 19/07/31 09:51, Sabrina Tanamal via RT wrote: > > Hi Jim, all, > > > > Before we can make RFC 7120 early allocations for the registrations listed below, we need approval from a chair and an AD. > > > > Because these are Standards Action with Expert Review registries, we'll have to ask the designated experts for approval as well. > > > > Best regards, > > > > Sabrina Tanamal > > Senior IANA Services Specialist > > > > On Mon Jul 29 14:52:02 2019, ietf@augustcellars.com wrote: > >> Following the meeting in Montreal where I asked for the ability to do early > >> point assignment for documents in the working group and got permission, > >> these are the code points that I am assigning. I am only assigning points > >> that I know people are asking for now, some points will be setup later. > >> > >> For draft-ietf-cose-x509 (https://tools.ietf.org/html/draft-ietf-cose-x509): > >> > >> Table COSE Header Parameters > >> https://www.iana.org/assignments/cose/cose.xhtml#header-parameters > >> > >> Name Value > >> x5bag 32 > >> x5chain 33 > >> x5t 34 > >> x5u 35 > >> > >> For draft-ietf-cose-hash-algs > >> (https://tools.ietf.org/html/draft-ietf-cose-hash-algs): > >> > >> Table COSE Algorithms > >> https://www.iana.org/assignments/cose/cose.xhtml#algorithms > >> > >> Name Value > >> > >> SHA-1 -14 > >> SHA-256/64 -15 > >> SHA-256 -16 > >> SHA-384 -43 > >> SHA-512 -44 > >> SHA-512/256 -17 > >> SHAKE128 -18 > >> SHAKE256 -45 > >> > >> > >> Jim > >> > >> > > From nobody Wed Jul 31 18:30:00 2019 Return-Path: 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 66AA112011B for ; Wed, 31 Jul 2019 18:29:58 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.898 X-Spam-Level: X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 H0Ti-fahfBDZ for ; Wed, 31 Jul 2019 18:29:57 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 079061200B9 for ; Wed, 31 Jul 2019 18:29:57 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 1B7F0300B00 for ; Wed, 31 Jul 2019 21:10:39 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9QjEnhA3asag for ; Wed, 31 Jul 2019 21:10:38 -0400 (EDT) Received: from [172.20.4.59] (unknown [50.228.128.211]) by mail.smeinc.net (Postfix) with ESMTPSA id 8831D3005D6; Wed, 31 Jul 2019 21:10:37 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) From: Russ Housley In-Reply-To: Date: Wed, 31 Jul 2019 21:29:52 -0400 Cc: cose Content-Transfer-Encoding: quoted-printable Message-Id: References: <835.1562080969@localhost> To: Derek Atkins X-Mailer: Apple Mail (2.3445.104.11) Archived-At: Subject: Re: [COSE] draft-atkins-suit-cose-walnutdsa X-BeenThere: cose@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: CBOR Object Signing and Encryption List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Aug 2019 01:29:58 -0000 Derek: >> That's what I would do: just ask for the values via Expert Review, = and live >> for now, with the a five-byte (encoded) COSE Algorithm code, if your = market >> need is urgent. >=20 > Yes, I could just request the entries in the registry. However, I am > trying to be a good netizen; I want to have a document that people can > look at to understand what the registry items mean. I think that a document that includes the code point is the best outcome = here. Russ