VICAL - Revision history

Tom: /* ISO */

2021-09-03T15:58:53Z

‎ISO

2021-09-03T15:29:43Z

‎References

2021-08-16T18:26:49Z

‎AAMVA

2021-08-12T01:54:15Z

‎ISO

2021-08-11T04:34:01Z

‎ISO

2021-08-11T01:13:51Z

‎ISO

2021-08-11T01:13:11Z

‎ISO

2021-08-11T01:12:31Z

‎References

2021-08-11T01:03:12Z

‎Full Title

2021-08-11T01:01:58Z

‎AAMVA

@@ Line 9: / Line 9: @@
 * Given the limited scope, number of participants and expected duration of the MVP... AAMVA does not believe it is required that the solution reside in a [[FedRamp]] certified/compliant environment.
-==ISO==
+==ISO 18013-5==
-A.1.1.1       Master list CDDL profile
+APPENDIX  -     Master list CDDL profile
 The master list profile uses a COSE_Sign structure with the X509 (chain) element from draft-ietf-cose-x509-07 to the ML signer certificate.

@@ Line 7: / Line 7: @@
 *The VICAL is validated by verification of the VICAL signing key which will be provided to the RPs. Any specific requirements from a governance/policy perspective regarding the requirements that must be met for inclusion in the MVP will be determined at a later time
 * AAMVA’s desire is that during normal VICAL generation and signing that AAMVA personnel would not need to be involved. However, if you feel that it is important feel free to propose it.
-* Given the limited scope, number of participants and expected duration of the MVP... AAMVA does not believe it is required that the solution reside in a FedRamp certified/compliant environment.
+* Given the limited scope, number of participants and expected duration of the MVP... AAMVA does not believe it is required that the solution reside in a [[FedRamp]] certified/compliant environment.
 ==ISO==

@@ Line 20: / Line 20: @@
     "type" : tstr      ; currently "1.0"
     "version" : tstr     : currenlty "1.0"
-    "date" : tdate     ; date-time according to RFC 7049
+    "date" : tdate     ; date-time according to RFC 7049 (eg 1990-12-31T23:59:60Z)
     ? "nextUpdate" : tdate ; date-time according to RFC 7049
     "certificateInfo : [+ CertificateInfo]

@@ Line 15: / Line 15: @@
 The master list profile uses a COSE_Sign structure with the X509 (chain) element from draft-ietf-cose-x509-07 to the ML signer certificate.
-The payload shall use the following CDDL structure:
+The payload shall use the following [[CDDL]] structure:
   MasterList = {

@@ Line 24: / Line 24: @@
     "certificateInfo : [+ CertificateInfo]
+  }
-−
   CertificateInfo = {
     "issuingCountry": tstr ; ISO3166-1 or ISO3166-2 depending on the issuer

@@ Line 25: / Line 25: @@
+  }
   CertificateInfo = {
     "issuingCountry": tstr ; ISO3166-1 or ISO3166-2 depending on the issuer
@@ Line 34: / Line 33: @@
+   }
   CertStructure = {
     ? "DN": bstr

@@ Line 8: / Line 8: @@
 * AAMVA’s desire is that during normal VICAL generation and signing that AAMVA personnel would not need to be involved. However, if you feel that it is important feel free to propose it.
 * Given the limited scope, number of participants and expected duration of the MVP... AAMVA does not believe it is required that the solution reside in a FedRamp certified/compliant environment.
 ==References==
 [[Category: Trust]]

@@ Line 1: / Line 1: @@
 ==Full Title==
-The [[VICAL]] is the new name for the ISO 18013-5 master list of certificates for issuers (and perhaps others) for [[Mobile Driver's License]]s.
+The [[VICAL]] I(Verified issuer certificate authority list) s the new name for the ISO 18013-5 master list of certificates for issuers (and perhaps others) for [[Mobile Driver's License]]s.
 ==AAMVA==