idnits 2.17.1 draft-bryan-http-digest-algorithm-values-update-00.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 6, 2009) is 5315 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 6, 2009 4 Intended status: Informational 5 Expires: April 9, 2010 7 Hypertext Transfer Protocol (HTTP) Digest Algorithm Values Registry 8 Update 9 draft-bryan-http-digest-algorithm-values-update-00 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 9, 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. 52 Table of Contents 54 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1.1. Examples . . . . . . . . . . . . . . . . . . . . . . . . . 3 56 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 57 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 58 4. Normative References . . . . . . . . . . . . . . . . . . . . . 4 59 Appendix A. Acknowledgements and Contributors . . . . . . . . . . 4 60 Appendix B. Document History (to be removed by RFC Editor 61 before publication) . . . . . . . . . . . . . . . . . 4 62 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 1. Introduction 66 The IANA registry named "Hypertext Transfer Protocol (HTTP) Digest 67 Algorithm Values" defines values for digest algorithms used in HTTP. 69 This registry was created by [RFC3230] in 2002 and some useful values 70 could be added to it. 72 [[ Discussion of this draft should take place on IETF HTTP WG mailing 73 list at ietf-http-wg@w3.org or directly to the author. ]] 75 1.1. Examples 77 Examples of Instance Digest for SHA-256: 79 Digest: SHA-256=MWVkMWQxYTRiMzk5MDQ0MzI3NGU5NDEyZTk5OWY1ZGFmNzgyZTJlO 80 DYzYjRjYzFhOTlmNTQwYzI2M2QwM2U2MQ== 82 2. IANA Considerations 84 This document makes use of the IANA registry named "Hypertext 85 Transfer Protocol (HTTP) Digest Algorithm Values" specified in 86 [RFC3230]. 88 Accordingly, IANA has made the following registrations: 90 Digest Algorithm: SHA-224 91 Description: The SHA-224 algorithm [SHS]. The output of this 92 algorithm is encoded using the base64 encoding [RFC2045]. 93 Reference: [SHS] [RFC2045] 95 Digest Algorithm: SHA-256 96 Description: The SHA-256 algorithm [SHS]. The output of this 97 algorithm is encoded using the base64 encoding [RFC2045]. 98 Reference: [SHS] [RFC2045] 100 Digest Algorithm: SHA-384 101 Description: The SHA-384 algorithm [SHS]. The output of this 102 algorithm is encoded using the base64 encoding [RFC2045]. 103 Reference: [SHS] [RFC2045] 105 Digest Algorithm: SHA-512 106 Description: The SHA-512 algorithm [SHS]. The output of this 107 algorithm is encoded using the base64 encoding [RFC2045]. 108 Reference: [SHS] [RFC2045] 110 3. Security Considerations 112 Same as [RFC3230]. 114 4. Normative References 116 [RFC2045] Freed, N. and N. Borenstein, "Multipurpose Internet Mail 117 Extensions (MIME) Part One: Format of Internet Message 118 Bodies", RFC 2045, November 1996. 120 [RFC3230] Mogul, J. and A. Van Hoff, "Instance Digests in HTTP", 121 RFC 3230, January 2002. 123 [SHS] National Institute of Standards and Technology (NIST), 124 "Secure Hash Standard", FIPS PUB 180-3, October 2008, . 128 Appendix A. Acknowledgements and Contributors 130 Thanks to Mark Nottingham, Eran Hammer-Lahav, and Nils Maier. 132 Appendix B. Document History (to be removed by RFC Editor before 133 publication) 135 [[ to be removed by the RFC editor before publication as an RFC. ]] 137 Known issues concerning this draft: 138 o Current registry: MD5 lists both RFC1521 and RFC20456 for base64 139 encoding. Should this draft update it to refer to just one? 140 o Current registry: SHA link ( 141 http://csrc.nist.gov/fips/fip180-1.txt ) is no longer valid. 142 Should this draft update it? 143 o If we update SHA in the registry, should this draft refer to SHS 144 or RFC3174? 146 -00 : September 08, 2009. 147 o Initial draft. 149 Author's Address 151 Anthony Bryan 152 Pompano Beach, FL 153 USA 155 Email: anthonybryan@gmail.com 156 URI: http://www.metalinker.org