IETF Logo Mail Archive

Re: [AVT] 2833bis - RTP ping

Henning Schulzrinne <hgs@cs.columbia.edu> Thu, 24 October 2002 15:26 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12208 for <avt-archive@odin.ietf.org>; Thu, 24 Oct 2002 11:26:53 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id g9OFSiv24126 for avt-archive@odin.ietf.org; Thu, 24 Oct 2002 11:28:44 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OFSGv24093; Thu, 24 Oct 2002 11:28:16 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9OFPxv23969 for <avt@optimus.ietf.org>; Thu, 24 Oct 2002 11:25:59 -0400
Received: from cs.columbia.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12074 for <avt@ietf.org>; Thu, 24 Oct 2002 11:23:38 -0400 (EDT)
Received: from opus.cs.columbia.edu (opus.cs.columbia.edu [128.59.20.100]) by cs.columbia.edu (8.12.6/8.12.6) with ESMTP id g9OFPim6016403; Thu, 24 Oct 2002 11:25:44 -0400 (EDT)
Received: from cs.columbia.edu (tallgrass.netlab.uky.edu [204.198.76.66]) (authenticated bits=0) by opus.cs.columbia.edu (8.12.6/8.12.6) with ESMTP id g9OFPh4l014656 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 24 Oct 2002 11:25:43 -0400 (EDT)
Message-ID: <3DB810E0.1000809@cs.columbia.edu>
Date: Thu, 24 Oct 2002 11:25:20 -0400
From: Henning Schulzrinne <hgs@cs.columbia.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Flemming Andreasen <fandreas@cisco.com>
CC: avt@ietf.org
Subject: Re: [AVT] 2833bis - RTP ping
References: <3CF3F6E3.3080602@cs.columbia.edu> <3D3731FB.E0FA609E@cisco.com> <3DB47096.2030706@cs.columbia.edu> <3DB6EE02.E2BE6E9C@cisco.com> <3DB8093B.9020606@cs.columbia.edu> <3DB80F6A.338C617@cisco.com>
In-Reply-To: <3CF3F6E3.3080602@cs.columbia.edu>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: avt-admin@ietf.org
Errors-To: avt-admin@ietf.org
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

That makes more sense. Triggered media transmission is probably the 
right mental model. The flooding issues are still similar, including in 
large conferences with a mixer in the middle (where most of the time, 
only one person speaks).

Would a periodic RTP beacon serve the same purpose? Via RTCP, you'd know 
whether the other side has received the beacon.

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

v2.46.0 | Report a Bug | By Email | System Status