Re: [Tsvwg] comments wanted: draft-eggert-tsvwg-udp-guidelines

Sally Floyd <sallyfloyd@mac.com> Wed, 07 March 2007 17:48 UTC

Return-path: <tsvwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HP0FO-0007pX-3M; Wed, 07 Mar 2007 12:48:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HP0FL-0007oI-NU for tsvwg@ietf.org; Wed, 07 Mar 2007 12:48:16 -0500
Received: from smtpout.mac.com ([17.250.248.177]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HP0FF-0003es-M5 for tsvwg@ietf.org; Wed, 07 Mar 2007 12:48:15 -0500
Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/smtpout07/MantshX 4.0) with ESMTP id l27Hm7bI023740; Wed, 7 Mar 2007 09:48:07 -0800 (PST)
Received: from [192.168.1.64] (adsl-70-231-254-220.dsl.snfc21.sbcglobal.net [70.231.254.220]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id l27Hm00n017923; Wed, 7 Mar 2007 09:48:05 -0800 (PST)
In-Reply-To: <845E19EA-69FD-44BF-858C-DECBB6BB387B@nokia.com>
References: <E1HM9Gt-0001fP-8L@stiedprstage1.ietf.org> <21B62EB2-7A61-44EA-A346-3C86BCAADD76@nokia.com> <311b45ff3aec752861e167899b6a0842@mac.com> <845E19EA-69FD-44BF-858C-DECBB6BB387B@nokia.com>
Mime-Version: 1.0 (Apple Message framework v624)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <006e30641e6eef188dfcd7f955a3ff08@mac.com>
Content-Transfer-Encoding: 7bit
From: Sally Floyd <sallyfloyd@mac.com>
Subject: Re: [Tsvwg] comments wanted: draft-eggert-tsvwg-udp-guidelines
Date: Wed, 07 Mar 2007 09:47:59 -0800
To: Lars Eggert <lars.eggert@nokia.com>
X-Mailer: Apple Mail (2.624)
X-Brightmail-Tracker: AAAAAA==
X-Brightmail-scanned: yes
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Cc: tsvwg WG <tsvwg@ietf.org>
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
Errors-To: tsvwg-bounces@ietf.org

Lars -

>> My only feedback is that in Section 3.1, when the document says that 
>> applications
>> should consider implementing TFRC "or otherwise ensure that the 
>> application
>> complies with the congestion control principles", it might be worth 
>> mentioning
>> TCP-like congestion control as well.  E.g., "TFRC, TCP-like 
>> congestion control,
>> or otherwise ensure...".
>
> I assume you mean DCCP CCID2 by "TCP-like congestion control?"
>
> If so, the first paragraph in Section 3 alreadys recommends that apps 
> use a congestion-controlled protocol instead of UDP, and points to 
> DCCP.
>
> Or am I misunderstanding?

I was just suggesting that in the sentence where you mention TFRC  "or 
otherwise..." as recommended
action, you also mention TCP-like congestion control, by name.  Just to 
make it clear that it
TFRC isn't necessarily being recommended over TCP-like congestion 
control, for the purposes of
this document.  (If the application is implementing it, it is better 
called "TCP-like congestion control
[CCID2]" instead of just "CCID2", I think.  Because CCID2 contains some 
DCCP-specific stuff that wouldn't
be included if an application was implementing it itself.)

So:  "TFRC, TCP-like congestion control (as in [CCID2]), or otherwise 
ensure..."

Does that make sense?

- Sally
http://www.icir.org/floyd/