W3C home > Mailing lists > Public > public-webauthn@w3.org > October 2016

AW: why is "Public key algorithm and encoding" 2 bytes long?

From: Rolf Lindemann <rlindemann@noknok.com>
Date: Wed, 26 Oct 2016 16:05:44 -0700
To: "'Vijay Bharadwaj'" <vijaybh@microsoft.com>, "'Hodges, Jeff'" <jeff.hodges@paypal.com>, "'W3C WebAuthn WG'" <public-webauthn@w3.org>
Message-ID: <019f01d22fdd$7beea140$73cbe3c0$@noknok.com>
Yes, I think it was.

-----Ursprüngliche Nachricht-----
Von: Vijay Bharadwaj [mailto:vijaybh@microsoft.com] 
Gesendet: Mittwoch, 26. Oktober 2016 10:57
An: Hodges, Jeff; W3C WebAuthn WG
Betreff: RE: why is "Public key algorithm and encoding" 2 bytes long?

This was inherited from FIDO I believe. It was in the initial submission of
attestation formats. Rolf?

-----Original Message-----
From: Hodges, Jeff [mailto:jeff.hodges@paypal.com] 
Sent: Tuesday, October 25, 2016 3:18 PM
To: W3C WebAuthn WG <public-webauthn@w3.org>
Subject: why is "Public key algorithm and encoding" 2 bytes long?

in S 5.3.3 "Generating an Attestation Statement"
{#generating-an-attestation-statement}, the "Public key algorithm and
encoding" is described as..

  Public key algorithm and encoding (16-bit big-endian value). Allowed

    1. 0x0100. This is raw ... Elliptic Curve public key [SEC1] ...

    2. 0x0102.  Raw encoded RSA ... public key [RFC3447] ...


1. Why do we need to use two bytes here?

2. Were there any particular reasons the values of 0x0100 and 0x0102 were

3. This "Public key algorithm and encoding" does not seem to be used as a
set of bit flags ... is there any reason we cannot use a single byte here,
which would ostensibly have enough distinct values to represent whatever
different PK key types and encodings evolve in the future?


Received on Wednesday, 26 October 2016 23:06:15 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 07:26:23 UTC