Difference between revisions of "Mobile Driver's License Presentation"

From MgmtWiki
Jump to: navigation, search
(→‎Request)
(→‎Request)
Line 19: Line 19:
 
*Transport can be by various NFC or QR code.
 
*Transport can be by various NFC or QR code.
 
*Format is CBOR - represented here as json.
 
*Format is CBOR - represented here as json.
−
==Request==
+
==Security==
 
{| class="wikitable" style="text-align: center;"
 
{| class="wikitable" style="text-align: center;"
 
!data
 
!data
Line 28: Line 28:
 
!scope="row" |Device request
 
!scope="row" |Device request
 
| colspan="4" |The point of this piece is the assurance that the device is trustworthy
 
| colspan="4" |The point of this piece is the assurance that the device is trustworthy
 +
| colspan="2" |1 byte (CBOR data item header)
 +
|Variable
 +
|Variable
 +
|etc...
 +
|-
 +
!scope="row"|version
 +
| colspan="4" |tstr
 +
|Additional information
 +
|Payload length (optional)
 +
|Data payload (optional)
 +
|etc...
 +
|-
 +
!scope="row"|Security
 +
|3 Bits
 +
|5 Bits
 +
|8 Bits × variable
 +
|8 Bits × variable
 +
|3 Bits
 +
|5 Bits
 +
|8 Bits × variable
 +
|8 Bits × variable
 +
|etc..
 +
|}
 +
==Request==
 +
{| class="wikitable" style="text-align: center;"
 +
!data
 +
! colspan="4" |mDL
 +
! colspan="4" |DIF
 +
!Comments
 +
|-
 +
!scope="row" |Encryption
 +
| colspan="4" |Encrypting with authentication of the mdoc requests and mdoc responses with the session key protects mdoc data from eavesdropping and alteration.
 
| colspan="2" |1 byte (CBOR data item header)
 
| colspan="2" |1 byte (CBOR data item header)
 
|Variable
 
|Variable

Revision as of 13:10, 15 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

  1. The holder and verifier establish a session
  2. The verifier asks for mDL data
  3. mDL send data by value or by reference
  4. 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.

Security

data mDL DIF Comments
Device request The point of this piece is the assurance that the device is trustworthy 1 byte (CBOR data item header) Variable Variable etc...
version tstr Additional information Payload length (optional) Data payload (optional) etc...
Security 3 Bits 5 Bits 8 Bits × variable 8 Bits × variable 3 Bits 5 Bits 8 Bits × variable 8 Bits × variable etc..

Request

data mDL DIF Comments
Encryption Encrypting with authentication of the mdoc requests and mdoc responses with the session key protects mdoc data from eavesdropping and alteration. 1 byte (CBOR data item header) Variable Variable etc...
version tstr Additional information Payload length (optional) Data payload (optional) etc...
docRequests 3 Bits 5 Bits 8 Bits × variable 8 Bits × variable 3 Bits 5 Bits 8 Bits × variable 8 Bits × variable etc..

Response

Reference

Retrieved from "http://tcwiki.azurewebsites.net/index.php?title=Mobile_Driver%27s_License_Presentation&oldid=9101"