From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <toke@toke.dk>
Received: from mail.toke.dk (mail.toke.dk [52.28.52.200])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by lists.bufferbloat.net (Postfix) with ESMTPS id D7E7A3B2A4
 for <cerowrt-devel@lists.bufferbloat.net>;
 Wed,  5 Dec 2018 03:41:48 -0500 (EST)
From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023;
 t=1543999307; bh=jeKrMpgGUeWjSUXsp0Ic1xHN/jLwScIQ5IeTj6oR/cg=;
 h=From:To:Cc:Subject:In-Reply-To:References:Date:From;
 b=nU09p4poPKzHW6my+y8yYTpVBOsMWrc2EPTYna0vUlFZQpgTQj//JJ1ScznxgzrS0
 MzR/d5cCRE3Biki+MiiNjM8aJLjNvCqsmFC/0aIjuUxRP2ge52R+BlqxrW+psMnEEh
 1JmHY75PgMvo4Ry8EYLMGCsLhgwXyjizvtNnPXI6p7WeOsqK3MH7rdIcQXmaZE4eVN
 F9+6y1X10XJscVfwJCCJGA2bCe8UjAEtVpx5j4WkWi4n1EDXakSMpNl1lDzicT3/by
 AetewcbZSI7LcP9YoR9pSbHi3KhZEgcGIGYuBpyRm/QRAWpA2qyRLhs1HUCUycNgwt
 ePoAlJuGNe1Kg==
To: Mikael Abrahamsson <swmike@swm.pp.se>, Dave Taht <dave.taht@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
In-Reply-To: <alpine.DEB.2.20.1812050838520.8891@uplift.swm.pp.se>
References: <CAA93jw4zhPjCV-apVpsWdK_E9-=4nYVPej7ueUqABmzd0paciA@mail.gmail.com>
 <alpine.DEB.2.20.1812050838520.8891@uplift.swm.pp.se>
Date: Wed, 05 Dec 2018 10:41:45 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87pnuggyba.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Subject: Re: [Cerowrt-devel] dlte
X-BeenThere: cerowrt-devel@lists.bufferbloat.net
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Development issues regarding the cerowrt test router project
 <cerowrt-devel.lists.bufferbloat.net>
List-Unsubscribe: <https://lists.bufferbloat.net/options/cerowrt-devel>,
 <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=unsubscribe>
List-Archive: <https://lists.bufferbloat.net/pipermail/cerowrt-devel>
List-Post: <mailto:cerowrt-devel@lists.bufferbloat.net>
List-Help: <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=help>
List-Subscribe: <https://lists.bufferbloat.net/listinfo/cerowrt-devel>,
 <mailto:cerowrt-devel-request@lists.bufferbloat.net?subject=subscribe>
X-List-Received-Date: Wed, 05 Dec 2018 08:41:49 -0000

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