{"action":"created","issue":{"url":"https://api.github.com/repos/node-xmpp/JID/issues/1","labels_url":"https://api.github.com/repos/node-xmpp/JID/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/node-xmpp/JID/issues/1/comments","events_url":"https://api.github.com/repos/node-xmpp/JID/issues/1/events","html_url":"https://github.com/node-xmpp/JID/issues/1","id":105991133,"number":1,"title":"RFC 7622","user":{"login":"sonnyp","id":19673,"avatar_url":"https://avatars.githubusercontent.com/u/19673?v=3","gravatar_id":"","url":"https://api.github.com/users/sonnyp","html_url":"https://github.com/sonnyp","followers_url":"https://api.github.com/users/sonnyp/followers","following_url":"https://api.github.com/users/sonnyp/following{/other_user}","gists_url":"https://api.github.com/users/sonnyp/gists{/gist_id}","starred_url":"https://api.github.com/users/sonnyp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sonnyp/subscriptions","organizations_url":"https://api.github.com/users/sonnyp/orgs","repos_url":"https://api.github.com/users/sonnyp/repos","events_url":"https://api.github.com/users/sonnyp/events{/privacy}","received_events_url":"https://api.github.com/users/sonnyp/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-09-11T11:19:57Z","updated_at":"2015-12-10T04:43:24Z","closed_at":null,"body":"http://www.rfc-editor.org/rfc/rfc7622.txt\r\n\r\n> As specified in RFCs 3920 and 6122, the XMPP address format used the\r\n   \"stringprep\" technology for preparation and comparison of non-ASCII\r\n   characters [RFC3454].  Following the movement of internationalized\r\n   domain names away from stringprep, this document defines the XMPP\r\n   address format in a way that no longer depends on stringprep (see the\r\n   Preparation, Enforcement, and Comparison of Internationalized Strings\r\n   (PRECIS) problem statement [RFC6885]).  Instead, this document builds\r\n   upon the internationalization framework defined by the IETF's PRECIS\r\n   working group [RFC7564]."},"comment":{"url":"https://api.github.com/repos/node-xmpp/JID/issues/comments/163486451","html_url":"https://github.com/node-xmpp/JID/issues/1#issuecomment-163486451","issue_url":"https://api.github.com/repos/node-xmpp/JID/issues/1","id":163486451,"user":{"login":"ezzatron","id":100152,"avatar_url":"https://avatars.githubusercontent.com/u/100152?v=3","gravatar_id":"","url":"https://api.github.com/users/ezzatron","html_url":"https://github.com/ezzatron","followers_url":"https://api.github.com/users/ezzatron/followers","following_url":"https://api.github.com/users/ezzatron/following{/other_user}","gists_url":"https://api.github.com/users/ezzatron/gists{/gist_id}","starred_url":"https://api.github.com/users/ezzatron/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ezzatron/subscriptions","organizations_url":"https://api.github.com/users/ezzatron/orgs","repos_url":"https://api.github.com/users/ezzatron/repos","events_url":"https://api.github.com/users/ezzatron/events{/privacy}","received_events_url":"https://api.github.com/users/ezzatron/received_events","type":"User","site_admin":false},"created_at":"2015-12-10T04:43:24Z","updated_at":"2015-12-10T04:43:24Z","body":"@sonnyp Unfortunately it's probably not something I can take on right now, as I have a fairly ridiculous stack of projects to maintain already (I'm sure you can relate). The other obstacle is that I don't have any XMPP knowledge at all.\r\n\r\nI actually wrote `precis-js` simply to deal with Unicode usernames and passwords on a toy project, because there are no available stringprep implementations that could feasibly work in a browser. I only learned that it was relevant to XMPP later.\r\n\r\nI'm more than happy to help with advice on integrating `precis-js` into this repo if that's helpful, but I just don't have the time to read, and to *really* understand another bunch of RFCs at the moment.\r\n\r\nSide note, there are still some serious issues with `precis-js`, brought up just a couple of days ago in eloquent/precis-js#1, and further documented in eloquent/precis-js#6 and eloquent/precis-js#7. And there's also (potentially) a big problem with PRECIS itself (see [this discussion](https://mailarchive.ietf.org/arch/msg/precis/Jua858TgnE6GFGb5XUnPqPK3CmQ))."}}