Re: [AVTCORE] Mandatory nature of RTCP
Paul Kyzivat <pkyzivat@cisco.com> Mon, 09 May 2011 13:15 UTC
Return-Path: <pkyzivat@cisco.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFAAAE0720 for <avt@ietfa.amsl.com>; Mon, 9 May 2011 06:15:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.351
X-Spam-Level:
X-Spam-Status: No, score=-109.351 tagged_above=-999 required=5 tests=[AWL=-0.856, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_HI=-8, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wQmytkvL9ltX for <avt@ietfa.amsl.com>; Mon, 9 May 2011 06:15:24 -0700 (PDT)
Received: from sj-iport-1.cisco.com (unknown [171.71.176.70]) by ietfa.amsl.com (Postfix) with ESMTP id 6284AE072C for <avt@ietf.org>; Mon, 9 May 2011 06:15:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=pkyzivat@cisco.com; l=2784; q=dns/txt; s=iport; t=1304946919; x=1306156519; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=TJCVdTLCAwfPYUnK6Qg/RGYTCX3YvX7POLaW23kpFoI=; b=IbWOdeaqZyLPTKCIe/zv3QZdUGPuPFwhCpAuWkZVsi0dWHp8YPVLCG4p mlqXLw2EBOhel8Iwy60prLEf71oQ8RpAz6++c71W8N4plcfJiW8nJKs3S 1hNuiJVgnguEEkhaY5SsbGzK96hEE0LAqwZfGbJV0/vkuEpxTIRn+5FcA 4=;
X-IronPort-AV: E=Sophos;i="4.64,340,1301875200"; d="scan'208";a="444179794"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by sj-iport-1.cisco.com with ESMTP; 09 May 2011 13:15:18 +0000
Received: from [161.44.174.124] (dhcp-161-44-174-124.cisco.com [161.44.174.124]) by rcdn-core2-2.cisco.com (8.14.3/8.14.3) with ESMTP id p49DFH2h020458; Mon, 9 May 2011 13:15:18 GMT
Message-ID: <4DC7E8E5.7080609@cisco.com>
Date: Mon, 09 May 2011 09:15:17 -0400
From: Paul Kyzivat <pkyzivat@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
References: <A444A0F8084434499206E78C106220CA089BB30490@MCHP058A.global-ad.net> <5F7BCCF5541B7444830A2288ABBEBC9620B9D67862@FRMRSSXCHMBSD2.dc-m.alcatel-lucent.com> <4DC7DE29.80602@ericsson.com>
In-Reply-To: <4DC7DE29.80602@ericsson.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Mailman-Approved-At: Mon, 09 May 2011 08:07:11 -0700
Cc: "avt@ietf.org" <avt@ietf.org>, "Schwarz, Albrecht (Albrecht)" <albrecht.schwarz@alcatel-lucent.com>
Subject: Re: [AVTCORE] Mandatory nature of RTCP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 09 May 2011 13:15:26 -0000
Magnus, IMO the first question in this area that comes up for siprec is: 1) must we be able to record the RTP of a call when that RTP doesn't have RTCP? I think the answer is clearly yes. There seems to be enough wiggle room in 3550 that we can't argue that the call is invalid and we don't need to record it. (And in general we should try to record calls even if they *are* invalid.) The next question that comes up is: 2) when recording a call with a media stream that doesn't have RTCP, must the siprec SRC synthesize RTCP in order that it will be available to the receiver? Or can we leave it to the siprec SRS to deal with it? I think we need AVTxxx input into siprec on such issues. Decisions on these things can potentially have significant architectural impact on the way recording is done. Thanks, Paul On 5/9/2011 8:29 AM, Magnus Westerlund wrote: > On 2011-05-09 13:20, Schwarz, Albrecht (Albrecht) wrote: >> RTCP is NOT MANDATORY according RFC 3550. >> I fail to see any normative statement, too. >> I could also imagine RTP use cases which do not need at all RTCP. > > I think I agree that RTCP is not mandated directly. However, in reality > it is required. Only in a few very limited usages can one skip to use RTCP. > > If one uses UDP as underlying transport then RTCP is needed to fulfill > the congestion control requirements in RFC 3550 and the profiles > (RFC3551). Both has a SHOULD requirement and that SHOULD exist to allow > cases where you have dedicated resource. > > Then we have all the binding information that RTCP provides, like time > synchronization (RTCP SR), which to be synchronized (SDES CNAME). Some > single media applications can live without this, but any multi-media do > need some of this. > > There is a reason why RTP doesn't contain so much hard requirements. RTP > is a toolbox and applications are suppsed to pick the pieces it needs. > And general RTCP is needed in most cases. So I would recommend any one > deciding on RTP/RTCP should start with describing what application > requirements they have. Then pick the RTP parts. > > But I will guess that SIPREC is likely to need RTCP. But please do your > analysis of what you need. > > Cheers > > Magnus Westerlund > > ---------------------------------------------------------------------- > Multimedia Technologies, Ericsson Research EAB/TVM > ---------------------------------------------------------------------- > Ericsson AB | Phone +46 10 7148287 > Färögatan 6 | Mobile +46 73 0949079 > SE-164 80 Stockholm, Sweden| mailto: magnus.westerlund@ericsson.com > ---------------------------------------------------------------------- > >
- [AVTCORE] Mandatory nature of RTCP Elwell, John
- Re: [AVTCORE] Mandatory nature of RTCP Schwarz, Albrecht (Albrecht)
- Re: [AVTCORE] Mandatory nature of RTCP Magnus Westerlund
- Re: [AVTCORE] Mandatory nature of RTCP Schwarz, Albrecht (Albrecht)
- Re: [AVTCORE] Mandatory nature of RTCP Paul Kyzivat
- Re: [AVTCORE] Mandatory nature of RTCP Elwell, John
- Re: [AVTCORE] Mandatory nature of RTCP Magnus Westerlund
- Re: [AVTCORE] Mandatory nature of RTCP Paul Kyzivat