On 11/13/09 1:54 AM, Marcus Lundblad wrote: > tor 2009-11-12 klockan 16:52 +0000 skrev Pedro Melo: >> On 2009/11/12, at 16:20, Dirk Meyer wrote: >> >>> Marcus Lundblad wrote: >>>> A has access to a proxy. >>> [...] >>>> At this point A will try to connect to the proxy in order to activate >>>> the bytestream, but this will fail since A's firewall blocks port >>>> 7777. >>> OK, the problem is a A THINKS it has access to a proxy but that is not >>> the case. A never tried if the proxy works. >> 'A' could try to connect to the proxy before announcing that >> candidate... >> > > Yes, but that wouldn't catch the case when something went wrong with the > activation.
So this is only for problems connecting to the proxy (which perhaps could be checked ahead of time, as Pedro suggests) or also with problems related to activation (as you say, if the hashes don't match or the proxy doesn't like A's credentials)? Do you think we need separate error conditions for those cases? IMHO we can use <proxy-error/> for both. Thus A would send something like the following to B: <iq from='[email protected]/orchard' id='hx91j3s6' to='[email protected]/balcony' type='set'> <jingle xmlns='urn:xmpp:jingle:1'> action='transport-info' initiator='[email protected]/orchard' sid='a73sjjvkla37jfea'> <content creator='initiator' name='stub'> <transport xmlns='urn:xmpp:jingle:transports:s5b:1' sid='vj3hs98y'> <proxy-error/> </transport> </content> </jingle> </iq> Good catch! /psa
smime.p7s
Description: S/MIME Cryptographic Signature
