IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Tue, 14 October 2014 16:25 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 2A7EA1A8A28 for <homenet@ietfa.amsl.com>; Tue, 14 Oct 2014 09:25:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.693
X-Spam-Level:
X-Spam-Status: No, score=-1.693 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PLING_QUERY=0.994, RP_MATCHES_RCVD=-0.786, 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 tSWao09TChiU for <homenet@ietfa.amsl.com>; Tue, 14 Oct 2014 09:25:51 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id F25621A8963 for <homenet@ietf.org>; Tue, 14 Oct 2014 09:25:50 -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 CD4F12380423; Tue, 14 Oct 2014 12:25:49 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <20141014154606.GA31092@Space.Net>
Date: Tue, 14 Oct 2014 11:25:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9C17A8E0-2BE7-4FB3-9A66-576E197A059F@fugue.com>
References: <72CC13D1-7E7A-4421-B23E-16D8FFAEEB58@darou.fr> <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> <7D59D80C-2BF0-428B-A872-B2922B2D0F98@fugue.com> <20141014154606.GA31092@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/homenet/0e53JO5_ZrcSv5yWTOBNScy4bxQ
Cc: Erik Kline <ek@google.com>, HOMENET Working Group <homenet@ietf.org>, Pierre Pfister <pierre.pfister@darou.fr>
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: Tue, 14 Oct 2014 16:25:52 -0000

On Oct 14, 2014, at 10:46 AM, Gert Doering <gert@space.net> wrote:
> Application developers MUST handle changing addresses, for example by not
> doing silly things like "at startup, do some DNS resolving and socket
> binding to a fixed address, and assume that the addresses you receive
> are not changing".

This has little to do with renumbering on the network to which the application is connected.   I agree that applications should do this, and that applications that don't will break if the provider renumbers, but we are talking about renumbering in the homenet, not renumbering of network services outside the home.

If you are referring specifically to naming in the home, while it's true that applications should support service address renumbering in the home, that is orthogonal to the question of whether services in the home should be numbered using ULAs or GUAs.

v2.23.0 | Report a Bug | By Email