[Standards-JIG] RE: [jdev] Call for Experience: JEP-0077 (In-Band Registration)
tcoffin at asg.bellsouth.net
Mon Apr 26 17:31:55 UTC 2004
I definitely think it's time to get this one as part of the standards.
We've been using it in our client and server for a couple of years and
we're happy with it.
Even though we've talked about dropping an actual registration
requirement (since the users are already provisioned as part of their
ISP service), we will still use this protocol to allow them to choose
their own "cool" nicknames.
1. We've implemented JEP 77 in the BellSouth Messenger, with the
+ We don't actually use the get stanza, since we already know what
our server expects.
+ We use a non-standard coding of the <name> field to capture first
name, last name and nick name. We plan to use <first/>, <last/> and
<nick/> in the future.
+ We don't support the Password Change feature. That's provisioned
out of band.
+ We don't allow users to unregister themselves. We unregister them
as part of the provisioning flow when they drop their BellSouth Email
+ And, of course, we're working with the old-style errors.
2. No problems with the protocol itself.
3. The JEP has an inconsistency in section 4.1: Example 1 says you
request the reg info (get) anonymously, and Example 3 says the server
should tell you if you're already registered. Without a jid, how can
the server do this? Either:
+ The iq/get should have a jid in it (which also would allow the
server to request different information for users with different
domains, etc.) or
+ The <registered/> message could come instead of the error 409
Username Conflict. Although, really, how can the server tell the
difference, unless you happen to send the same password?
Actually, I think this provides the same info as the Username Conflict,
and so should be dropped as redundant.
Server Products Architect and Team Lead
BellSouth Internet Group
tom.coffin at asg.bellsouth.net <mailto:tom.coffin at asg.bellsouth.net>
From: Peter Saint-Andre [mailto:stpeter at jabber.org]
Sent: Sunday, April 25, 2004 11:32 PM
To: standards-jig at jabber.org
Cc: jdev at jabber.org
Subject: [jdev] Call for Experience: JEP-0077 (In-Band Registration)
A little over a month ago, the Jabber Council agreed that it would be
desirable to advance several JEPs from Draft to Final if the Jabber
community deems them to be stable and well-received. The first of them
was JEP-0030 (Service Discovery), for which the Call for Experience has
been completed. The second was JEP-0077 (In-Band Registration).
Therefore, as JEP Editor I would like to issue a Call for Experience on
JEP-0077. To help the Jabber Council decide whether this JEP is ready to
advance to a status of Final, the JSF would like to gather the following
1. Who has implemented JEP-0077? I realize that the list is probably
quite long, since in-band registration has been around for a long time
and is considered a fairly "core" feature, but a list of implementations
would be appreciated. (But probably I can just go to the software pages
at <http://www.jabber.org/software/> for a list.)
2. Have implementers experienced any problems with the protocol as
defined in JEP-0077? If so, please describe the problems and, if
possible, suggested solutions.
3. Is the text of JEP-0077 clear and unambiguous? Are more examples
necessary? Is the conformance language (MAY/SHOULD/MUST) appropriate?
Have implementers found the text confusing at all? Please describe any
suggestions you have for improving the text.
If you have any comments on this JEP, please provide them by the close
of business on May 10, at which time the Call for Experience will end.
After the Call for Experience, this JEP may undergo revisions to address
feedback received, after which it will be presented to the Jabber
Council for voting to a status of Final.
You may review the JEP here:
Please send all feedback to <standards-jig at jabber.org>.
Jabber Software Foundation
jdev mailing list
jdev at jabber.org
More information about the Standards