Explicitly specify encoding format. Namespace version bump to urn:xmpp:hashes:2.
This document defines a new XML element that can be used in any XMPP protocol extension. An example follows.
-2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=
- ]]>
+ 2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=åå]]>
An XMPP protocol can include more than one instance of the <hash/> element, as long as each one has a different value for the 'algo' attribute:
-2AfMGH8O7UNPTvUVAM9aK13mpCY=
-2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU=
- ]]>
- The value of the 'algo' attribute MUST be one of the values from the &ianahashes; maintained by &IANA;.
+2AfMGH8O7UNPTvUVAM9aK13mpCY=
+2XarmwTlNxDAMkvymloX3S5+VbylNrJt/l5QyPa+YoU= ]]>
+ The value of the 'algo' attribute MUST be one of the values from the &ianahashes; maintained by &IANA;, or one of the values + defined in the following table.
+Hash Function Name | +Reference | +
---|---|
"sha3-256" | +FIPS PUB 202: SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions |
+
"sha3-512" | +FIPS PUB 202: SHA-3 Standard: Permutation-Based Hash and Extendable-Output Functions |
+
"blake2b-256" | +&rfc7693; | +
"blake2b-512" | +&rfc7693; | +
The CDATA of the <hash/> element MUST conform to the base64Binary datatype
The current plan is to move SHA-1 to a SHOULD NOT, SHA-256, SHA3-256 and BLAKE2b256 to MUST, and SHA-512, SHA3-512, and BLAKE2b512 to SHOULD by the end of 2016.
These recommendations ought to be reviewed yearly by the &COUNCIL;.
If an entity supports the protocol defined herein, it MUST report that by including a &xep0030; feature of "urn:xmpp:hashes:1" in response to disco#info requests, along with one service discovery feature for each algorithm it supports:
+If an entity supports the protocol defined herein, it MUST report that by including a &xep0030; feature of "urn:xmpp:hashes:2" in response to disco#info requests, along with one service discovery feature for each algorithm it supports:
This specification defines the following XML namespace:
The ®ISTRAR; shall include the foregoing namespace in its registry at &NAMESPACES;, as governed by &xep0053;.