IETF Logo Mail Archive

Re: [Suit] [COSE] draft-atkins-suit-cose-walnutdsa

Benjamin Kaduk <kaduk@mit.edu> Thu, 01 August 2019 22:28 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: suit@ietfa.amsl.com
Delivered-To: suit@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7797C1201CF; Thu, 1 Aug 2019 15:28:43 -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 5GglAbL7FWhg; Thu, 1 Aug 2019 15:28:41 -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 418CD120241; Thu, 1 Aug 2019 15:28:41 -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 x71MSafH005893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 1 Aug 2019 18:28:38 -0400
Date: Thu, 01 Aug 2019 17:28:36 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Derek Atkins <derek@ihtfp.com>
Cc: Russ Housley <housley@vigilsec.com>, suit@ietf.org, cose <cose@ietf.org>
Message-ID: <20190801222835.GJ1006@kduck.mit.edu>
References: <AM0PR08MB33796BC8E8E7A039525EC5C3E8150@AM0PR08MB3379.eurprd08.prod.outlook.com> <sjm7e90zfo5.fsf@securerf.ihtfp.org> <835.1562080969@localhost> <sjm36imutkc.fsf@securerf.ihtfp.org> <BFA23FAF-436A-42CC-A1D3-B02B4AC753EB@vigilsec.com> <sjmimrht021.fsf@securerf.ihtfp.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <sjmimrht021.fsf@securerf.ihtfp.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/suit/el4OD-mUmpkGateexaT4Sf7c3pc>
Subject: Re: [Suit] [COSE] draft-atkins-suit-cose-walnutdsa
X-BeenThere: suit@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Software Updates for Internet of Things <suit.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/suit>, <mailto:suit-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/suit/>
List-Post: <mailto:suit@ietf.org>
List-Help: <mailto:suit-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/suit>, <mailto:suit-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Aug 2019 22:28:44 -0000

On Thu, Aug 01, 2019 at 10:47:18AM -0400, Derek Atkins wrote:
> Russ Housley <housley@vigilsec.com> writes:
> 
> > 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.
> >> 
> >> 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.
> 
> So I guess the question is:  Does the COSE WG want to adopt this draft?

Note that we'd have to recharter to take it on.

-Ben

> Or should I submit to ISE?
> 
> Thanks,
> 
> > Russ
> 
> -derek
> -- 
>        Derek Atkins                 617-623-3745
>        derek@ihtfp.com             www.ihtfp.com
>        Computer and Internet Security Consultant
> 
> _______________________________________________
> Suit mailing list
> Suit@ietf.org
> https://www.ietf.org/mailman/listinfo/suit

v2.23.0 | Report a Bug | By Email