RE: RE : RE : [AVT] draft-ietf-avt-rtcp-report-extns-02.txt

"Alan Clark" <alan@telchemy.com> Tue, 25 February 2003 18:30 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 NAA09776 for <avt-archive@odin.ietf.org>; Tue, 25 Feb 2003 13:30:21 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h1PIdSn20577 for avt-archive@odin.ietf.org; Tue, 25 Feb 2003 13:39:28 -0500
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PId5p20556; Tue, 25 Feb 2003 13:39:05 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h1PIcVp20518 for <avt@optimus.ietf.org>; Tue, 25 Feb 2003 13:38:31 -0500
Received: from telchemy.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09705 for <avt@ietf.org>; Tue, 25 Feb 2003 13:28:54 -0500 (EST)
Received: from TELWS104 [64.238.103.215] by telchemy.com with ESMTP (SMTPD32-7.11) id A6D32070148; Tue, 25 Feb 2003 13:32:51 -0500
Reply-To: alan@telchemy.com
From: Alan Clark <alan@telchemy.com>
To: "'Magnus Westerlund (EAB)'" <Magnus.Westerlund@era.ericsson.se>, ''Timur Friedman' ' <timur.friedman@lip6.fr>
Cc: avt@ietf.org
Subject: RE: RE : RE : [AVT] draft-ietf-avt-rtcp-report-extns-02.txt
Date: Tue, 25 Feb 2003 13:30:41 -0500
Message-ID: <002301c2dcfc$0132a200$6801a8c0@telchemy.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
In-Reply-To: <034BEFD03799D411A59F00508BDF754602BF4174@esealnt448.al.sw.ericsson.se>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Content-Transfer-Encoding: 8bit
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: 8bit

Magnus

>To my knowledge the necessary signalling is in place for all other types of
RTCP reporting. The AVPF defines SDP attribute that allows control of the
usage of the formats within that proposal. So I don´t think arguing that it
is a general problem would lessen the need for SDP attributes in regards to
XR formats.

[Alan] I don't recall seeing any explicit means of turning RTCP reports on
and off and was only able to locate an expired draft on using SDP to
negotiate RTCP bandwidth.  It would be helpful if you could provide some
references to existing signalling protocols.

>By supporting SDP you support the basic signalling that are currenlty in
use by the most common real-time media applications using RTP/RTCP. SIP uses
SDP, RTSP uses SDP.

[Alan] How about H.323?

Regards

Alan Clark
Telchemy



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