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

Ted Lemon <> Tue, 14 October 2014 19:31 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 6D74D1ACEBF for <>; Tue, 14 Oct 2014 12:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.693
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id Ayn9o2Mvqh3h for <>; Tue, 14 Oct 2014 12:31:30 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 32FBB1ACEB4 for <>; Tue, 14 Oct 2014 12:31:29 -0700 (PDT)
Received: from [] ( []) by (Postfix) with ESMTPSA id 887B823803D1; Tue, 14 Oct 2014 15:31:28 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Ted Lemon <>
In-Reply-To: <>
Date: Tue, 14 Oct 2014 14:31:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <>
To: James Woodyatt <>
X-Mailer: Apple Mail (2.1878.6)
Cc: HOMENET Working Group <>
Subject: Re: [homenet] Let's make in-home ULA presence a MUST !?
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 14 Oct 2014 19:31:37 -0000

On Oct 14, 2014, at 2:19 PM, James Woodyatt <> wrote:
> On the topic of the original question, if I were to editorialize here, then I would want to see something like this:

I get that you have an opinion on this, but you haven't actually stated any argument to support what you think we should do.   And there are some implications in what you are saying that I don't think are necessary.

> A) An autonomously generated ULA prefix SHOULD be advertised when no other delegated prefix is valid.

OK, although underspecified.

> B) Whenever there is any valid delegated prefix, advertisements for an existing autonomously generated ULA prefix MUST be deprecated, i.e. updated with preferred lifetime of zero.

Why?   What problem does this solve?   Given that it's going to mean additional work, there should be some benefit to doing it.

> C) A deprecated autonomously generated ULA prefix MUST be withdrawn when it expires, i.e. its valid time reaches zero.

Okay, given that a prefix expires, it should be withdrawn, whether it's a ULA or a GUA.

> D) Whenever there is no longer any valid delegated prefix, advertisements for a previously deprecated autonomously generated ULA prefix MUST be updated with non-zero preferred lifetime.

OK, but seems like unnecessary work.   You're essentially recapitulating the brokenness of IPv4 zeroconf.

> The idea here is to make sure IPv6 applications can generally rely on home network interior routers to forward traffic among the multiple links in the home, regardless of whether any first-mile Internet services are provisioned, configured and operational, i.e. there shall always be at least one preferred global scope network prefix, and there shall be an autonomously generated local prefix available as a last resort whenever there are no valid delegated prefixes.

This is where I am just completely puzzled.   We talked about this previously.   I thought the idea was that the homenet ULA should converge: that there should only be one, ultimately, and that when there are two, routing should still work.  You are stating this as if the ULAs are per-subnet of a homenet, and that routing across homenet routers using ULAs isn't supported.

If you really think that's how this should work, I can see why you want to deprecate them.   But that's not how they should work.