idnits 2.17.1 draft-bryan-http-digest-algorithm-values-update-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC3230]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (October 7, 2009) is 5312 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- ** Obsolete normative reference: RFC 3230 (Obsoleted by RFC 9530) Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group A. Bryan 3 Internet-Draft October 7, 2009 4 Intended status: Informational 5 Expires: April 10, 2010 7 Hypertext Transfer Protocol (HTTP) Digest Algorithm Values Registry 8 Update 9 draft-bryan-http-digest-algorithm-values-update-01 11 Status of this Memo 13 This Internet-Draft is submitted to IETF in full conformance with the 14 provisions of BCP 78 and BCP 79. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This Internet-Draft will expire on April 10, 2010. 34 Copyright Notice 36 Copyright (c) 2009 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents in effect on the date of 41 publication of this document (http://trustee.ietf.org/license-info). 42 Please review these documents carefully, as they describe your rights 43 and restrictions with respect to this document. 45 Abstract 47 [RFC3230] created the IANA registry named "Hypertext Transfer 48 Protocol (HTTP) Digest Algorithm Values" which defines values for 49 digest algorithms used in HTTP. This draft adds new values to the 50 registry and updates previous values. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 57 2.1. Previous Registrations Updated . . . . . . . . . . . . . . 3 58 2.2. New Registrations . . . . . . . . . . . . . . . . . . . . . 3 59 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 60 4. Normative References . . . . . . . . . . . . . . . . . . . . . 4 61 Appendix A. Acknowledgements and Contributors . . . . . . . . . . 4 62 Appendix B. Document History (to be removed by RFC Editor 63 before publication) . . . . . . . . . . . . . . . . . 4 64 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5 66 1. Introduction 68 The IANA registry named "Hypertext Transfer Protocol (HTTP) Digest 69 Algorithm Values" defines values for digest algorithms used in HTTP. 71 The registry was created by [RFC3230] in 2002. This draft adds new 72 values to the registry and updates previous values. 74 [[ Discussion of this draft should take place on IETF HTTP WG mailing 75 list at ietf-http-wg@w3.org or directly to the author. ]] 77 1.1. Examples 79 Examples of Instance Digest for SHA-256: 81 Digest: SHA-256=MWVkMWQxYTRiMzk5MDQ0MzI3NGU5NDEyZTk5OWY1ZGFmNzgyZTJlO 82 DYzYjRjYzFhOTlmNTQwYzI2M2QwM2U2MQ== 84 2. IANA Considerations 86 This document makes use of the IANA registry named "Hypertext 87 Transfer Protocol (HTTP) Digest Algorithm Values" specified in 88 [RFC3230]. 90 2.1. Previous Registrations Updated 92 Accordingly, IANA has updated the following registrations: 94 Digest Algorithm: MD5 95 Description: The MD5 algorithm, as specified in [RFC1321]. The 96 output of this algorithm is encoded using the base64 encoding 97 [RFC4648]. 98 Reference: [RFC1321] [RFC4648] 100 Digest Algorithm: SHA 101 Description: The SHA-1 algorithm [FIPS-180-3]. The output of this 102 algorithm is encoded using the base64 encoding [RFC4648]. 103 Reference: [FIPS-180-3] [RFC4648] 105 2.2. New Registrations 107 Accordingly, IANA has made the following registrations: 109 Digest Algorithm: SHA-224 110 Description: The SHA-224 algorithm [FIPS-180-3]. The output of 111 this algorithm is encoded using the base64 encoding [RFC4648]. 113 Reference: [FIPS-180-3] [RFC4648] 115 Digest Algorithm: SHA-256 116 Description: The SHA-256 algorithm [FIPS-180-3]. The output of 117 this algorithm is encoded using the base64 encoding [RFC4648]. 118 Reference: [FIPS-180-3] [RFC4648] 120 Digest Algorithm: SHA-384 121 Description: The SHA-384 algorithm [FIPS-180-3]. The output of 122 this algorithm is encoded using the base64 encoding [RFC4648]. 123 Reference: [FIPS-180-3] [RFC4648] 125 Digest Algorithm: SHA-512 126 Description: The SHA-512 algorithm [FIPS-180-3]. The output of 127 this algorithm is encoded using the base64 encoding [RFC4648]. 128 Reference: [FIPS-180-3] [RFC4648] 130 3. Security Considerations 132 Same as [RFC3230]. 134 4. Normative References 136 [FIPS-180-3] 137 National Institute of Standards and Technology (NIST), 138 "Secure Hash Standard (SHS)", FIPS PUB 180-3, 139 October 2008. 141 [RFC1321] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, 142 April 1992. 144 [RFC3230] Mogul, J. and A. Van Hoff, "Instance Digests in HTTP", 145 RFC 3230, January 2002. 147 [RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data 148 Encodings", RFC 4648, October 2006. 150 Appendix A. Acknowledgements and Contributors 152 Thanks to Mark Nottingham, Eran Hammer-Lahav, and Nils Maier. 154 Appendix B. Document History (to be removed by RFC Editor before 155 publication) 157 [[ to be removed by the RFC editor before publication as an RFC. ]] 159 Known issues concerning this draft: 160 o None known. 162 -01 : October 07, 2009. 163 o Update previous values that are outdated. 164 o RFC 4648 for Base64 encoding. 166 -00 : September 08, 2009. 167 o Initial draft. 169 Author's Address 171 Anthony Bryan 172 Pompano Beach, FL 173 USA 175 Email: anthonybryan@gmail.com 176 URI: http://www.metalinker.org