W3C home > Mailing lists > Public > public-credentials@w3.org > February 2020

Re: Real BTCR DID Document

From: Christopher Allen <ChristopherA@lifewithalacrity.com>
Date: Wed, 12 Feb 2020 21:23:05 -0800
Message-ID: <CACrqygAmxfCGEw6X9p5mykSPK2LrcpX0A6m_2A5AOb6dDM9DVw@mail.gmail.com>
To: Leonard Rosenthol <lrosenth@adobe.com>, Mike Jones <Michael.Jones@microsoft.com>
Cc: Dave Longley <dlongley@digitalbazaar.com>, Wolf McNally <wolf@wolfmcnally.com>, "public-credentials@w3.org" <public-credentials@w3.org>
On Wed, Feb 12, 2020 at 1:53 PM Leonard Rosenthol <lrosenth@adobe.com>

> To Chris’s original question – I’ve been using a fork of
> https://github.com/Thalhammer/jwt-cpp for our JWS/JWT work (though not
> DID specific).   (FWIW: my fork adds support for non-JSON payloads and
> detached signatures)
Thanks, Leonard, this is useful.

My challenge is that I’ve yet to find a library that supports the secp256k1
magic values as proposed in
https://tools.ietf.org/html/draft-ietf-cose-webauthn-algorithms-05 but is
not in the RFC that jwt-cpp code yet.

Mike Jones, what is the status of this internet draft to become an RFC? Do
you have any reference examples I can test against? Section 3.1 and 3.2
specify the magic values, but there are no test vectors.

— Christopher Allen

Received on Thursday, 13 February 2020 05:23:30 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:57 UTC