On Tue, Jul 02, 2013 at 09:32:50AM +0200, Daniele Ricci wrote:
(1) Matt's work on draft-miller-xmpp-e2e
(2) OTR (potentially with future enhancements to make it more
XMPP-friendly)
Some energy is going into both of those (Paul Wouters and I plan to
sync up at the IETF meeting at the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/16/13 4:27 AM, Carlo v. Loesch wrote:
On Tue, Jul 02, 2013 at 09:32:50AM +0200, Daniele Ricci wrote:
(1) Matt's work on draft-miller-xmpp-e2e (2) OTR (potentially
with future enhancements to make it more XMPP-friendly)
Some energy is going
On Mon, Jul 1, 2013 at 7:06 PM, Peter Saint-Andre stpe...@stpeter.im wrote:
What about applying PGP/MIME instead
As in http://xmpp.org/extensions/xep-0027.html perhaps?
I mean using PGP/MIME the same way RFC 3923 uses S/MIME.
I think you mean: draft-miller-xmpp-e2e replaces RFC 3923.
Yes,
Greetings,
I was reading RFC 3923 [1], and it always talks about S/MIME encrypted
message format. What about applying PGP/MIME instead - or better, let
the RFC handle both cases?
If I understand correctly, draft-miller-xmpp-e2e-* are replaced by RFC
3923. Is there some draft to follow/improve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 7/1/13 10:24 AM, Daniele Ricci wrote:
Greetings, I was reading RFC 3923 [1],
Yeah, we're not proud of that spec.
and it always talks about S/MIME encrypted message format.
IETF dogma at the time required that.
What about applying PGP/MIME
