| < draft-ietf-pkix-sha244-01.txt | draft-ietf-pkix-sha244-02.txt > | |||
|---|---|---|---|---|
| PKIX Working Group R. Housley | PKIX Working Group R. Housley | |||
| Internet Draft Vigil Security | Internet Draft Vigil Security | |||
| Expires in six months December 2003 | Expires in six months December 2003 | |||
| A 224-bit One-way Hash Function: SHA-224 | A 224-bit One-way Hash Function: SHA-224 | |||
| <draft-ietf-pkix-sha244-01.txt> | <draft-ietf-pkix-sha244-02.txt> | |||
| Status of this Memo | Status of this Memo | |||
| This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
| all provisions of Section 10 of RFC 2026. Internet-Drafts are | all provisions of Section 10 of RFC 2026. Internet-Drafts are | |||
| working documents of the Internet Engineering Task Force (IETF), its | working documents of the Internet Engineering Task Force (IETF), its | |||
| areas, and its working groups. Note that other groups may also | areas, and its working groups. Note that other groups may also | |||
| distribute working documents as Internet-Drafts. | distribute working documents as Internet-Drafts. | |||
| Internet-Drafts are draft documents valid for a maximum of six months | Internet-Drafts are draft documents valid for a maximum of six months | |||
| skipping to change at page 1, line 34 ¶ | skipping to change at page 1, line 34 ¶ | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
| The list of Internet-Drafts Shadow Directories can be accessed at | The list of Internet-Drafts Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| Abstract | Abstract | |||
| This document specifies a 224-bit one-way hash function, called | This document specifies a 224-bit one-way hash function, called | |||
| SHA-224. A SHA-224 is based on SHA-256, but it uses an different | SHA-224. A SHA-224 is based on SHA-256, but it uses an different | |||
| initial value and the value is truncated to 224 bits. | initial value and the result is truncated to 224 bits. | |||
| 1 Introduction | 1 Introduction | |||
| This document specifies a 224-bit one-way hash function, called | This document specifies a 224-bit one-way hash function, called | |||
| SHA-224. One-way hash functions are also known as message digests. | SHA-224. One-way hash functions are also known as message digests. | |||
| SHA-224 is based on SHA-256, the 256-bit one-way hash function | SHA-224 is based on SHA-256, the 256-bit one-way hash function | |||
| already specified by the National Institute of Standards and | already specified by the National Institute of Standards and | |||
| Technology (NIST) [SHA2]. Computation of a SHA-224 hash value is two | Technology (NIST) [SHA2]. Computation of a SHA-224 hash value is two | |||
| steps. First, the SHA-256 hash value is computed, except that a | steps. First, the SHA-256 hash value is computed, except that a | |||
| different initial value is used. Second, the resulting 256-bit hash | different initial value is used. Second, the resulting 256-bit hash | |||
| skipping to change at page 3, line 26 ¶ | skipping to change at page 3, line 26 ¶ | |||
| 3.1 Test Vector #1 | 3.1 Test Vector #1 | |||
| Let the message to be hashed be the 24-bit ASCII string "abc", which | Let the message to be hashed be the 24-bit ASCII string "abc", which | |||
| is equivalent to the following binary string: | is equivalent to the following binary string: | |||
| 01100001 01100010 01100011 | 01100001 01100010 01100011 | |||
| The SHA-224 hash value (in hex): | The SHA-224 hash value (in hex): | |||
| <TBD> | 23097d22 3405d822 8642a477 bda255b3 2aadbce4 bda0b3f7 e36c9da7 | |||
| 3.2 Test Vector #2 | 3.2 Test Vector #2 | |||
| Let the message to be hashed be the 448-bit ASCII string | Let the message to be hashed be the 448-bit ASCII string | |||
| "abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq". | "abcdbcdecdefdefgefghfghighijhijkijkljklmklmnlmnomnopnopq". | |||
| The SHA-224 hash value is (in hex): | The SHA-224 hash value is (in hex): | |||
| <TBD> | 75388b16 512776cc 5dba5da1 fd890150 b0c6455c b4f58b19 52522525 | |||
| 3.3 Test Vector #3 | 3.3 Test Vector #3 | |||
| Let the message to hashed be the binary-coded form of the ASCII | Let the message to be hashed be the binary-coded form of the ASCII | |||
| string which consists of 1,000,000 repetitions of the character "a". | string which consists of 1,000,000 repetitions of the character "a". | |||
| The SHA-224 hash value is (in hex): | The SHA-224 hash value is (in hex): | |||
| <TBD> | 20794655 980c91d8 bbb4c1ea 97618a4b f03f4258 1948b2ee 4ee7ad67 | |||
| 4 Object Identifier | 4 Object Identifier | |||
| NIST has assigned an ASN.1 [X.208-88, X.209-88] object identifier for | NIST has assigned an ASN.1 [X.208-88, X.209-88] object identifier for | |||
| SHA-224. Some protocols use object identifiers to name one-way hash | SHA-224. Some protocols use object identifiers to name one-way hash | |||
| functions. One example is CMS [CMS]. Implementations of such | functions. One example is CMS [CMS]. Implementations of such | |||
| protocols that make use of SHA-224 MUST use the following object | protocols that make use of SHA-224 MUST use the following object | |||
| identifier. | identifier. | |||
| id-sha224 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) | id-sha224 OBJECT IDENTIFIER ::= { joint-iso-itu-t(2) | |||
| skipping to change at page 5, line 34 ¶ | skipping to change at page 5, line 34 ¶ | |||
| might or might not be available; neither does it represent that it | might or might not be available; neither does it represent that it | |||
| has made any effort to identify any such rights. Information on the | has made any effort to identify any such rights. Information on the | |||
| IETF's procedures with respect to rights in standards-track and | IETF's procedures with respect to rights in standards-track and | |||
| standards-related documentation can be found in BCP-11. Copies of | standards-related documentation can be found in BCP-11. Copies of | |||
| claims of rights made available for publication and any assurances of | claims of rights made available for publication and any assurances of | |||
| licenses to be made available, or the result of an attempt made to | licenses to be made available, or the result of an attempt made to | |||
| obtain a general license or permission for the use of such | obtain a general license or permission for the use of such | |||
| proprietary rights by implementors or users of this specification can | proprietary rights by implementors or users of this specification can | |||
| be obtained from the IETF Secretariat. | be obtained from the IETF Secretariat. | |||
| 7 Author's Address | 7 Acknowledgment | |||
| Many thanks to Jim Schaad for generating the test vectors. | ||||
| 8 Author's Address | ||||
| Russell Housley | Russell Housley | |||
| Vigil Security, LLC | Vigil Security, LLC | |||
| 918 Spring Knoll Drive | 918 Spring Knoll Drive | |||
| Herndon, VA 20170 | Herndon, VA 20170 | |||
| USA | USA | |||
| housley@vigilsec.com | housley@vigilsec.com | |||
| Full Copyright Statement | Full Copyright Statement | |||
| End of changes. 7 change blocks. | ||||
| 7 lines changed or deleted | 11 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||