Difference between revisions of "Mobile Driver's License Presentation"
From MgmtWiki
(→Transaction) |
(→Request) |
||
| Line 20: | Line 20: | ||
*Format is CBOR - represented here as json. | *Format is CBOR - represented here as json. | ||
==Request== | ==Request== | ||
| + | {| class="wikitable" style="text-align: center;" | ||
| + | !data | ||
| + | ! colspan="4" |Data item 1 | ||
| + | ! colspan="4" |Data item 2 | ||
| + | !Data item X... | ||
| + | |- | ||
| + | !scope="row" |Byte count | ||
| + | | colspan="2" |1 byte (CBOR data item header) | ||
| + | |Variable | ||
| + | |Variable | ||
| + | | colspan="2" |1 byte (CBOR data item header) | ||
| + | |Variable | ||
| + | |Variable | ||
| + | |etc... | ||
| + | |- | ||
| + | !scope="row"|Structure | ||
| + | |Major type | ||
| + | |Additional information | ||
| + | |Payload length (optional) | ||
| + | |Data payload (optional) | ||
| + | |Major type | ||
| + | |Additional information | ||
| + | |Payload length (optional) | ||
| + | |Data payload (optional) | ||
| + | |etc... | ||
| + | |- | ||
| + | !scope="row"|Bit count | ||
| + | |3 Bits | ||
| + | |5 Bits | ||
| + | |8 Bits × variable | ||
| + | |8 Bits × variable | ||
| + | |3 Bits | ||
| + | |5 Bits | ||
| + | |8 Bits × variable | ||
| + | |8 Bits × variable | ||
| + | |etc.. | ||
| + | |} | ||
| + | |||
==Response== | ==Response== | ||
Revision as of 18:43, 14 January 2021
Full Title or Meme
Mobile Driver's License Presentation maps ISO 18013-5 wallet presentation to DIF Presentation Exchange.
Context
- The DIF Presentation Exchange is looking for test cases. This is such a test case (ie a use case with teeth).
- This use case looks at the wallet as the source of Presentation Statements, which is not necessarily the full scope of the DIF WG.
Actors
- Holder = The entity that submits proofs to a Verifier to satisfy the requirements described in a Presentation Definition (may or may not be the subject)
- mDL holder = individual to whom an mDL is issued = legitimate holder of the driving privileges reflected on an mDL = subject of the mDL
- Verifier = The entity that defines what proofs they require from a Holder (via a Presentation Definition) in order to proceed with an interaction.
- mDL verifier = entity using an mDL reader to verify an mDL
- Issuing Authority = trusted signer of data elements
Transaction
- The holder and verifier establish a session
- The verifier asks for mDL data
- mDL send data by value or by reference
- The verifier may or may not request other data
- Transport can be by various NFC or QR code.
- Format is CBOR - represented here as json.
Request
| data | Data item 1 | Data item 2 | Data item X... | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Byte count | 1 byte (CBOR data item header) | Variable | Variable | 1 byte (CBOR data item header) | Variable | Variable | etc... | ||
| Structure | Major type | Additional information | Payload length (optional) | Data payload (optional) | Major type | Additional information | Payload length (optional) | Data payload (optional) | etc... |
| Bit count | 3 Bits | 5 Bits | 8 Bits × variable | 8 Bits × variable | 3 Bits | 5 Bits | 8 Bits × variable | 8 Bits × variable | etc.. |
Response
Reference
- GitHub issues of the Presentation Exchange.
