[AVTCORE] Mandatory nature of RTCP
"Elwell, John" <john.elwell@siemens-enterprise.com> Mon, 09 May 2011 10:34 UTC
Return-Path: <john.elwell@siemens-enterprise.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 8F16DE07E8 for <avt@ietfa.amsl.com>; Mon, 9 May 2011 03:34:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.329
X-Spam-Level:
X-Spam-Status: No, score=-105.329 tagged_above=-999 required=5 tests=[AWL=1.270, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 H9a4K0+zV0vb for <avt@ietfa.amsl.com>; Mon, 9 May 2011 03:34:19 -0700 (PDT)
Received: from mail21.messagelabs.com (mail21.messagelabs.com [85.158.143.35]) by ietfa.amsl.com (Postfix) with SMTP id 1537BE068D for <avt@ietf.org>; Mon, 9 May 2011 03:34:18 -0700 (PDT)
X-VirusChecked: Checked
X-Env-Sender: john.elwell@siemens-enterprise.com
X-Msg-Ref: server-5.tower-21.messagelabs.com!1304937242!43085192!1
X-StarScan-Version: 6.2.16; banners=-,-,-
X-Originating-IP: [62.134.46.10]
Received: (qmail 18625 invoked from network); 9 May 2011 10:34:02 -0000
Received: from unknown (HELO senmx12-mx) (62.134.46.10) by server-5.tower-21.messagelabs.com with SMTP; 9 May 2011 10:34:02 -0000
Received: from MCHP063A.global-ad.net (unknown [172.29.37.61]) by senmx12-mx (Server) with ESMTP id BB79623F03DB; Mon, 9 May 2011 12:34:17 +0200 (CEST)
Received: from MCHP058A.global-ad.net ([172.29.37.55]) by MCHP063A.global-ad.net ([172.29.37.61]) with mapi; Mon, 9 May 2011 12:34:17 +0200
From: "Elwell, John" <john.elwell@siemens-enterprise.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Mon, 09 May 2011 12:34:16 +0200
Thread-Topic: Mandatory nature of RTCP
Thread-Index: AcwOM3h+37XBoCL+T6yltj1OV9eVeg==
Message-ID: <A444A0F8084434499206E78C106220CA089BB30490@MCHP058A.global-ad.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "Paul Kyzivat (pkyzivat)" <pkyzivat@cisco.com>
Subject: [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 10:34:20 -0000
I am sure I have heard many times experts say that RTCP is a mandatory part of RTP. However, some people looking into RTP as part of work in the SIPREC WG have failed to find convincing normative statements in RFC 3550. Any pointers would be appreciated. Thanks, John
- [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