Interworking between the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP): Presence
RFC 7248

Note: This ballot was opened for revision 07 and is now closed.

(Richard Barnes) Yes

(Gonzalo Camarillo) Yes

(Spencer Dawkins) Yes

(Pete Resnick) (was Discuss) Yes

Comment (2014-02-09)
No email
send info
This last version (and some conversation from the author) has answered my concerns with this document. Thanks.

(Sean Turner) Yes

(Jari Arkko) No Objection

(Stewart Bryant) No Objection

(Benoît Claise) No Objection

(Adrian Farrel) No Objection

(Stephen Farrell) No Objection

Comment (2014-02-06 for -07)
No email
send info
If the protocol between the gateways is not protected via
(D)TLS, then doesn't this (and probabaly all other gateway
functions) act in a potentially privacy unfriendly manner?
I would have thought that worth noting at least, e.g. say
that if (D)TLS is not used when gatewaying then the user
has lost whatever security they used to have for their
presence. (See also my comment on stox-core wrt turning on
or requiring implementation of (D)TLS beteen gateways.)

Sorry - forgot to note the change resulting from the
secdir review [1] just in case it gets forgotten in a 
rush of some sort.

   [1] https://www.ietf.org/mail-archive/web/secdir/current/msg04581.html

(Brian Haberman) No Objection

(Joel Jaeggli) No Objection

Barry Leiba No Objection

(Ted Lemon) No Objection

(Martin Stiemerling) No Objection