Errata for SP 800-76 

Date Section/Table, Page Change 

3/13/06 Sec.3.3.2 Para 1. Page 12 “Further, each finger's template record shall be individually wrapped 

in the CBEFF structure...” shall read as “Further both fingers' template 

records shall be wrapped in a single CBEFF structure ...” 

April 17, 2006: NOTE: The intent here is that the minutia record from 

both the primary and secondary fingers should reside within a single 

INCITS 378 record. That means there shall be: 

1. one instance of the CBEFF Header (Table 7, Sec. 6, SP800-76) 

2. one instance of the "General Record Header" (Sec. 6.4 on 

INCITS 378) 

3. two instances of the "Finger View Record" (Sec. 6.5 of INCITS 

378) 

4. one instance of the CBEFF Signature Block (Table 7, Sec. 6, 

SP800-76) 

The placement of both fingers' templates in one INCITS 378 record is a 

departure from all 2004 and 2005 drafts of Special Publication 800-76. 

Now a single read from a PIV Card will yield this single record 

containing both templates. 

Notice that an errata on SP 800-73-1 has been issued (April 17, 2006) 

to affirm this. 

3/13/06 Table 3, Line 24, Column “PIV 

Conformance Values Allowed” 

The value “1” shall read as “2”. 

3/28/06 Table 3, Line 28, Column “PIV 

Conformance Values Allowed” 

The value “1” shall read as “0” 

April 26, 2006: Per [MINUSTD, clause 6.5.1.2] this field shall be 0 for 

the primary finger and 0 for the secondary finger. The combination 

of view number and finger position uniquely identifies each template. 

3/13/06 Table 3, Line 22, Column "PIV 

Conformance Values Allowed" 

The value "500" shall read as "197". 

3/13/06 Table 3, Line 23, Column "PIV 

Conformance Values Allowed" 

The value "500" shall read as "197". 

3/13/06 Table 3, Normative Note 4, Page 14 "Capture Device ID" shall read as "Capture Equipment ID" 

3/28/06 Table3, Line 2, Column “PIV 

Conformance Values Allowed” 

Should read "Note 6" not "note 2"? 

3/28/06 Table 3, Line 6, Column “PIV 

Conformance Values Allowed” 

Should read "Note 6" not "note 2"? 

3/28/06 Table 3, Line 17, Column 

"Informative Remarks" 

Should read "Note 3" not "note 4"? 

3/28/06 Table 3, Line 19, Column 

"Informative Remarks" 

Should read "Note 4" not "note 5"? 

3/28/06 Table 12, Line 19, Column 

"Informative Remarks" 

Should read "Note 6" not "note 2"? 

4/18/06 Table 3, Line 14 Replace value "0x30323000" with "0x20323000" 

Replace "020\0" with " 20\0" (i.e. replace ASCII '0' with ASCII ' ' (space) 
instead 

4/18/06 Table 3, Note 1 Replace "The second paragraph of [MINUSTD, 6.4.2] shall be ignored" 

with "The practice of [MINUSTD, 6.4.2] of using an ASCII space 

character as the first character of the version number shall be 

followed." 

4/18/06 Table 12, Line 2 Replace value "0x30323000" with "0x20323000" 

Replace "020\0" with " 20\0" (i.e. replace ASCII '0' with ASCII ' ' (space) 

instead. 

4/26/06 Table 3, Line 20 and Line 21 Insert in the "Informative Remarks" column: "See Note 10". 

Insert new Note 10 below Table 3: 

When two or more templates are stored in the record, and these are 

extracted from images of different size, [MINUSTD] does not give 

guidance on how to report the image sizes in the header. For PIV, the 

width on Line 20 shall be the larger of the widths of the two input 

images. Similarly the height on Line 21 shall be the larger of the 

heights of the two input images. 

5/15/06 Section 3.4, Paragraph 2. Replace sentence "Row 11 mandates the CBEFF header." with the 

following: 

Row 11 requires the CBEFF structure of Section 6. However, 

its FASC-N value (Table 8, Line 13) may be replaced by a field 

of all zeroes. This CBEFF exception supports storage of PIV 

registration images ahead of FASC-N assignment. 

7/10/06 Table 12, Line 3 Replace "794" with "800". 

7/19/06 Table 4 Renumber line 36 as line 37. 

Insert new line 36 to read as follows 

36 Reserved MF MV 0 See [FINGSTD, Table 4] 

The INCITS 381 standard includes, in Table 4, a single-byte reserved 

field, but there is no corresponding clause to formally define it. The 

M1 committee has undertaken to resolve this by inserting a new 

subclause (7.2.9) to require inclusion of the "Reserved" field. This will 

appear in a revision of INCITS 381. 

PIV implementations must include the single byte field, setting the 

value to 0. 

7/19/06 Table 11 Renumber line 24 as line 25. 

Insert new line 24 to read as follows 

24 Reserved MF MV 0 See [FINGSTD, Table 4] 

See comment in the erratum immediately above. 

7/19/06 Table 4, Line 27 No change. 

Line 27 indicates that the "Reserved" field shall have length 2 bytes. 

The INCITS 381 standard, in clause 7.1.15, indicates a length of 4 

bytes. This disagrees with the value in Table 2. The M1 committee 

has undertaken to specify 2 bytes as the correct value. 

PIV implementations shall include the two byte field, setting the value 

to 0. This is the intent of the note in SP 800-76, Table 4, Line 27 and 
this erratum is included to be definitive.