XEP-0077 password change

Stephen Paul Weber <[email protected]> Sun, 12 Apr 2026 19:31:49 -0500
Newsgroups gmane.network.jabber.standards-jig
Message-ID <[email protected]>
It seems to me that XEP-0077 is not RFC compliant in section 3.3 
specifically it says:

> In order to require additional information before changing the password, 
> the server or service SHOULD return a Data Form in the error stanza:

However https://datatracker.ietf.org/doc/html/rfc6120#section-8.2.3 says:

> An IQ stanza of type "error" MAY include the child element
> contained in the associated "get" or "set" and MUST include an
> <error/> child

That is to say, it may not contain any child other than an <error/> child 
and possibly an echo of the request.

Now, one could imagine a syntax for embedding a data form in an <error/> but 
this is not what XEP-0077 describes.

Has anyone implemented this part of XEP-0077 in practise? If I return the 
error with this form will anyone respect it? Do we need to care that this is 
not RFC compliant or can we squint and say that it's a sort-of echo of the 
request but with more fields to fill out...

_______________________________________________
Standards mailing list -- [email protected]
To unsubscribe send an email to [email protected]
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEWeaCw+rzmiEMpzU00RwpEc5RnN4FAmncOXEACgkQ0RwpEc5R
nN7SmRAAzfxzA1dQJBzeSqlwNYKAR4rrsuvZ1q0y2SmB1PL2ntzKupt3U2MGFfad
pQ46wqBV4eoG8+4ZePV7mPIx3Don72iFj32fJ16/BPrhBQ5e0bJOOLW/DrqYbUAI
Fcot9c0+vKvcOXgB2jPtoNfjjfqbtJ6Or+cdjPUpKCqklCliDxucUeDAgTB80FN4
GNbjYTU2US+Xhf5UZWOfjdlOJrd8YmQgxDvJOA6esUKZXFQD9X3i0ZsrGGfygMyw
irMtU/wfqAkrKRuGzCJ+25eFRcBYPiplX0bBEG8h5pwNYtUQo7uE+jNeRPTlFROH
rPaodPPX4TiuYKnz8N0RhVBrWGTd/a0DqvCxFwZ3FRDGlrDWLSq1ZQTG+PU9kI2H
BFHc4icCtCylC3lx0fkJFmVAGGAw+tOApDzUBfiTCC+wY86qlTNWakie19sfAnun
OKAIjx2vzdRqTMbk3l3kRzjirUzc9bEMA2I+Pjww7ujm4SmTYAtQzAd31Lo2Timq
XFk+jQQ8BGPkPfUEYUM8fqGe/7tishPg4Ft6bilQ+4hUMwJOb2+vjOIoc36LFZGC
MED0AF4Owio5MfufhKy99tyYpXfEfxG/cf/kgtPte2oNmfMVFalilXf+ZXroOx/+
mQLyRlJqilV/Sv7qUIu1vfwAV2lLN6xX3DxRuMQVpCrJGbUiYdM=
=1S3b
-----END PGP SIGNATURE-----