From 5c3565a794ec251e190a767668b1ae1c54973d86 Mon Sep 17 00:00:00 2001 From: Peter Saint-Andre Date: Thu, 12 Jul 2007 15:47:31 +0000 Subject: [PATCH] Base64 clarifications git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1059 4b5297f7-1745-476d-ba37-a9c6900126ab --- xep-0115.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/xep-0115.xml b/xep-0115.xml index e5baac0d..3c64cc51 100644 --- a/xep-0115.xml +++ b/xep-0115.xml @@ -237,7 +237,7 @@
  • For each identity, append the category/type (if it exists) to S, followed by the '<' character.
  • Sort the supported features.
  • For each feature, append the feature to S, followed by the '<' character.
    • -
  • Compute ver by hashing S using the SHA-1 algorithm as specified in &rfc3174; (with binary output) and encoding the hash using Base64 as specified in Section 4 of &rfc4648;.
    • +
  • Compute ver by hashing S using the SHA-1 algorithm as specified in &rfc3174; (with binary output) and encoding the hash using Base64 as specified in Section 4 of &rfc4648; (note: the Base64 output MUST NOT include whitespace and MUST set padding bits to zero).

    • For example, consider an entity whose service discovery category is "client", whose service discovery type is "pc", and whose supported features are "http://jabber.org/protocol/disco#info", "http://jabber.org/protocol/disco#items", and "http://jabber.org/protocol/muc". The value of the 'ver' attribute would be generated as follows: