[AVT] RE: [Ietf-behave] RTP in draft-ietf-behave-nat-00

On Mon, 8 Nov 2004, Francois Audet wrote:

> Dan is correct.
>
> We are not looking at implementations that don't support RTCP. This is not
> what we were trying to address.

Good.

> We were looking at applications that, upon receiving an
> instruction to send RTP to an odd address would interpret the RFC 3550
> wording to say that it should send it to the the even address that is
> one lower than the one advertized (which would break protocols such
> as SIP/SDP).

If a SIP/SDP application receives instructions to send RTP to an odd
address (that is, port) when the SDP does not include an a=rtcp
attribute (RFC 3605) to specify the RTCP port separately, then indeed,
RFC 3550 does say that the RTP should be sent to the even port that is
one lower.  But, I claim this SIP/SDP application is broken if it was
expecting the application to send RTP on the odd port and RTCP on the
next higher even port (or maybe the next lower even port, or even the
odd port two higher).  Do you disagree?

                                                        -- Steve

_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt