Re: draft-ietf-sipping-nat-scenarios, TURN and RTCP

On 2010/06/18 10:24, Frank Shearar wrote:
> draft-ietf-sipping-nat-scenarios-13 section 5.2.2.2 TURN Solution shows
> a user agent sending two Alloc Reqs to a TURN server for its two media
> ports (RTP + RTCP). The TURN server returns (message (3)) STUN-PUB-2 for
> the first Alloc Req and (message (7)) STUN-PUB-3 for the second Alloc Req.
>
> Surely STUN-PUB-2 is not necessarily the same as STUN-PUB-3?
>
> I would imagine that in most environments it would be, but if it's not a
> MUST, what does one do in the SDP, given that "a=rtcp:$STUN-PUB-3.port"
> defines the port that RTCP will use, but not the address?

It occurs to me that if $STUN-PUB-2.address != $STUN-PUB-3.address then 
the user agent could
* repeatedly ask for TURN bindings until it gets a pair with the same 
address or
* elect to multiplex RTP and RTCP over the same port, and abandon the 
TURN binding for RTCP.
* ???

frank
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email protected] for questions on current sip
Use [email protected] for new developments of core SIP