[AVT] Comments on draft-ietf-avt-rtcpssm-13 part 1
Tom Taylor <tom.taylor@rogers.com> Thu, 05 July 2007 00:50 UTC
Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6FYM-00050C-QL; Wed, 04 Jul 2007 20:50:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I6FYM-000507-57 for avt@ietf.org; Wed, 04 Jul 2007 20:50:38 -0400
Received: from smtp106.rog.mail.re2.yahoo.com ([68.142.225.204]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I6FYI-0008NY-S1 for avt@ietf.org; Wed, 04 Jul 2007 20:50:38 -0400
Received: (qmail 98741 invoked from network); 5 Jul 2007 00:50:34 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:X-YMail-OSG:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding; b=ND8prqMqvTc1ca7U5SRlHUxvlKGjHrIKFj8iSf2+RZtl2daPJoc7zuM0cLhmNTuj04smOLJMMjB12KMQvq4ueDDmFLeo3G45hnrFhAi5jis0udAm1qmzTDlMusJn7gMbN4X0VUEWQQPvvtpZ7Ozb7cvwM68P65Y8cnQ+gOEoVFE= ;
Received: from unknown (HELO ?192.168.0.100?) (tom.taylor@rogers.com@74.105.35.229 with plain) by smtp106.rog.mail.re2.yahoo.com with SMTP; 5 Jul 2007 00:50:34 -0000
X-YMail-OSG: jF7_lr8VM1mNtV4fAjxedXO5yBq4pfJ.a6R00BNl1L9tBZ69lJagf2ovm2jgs7x9XA--
Message-ID: <468C40FB.60505@rogers.com>
Date: Wed, 04 Jul 2007 20:53:15 -0400
From: Tom Taylor <tom.taylor@rogers.com>
User-Agent: Thunderbird 2.0.0.4 (Windows/20070604)
MIME-Version: 1.0
To: jo@acm.org, Julian.chesterfield@cl.cam.ac.uk, eve_schooler@acm.org, IETF AVT WG <avt@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc:
Subject: [AVT] Comments on draft-ietf-avt-rtcpssm-13 part 1
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
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>
Errors-To: avt-bounces@ietf.org
These comments come way too late given the looming I-D deadline, but they may be helpful. 1. I suggest putting the Definitions section before the section describing basic operation, so the latter can build on the definitions without repeating them. 2. I found some points in the architecture were unclear. In particular, do the Media Senders send their RTCP sender reports to the Distribution Source or to Feedback Target instances? The reason I ask this is because I wasn't sure why the the Media Senders needed to be configured with the transport addresses of the Feedback Target instances. 3. Is the following paragraph a correct summary of basic operation? If so, it might be considered as a replacement for much of the "Basic Operation" section. (Editorial note: capitalization of "Media Sender", Distribution Source", and Feedback Target" needs to be made consistent throughout the document. I show the terms captialized, but the alternative is equally acceptable.] "One or Media Senders send RTP and RTCP sessions to the Distribution Source. The Distribution Source relays the RTP sessions to the receivers using a source-specific multicast arrangement. In the reverse direction, each receiver transmits a unicast RTCP stream to a specific instance of the Feedback Target. Each Feedback Target instance sends either the original RTCP reports (the Simple Feedback Model) or summaries of these reports (the Summary Feedback model) to the Distribution Source, using unicast transport if it is not actually co-located with the Distribution Source. The Distribution Source in turn relays the RTCP reports and/or summaries to the Media Sender(s). The Distribution Source also transmits the RTCP sender reports and receiver reports or summaries back out to the receivers, using source-specific multicast." More later. Tom _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt