IETF Logo Mail Archive

Re: [homenet] Status of draft-tldm-simple-homenet-naming CFA

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 17 August 2017 14:31 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C40EF132392 for <homenet@ietfa.amsl.com>; Thu, 17 Aug 2017 07:31:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 oXo_5NXfex8N for <homenet@ietfa.amsl.com>; Thu, 17 Aug 2017 07:31:26 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D81A1200C5 for <homenet@ietf.org>; Thu, 17 Aug 2017 07:31:26 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id CA9E52009E; Thu, 17 Aug 2017 10:34:07 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 94819806D2; Thu, 17 Aug 2017 10:31:25 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Juliusz Chroboczek <jch@irif.fr>
cc: Ted Lemon <mellon@fugue.com>, HOMENET <homenet@ietf.org>
In-Reply-To: <87k223jjdg.wl-jch@irif.fr>
References: <2D09D61DDFA73D4C884805CC7865E6114DBF5904@GAALPA1MSGUSRBF.ITServices.sbc.com> <877eyaz2jm.fsf@toke.dk> <CAPt1N1m5nVGD-y2VrbkoTEPTs4qF98oRxGuvd-Has1yzuS0fmg@mail.gmail.com> <874ltez1wg.fsf@toke.dk> <7E8390B5-9048-4783-B17F-6C9EA5610887@fugue.com> <7ivalujdfu.wl-jch@irif.fr> <15F1CE39-82EE-4B0D-A31B-2C1805991541@fugue.com> <871sofzqma.fsf@toke.dk> <CAPt1N1=oiU+DbjD6izOBNJOnC25d=-S3ARqFxydRfWLEet5mEQ@mail.gmail.com> <87valry4o7.fsf@toke.dk> <FCAD81FA-BBA0-45B0-8F1F-D1D5FD010484@fugue.com> <87shgvxybl.fsf@toke.dk> <4AF8CF8A-F781-449F-9C53-A9603889746E@fugue.com> <87lgmnxr3u.fsf@toke.dk> <E3E75086-BF36-4F59-86BD-7FFDAFE772AB@fugue.com> <87fuctxdrc.fsf@toke.dk> <FB44A942-9DE3-4CE6-88C5-402B20756462@fugue.com> <877ey4y62g.fsf@toke.dk> <6DF8489E-D780-4E4C-A132-31EEF8285BB7@fugue.com> <874lt8xv9j.fsf@toke.dk> <3DE50D7C-53BF-4758-8DED-A2CA89C8ABE7@fugue.com> <871soby776.fsf@toke.dk> <769C4508-BB58-4BCB-A3CE-3657FB43A8AA@fugue.com> <87k223jjdg.wl-jch@irif.fr>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Thu, 17 Aug 2017 10:31:25 -0400
Message-ID: <4488.1502980285@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/Fi7JYeicQj14kEsjl0gTOwbIp_E>
Subject: Re: [homenet] Status of draft-tldm-simple-homenet-naming CFA
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/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: Thu, 17 Aug 2017 14:31:28 -0000

Juliusz Chroboczek <jch@irif.fr> wrote:
    > That's exactly the kind of situation that we'd like Homenet to work well
    > in.  Connection A is a 1.5Mbit/s leased line, it's rock solid, and has
    > rock solid infrastructure behind it.  Connection B is consumer FTTH at
    > 1Gbit/s, it's flaky, and it's backed by infrastructure that works on
    > Mondays only.

    > Quite frankly, if it's not for combining fast with reliable, I just don't
    > see what's the purpose of having multiple connections.

The 1.5Mb/s is for "work" use only (is very low-latency too), but tolerates
some moderate amount of non-work traffic, as long as it's not so much that
anyone notices.  That's why you'd have two connections.  Work traffic SHOULD
not go out the flaky connection.

That the result is what you describe (which I believe 200%...) is what
happens is not the plan.  It's not why the multiple connections are justified.
Now, assume a second spouse working at home, with another "work" connection :-)
(And of course, don't forget the mesh network to the neighbourhood)

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email