On 06/03/2008 2:14 PM, Maiku wrote: > In XEP-0176, Jingle using the ICE-UDP transport method, it says for > the initiator to send out the transport candidates either as soon as > getting the ACK from the session-initiate message or just as soon as > sending the session-initiate message, but I can't seem to find any > place that mentions where the responder's client would wait for the > responder to actually click to accept the session. Where would this > happen? Would the responder wait to send transport-info packets until > the user actually accepts? If not, wouldn't that be a security issue, > sending out your IP address to anyone who tries to start a session > with you?
Maiku and I chatted about this via IM just now. I think it would make sense for the client to have a configuration setting such as "it's OK to share my personally identifying information (such as my network location) with people who can see my presence" [yeah yeah yeah that's long, shorten it as necessary!]. So if you share presence, your client will ack the session-initiate, return a ringing message, and start sending candidates. If you don't share presence, you would ack and send ringing but not share candidates until the user accepts the negotiation. Thoughts? Peter -- Peter Saint-Andre https://stpeter.im/
smime.p7s
Description: S/MIME Cryptographic Signature
