XMPP WG Discussion IETF 57, Vienna Peter Saint-Andre
End-to-End Encryption: Basic Architecture Encapsulate multipart S/MIME object as CDATA section in child of of message, presence, or IQ For message interoperability, use "Message/CPIM" as defined in CPIM MSGFMT For presence interoperability, use "application/pidf+xml" as defined in CPIM PIDF Use of new "application/xmpp+xml" MIME type enables inclusion of arbitrary XMPP data
End-to-End Encryption: Certificates Etc. Enrollment out of scope (specified by PKIX WG) Retrieval must be handled by receiving agent JID included in subjectAltName extension (not in subject distinguished name), choice = otherName, type-id = xmpp Inclusion of certificate is not required Signatures should be attached
End-to-End Encryption: Technologies Mandatory-to-implement technologies: for digest: DIGEST-MD5 for signing: RSA for content encryption: Triple-DES CBC
CPIM Mapping Detailed mappings from XMPP to MSGFMT, PIDF, and "Message/CPIM" headers (and back) Definition of an XMPP-CPIM gateway as a presence service, including subscription requests, subscription durations, the notify operation, unsubscribing, and cancelling a subscription What specs require what other specs?
Core, IM, Nodeprep, Resourceprep Last call comments have ended Desirable to add a state chart for subscriptions (will do before sending to AD)