The 2nd mDL Prototype Interoperability Party is coming!
What is it about?
The ISO 18013-5 mDL standard defines interface specifications for the implementation of a mobile driver’s license (mDL). The implementation of the standard, by issuing authorities and their suppliers in various mDL solutions, should contribute to a secure and interoperable mDL ecosystem.
The ISO working group (ISO/IEC JTC1/SC17/WG10) has worked towards the standardization of mDL since 2014. After a successful first interoperability party in October 2018, held in Okayama, Japan, an updated draft of the ISO/IEC 18013-5 standard was issued in March 2019. This draft mDL standard forms the basis for the next mDL test event.
The first North American edition of the mDL Prototype Interoperability Party will be hosted by the American Association of Motor Vehicle Administrators (AAMVA) at the eve of their Annual International Conference (AAMVA AIC 2019), is endorsed by EReg and Austroads, and is coordinated by UL.
The mDL Prototype Interoperability Party took place on August 18 and 19, 2019; the AAMVA AIC takes place on August 20-22, both in Omaha, NE, USA. The preliminary results of the mDL test event will be presented to the AAMVA AIC on Thursday, August 22.
What is going to happen in the event?
For the event, over 70 participants have registered, bringing 33 mDL prototype implementations (15 mDL and 18 mDL reader implementations). Participants include mDL solution providers, and a dozen of independent observers representing, amongst others, AAMVA, EReg and Austroads.
On the 1st day, August 18, participants were invited to demonstrate their prototype mDL and/or mDL Reader implementations, to verify and confirm that the implementations match with the registered configuration, as declared in the Implementation Conformance Statement (ICS) upon registration. This is a closed door session for each registered mDL/mDL Reader provider with UL, the coordinator of the event, in attendance of the independent observers.
On the 2nd day, August 19, cross-over tests between mDL implementation and mDL reader implementation is conducted. Each mDL and mDL reader combination will be given a session of 20 minutes to try out a number of transactions using the various technologies supported by the standard. For each transaction, participants check whether the applicable data is transferred and whether mandatory security mechanisms have been implemented. After all combinations of mDLs and mDL Readers have met each other, participants are free to use a 2-hour window for debugging and regression testing.
How does UL contribute the event?
Following up on last year’s first edition in Japan, UL is coordinating the mDL interoperability party once again, this time in collaboration with AAMVA, who have been a leading participant in and supporter of the international standardization work. UL is in the position of leading discussions about the scope of the event and clarification of interpretation and implementation issues with the standard. UL is also in charge of documentation including the guidance document, test report and publication of results. In addition, UL manages registration of participants, communication, scheduling and on-site coordination.
Why are we doing this?
The main objectives of the event are to test interoperability of functions standardized in the latest draft of ISO/IEC 18013-5 between implementations of different mDL solution providers, to keep momentum in the industry, and to generate further feedback on the draft standard.
The event allows issuing authorities, mDL solution providers, and the standardization community to
- try out prototype implementations
- evaluate the interoperability of their implementation with other prototypes
- confirm their interpretation of the draft standard
- generate further feedback to clarify requirements, and to enhance uniform interpretation of provisions in the standard under development
We hope that our efforts in standardization and testing, which includes coordination of America’s first mDL Prototype Interoperability Party, contribute to the rollout of a well-functioning, highly trustworthy and interoperable mDL ecosystem.