ISO/IEC 7816-4
Identification cards — Integrated circuit cards — Part 4: Organization, security and commands for interchange
Cartes d’identification — Cartes à circuit intégré — Partie 4: Organisation, sécurité et commandes pour les échanges

File control information
By definition, the file control information is the byte string available in response to the SELECT command (see 7.1.1); it may be present for any structure, i.e., any DF and any EF.
–If the first byte is valued from ’00′ to ‘BF’, then the byte string shall be BER-TLV encoded. ISO/IEC JTC 1/ SC 17 reserves for future use all the values in the range ’00′ to ‘BF’ that are not defined in this document.
–If the first byte is valued from ‘C0′ to ‘FF’, then the byte string is not encoded according to this document. Table 11 shows three interindustry templates for nesting file control information BER-TLV data objects.
–The FCP template is a set of file control parameters, i.e., logical, structural and security attributes as listed in Table 12 and defined hereafter. Within the FCP template, the context-specific class (first byte from ’80′ to ‘BF’) is reserved for file control parameters; tags ’85′ and ‘A5′ reference discretionary data.
–The FMD template is a set of file management data, i.e., interindustry data objects such as an application identifier as defined in 8.2.1.2, an application label as defined in 8.2.1.4 and an application expiration date as defined in ISO/IEC 7816-6, possibly nested within an application template as defined in 8.2.1.3. Within the FMD template, tags ’53′ and ’73′ reference discretionary data.
–The FCI template is a set of file control parameters and file management data.

Table 11 Interindustry templates for file control information
Tag Value
’62′ Set of file control parameters (FCP template)
’64′ Set of file management data (FMD template)
’6F’ Set of file control parameters and file management data (FCI template)

  The three templates may be retrieved according to selection options of the SELECT command (see Table 40).
–If the FCI option is set, then the FCI tag is optional for introducing the template in the response data field.
–If the FCP or FMD option is set, then the corresponding tag is mandatory for introducing the template.

     Table 12 lists the file control parameters, all in the context-specific class. When a control parameter is present for a file, the Table says whether it occurs only once (explicit indication), or it may be repeated (no indication).

Table 12 File control parameter data objects
Tag Length Value   Applies to
’80′ Var. Number of data bytes in the file, excluding structural information   Any EF, Once
’81′ 2 Number of data bytes in the file, including structural information if any   Any file, Once
’82′ 1 File descriptor byte (see 5.3.3.3 and Table 14)   Any file
3 or 4 File descriptor byte, data coding byte and maximum record size on one or two bytes   Any EF supporting records
’83′  2 File identifier   Any file
’84′ up to 16 DF name   Any DF
’85′ Var. Proprietary information not encoded in BER-TLV    Any file
’86′ Var. Security attribute in proprietary format   Any file
’87′ 2 Identifier of an EF containing an extension of the file control information   Any DF, Once
’88′ 0 or 1 Short EF identifier (see 5.3.3.1)   Any EF, Once
’8A’ 1 Life cycle status byte (LCS byte, see 5.3.3.2 and Table 13)   Any file, Once
’8B’ Var. Security attribute referencing the expanded format (see 5.4.3.3 and Table 25)   Any file, Once
’8C’ Var. Security attribute in compact format (see 5.4.3.1)   Any file, Once
’8D’ 2 Identifier of an EF containing security environment templates (see 6.3.4)   Any DF
’8E’ 1 Channel security attribute (see 5.4.3 and Table 15)   Any file, Once
‘A0′ Var. Security attribute template for data objects (see 5.4.3)   Any file, Once
‘A1′ Var. Security attribute template in proprietary format   Any file
‘A2′ Var. Template consisting of one or more pairs of data objects:  Short EF identifier (tag ’88′) – File reference (tag ’51′, L > 2, see 5.3.1.2)   Any DF
‘A5′ Var. Proprietary information encoded in BER-TLV    Any file
‘AB’ Var. Security attribute template in expanded format (see 5.4.3.2)   Any file, Once
‘AC’ Var. Cryptographic mechanism identifier template (see 5.4.2)   Any DF
In this context, ISO/IEC JTC 1/SC 17 reserves any other data object of the context-specific class (first byte from ’80′ to ‘BF’).

Part of the control information of a DF may additionally be present in an EF under the control of an application and referenced by tag ’87′ in the file control parameters. If present within such an EF, file control information shall be introduced by the appropriate tag, either a FCP tag, or a FCI tag.