[Council] Fwd: Re: [Standards] XEP-0077 In-band registration: error code handling

Peter Saint-Andre stpeter at stpeter.im
Mon Jun 13 21:58:42 UTC 2011


This raise a more general issue, because several specs (e.g., XEP-0045)
contain MUST/SHOULD references to XEP-0086. Perhaps we can discuss this
briefly during the meeting this Wednesday.

-------- Original Message --------
Subject: Re: [Standards] XEP-0077 In-band registration: error code handling
Date: Mon, 13 Jun 2011 15:49:25 -0600
From: Peter Saint-Andre <stpeter at stpeter.im>
Reply-To: XMPP Standards <standards at xmpp.org>
To: XMPP Standards <standards at xmpp.org>

On 5/26/11 5:42 PM, Glenn Maynard wrote:
> XEP-0077 sec9:
> 
>> As defined herein, the 'jabber:iq:register' namespace supports both the old (HTTP-style) error codes and the extensible error classes and conditions specified in XMPP Core. A compliant server or service implementation MUST support both old-style and new-style error handling. A compliant client implementation SHOULD support both. For mappings of HTTP-style errors to XMPP-style conditions, refer to Error Condition Mappings [12].
> 
> XEP-0086 is deprecated.  It doesn't make sense for an active spec to
> have a normative requirement on a deprecated one.  Should this
> paragraph be removed?

Good point. In fact there is one other open issue with XEP-0077 so I'll
fix the XEP-0086 reference when I close that other issue.

http://tracker.xmpp.org/browse/SPEC-21

Peter

-- 
Peter Saint-Andre
https://stpeter.im/




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6105 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/council/attachments/20110613/d848dec2/attachment.bin>


More information about the Council mailing list