-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI.
- Original Message
Subject: [Council] meeting minutes, 2009-04-29
Date: Wed, 29 Apr 2009 21:12:30 -0600
From: Peter Saint-Andre
Reply-To: XMPP Council
To: XMPP Council
Results of the XMPP Council meeting held 2009-04-29...
Philipp Hancke wrote:
Peter Saint-Andre wrote:
Joe Hildebrand and I have started working on an Internet-Draft that
describes at least the requirements and possibly proposed solutions to
the challenge of securely multiplexing multiple domains over the same
XML stream.
Btw, could you remove t
Peter Saint-Andre wrote:
Joe Hildebrand and I have started working on an Internet-Draft that
describes at least the requirements and possibly proposed solutions to
the challenge of securely multiplexing multiple domains over the same
XML stream.
Btw, could you remove the other usage of 'multipl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Joe Hildebrand and I have started working on an Internet-Draft that
describes at least the requirements and possibly proposed solutions to
the challenge of securely multiplexing multiple domains over the same
XML stream.
The deployment scenario we hav
On Wed, Apr 29, 2009 at 5:42 AM, Peter Saint-Andre wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> FYI. This proposal emerged from discussions among some operators and
> server vendors at XMPP Summit #6 in February...
>
The current proposal doesn't look bad. A few notes follow.
The
> Is it a question of message, presence (in/out) or iq? Or all stanza types?
Well, it should behave the same as the rules described in the XEP, so
that means all stanza types (see 5.3). I'm not sure repeating the
rules helps much in clarifying that.
cheers,
Remko
Hi,
XEP-0191: Simple Communications Blocking
http://xmpp.org/extensions/xep-0191.html
IMHO, as a non-english native (o not), the mapping with Privacy lists
(XEP-0016) needs a little bit of clarification:
"A service SHOULD map the blocklist to the default privacy list, where
each blocked JID is r
