RFC 5843

Additional Hash Algorithms for HTTP Instance Digests 💖

RFC 5843 🎀 Authors: A. Bryan (Anthony Bryan) 🧚 Category: Informational Date: April 2010 ISSN: 2070-1721 Obsoletes/Updates: The title block has no Obsoletes or Updates line. The document does update existing registry entries (the ones from RFC 3230) that had redundant or outdated references. See Section 2.1. 💅

Abstract ✨

okay so the IANA registry called "Hypertext Transfer Protocol (HTTP) Digest Algorithm Values" holds the values for the digest algorithms that Instance Digests in HTTP use 🔥 Instance Digests give you a digest (aka a checksum or hash) of the entire current representation of a resource 🦋 This document adds new values to that registry and updates some previous ones 💜

Status of This Memo 🌸

this one is not an Internet Standards Track spec. It's published for informational purposes 🫶

It's a product of the Internet Engineering Task Force (IETF) and represents the consensus of the IETF community. It got public review and was approved for publication by the Internet Engineering Steering Group (IESG). Not every IESG-approved doc is a candidate for any level of Internet Standard, so check Section 2 of RFC 5741 if you want the details 🌈

For the latest status, errata, and how to send feedback, look at http://www.rfc-editor.org/info/rfc5843 🔗

Copyright Notice 🎀

Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved 💅

This doc is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as they stand on the publication date. Read those carefully, because they spell out your rights and restrictions for this document 📜 Any Code Components pulled out of this document have to include the Simplified BSD License text, as described in Section 4.e of the Trust Legal Provisions. They come with no warranty, as the Simplified BSD License describes 🫶

Table of Contents 🧚

   1. Introduction ....................................................2
      1.1. Example ....................................................2
   2. IANA Considerations .............................................2
      2.1. Previous Registrations Updated .............................2
      2.2. New Registrations ..........................................3
   3. Security Considerations .........................................3
   4. Changes Compared to RFC 3230 ....................................3
   5. Normative References ............................................4
   Appendix A. Acknowledgements and Contributors ......................5

1. Introduction ✨

okay so the registry named "Hypertext Transfer Protocol (HTTP) Digest Algorithm Values" is where the digest algorithm values for Instance Digests in HTTP live 🌸

Note: This is NOT the same thing as HTTP Digest Authentication 🙈 Instance Digests in HTTP give you a digest (checksum or hash) of the entire current state of a resource.

The registry was created by [RFC3230] back in 2002 🍓 This document adds new values and updates the previous values that had redundant or outdated references 💖

1.1. Example 🦋

Here's an Instance Digest for SHA-256:

Digest: SHA-256=MWVkMWQxYTRiMzk5MDQ0MzI3NGU5NDEyZTk5OWY1ZGFmNzgyZTJlO
DYzYjRjYzFhOTlmNTQwYzI2M2QwM2U2MQ==

2. IANA Considerations 👑

This document uses the IANA registry named "Hypertext Transfer Protocol (HTTP) Digest Algorithm Values" that's specified in [RFC3230] 💜

2.1. Previous Registrations Updated 🔥

IANA has updated these registrations, so here's the tea:

   Digest Algorithm: MD5

   Description: The MD5 algorithm, as specified in [RFC1321].  The
   output of this algorithm is encoded using the base64 encoding
   [RFC4648].

   Reference: [RFC1321], [RFC4648], this document.

   Digest Algorithm: SHA

   Description: The SHA-1 algorithm [FIPS-180-3].  The output of this
   algorithm is encoded using the base64 encoding [RFC4648].

   Reference: [FIPS-180-3], [RFC4648], this document.

2.2. New Registrations 🧚

IANA has also made these brand-new registrations 🌈

   Digest Algorithm: SHA-256

   Description: The SHA-256 algorithm [FIPS-180-3].  The output of
   this algorithm is encoded using the base64 encoding [RFC4648].

   Reference: [FIPS-180-3], [RFC4648], this document.

   Digest Algorithm: SHA-512

   Description: The SHA-512 algorithm [FIPS-180-3].  The output of
   this algorithm is encoded using the base64 encoding [RFC4648].

   Reference: [FIPS-180-3], [RFC4648], this document.

3. Security Considerations 💀

Same as [RFC3230]. Go read that one for the full security picture, bestie 😭

4. Changes Compared to RFC 3230 🦋

Here's what changed since RFC 3230 ✨

• The base64 encoding reference got updated for both MD5 and SHA 💅
• The reference for SHA got updated too 🌸
• SHA-256 and SHA-512 were added to the registry 🔥
• Every other previous value in the registry is still valid 🫶

5. Normative References 📜

[FIPS-180-3]  National Institute of Standards and Technology (NIST),
              "Secure Hash Standard (SHS)", FIPS PUB 180-3,
              October 2008.

[RFC1321]     Rivest, R., "The MD5 Message-Digest Algorithm",
              RFC 1321, April 1992.

[RFC3230]     Mogul, J. and A. Van Hoff, "Instance Digests in HTTP",
              RFC 3230, January 2002.

[RFC4648]     Josefsson, S., "The Base16, Base32, and Base64 Data
              Encodings", RFC 4648, October 2006.

Appendix A. Acknowledgements and Contributors 🎀

Huge thanks to Mark Nottingham, Eran Hammer-Lahav, Nils Maier, Lisa Dusseault, Alfred Hoenes, Pasi Eronen, Gonzalo Camarillo, Radia Perlman, and Jeffrey Mogul 🫶💖

Author's Address 🧚

Anthony Bryan
Pompano Beach, FL
USA

EMail: anthonybryan@gmail.com
URI:   http://www.metalinker.org

---