Re: [homenet] Let's make in-home ULA presence a MUST !?

Ted Lemon <mellon@fugue.com> Wed, 15 October 2014 23:06 UTC

Return-Path: <mellon@fugue.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 1E3891ACE0F for <homenet@ietfa.amsl.com>; Wed, 15 Oct 2014 16:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.917
X-Spam-Level:
X-Spam-Status: No, score=-0.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PLING_QUERY=0.994, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 4Q8isCssG5P8 for <homenet@ietfa.amsl.com>; Wed, 15 Oct 2014 16:06:32 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id AC3AD1ACE11 for <homenet@ietf.org>; Wed, 15 Oct 2014 16:06:30 -0700 (PDT)
Received: from [192.168.1.63] (c-71-201-198-58.hsd1.il.comcast.net [71.201.198.58]) by toccata.fugue.com (Postfix) with ESMTPSA id 820862381535; Wed, 15 Oct 2014 19:06:29 -0400 (EDT)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <543EFBF1.6040101@mtcc.com>
Date: Wed, 15 Oct 2014 18:06:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <457D177C-232E-4590-A9ED-80048140157F@fugue.com>
References: <CAAedzxp1R-C5E9RJVMVLRJxPc0w4zooPtqnvWK9eggpZu4=xtg@mail.gmail.com> <C7F3DE60-F596-4BAD-9C28-74006966E5B9@fugue.com> <20141014142746.GX31092@Space.Net> <69B1F2CB-88C6-4211-83F3-11C8A3E7BFD2@fugue.com> <20141014145930.GY31092@Space.Net> <m1Xe3jL-0000I7C@stereo.hq.phicoh.net> <20141014154111.GZ31092@Space.Net> <C6760B68-C913-4B22-98E6-6D29A66F80D9@fugue.com> <20141015150422.GW31092@Space.Net> <4E2E154E-D231-4E79-860A-56948A13CDD4@fugue.com> <20141015154841.GY31092@Space.Net> <CBC8A3D9-9EBD-47FF-B066-247898FF2000@fugue.com> <543EA248.2080700@mtcc.com> <CB50B30B-DC36-4354-96B7-19AE415BD03F@fugue.com> <543EBE40.3030201@mtcc.com> <BA5ABBFA-9D13-4975-A96C-530FE958322A@fugue.com> <543ED2A7.3090409@mtcc.com> <1569644A-50C4-47B6-908E-262BC62BCD14@fugue.com> <543EFBF1.6040101@mtcc.com>
To: Michael Thomas <mike@mtcc.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/d1jYyF4DTB-boqP8df3rzF_GYzk
Cc: homenet@ietf.org
Subject: Re: [homenet] Let's make in-home ULA presence a MUST !?
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: Wed, 15 Oct 2014 23:06:34 -0000

On Oct 15, 2014, at 5:57 PM, Michael Thomas <mike@mtcc.com> wrote:
> If I use a GUA to my jukebox, the routing will just work regardless of which
> AP I'm currently connected to. With ULA's, not so much. That's hardly a non-sequitur.

You appear to have some misconceptions both about how IP routing works and how streaming works.

Suppose you are connected to your homenet.   You are streaming video from your jukebox using your ULA.   Now your device switches to your neighbor's Wifi, which is advertising a different GUA and a different ULA.   At this point your device does a flash renumber because it realizes it's no longer on the same network, and that the prefixes it had are no longer valid.

At this point, your application should get a notification from the stack that the connection has broken, at which point it should reconnect to your jukebox.  Supposing that your jukebox is reachable from the outside, the ULA that your neighbor's WiFi is advertising won't match the ULA your jukebox is advertising, so your device will attempt to reconnect using a GUA, not a ULA.

So whether you have a ULA on your homenet or not, two things will be true.  First, if your app isn't smart enough to re-connect, your stream will die.   Second, if it is smart enough, then it will succeed in reconnecting, whether you have a ULA configured on your homenet or not.

This is why I say that the concern you have raised is a non-sequitur.