All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sally Floyd <sallyfloyd@mac.com>
To: dccp@vger.kernel.org
Subject: Re: [dccp] Packet size s on CCID3
Date: Fri, 22 Sep 2006 13:26:01 +0000	[thread overview]
Message-ID: <cf450b133ceda5ddfceb0d0d2d998301@mac.com> (raw)
In-Reply-To: <5640c7e00609202022j1b97cf1g30797ffcd9b650b6@mail.gmail.com>

> Why not just calculate a packet rate per second? Or am I missing
> something obvious?

No, that is a good question.

One reason for including the packet size s is discussed in
Section 5.3 of RFC 4342:

    "The packet size s is used in the TCP throughput equation.  A CCID 3
    implementation MAY calculate s as the segment size averaged over
    multiple round trip times -- for example, over the most recent four
    loss intervals, for loss intervals as defined in Section 6.1.
    Alternately, a CCID 3 implementation MAY use the Maximum Packet Size
    to derive s.  In this case, s is set to the Maximum Segment Size
    (MSS), the maximum size in bytes for the data segment, not including
    the default DCCP and IP packet headers.  Each packet transmitted then
    counts as one MSS, regardless of the actual segment size, and the TCP
    throughput equation can be interpreted as specifying the sending rate
    in packets per second."

Thus, an implementation MAY calculate the allowed sending rate
in bytes per second, using for s the average segment size.
Or an implementation may use the MSS for s, and in fact calculate
the allowed sending rate simply in packets per second.  This would be
a purely local implementation decision.

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


  parent reply	other threads:[~2006-09-22 13:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  3:22 Packet size s on CCID3 Ian McDonald
2006-09-21 16:19 ` [dccp] " Gorry Fairhurst
2006-09-21 23:37 ` Ian McDonald
2006-09-22 13:26 ` Sally Floyd [this message]
2006-09-22 13:42 ` Gerrit Renker
2006-09-22 17:30 ` [dccp] " Eddie Kohler
2006-09-26 12:19 ` Gorry Fairhurst
2006-10-03  3:26 ` Ian McDonald
2006-10-03  3:40 ` Ian McDonald
2006-10-03 15:43 ` Eddie Kohler
2006-10-03 15:50 ` Eddie Kohler
2006-10-03 18:15 ` Ian McDonald
2006-10-03 18:18 ` Eddie Kohler
2006-10-03 19:48 ` Ian McDonald
2006-10-04 16:20 ` 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=cf450b133ceda5ddfceb0d0d2d998301@mac.com \
    --to=sallyfloyd@mac.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.