From af819dd5823351adab9a42887b116c5d28aacc54 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Wed, 16 Oct 2013 09:47:34 -0600 Subject: [PATCH] updated references --- xep-0065.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/xep-0065.xml b/xep-0065.xml index 01ec84c1..c2de88c6 100755 --- a/xep-0065.xml +++ b/xep-0065.xml @@ -409,7 +409,7 @@ Requester Target
  • The hostname MUST be SHA1(SID + Requester JID + Target JID) where the definition of the SHA1 hashing algorithm is as specified by &rfc3174; and the output is hexadecimal-encoded (not binary); as noted above and under Use with Multi-User Chat, the DST.ADDR value might have been provided directly from the Requester to the Target).
  • The port MUST be 0 (zero).
  • The JIDs used as input to the hash function MUST be the actual JIDs used for the IQ exchange between the Requester and the Target (these might be full JIDs &FULLJID; or bare JIDs &BAREJID; depending on the addresses of the entities involved in the negotiation).
    • -
  • The appropriate stringprep profiles (as specified in &rfc3920;) MUST be applied to the JIDs before application of the SHA1 hashing algorithm.
    • +
  • The appropriate stringprep profiles (as specified in &rfc6122;) MUST be applied to the JIDs before application of the SHA1 hashing algorithm.
    • The hostname MUST be SHA1(SID + Requester JID + Target JID) where the definition of the SHA1 hashing algorithm is as specified by &rfc3174; and the output is hexadecimal-encoded (not binary); as noted above and under Use with Multi-User Chat, the DST.ADDR value might have been provided directly from the Requester to the Target).
  • The port MUST be 0 (zero).
  • The JIDs provided MUST be the JIDs used for the IQ exchange between the Requester and the Target, which MAY be full JIDs &FULLJID; or bare JIDs &BAREJID;.
    • -
  • The appropriate stringprep profiles (as specified in RFC 3920) MUST be applied to the JIDs before application of the SHA1 hashing algorithm.
    • +
  • The appropriate stringprep profiles (as specified in RFC 6122) MUST be applied to the JIDs before application of the SHA1 hashing algorithm.