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

Don Sturek <d.sturek@att.net> Fri, 17 October 2014 19:57 UTC

Return-Path: <d.sturek@att.net>
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 3B3AD1A6FB5 for <homenet@ietfa.amsl.com>; Fri, 17 Oct 2014 12:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.508
X-Spam-Level: *
X-Spam-Status: No, score=1.508 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, HTML_MESSAGE=0.001, MALFORMED_FREEMAIL=2.511, MIME_QP_LONG_LINE=0.001, PLING_QUERY=0.994, RCVD_IN_DNSWL_NONE=-0.0001] 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 4uLHLmQy_ssm for <homenet@ietfa.amsl.com>; Fri, 17 Oct 2014 12:57:01 -0700 (PDT)
Received: from nm15-vm7.access.bullet.mail.gq1.yahoo.com (nm15-vm7.access.bullet.mail.gq1.yahoo.com [216.39.63.193]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 482301A6F9C for <homenet@ietf.org>; Fri, 17 Oct 2014 12:57:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1413575821; bh=8pY4D45/WD2XfwSTRUThziI420qynxUiRi9QDPywv+Y=; h=Date:Subject:From:To:References:In-Reply-To:From:Subject; b=WFt7PxMsYjCPljj9f3yJLT0gnmgT8RlMLzWo1Qs5ihYFXwXd5eVH6ShsqmW9qW604OpYQGz29XRQ/HUeL87e617D6wFZ/pwGhoBbg7n1YHEJ/F3Qj9IHtTbgUYfq4Ro6JR9jPX/wEa7OMdgNbUYFqtB3eIYSKohZtHfQqrgVNjo=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=att.net; b=HFK8N9ZypzzjKzAVOO0Ynl2HSuYVHhokbY6QmJtIXjWa0R3CRdU8okHh5Eg9+u7FAeE5FnyngZVzwkcOkPtKxUjW38AtcyT6i/zUBnnI6Y4NCOsvReDYT0Y6XzBXwbR25JrOSrGA0LyNQTXJhlL0na5TWTMGIqfjDVsPTZVH8P0=;
Received: from [216.39.60.166] by nm15.access.bullet.mail.gq1.yahoo.com with NNFMP; 17 Oct 2014 19:57:01 -0000
Received: from [98.138.104.96] by tm2.access.bullet.mail.gq1.yahoo.com with NNFMP; 17 Oct 2014 19:57:00 -0000
Received: from [127.0.0.1] by smtp116.sbc.mail.ne1.yahoo.com with NNFMP; 17 Oct 2014 19:57:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1413575820; bh=8pY4D45/WD2XfwSTRUThziI420qynxUiRi9QDPywv+Y=; h=X-Yahoo-Newman-Id:X-Yahoo-Newman-Property:X-YMail-OSG:X-Yahoo-SMTP:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To:Mime-version:Content-type; b=0GAOLshPEvpxOwzWBSR5G/v3yizJHqgy7tXVSQI3PpQRF2QqcCQFvWP2HHMflaJi9BnS75K4TEnEZa+86tz1rlMWjuFnU2qk8NoC6MTAhGnDknkEVFbEgXo8MCMh164k3pp8eFWfZZkIOYzO7AZ4QR1PrPmNaNQ1SaGosDMUS9U=
X-Yahoo-Newman-Id: 741776.45022.bm@smtp116.sbc.mail.ne1.yahoo.com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: 7Tyfy.sVM1lLnyfi.SeJpFK53sjvbg4i4KXC75tGkDyVTrY ZEJ1xO7ZW7Rrh7DIofS5blfvghCMaUpobVBPKCYwK9MfFtqc8xorrZ9vZ_NF C.lEY64Dd048l6FYCQg0ZzwOxq.zOcQ0bj3SEZLp2t4IIkItGrMzVhdcQIff V9OEHDUIX4gCZ.H3HJD9xVYRrw0uGf5m3KevHYEOUqcLkxjNCfY6cctmkeg5 mdjh1AOL0rJGPjhHs1YugAcOo6exEx0fhpmllsHEgguJYYTk9tKPX2cO2HFQ 9.Uy6d1lPJnyppGI5dX7bL5ZPC3ThG_IyawWBpcWuAedSPg_PX5kErzsb.BM Qdulue.gw7A67kApBsJspApzjikXtbqHzCcfEO8RiJFDB4P6.M5FFKT2ddNJ RMKULBlxF8r3Don3Iklh2YLJu9F0s71tEyxCX4x_lI1ITF6R22UAKpzWPmOA Tl0Hvo98296AtmRkdvdeJZ8p4lMqtJfCZXes6nUXeSJL7r5bEn8KOsDk0pKC 8AH_xMQnlerHD0djsFTzlLSv7RqilNcqZOFqk6jBW
X-Yahoo-SMTP: fvjol_aswBAraSJvMLe2r1XTzhBhbFxY8q8c3jo-
User-Agent: Microsoft-MacOutlook/14.4.5.141003
Date: Fri, 17 Oct 2014 12:56:56 -0700
From: Don Sturek <d.sturek@att.net>
To: James Woodyatt <jhw@nestlabs.com>, HOMENET Working Group <homenet@ietf.org>
Message-ID: <D066C15F.2EBF5%d.sturek@att.net>
Thread-Topic: [homenet] Let's make in-home ULA presence a MUST !?
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> <457D177C-232E-4590-A9ED-80048140157F@fugue.com> <CAKD1Yr1kix0HxWsC4n7ta4EG-6YhMMdYCTnFFXGb2ATQBbkMHA@mail.gmail.com> <DCB62D43-DFD3-4985-8FAA-896CEA3BD342@fugue.com> <CAKD1Yr1rpFeZuy=nXFSj+dpa749RhJJ2j9+U=cmFq_4cCsC_4g@mail.gmail.com> <4D6F2B13-D63E-4FEE-A136-B510126CC1C9@fugue.com> <2D09D61DDFA73D4C884805CC7865E61130EA3B9A@GAALPA1MSGUSRBF.ITServices.sbc.com> <1AA5DBBD-C3C5-4AFD-A043-6A69AE7FBDB9@fugue.com> <CAKD1Yr3Fa7hgXZReWFgmHA9pLnH=ezHLXh-aAdA-_N=AR3AiyA@mail.gmail.com> <3F36952F-CF6A-4F21-A713-A8A7DE7BDC42@fugue.com> <CAKD1Yr3eP+8qs8uMzrfOmebp+bihGed7PjWi0=8+cV4N6Dx=ww@mail.gmail.com> <8352C2EF-A888-4279-BFFF-37E204A0E2D3@fugue.com> <CADhXe53yJNA6bnnmssuG4sq0i2gyAih0LsRW64XTZ-aK7LS+tw@mail.gmail.com>
In-Reply-To: <CADhXe53yJNA6bnnmssuG4sq0i2gyAih0LsRW64XTZ-aK7LS+tw@mail.gmail.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3496395419_1479581"
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/jNSvwIV_Wi7I9rC-JOSTxr_jfWs
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: Fri, 17 Oct 2014 19:57:03 -0000

Hi James,

One more issue that maybe needs some consideration:    How would a router
know the boundary for dissemination of ULA prefixes?  Here I am thinking of
the case where there may be more than one ISP interface and particularly in
the case of network splits and joins in the home.

So really I think there are a couple of different topics ripe for I-Ds:
1)  How to handle splits/joins of networks in the home where different ULA
prefixes are in use
2)  Guidance on when (and when not) to propagate ULA prefixes.  I think I
have heard anecdotally that most ISP see traffic using ULAs on their ISP
interface (which they drop).  It would be nice to have a definitive draft
that clearly states when this traffic should not be routed (so at least
dilligent implementers can attempt to do the right thing).  Again, I think
this topic is fairly obvious in a home with a single ISP and all devices are
connected from day 1 but it is less than clear when merging two or more
networks in your home (or attempting to split the networks)

