Document ID: chunk:federal_register_of_legislation:F2024L01443:body:0:p52
Version: federal_register_of_legislation:F2024L01443
Segment Type: other
Provision Reference: 
Character Range: 180536–183966

in Table 8 above.
 An IXP MUST request express consent from the individual on every use of the Verified Documents attribute set.

 An IXP MUST NOT broker requests for Verified Documents for assurance levels weaker than IP2. An IXP MUST support brokering of attribute requests for a single or multiple Verified Documents. An IXP MUST only broker attribute requests for Verified Documents from approved PRPs.
 An ISP MUST support attribute request for single or multiple Verified Documents.

 When processing generic requests for Verified Documents, an ISP MUST prepare a response that conforms to IP2 or higher.

 When processing requests for specific Verified Documents, an ISP MUST only respond to request for valid document types and for documents the individual has verified. Valid document types are outlined in Table 11 below.

 The data representation for a Verified Document is set of named simple and complex attributes. Each set representing an instance of a Verified Document MUST have the following members:

      1.             Document Type Code with a value that MUST be one of the URNs outlined in Table 11 below;
      2.             Document Verification Method that MUST be one of the enumerated values in Table 12 below;
      3.             Document Verification Date MUST be valid a date and time value;
      4.             Document Date of Birth MUST be a valid date extracted from the document;
      5.             Document Identifiers is a collection that MUST contain one or more document identifiers outlined in the document type's schema;
      6.             Document Names is a collection that MUST contain the required document names for the document type's schema;
      7.             Document Attributes is a collection that MUST contain the required document attributes outlined in the document type's schema.

 A more detailed overview of the fields is provided in Table 9 below.

 An ISP's attribute response for each document MUST be conformant to the schema for that document's type. Schemas for each document type make use of the enumerations outlined in the following tables and the schemas for each document type are outlined in the following sections.

 Table 9 Verified document structure

Field                         Description                                                                                                                                                 Data representation
Document Type Code            A URN representing the type of document. To be a valid the URN MUST be specified in this profile.                                                           The valid URNs are enumerated in Table 11 below.
Document Verification Method  The verification method that was used to verify the document during the identity proofing process.                                                          A single character string enumerating the document verification methods.

                              The Verification Method in the response MUST match one the values outlined in this profile.                                                                 The enumeration is outlined in Table 12 below of these values for the AGDIS.
Document Verification Date    The date and time the document was verified.                                                                                                                A string representing the RFC 3339 date time