From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Mikael Abrahamsson <swmike@swm.pp.se>, Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] dlte
Date: Wed, 05 Dec 2018 10:41:45 +0200 [thread overview]
Message-ID: <87pnuggyba.fsf@toke.dk> (raw)
In-Reply-To: <alpine.DEB.2.20.1812050838520.8891@uplift.swm.pp.se>
Mikael Abrahamsson <swmike@swm.pp.se> writes:
> On Tue, 4 Dec 2018, Dave Taht wrote:
>
>> I expect dave reed to comment, so I'll withhold mine for now
>>
>> https://kurti.sh/pubs/dLTE-Johnson-HotNets-2018.pdf
>
> When I read the first page I was hopeful, then unfortunately I got
> disappointed and just quickly scanned the rest. It's still tunneled and
> the same architecture, just more distributed.
>
> I'd prefer if the device had two radios and could handle its own handover
> for most traffic. Most traffic today is streaming video so when you want
> to do handover just attach to the new radio, get new address, deprecate
> the old address, open new connections using the new address/radio close
> connections based on the old address, and move on.
>
> Traffic that needs to be always the same can be tunneled,
Totally agree. I'll add that even persistent "connections" can do
end-to-end mobility with changing addresses. Mosh is an example of an
application that does this right. I believe Apple uses MPTCP to achieve
the same thing with TCP...
-Toke
next prev parent reply other threads:[~2018-12-05 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 18:07 Dave Taht
2018-12-05 7:44 ` Mikael Abrahamsson
2018-12-05 8:41 ` Toke Høiland-Jørgensen [this message]
2018-12-05 13:11 ` Toke Høiland-Jørgensen
2018-12-05 13:36 ` Mikael Abrahamsson
2018-12-06 20:22 ` Dave Taht
2018-12-07 9:08 ` Toke Høiland-Jørgensen
2018-12-10 2:23 David P. Reed
2018-12-11 19:02 ` Dave Taht
2018-12-13 6:40 ` Aaron Wood
2018-12-15 16:17 ` Dave Taht
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/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnuggyba.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=swmike@swm.pp.se \
/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