INTRO TO What is ITU-T.1254 flowing text introduction to the ITU thing plus arguments for using itand why to use it?
The following generalised functional units (actions) serve to design and implement the vetting scenarios for second factor and multifactor authentication that fulfil some of ITU-T X.1254 entity authentication assurance framework processes. The following processes from its "8.1 Enrollment phase" are to be covered:
...
The names and descriptions used in these elaborations aim to be mappable to those processes and be terminologically compatible with ITU-T X.1254 and its definitions of terms. An additional specifics in relation the above-listed processes is that they focus on the credentials (sets of data supporting identity or entitlement claims), while our scenarios are focused on authentication factors (something specific that is possessed, known or inherent). The subject entities are referred to as applicants, who are the physical persons whose identity is to be authenticated.
These The below are now descriptions our use own terminology
These below is a vocabulary developed by ourselves
Factors terminology, slightly shifted terminology, e.g. factors vs credentials.
Explain CIVB sections, 3 general phasesActions are grouped in four sections: Common Actions, three general phases (Initiation, Verification, Binding).
Descriptions of actions are process and flow oriented, not data-oriented. therefor, the descriptions of inputs Inputs and outputs descriptions are therefore rather informal.
C: Common Actions
...