From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] pppoe-ptm overhead calculation question
Date: Thu, 3 Sep 2015 21:02:52 +0300 [thread overview]
Message-ID: <CAJq5cE1H3iexcR3YJZtdKxC8Frexg9oJ+Ft2Tvt_pM63beQa1A@mail.gmail.com> (raw)
In-Reply-To: <F3FE5AF4-5E68-4A61-98C3-2AC5E8A6FA76@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
I'm getting the distinct impression that VDSL1 & VDSL2 are completely
different technologies with the misfortune of sharing an acronym and
physical medium. It's certainly far too easy to confuse data about one for
the other.
Ideally, I'd like to see measurements on a real line to corroborate one way
or the other. However, the use of a fixed-size word frame does sound much
more elegant than HDLC.
- Jonathan Morton
[-- Attachment #2: Type: text/html, Size: 498 bytes --]
next prev parent reply other threads:[~2015-09-03 18:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 13:58 Sebastian Moeller
2015-09-03 18:02 ` Jonathan Morton [this message]
2015-09-03 18:14 ` Sebastian Moeller
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJq5cE1H3iexcR3YJZtdKxC8Frexg9oJ+Ft2Tvt_pM63beQa1A@mail.gmail.com \
--to=chromatix99@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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