acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...
acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ... acknowledgements for ansi/nist-itl 1-2011 - NIST Visual Image ...
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION8.22.21 Field 22.999: Imagery data block / DATAThis field shall contain the imagery data if conveyed in the transaction. If the data is storedexternally, Field 22.994: External file reference / EFR is used. Only one of these twofields may be present in a single record. See Section 7.2 for details on the Data field entry.In Traditional encoding, this shall be the last physical field in the record.[
ANSI/NIST-ITL 1-2011 - UPDATE 2013 DRAFT VERSION8.23 Record Type-98: Information assurance recordThe Type-98 record shall contain security information that assures the authenticity and/orintegrity of the transaction, possibly utilizing such techniques as binary data hashes, and/ordigital signatures. Two mandatory fields in the Information Assurance (IA) Header are Field98.003: IA data format owner / DFO and Field 98.005: IA data format type / DFT .The IA data format owner field denotes the vendor, standards body, working group, orindustry consortium that has defined the format of the IA data. The values in the IA dataformat type field are assigned by the format owner and represent a specific IA Data formatas specified by the format owner. This may be a non-standard, unpublished data format or adata format that has been standardized by an industry group, consortium, or standards body.It is the combined IA Data Format Owner / IA Data Format Type value that uniquelyidentifies the IA Data format. There may be many instances of this Record Type pertransaction. The records that are protected by a Type-98 are all records other than the Type-98 itself.Table 105 Type-98 record layoutFieldNumberMnemonic Content Description CondcodeTypeCharacterMIn#Max#ValueConstraintsOccurrenceMIn#Max#98.001 RECORD HEADER Mencoding specific: seeAnnex B:Traditional encodingor Annex C: NIEMconformantencoding rulesencoding specific:see Annex B:Traditionalencoding orAnnex C: NIEMconformantencoding rules1 198.002 IDCINFORMATIONDESIGNATIONCHARACTERM N 1 20 < IDC < 99integer1 198.003 DFO IA DATA FORMAT OWNER M H 4 4 none 1 198.004 SRC SOURCE AGENCY M U 1 * none 1 198.005 DFT IA DATA FORMAT TYPE M U 1 20 none 1 198.006 DCD IA DATA CREATION DATE Mencoding specific: seeAnnex B or Annex Cencoding specific:see Annex B orAnnex C1 198.007-98.199RESERVED FOR FUTUREUSE ONLY BY ANSI/NIST-ITLNot to be used98.200-98.899UDF USER-DEFINED FIELDS O user-defined user-defined user-defined424
- Page 414 and 415: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 416 and 417: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 418 and 419: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 420 and 421: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 422 and 423: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 424 and 425: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 426 and 427: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 428 and 429: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 430 and 431: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 432 and 433: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 434 and 435: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 436 and 437: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 438 and 439: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 440 and 441: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 442 and 443: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 444 and 445: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 446 and 447: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 448 and 449: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 450 and 451: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 452 and 453: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 454 and 455: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 456 and 457: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 458 and 459: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 460 and 461: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 462 and 463: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 466 and 467: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 468 and 469: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 470 and 471: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 472 and 473: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 474 and 475: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 476 and 477: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 478 and 479: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 480 and 481: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 483 and 484: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 485 and 486: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 487 and 488: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 489 and 490: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 491 and 492: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 493 and 494: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 495 and 496: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 497 and 498: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 499 and 500: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 501 and 502: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 503 and 504: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 505 and 506: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 507 and 508: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 509 and 510: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 511 and 512: ANSI/NIST-ITL 1-2011 - UPDATE 2013
- Page 513 and 514: ANSI/NIST-ITL 1-2011 - UPDATE 2013
ANSI/<strong>NIST</strong>-ITL 1-<strong>2011</strong> - UPDATE 2013 DRAFT VERSION8.23 Record Type-98: In<strong>for</strong>mation assurance recordThe Type-98 record shall contain security in<strong>for</strong>mation that assures the authenticity and/orintegrity of the transaction, possibly utilizing such techniques as binary data hashes, and/ordigital signatures. Two mandatory fields in the In<strong>for</strong>mation Assurance (IA) Header are Field98.003: IA data <strong>for</strong>mat owner / DFO and Field 98.005: IA data <strong>for</strong>mat type / DFT .The IA data <strong>for</strong>mat owner field denotes the vendor, standards body, working group, orindustry consortium that has defined the <strong>for</strong>mat of the IA data. The values in the IA data<strong>for</strong>mat type field are assigned by the <strong>for</strong>mat owner and represent a specific IA Data <strong>for</strong>matas specified by the <strong>for</strong>mat owner. This may be a non-standard, unpublished data <strong>for</strong>mat or adata <strong>for</strong>mat that has been standardized by an industry group, consortium, or standards body.It is the combined IA Data Format Owner / IA Data Format Type value that uniquelyidentifies the IA Data <strong>for</strong>mat. There may be many instances of this Record Type pertransaction. The records that are protected by a Type-98 are all records other than the Type-98 itself.Table 105 Type-98 record layoutFieldNumberMnemonic Content Description CondcodeTypeCharacterMIn#Max#ValueConstraintsOccurrenceMIn#Max#98.001 RECORD HEADER Mencoding specific: seeAnnex B:Traditional encodingor Annex C: NIEMcon<strong>for</strong>mantencoding rulesencoding specific:see Annex B:Traditionalencoding orAnnex C: NIEMcon<strong>for</strong>mantencoding rules1 198.002 IDCINFORMATIONDESIGNATIONCHARACTERM N 1 20 < IDC < 99integer1 198.003 DFO IA DATA FORMAT OWNER M H 4 4 none 1 198.004 SRC SOURCE AGENCY M U 1 * none 1 198.005 DFT IA DATA FORMAT TYPE M U 1 20 none 1 198.006 DCD IA DATA CREATION DATE Mencoding specific: seeAnnex B or Annex Cencoding specific:see Annex B orAnnex C1 198.007-98.199RESERVED FOR FUTUREUSE ONLY BY ANSI/<strong>NIST</strong>-ITLNot to be used98.200-98.899UDF USER-DEFINED FIELDS O user-defined user-defined user-defined424