-
Hi @rascafr well job and great work for this Eu-qr-parser, It seem to work very well after several hours of search ...
But Id like to know why I can read the data from : (https://ehealth.vyncke.org/…
-
The challenger could inject identifying information into the nonce claim.
Do you need to say something specific about this?
-
RATS architecture and other documents describe architecture for freshness that doesn't use a nonce. EAT should support them.
-
2 reasons:
a) Neither RFC 8392 (CWT) nor RFC 7519 (JWT) have operational models. Since EAT is derived from these specifications, it would be desirable to maintain consistency.
b) This topic is …
-
UCCS refers to a CWT claims set. "Unprotected" is redundant. That change would makes the CBOR header 'kccs' more natural.
-
**Affected Country**: ES
## Issue Description
ES is not using integer NumericDate format for attributes Issued At and Expiration Time in CWT Structure (payload section).
Official documentation …
-
This may be a bit of a minor point, but I would like to point it out because it bothered me when I read this specification.
This specification does not explicitly specify the structure of COSE. Spe…
-
Many of the classes that I would like to access is package private, for example CBORUtilities, PropertyMap. Is there a reason that you don't expose all of your classes?
-
Guidance on verification procedures not covered in document. It is touched upon in Sec. 1.3, but not to the level described in comparable specifications (see https://www.w3.org/TR/webauthn/#defined-a…
-
A compilation of all nits:
== Line 497 has weird spacing: '...rotocol name ...'
== Line 901 has weird spacing: '...rotocol name ...'
== The document seems to lack the recommended RFC 2119 boi…