[AVT] rtcpssm and RTP MIDI ...
John Lazzaro <lazzaro@CS.Berkeley.EDU> Thu, 05 June 2003 00:41 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 UAA19837 for <avt-archive@odin.ietf.org>; Wed, 4 Jun 2003 20:41:14 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h550elY03164 for avt-archive@odin.ietf.org; Wed, 4 Jun 2003 20:40:47 -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 h550bJB02655; Wed, 4 Jun 2003 20:37:21 -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 h550YMB02006 for <avt@optimus.ietf.org>; Wed, 4 Jun 2003 20:34:22 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19541 for <avt@ietf.org>; Wed, 4 Jun 2003 20:34:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Nig8-0001dF-00 for avt@ietf.org; Wed, 04 Jun 2003 20:32:28 -0400
Received: from snap.cs.berkeley.edu ([128.32.34.209] ident=root) by ietf-mx with esmtp (Exim 4.12) id 19Nig8-0001dB-00 for avt@ietf.org; Wed, 04 Jun 2003 20:32:28 -0400
Received: (from lazzaro@localhost) by snap.CS.Berkeley.EDU (8.11.6/8.9.3-ZUUL) id h550W4d04165 for avt@ietf.org; Wed, 4 Jun 2003 17:32:04 -0700
Date: Wed, 04 Jun 2003 17:32:04 -0700
From: John Lazzaro <lazzaro@CS.Berkeley.EDU>
Message-Id: <200306050032.h550W4d04165@snap.CS.Berkeley.EDU>
To: avt@ietf.org
Subject: [AVT] rtcpssm and RTP MIDI ...
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>
Hi everyone, I've been looking over draft-ietf-avt-rtcpssm-03.txt, with respect to RTP MIDI issues ... good news to report. The defined summary information report blocks are sufficient for RTP MIDI receivers -- additional summary information report blocks for the "extended highest sequence number received" RR field are not necessary. However, the RTP _sender_ does need to see the raw unicast RTCP feedback stream. The summarized view of the feedback in the RSI XR packets is not sufficient for a sender to manage the recovery journal system. The only reason I could see for adding new summary information report blocks would be to support a distributed architecture, where one process generates RSI XR packets from the unicast feedback stream, a second process generates RTP packets, and the second process does not have access to the raw unicast RTCP feedback stream (only the summaries). Was this sort of architecture viewed as a common usage scenario? ------------------------------------------------------------------------- John Lazzaro -- Research Specialist -- CS Division -- EECS -- UC Berkeley lazzaro [at] cs [dot] berkeley [dot] edu www.cs.berkeley.edu/~lazzaro ------------------------------------------------------------------------- _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] rtcpssm and RTP MIDI ... John Lazzaro