[AVT] Comments on draft-ietf-avt-tfrc-profile-08.txt
Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 02 July 2007 15:28 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 1I5NpW-0002K2-R5; Mon, 02 Jul 2007 11:28:46 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1I5NpU-0002D4-Ij for avt@ietf.org; Mon, 02 Jul 2007 11:28:44 -0400
Received: from [2001:630:241:204:203:baff:fe9a:8c9b] (helo=erg.abdn.ac.uk) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I5NoV-0005wu-4Y for avt@ietf.org; Mon, 02 Jul 2007 11:28:44 -0400
Received: from [139.133.204.42] (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id l62FPa14006492 (version=TLSv1/SSLv3 cipher=DES-CBC3-SHA bits=168 verify=NOT); Mon, 2 Jul 2007 16:25:39 +0100 (BST)
User-Agent: Microsoft-Entourage/11.3.3.061214
Date: Mon, 02 Jul 2007 17:25:36 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
To: avt@ietf.org
Message-ID: <C2AEE590.7492%gorry@erg.abdn.ac.uk>
Thread-Topic: Comments on draft-ietf-avt-tfrc-profile-08.txt
Thread-Index: Ace8vTzne1wz8SiwEdy+OgAKlc/qXg==
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
X-Spam-Status: No
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Cc: gorry@erg.abdn.ac.uk
Subject: [AVT] Comments on draft-ietf-avt-tfrc-profile-08.txt
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
Ladan I enclose some comments after reading your latest rev of draft-ietf-avt-tfrc-profile. These comments concern questions on RFC keywords, and some other queries. I will send editorial comments separately. Please do keep me in the loop on further revisions, I'd be happy to read. Best wishes, Gorry Fairhurst ---- Questions: Section 7., paragraph 3: OLD: Based on initial assumptions on round trip time if more than the recommended 5% is needed for RTCP bandwidth, the applications should use the SDP bandwidth modifiers RS and RR [3556] to signal the amount of RTCP bandwidth needed. Should this assumptions change once the RTP flows are running, the application can recalculate the amount of RTCP bandwidth needed and resignal this new value using its signaling protocol of choice. = The phrase "should take into account" needs some clarification (a) Is this a RFC2119 "SHOULD"? (b) Please clarify "take into account", what does this imply, is it just a matter of increasing the advertised bandwidth value? - The phrase "should use the SDP bandwidth modifiers RS and RR" Is this a RFC2119 "SHOULD"? Section 7. - The phrase "the application can recalculate the amount of RTCP bandwidth" - Is this a RFC2119 "MAY" or "SHOULD" Section 8., paragraph 0: - The phrase: "the AVPF T_rr_interval variable must not be set" - Is this a RFC2119 "MUST NOT"? Section 8., paragraph 2: - The phrase: "must signal their use of the AVPF profile" - Is this a RFC2119 "MUST"? - The phrase: "and optionally an initial" - Consider changing to "and optionally MAY sends an initial" Please add (informative) References: [RFC4336] Floyd, S., Handley, M., and E. Kohler, "Problem Statement for the Datagram Congestion Control Protocol (DCCP)", RFC 4336, March 2006. [RFC4340] Kohler, E., Handley, M., and S. Floyd, "Datagram Congestion Control Protocol (DCCP)", RFC 4340, March 2006. [RFC4341] Floyd, S. and E. Kohler, "Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion Control", RFC 4341, March 2006. [RFC4342] Floyd, S., Kohler, E., and J. Padhye, "Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC)", RFC 4342, March 2006. [RFCxRTP] C. Perkins, "RTP and the Datagram Congestion Control Protocol (DCCP)", IETF Work in Progress, draft-ietf-dccp- rtp-xx.txt. [ID.DTLS] T.Phelan, "Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP)", IETF Work in Progress, draft-phelan-dccp-dtls-xx.txt. --- _______________________________________________ Audio/Video Transport Working Group avt@ietf.org https://www1.ietf.org/mailman/listinfo/avt
- [AVT] Comments on draft-ietf-avt-tfrc-profile-08.… Gorry Fairhurst
- Re: [AVT] Comments on draft-ietf-avt-tfrc-profile… Ladan Gharai