On 2010-06-18 04: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? Yes, this is important. Assuming that this exchange implicitly uses the EVEN-PORT and RESERVATION-TOKEN attributes, I think it should be made explicit in the text. i.e. Message (1) contains an EVEN-PORT attribute with the R flag set to 1. Message (3) contains a RESERVATION-TOKEN attribute, which is echoed in message (5). Simon -- NAT64/DNS64 open-source --> http://ecdysis.viagenie.ca STUN/TURN server --> http://numb.viagenie.ca vCard 4.0 --> http://www.vcarddav.org _______________________________________________ Sipping mailing list https://www.ietf.org/mailman/listinfo/sipping This list is for NEW development of the application of SIP Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