Don


From:  James Woodyatt <jhw@nestlabs.com>
Date:  Friday, October 17, 2014 12:49 PM
To:  HOMENET Working Group <homenet@ietf.org>
Subject:  Re: [homenet] Let's make in-home ULA presence a MUST !?

On Fri, Oct 17, 2014 at 7:17 AM, Ted Lemon <mellon@fugue.com> wrote:
> On Oct 17, 2014, at 8:46 AM, Lorenzo Colitti <lorenzo@google.com> wrote:
> 
>> > Oh, ULAs and stable addressing sound good on paper, sure. But as soon as
>> you actually try to use them, then suddenly there are a boatload of scenarios
>> that you need to deal with like the ones presented by James many messages
>> ago. What happens on splits? What happens on joins? Do you need to keep old
>> ULAs around? How many? Will implementations age them out? (I can tell you the
>> answer to that one: "no"; they're more likely to stop accepting new ones than
>> to have new ones replace old ones). And so on and so forth.
> 
> You may have missed the message where I responded to James with concrete
> proposals for how to solve these problems.   It is entirely possible that if
> we explore that solution space we will conclude, as you have, that no solution
> is reliable and not brittle, but I don't think we have explored it, so I think
> your conclusion that we will not come up with a good solution is premature.

As I recall, the proposals in your response were less than concrete and
didn't solve the problems. In particular, I remain curious about how to
expire the locally generated ULA prefixes that accumulate over repeated
network joins and splits.  I remember explaining how those events could be
rather more frequent than people might be assuming, and that's where the
discourse seemed to stop.


-- 
james woodyatt <jhw@nestlabs.com>
Nest Labs, Communications Engineering
_______________________________________________ homenet mailing list
homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet