JHildebrand at jabber.com
Fri Jun 13 12:16:40 CDT 2003
"If the entity is already registered, the IQ result MUST NOT contain
instructions and empty registration fields; "
Can this at least be weakened to a SHOULD NOT, if not removed altogether?
It makes the client-writers job hard, since you still have to show this to a
3.2, there are other error cases
-removing an unknown user
There should probably be a thing that says that re-setting the password for
an existing account (one with <registered/>) SHOULD NOT have an effect.
That's an iq:auth thing.
Oh... That needs to be in 0078, too. Sigh. That probably futzes with the
SHOULD NOT's for plaintext.
> -----Original Message-----
> From: Peter Saint-Andre [mailto:stpeter at jabber.org]
> Sent: Thursday, June 12, 2003 9:23 PM
> To: council at jabber.org
> On Wed, Jun 11, 2003 at 07:41:04PM -0600, Joe Hildebrand wrote:
> > Ack. Actually, -1 to 77.
> > It doesn't have <registered/>.
> I've added this, specified the FORM_TYPE, etc. The full changelog is:
> Added <registered/> element; specified FORM_TYPE for x:data
> form; clarified that support for the extensibility mechanism
> is optional; removed the <misc/> and <text/> elements (not
> necessary given extensibility option); added <nick/>,
> <first/>, and <last/> elements that were traditionally
> documented as part of jabber:iq:register. (psa)
> Let me know if this addresses the Council's concerns (or
> introduces new ones!).
> Council mailing list
> Council at jabber.org
More information about the Council