Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] dlte
Date: Wed, 5 Dec 2018 14:36:12 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1812051435280.8891@uplift.swm.pp.se> (raw)
In-Reply-To: <87efawglui.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 939 bytes --]

On Wed, 5 Dec 2018, Toke Høiland-Jørgensen wrote:

> 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.
>
> OK, now I read the paper, and I think you may have missed the part where
> they say that they terminate the tunnelling at the AP and assign new IPs
> whenever a client roams. So it's basically WiFi APs over the LTE
> layer-2... Which is pretty cool, I think :)

Thanks, I now looked again and 4.1 said "local cores" and that's when my 
eyes rolled and I skipped on. But 4.2 is indeed what I have been talking 
about...

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

  reply	other threads:[~2018-12-05 13:36 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
2018-12-05 13:11   ` Toke Høiland-Jørgensen
2018-12-05 13:36     ` Mikael Abrahamsson [this message]
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=alpine.DEB.2.20.1812051435280.8891@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=toke@toke.dk \
    /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