|
CBEFF
Patron is an organization that has defined a standard or
specification incorporating a biometric data object that meets CBEFF
requirements. Examples of CBEFF Patrons are the BioAPI Consortium and ANSI
Subcommittee X9, Group F4.
CBEFF
Client is an entity that defines a specific biometric data
structure (e.g., a BSMB format owner) that meets CBEFF requirements. This
would include any vendor, standards body, working group, or industry
consortium that has registered itself with IBIA and has defined one or
more BSMB format types.
There
can be several different derived Patron File Formats. All Patron Formats
that meet the CBEFF requirements need to include the data elements
identified in CBEFF as “required”.
Each
Patron Format specifies:
(1)
Encoding
of the data elements (i.e. packaging of the data with reference
information)
(2)
Additional
(non-common) data elements
(3)
Which
Optional Fields are present and how the data elements are extracted
and processed
Each
Patron defines a Domain
Of Use (the context in which a format should be
used). It is intended that there be a limited number of formats with a
minimum of overlap in the areas (Domains) where the data is used. However,
there may be new technologies that have adopted new encoding rules and
require a new formatting.
For
a copy of a diagram describing the relationship between CBEFF, CBEFF
Patron Formats, and CBEFF Clients, please click
here, (9KB - pdf file)
Three
Patron Formats were identified in NISTIR 6529:
Patron Format A - The CBEFF Data Structure
Patron:
CBEFF (www.nist.gov/cbeff)
Domain
Of Use: Patron Format A is intended for small embedded or legacy
systems that have limited data storage capabilities. This format assumes
that the embedded system is not required to be BioAPI compliant.
This
format implies that default mechanisms are used for the signature and/or
encryption (There is not enough information to process a signature or
encryption process without assuming default values which are generally
passed with signed/encrypted data). Therefore this Format is NOT intended
to be passed between systems, it is intended for the local system only.
Patron
Format
B - The BioAPI Specification v1.0 Biometric Identification Record Format
Patron:
BioAPI Consortium (www.bioapi.org)
Domain
Of Use: Patron Format B is intended for applications that are BIOAPI
compliant. These systems are only required to store data and possibly
exchange data between a client and a Server.
The
BioAPI Consortium has published BioAPI Specification Version 1.0 and the
BioAPI Reference Implementation. The BioAPI Biometric Identification
Record (BIR) conforms to CBEFF v1.0.
Patron
Format C - Draft ANSI Standard X9.84 Biometric Object
Patron:
ANSI Subcommittee X9, Working Group F4.
Domain
Of Use: Patron Format C is intended for large systems that need to exchange
biometric information in a secure, authenticate-able manor.
X9.F4
is the Standards Working Group that has developed draft ANSI standard
X9.84, “Biometric Information Management and Security”. X9.84 suggests
the encoding of biometric data and defines the syntax via ASN.1 (refer to
Appendix C for the description of biometric data that meets their security
requirements). Refer to the
X9.84 draft ANSI standard, when it becomes publicly available.
When
existing Patron Formats are determined to be insufficient to meet the
requirements and constraints of the intended implementation, new CBEFF
Patron Formats can be added or created. For
information on how to add new CBEFF Patron Formats, please
click here.
NISTIR
6529 describes how CBEFF Patron Formats can be created when existing
Patron Formats are determined to be insufficient to meet the requirements
and constraints of the intended implementation.
The
authors will propose to the recently established Biometric
Interoperability, Performance, and Assurance Working Group,
a new initiative sponsored by NIST and the
Biometric Consortium, to take
on the responsibility to address these new requests and coordinate with
the requestor of new Patron Formats development of the new format.
In
the request for a new format the requestor needs to include:
(1)
The
intended Domain Of Use (where will it be used and how it differs from
the currently supported domains). A description of why one of the
existing Patron Formats cannot be used is suggested.
(2)
Additional
field descriptions that will be added (if known). (3)
The
reference document that will be created which describes the entire
format and its use.
(4)
The
timeframe in which the new format will be developed.
Home
| Background | Benefits
| Scope | CBEFF
Data Elements
Patron
Biometric File Formats | Format
Owner and Format Type Registration Adding
New CBEFF Patron Formats | Future
Plans Technical
Development Team | Contacts |
Related
Events/Activities
|
