From: moeller0 <moeller0@gmx.de>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Greg White <g.white@CableLabs.com>,
"codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] Per-Paket-Overhead in DOCSIS networks
Date: Thu, 23 Jun 2016 22:15:34 +0200 [thread overview]
Message-ID: <5A8FD2FC-0CCA-49AA-9976-C232DA265642@gmx.de> (raw)
In-Reply-To: <F9CB9D6C-B9C3-4DDE-BF15-B3E2D67CE582@gmail.com>
Hi Greg, hi Jonathan,
> On Jun 23, 2016, at 20:59 , Jonathan Morton <chromatix99@gmail.com> wrote:
>
>
>> On 23 Jun, 2016, at 21:51, Greg White <g.white@CableLabs.com> wrote:
>>
>> For downstream packets, the DOCSIS MAC header consists of the standard 6-byte MAC Header, plus 6 bytes for the DS EHDR and 5 bytes for the Downstream Privacy EH Element. So, 17+14+4=35 bytes of per-packet overhead for a downstream DOCSIS MAC Frame. For upstream packets, there will typically be only the 6-byte MAC Header, plus the 4 byte Upstream Privacy EH version 2 Element, so 10+14+4=28 bytes of per-packet overhead for an Upstream DOCSIS MAC Frame.
>
> Thanks Greg, this is useful information for me to build into my next overhead model update.
I fully agree, thanks a lot! Note to self, now it is clear that upstream and downstream overhead need independent entry fields…
Best Regards
Sebastian
>
> - Jonathan Morton
>
next prev parent reply other threads:[~2016-06-23 20:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <18D7F26F-B533-405A-9ED4-8ED0F4B2E5CF@caltech.edu>
2016-06-23 18:51 ` Greg White
2016-06-23 18:59 ` Jonathan Morton
2016-06-23 20:15 ` moeller0 [this message]
[not found] ` <CF598179-08C5-43B3-9E21-F405028A9A30@caltech.edu>
2016-10-18 17:55 ` Greg White
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5A8FD2FC-0CCA-49AA-9976-C232DA265642@gmx.de \
--to=moeller0@gmx.de \
--cc=chromatix99@gmail.com \
--cc=codel@lists.bufferbloat.net \
--cc=g.white@CableLabs.com \
/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