RE: [AVT] RFC3550 RTP Session defintion Q

["Oren Peleg" <OrenP at audiocodes.com>]

Sorry, still confused ... at the next paragraph it is written that a
three-way conference where each participant sends to each other, both
RTP & RTCP, is defined as three different RTP session, while according
to the fact here below that a single RTP session participant may have
distinct port pairs when communicating with other participants ... what
am I missing???

Oren P.

-----Original Message-----
From: casner at packetdesign.com [mailto:casner at packetdesign.com] On Behalf
Of Stephen Casner
Sent: Wednesday, August 11, 2004 7:54 PM
To: Oren Peleg
Cc: avt at ietf.org
Subject: Re: [AVT] RFC3550 RTP Session defintion Q

On Wed, 11 Aug 2004, Oren Peleg wrote:

> In the RFC 3550 RTP session definition it is written:
>
>      "A participant distinguishes
>       multiple RTP sessions by reception of different sessions using
>       different pairs of destination transport addresses"

This says that distinct sessions must use different port pairs.  It
does not say that a single session can use only one port pair.

> While at the end of the paragraph it is written:
>
>      "All participants in an RTP session may
>       share a common destination transport address pair, as in the
case
>       of IP multicast, or the pairs may be different for each
>       participant, as in the case of individual unicast network
>       addresses and port pairs.  In the unicast case, a participant
may
>       receive from all other participants in the session using the
same
>       pair of ports, or may use a distinct pair of ports for each"

This says that in one session, the port pairs may be the same for all
participants or may be different.  When they are different, then
usually some signaling will be required to know about all the
participants that should be joined into the session.  With IP
multicast using a common port pair for all, as in the early days of
the MBone, a participant needs only to know the destination address
(pair) to join and then learns of all the participants.

> How can one have distinct pair of ports for each participant in a RTP
> session while still maintaining the definition that different sessions
> have different destination transport addresses? Can anyone help me
> understand this contradiction?

Do the additional words above explain it for you?  The next paragraph
in RFC 3550 after the one you quote explains the distinguishing
feature of an RTP session.  Also note the paragraph after that which
says that a particular application design is likely to impose further
constraints.

                                                        -- Steve

************************************************************************************************************
This email and any files transmitted with it are confidential material.
They are intended solely for the use of the designated individual or entity to whom they are addressed.
If the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,use,
distribution or copying of this communication is strictly prohibited and may be unlawful.

If you have received this email in error please notify postmaster at audiocodes.com and permanently delete the e-mail and files.


***********************************************************************************************************

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