Machine Readable Travel Documents - ICAO
Machine Readable Travel Documents - ICAO
Machine Readable Travel Documents - ICAO
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
III-4 <strong>Machine</strong> <strong>Readable</strong> <strong>Travel</strong> <strong>Documents</strong><br />
• EF.COM, containing version information and tag list;<br />
• EF.SOD, containing data integrity and authenticity information.<br />
7.4 All other Data Elements defined for recording by an issuing State or organization are OPTIONAL.<br />
7.5 Groupings of Data Elements added by receiving States or approved receiving organizations may<br />
or may not be present in an LDS. More than one recording of grouped Data Elements added by receiving<br />
States or approved receiving organizations can be present in the LDS.<br />
Note.— The ability for a receiving State or approved receiving organization to add data to the LDS<br />
is not supported in this edition of Doc 9303, Part 3.<br />
7.6 The LDS is considered to be a single cohesive entity containing the number of groupings of Data<br />
Elements recorded in the optional capacity expansion technology at the time of machine reading.<br />
Note.—The LDS has been designed with sufficient flexibility that it can be applied to all types of<br />
MRTD. Within the figures and tables which follow, some data items are only applicable to machine readable<br />
visas and to machine readable passports or require a different presentation in relation to these documents.<br />
These items should be ignored in relation to the eMRtds.<br />
7.7 Within the LDS, logical groupings of related Data Elements have been established. These logical<br />
groupings are referred to as Data Groups.<br />
7.8 Each Data Group is assigned a reference number. Figure III-2 identifies the reference number<br />
assigned to each Data Group, for example, “DG2” identifies Data Group # 2, Encoded Identification Feature(s)<br />
for the face of the rightful holder of the MRtd (i.e. facial biometric details).<br />
8. DATA GROUPS CODED TO ALLOW CONFIRMATION OF<br />
AUTHENTICITY AND INTEGRITY OF DATA<br />
To allow confirmation of the authenticity and integrity of recorded details, an authenticity/integrity object is<br />
included. Each Data Group MUST be represented in this authenticity/integrity object, which is recorded within<br />
a separate elementary file (EF.SOD). (Refer to Section IV, PKI, for details.) Using the CBEFF structure utilized<br />
for Encoded Identification Feature Data Groups 2-4 and optional “additional biometric security” features<br />
defined in Section IV, PKI, identity confirmation details (e.g. biometric templates) MAY also be individually<br />
protected at the discretion of the issuing State or organization.