New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XEP-0176 data type of ICE foundation
#575
Comments
see https://xmpp.org/extensions/xep-0371.html#protocol-syntax -- we fixed this there. |
So it's just a matter of fixing the schema, replacing
with
? |
@Flowdalic there is a bigger issue. 0176 was written against a pre-RFC version of ICE which was in limbo for half a decade before it became RFC 5245 |
We really should deprecate XEP-0176 and advance XEP-0371. I had some non-related fixes in process but lost track of this work item a few years ago. :( |
we made notes in the wiki page... |
Yeah, but finding the time and energy to work on it is not so easy. :-) I will try to find my edits this weekend (unfortunately they were to the entire Jingle suite so it was a big changeset). |
Jingle ICE defines the "foundation" of it's ICE candidate as an unsigned byte in it's schema: https://xmpp.org/extensions/xep-0176.html#schema which does not seem to match the ICE RFC which defines it as a string: https://tools.ietf.org/html/rfc5245#section-15.1
XEP-0176 should change the type
foundation
string with valid chars A-z, 0-9, +, /@legastero @fippo @stpeter
The text was updated successfully, but these errors were encountered: