-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathrfc5843.xml
More file actions
196 lines (149 loc) · 6.54 KB
/
rfc5843.xml
File metadata and controls
196 lines (149 loc) · 6.54 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
<?xml version="1.0" encoding="US-ASCII"?>
<!-- [rfced] Please note that after you have approved the document,
post-xml2rfc changes will be made to update the header and
boilerplate as described in RFC 5741.
-->
<?xml-stylesheet type='text/xsl' href='rfc2629.xslt' ?>
<?rfc toc="yes" ?>
<?rfc tocdepth="3" ?>
<?rfc tocindent="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc sortrefs="yes"?>
<?rfc iprnotified="no" ?>
<?rfc rfcedstyle="yes" ?>
<?rfc comments="yes" ?>
<?rfc inline="yes" ?>
<!DOCTYPE rfc
PUBLIC "" "rfc2629.dtd">
<rfc number="5843" category="info" ipr="trust200902">
<front>
<title abbrev="More Algorithms for HTTP Instance Digests">Additional Hash Algorithms for HTTP Instance Digests</title>
<author initials="A." surname="Bryan" fullname="Anthony Bryan">
<organization></organization>
<address>
<postal>
<street></street>
<city>Pompano Beach</city>
<region>FL</region>
<country>USA</country>
</postal>
<email>anthonybryan@gmail.com</email>
<uri>http://www.metalinker.org</uri>
</address>
</author>
<date month="April" year="2010"/>
<!-- [rfced] Please insert any keywords (beyond those that appear in
the title) for use on http://www.rfc-editor.org/rfcsearch.html. Hypertext Transfer Protocol (HTTP) Digest Algorithm Values registry update-->
<abstract>
<t>The IANA registry named "Hypertext Transfer Protocol (HTTP) Digest Algorithm Values" defines values for digest algorithms used by Instance Digests in HTTP. Instance Digests in HTTP provide a digest, also known as a checksum or hash, of an entire representation of the current state of a
resource. This document adds new values to the registry and updates previous values.
</t>
</abstract>
</front>
<middle>
<section title="Introduction">
<t>The IANA registry named "Hypertext Transfer Protocol (HTTP) Digest Algorithm Values" defines values for digest algorithms used by Instance Digests in HTTP.</t>
<t>Note: This is unrelated to HTTP Digest Authentication. Instance Digests in HTTP provide a digest, also known as a checksum or hash, of an entire representation of the current state of a
resource.</t>
<t>The registry was created by <xref target="RFC3230"/> in 2002. This document adds new values to the registry and updates previous values that had redundant or outdated references.</t>
<section title="Example"><t><figure>
<preamble>Example of Instance Digest for SHA-256:</preamble>
<!-- [rfced] Does this section contain more than one example? If not,
may the title and text be changed to singular "Example"? DONE-->
<artwork type="example">
Digest: SHA-256=MWVkMWQxYTRiMzk5MDQ0MzI3NGU5NDEyZTk5OWY1ZGFmNzgyZTJlO
DYzYjRjYzFhOTlmNTQwYzI2M2QwM2U2MQ==
</artwork></figure></t>
</section>
</section>
<section title="IANA Considerations" anchor="IANA">
<t>This document makes use of the IANA registry named "Hypertext Transfer Protocol (HTTP) Digest Algorithm Values" specified in <xref target="RFC3230"/>.</t>
<section title="Previous Registrations Updated">
<t>Accordingly, IANA has updated the following registrations:</t>
<t><list>
<t>Digest Algorithm: MD5</t>
<t>Description: The MD5 algorithm, as specified in
<xref target="RFC1321"/>. The output of this algorithm is encoded
using the base64 encoding <xref target="RFC4648"/>.</t>
<t>Reference: <xref target="RFC1321"/>, <xref target="RFC4648"/>,
this document.</t>
</list></t>
<t><list>
<t>Digest Algorithm: SHA</t>
<t>Description: The SHA-1 algorithm
<xref target="FIPS-180-3"/>. The output of this algorithm is
encoded using the base64 encoding <xref target="RFC4648"/>.</t>
<t>Reference: <xref target="FIPS-180-3"/>, <xref target="RFC4648"/>,
this document.</t>
</list></t>
</section>
<section title="New Registrations">
<t>Accordingly, IANA has made the following registrations:</t>
<t><list>
<t>Digest Algorithm: SHA-256</t>
<t>Description: The SHA-256 algorithm <xref target="FIPS-180-3"/>. The output of this algorithm is encoded using the base64 encoding <xref target="RFC4648"/>.</t>
<t>Reference: <xref target="FIPS-180-3"/>, <xref target="RFC4648"/>,
this document.</t>
</list></t>
<t><list>
<t>Digest Algorithm: SHA-512</t>
<t>Description: The SHA-512 algorithm <xref target="FIPS-180-3"/>. The output of this algorithm is encoded using the base64 encoding <xref target="RFC4648"/>.</t>
<t>Reference: <xref target="FIPS-180-3"/>, <xref target="RFC4648"/>,
this document.</t>
</list></t>
</section>
</section>
<section title="Security Considerations">
<t>Same as <xref target="RFC3230"/>.</t>
</section>
<section title="Changes Compared to RFC 3230">
<t>The reference for base64 encoding has been updated for both MD5 and SHA.</t>
<t>The reference for SHA has been updated.</t>
<t>The SHA-256 and SHA-512 algorithms have been added to the registry.</t>
<t>All other previous values to the registry are still valid.</t>
</section>
</middle>
<back>
<references title="Normative References">
<reference anchor="RFC1321">
<front>
<title>The MD5 Message-Digest Algorithm</title>
<author initials="R." surname="Rivest" fullname="R. Rivest">
<organization/></author>
<date year="1992" month="April"/></front>
<seriesInfo name="RFC" value="1321"/>
</reference>
<reference anchor="RFC3230">
<front>
<title>Instance Digests in HTTP</title>
<author initials="J." surname="Mogul" fullname="J. Mogul">
<organization/></author>
<author initials="A." surname="Van Hoff" fullname="A. Van Hoff">
<organization/></author>
<date year="2002" month="January"/></front>
<seriesInfo name="RFC" value="3230"/>
</reference>
<reference anchor="RFC4648">
<front>
<title>The Base16, Base32, and Base64 Data Encodings</title>
<author initials="S." surname="Josefsson" fullname="S. Josefsson">
<organization/></author>
<date year="2006" month="October"/></front>
<seriesInfo name="RFC" value="4648"/>
</reference>
<reference anchor="FIPS-180-3">
<front>
<title>Secure Hash Standard (SHS)</title>
<author>
<organization>National Institute of Standards and Technology (NIST)</organization>
</author>
<date year="2008" month="October"></date>
</front>
<seriesInfo name="FIPS PUB" value="180-3"></seriesInfo>
</reference>
</references>
<section title="Acknowledgements and Contributors">
<t>Thanks to Mark Nottingham, Eran Hammer-Lahav, Nils Maier, Lisa Dusseault, Alfred Hoenes, Pasi Eronen, Gonzalo Camarillo, Radia Perlman, and Jeffrey Mogul.</t>
</section>
</back>
</rfc>