[Standards] Re: compliance: Basic Client (0211)

Peter Saint-Andre stpeter at jabber.org
Wed May 9 16:02:00 UTC 2007

Magnus Henoch wrote:
> Jakob Schroeter <js at camaya.net> writes:
>> E2EE is optional (a XEP, not a MUST in the RFC) and not a replacement for 
>> current TLS usage, since it doesn't cover things like e.g. roster fetch.
> Actually, E2E (in the shape of RFC 3923) is required, according to
> section 12.2 of RFC 3921:
> "12.2.  Clients
> In addition to core client compliance requirements, an instant
> messaging and presence client MUST additionally support the following
> protocols:
> [...]
> * End-to-end object encryption as defined in End-to-End Object
>   Encryption in the Extensible Messaging and Presence Protocol (XMPP)
>   (Saint-Andre, P., “End-to-End Signing and Object Encryption for the
>   Extensible Messaging and Presence Protocol (XMPP),” October 2004.)
>   [XMPP‑E2E]"
> I think the client compliance XEPs should have an exception for this,
> as RFC 3923 is, in its own words, "hrozny", and not likely to be
> implemented any time soon.

Yes I would agree. But did I actually call it hrozny in the RFC? ;-)

We could split up the features more, like I did here:



Peter Saint-Andre
XMPP Standards Foundation

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070509/567b12d2/attachment.bin>

More information about the Standards mailing list