From: Eddie Kohler <kohler@cs.ucla.edu>
To: dccp@vger.kernel.org
Subject: Re: [PATCH 1/1] DCCP: Fix up t_nom - FOLLOW-UP
Date: Fri, 12 Jan 2007 16:33:13 +0000 [thread overview]
Message-ID: <45A7B849.5080501@cs.ucla.edu> (raw)
In-Reply-To: <200701101021.38920@strip-the-willow>
> | For what it's worth, it's as close to in the RFC as it can get without a
> | revision. The authors of the RFC agree that we meant the initial
> | Request-Response RTT to be usable as an initial RTT estimate; the
> | working group agreed; errata has been sent.
> So we are RFC-compliant for the moment. One point which remains unresolved is,
> the above is about RTTs, but what about the initial sending rate of 1 packet
> per second, which implies an initial t_ipi of 1 second?
"Therefore, in contrast to [RFC3448], the initial CCID 3 sending rate is
allowed to be at least two packets per RTT, and at most four packets per
RTT, depending on the packet size. ..." [RFC4342, Sec 5]
Since CCID3 always has an estimate of the round trip time when it sends
packets, there is no such thing as an initial sending rate of 1 packet
per second. The initial sending rate, after the Response arrives (thus
providing an initial estimate of the round trip time), is 2-4 packets
per RTT, depending on s.
Eddie
next prev parent reply other threads:[~2007-01-12 16:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-10 10:21 [PATCH 1/1] DCCP: Fix up t_nom - FOLLOW-UP Gerrit Renker
2007-01-10 19:40 ` Ian McDonald
2007-01-12 10:39 ` Gerrit Renker
2007-01-12 12:54 ` Gerrit Renker
2007-01-12 16:33 ` Eddie Kohler [this message]
2007-01-12 16:41 ` Eddie Kohler
2007-01-12 16:58 ` Gerrit Renker
2007-01-12 20:02 ` Ian McDonald
2007-01-15 7:56 ` Gerrit Renker
2007-01-15 8:34 ` Gerrit Renker
2007-02-08 0:59 ` Eddie Kohler
2007-02-08 1:13 ` Ian McDonald
2007-02-08 1:23 ` Eddie Kohler
2007-02-08 1:47 ` Ian McDonald
2007-02-08 5:50 ` Eddie Kohler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45A7B849.5080501@cs.ucla.edu \
--to=kohler@cs.ucla.edu \
--cc=dccp@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox