On Sat, Feb 24, 2018, at 14:08, Sam Whited wrote:
> On Sat, Feb 24, 2018, at 13:53, Jonas Wielicki wrote:
> > Second: I could’ve sworn that there was some text which specified something 
> > like lower-case hex. But apparently there is none. Grepping through the 
> > presence I get from all my contacts, all of them are doing lower case 
> > hexadecimal. When we implemented it in aioxmpp, we thus also went for lower 
> > case hexadecimal.
> 
> This has been base64 for at least as long as we've been tracking this in 
> a repo (since the time when it was a JEP).
> I queried all of my online contacts and they all seem to be using base64 
> correctly, I didn't see any that were using hex encoding.
> Do you know what clients your contacts are using?


My apologies, I thought htis was in reference to the bindata, but I see now 
that it's the sha1. Thanks for pointing out my mistake Jonas.

This does seem as if it should be clarified; it references 
https://tools.ietf.org/html/rfc3174 which is where the hex encoding comes from.

—Sam
_______________________________________________
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: [email protected]
_______________________________________________

Reply via email to