Encodings File Syntax

Language:

The label_encodings file contains a VERSION specification and seven mandatory sections:

CLASSIFICATIONS
INFORMATION LABELS
SENSITIVITY LABELS
CLEARANCES
CHANNELS
PRINTER BANNERS
ACCREDITATION RANGE

The sections must appear in that order. An optional LOCAL DEFINITIONS section can follow.

In the following table, mandatory keyword means only that the keyword must be present. Not all keywords must have definitions. The notes for each section indicate what must be defined and what is optional.

Table 3-1 label_encodings Keywords

Section	Notes
`VERSION=`	Mandatory keyword. The version specification is the single keyword `VERSION=`, followed by a character string that identifies this particular version of encodings.
`CLASSIFICATIONS:`	Mandatory keyword. At least one classification must be defined.
`INFORMATION LABELS:` `WORDS:` `REQUIRED COMBINATIONS:` `COMBINATION CONSTRAINTS:`	Mandatory keywords. Even though information labels are not used in Trusted Extensions software, you must assign one bit to an information label word for each bit that you assign to a sensitivity label word. The sensitivity label words are defined in the following section.
`SENSITIVITY LABELS:` `WORDS:` `REQUIRED COMBINATIONS:` `COMBINATION CONSTRAINTS`	Mandatory keywords, although the `WORDS` definitions are optional. If you define sensitivity label words, the same bits must be assigned to `WORDS` in both the `INFORMATION LABELS` and `CLEARANCES` sections. The words that are assigned to the bits do not need to be the same.
`CLEARANCES:` `WORDS:` `REQUIRED COMBINATIONS:` `COMBINATION CONSTRAINTS`	Mandatory keywords. One bit must be assigned to a clearance word for any sensitivity label word that you have defined. Clearance labels can allow combinations of words that have been disallowed in the definitions for sensitivity label words.
`CHANNELS:`	Mandatory keyword.
`PRINTER BANNERS:`	Mandatory keyword.
`ACCREDITATION RANGE:`	Mandatory keyword. A rule must be defined for each classification name. The minimum clearance, minimum sensitivity label, and minimum “Protect As” classification must be defined.
`LOCAL DEFINITIONS:`	Optional keyword.

For all the required sections, the keywords in the preceding table must be present, but not all of the sections must have definitions. For example, a label_encodings file with only CLASSIFICATIONS and ACCREDITATION RANGE definitions is valid.