Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 19 December 2014 03:38 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD981A00B9 for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 19:38:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cppMMZi3JrY for <homenet@ietfa.amsl.com>; Thu, 18 Dec 2014 19:38:04 -0800 (PST)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EA8E61A9150 for <homenet@ietf.org>; Thu, 18 Dec 2014 19:38:03 -0800 (PST)
Received: by mail-pd0-f181.google.com with SMTP id v10so290379pde.40 for <homenet@ietf.org>; Thu, 18 Dec 2014 19:38:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=cGs0gxHddPn4NdCI1OaXHe8eyFgINcapj20zdRr+CnE=; b=DmxiIkeZUt4MTQv7ii5fPcluDhfjBXKkip0R4Ewi7bfdcjx0Qn2SZQQ/eB4Eirxhs0 1yMcakIijpktLb3PGDxE1uaDgfcEvALZ4admazjInBzhLVcboSq8XQ82+QJePYRN+gcQ i4coDc1OtlJvbP2fuzhYLHZL0GzQdoPwg2XsoX2b/jDqcgu2TuSuNRonDdYh5f/QrVIg qPjCOGtQqikAsapEaGU8YOjsWtOh5pkU/XG0YTtQyF72nX8nsEdYAQDwtGrnnyRM+WKt Wy/3UokPG/S/R6xb9XzjYkOqnBCF4AA8rYs6nll1t+KVIdT5qgfGhkAewmD8JtsTXprn Q8gw==
X-Received: by 10.68.136.70 with SMTP id py6mr2553521pbb.91.1418960283211; Thu, 18 Dec 2014 19:38:03 -0800 (PST)
Received: from ?IPv6:2406:e007:74cb:1:28cc:dc4c:9703:6781? ([2406:e007:74cb:1:28cc:dc4c:9703:6781]) by mx.google.com with ESMTPSA id se3sm8098705pbc.24.2014.12.18.19.37.59 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 18 Dec 2014 19:38:02 -0800 (PST)
Message-ID: <54939DA2.60602@gmail.com>
Date: Fri, 19 Dec 2014 16:38:10 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
References: <CAA93jw6uY=KY8WeoFn1e65ciyokN=y9SRpaCHewCvWqcBHMhKw@mail.gmail.com> <24024.1418915279@sandelman.ca> <54934FF5.2050108@gmail.com> <87zjakpphc.wl-jch@pps.univ-paris-diderot.fr> <54936F28.9070201@gmail.com> <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr>
In-Reply-To: <877fxopfxl.wl-jch@pps.univ-paris-diderot.fr>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/RpM7jFvTH4tkBbSPCDidBLgmcQE
Cc: boutier@pps.univ-paris-diderot.fr, Michael Richardson <mcr+ietf@sandelman.ca>, HOMENET <homenet@ietf.org>, Dave Taht <dave.taht@gmail.com>
Subject: Re: [homenet] sorting out the right ipv6 addr to choose and name in a source specific world
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2014 03:38:05 -0000

On 19/12/2014 14:49, Juliusz Chroboczek wrote:
>>> Boutier's version of mosh builds connections across all source/destination
>>> pairs, and picks the one with lowest RTT.  
> 
>> Sounds interesting. In the ideal world, that would be a pluggable
>> policy algorithm. Lowest RTT may not always be the best choice.
> 
> It is, in our particular context.  That's the nice thing about working at
> the application layer -- you are the application, so you have a pretty
> good idea of what the desirable properties are.  Mosh is an interactive
> shell, and in this particular context it's latency you want to optimise
> for.

Are you sure? Suppose I open a file transfer window (which as a matter
of fact I do almost every time I use SSH these days). For large file
transfers
I might want to specify "cheapest" not "fastest".

> Once we gain some real-world experience from mosh, we can think about
> making something more generic.  But I, at least, don't feel comfortable
> about doing that.

Understood. But all I'm thinking is that you might make that bit a
self-contained
module.

    Brian