Re: [dcp] Window counter
Sally Floyd <floyd@icir.org> Tue, 18 June 2002 23:12 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08046 for <dcp-archive@odin.ietf.org>; Tue, 18 Jun 2002 19:12:26 -0400 (EDT)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id TAA23264 for dcp-archive@odin.ietf.org; Tue, 18 Jun 2002 19:13:06 -0400 (EDT)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23148; Tue, 18 Jun 2002 19:11:41 -0400 (EDT)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id TAA23115 for <dcp@optimus.ietf.org>; Tue, 18 Jun 2002 19:11:39 -0400 (EDT)
Received: from cougar.icir.org (cougar.icir.org [192.150.187.76]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07970 for <dcp@ietf.org>; Tue, 18 Jun 2002 19:10:56 -0400 (EDT)
Received: from cougar.icir.org (localhost [127.0.0.1]) by cougar.icir.org (8.11.6/8.11.3) with ESMTP id g5INBWB33214; Tue, 18 Jun 2002 16:11:32 -0700 (PDT) (envelope-from floyd@cougar.icir.org)
Message-Id: <200206182311.g5INBWB33214@cougar.icir.org>
To: Sara Karlberg <Sara.Karlberg@epl.ericsson.se>
cc: dcp@ietf.org
From: Sally Floyd <floyd@icir.org>
Subject: Re: [dcp] Window counter
Date: Tue, 18 Jun 2002 16:11:32 -0700
Sender: dcp-admin@ietf.org
Errors-To: dcp-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Datagram Control Protocol <dcp.ietf.org>
X-BeenThere: dcp@ietf.org
Sara - My apologies for the very late reply. >As I understand it the purpose of the window counter option >(CCID 3) is to replace the RTT estimate. Basically the receiver needs to >know the RTT in order to report the current receive rate and to know >when to send feedback among other things. My question is how the window >counter option is to be used for this. This use of a coarse-grained counter that increments every quarter RTT in CCID 3 is largely to determine when multiple losses or marks belong to the same loss event. This is discussed in Section 8 of draft-padhye-dcp-ccid3-03.txt, and is discussed briefly in Section 3.2.1 of draft-ietf-tsvwg-tfrc-04.txt. The TFRC draft states that the receiver requires either the timestamp along with the sender's estimate of the RTT, or the coarse-grained counter, to determine when multiple losses belong to the same loss event. The DCCP/CCID 3 draft was changed to use the coarse-grained counter instead of the timestamp and the sender's estimate of the RTT. You are right that the receiver also needs an RTT estimate to set the feedback timer. With the new version of DCCP/CCID 3, the receiver will have to use the info in the coarse-grained counter to set the feedback timer. We need to add this to the DCCP/CCID 3 draft. The receiver reports the received rate X_recv in pkts per second, so this does not require the RTT estimate. >By the way, is it still recommended that the sender increases the window >counter by 4 once it receives a report of a congestion event? The current draft draft-padhye-dcp-ccid3-03.ps recommends the following: "When the sender receives an acknowledgement acknowledging a data packet with window counter i, the sender can increase its window counter, if necessary, so that subsequent data packets are sent with window counter values of at least i+4." This is still recommended. Many thanks, - Sally http://www.icir.org/floyd/ _______________________________________________ dcp mailing list: dcp@ietf.org archives: https://www1.ietf.org/mailman/listinfo/dcp project: http://www.icir.org/kohler/dcp/
- [dcp] Window counter Sara Karlberg
- Re: [dcp] Window counter Sally Floyd