[v6ops] renumbering [was Deaggregation by large organizations]

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 23 October 2014 19:21 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA7A1ACE9D; Thu, 23 Oct 2014 12:21:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, 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 sVwpwINEEF8l; Thu, 23 Oct 2014 12:21:21 -0700 (PDT)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47E0A1ACE9B; Thu, 23 Oct 2014 12:21:21 -0700 (PDT)
Received: by mail-pa0-f47.google.com with SMTP id kx10so1634496pab.6 for <multiple recipients>; Thu, 23 Oct 2014 12:21:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hwT25SGSDWM358gLuTKn4x12WjdVuwdJm0HVWfxRmIo=; b=zMiqapqqbMl9X9DLt5c9TClUXW2CzYT5JP61gFAAQjWLstPK4YTmc1GJoJcxzAbR0s 6Wfb1qfwnGkli/3aZQlB8KQJ7BZRqDS5zbiIxHhJNYh0A4l1fvkm5fYtdSit85GncM9X OnFrl+ceeo9HoOwJA8rwy+cUbuTiluZJarxedQlJ1hQaval1Cz61G0hUstyZswc8nUML S3hcB0t2WjwPb4gLs+P52o0c9vWHSXk3wsHcSh6RauaMdG5Ynggy/rM7LVCeu4sJBXjz M/uYF9GGutDTX6YJeGpHkyw4/KJhaPwMiFEkF1KrHr/wRTgHSmmNoXUWfTr46OfUZLUF LZVQ==
X-Received: by 10.66.154.111 with SMTP id vn15mr3161668pab.155.1414092080940; Thu, 23 Oct 2014 12:21:20 -0700 (PDT)
Received: from [192.168.178.23] (9.200.69.111.dynamic.snap.net.nz. [111.69.200.9]) by mx.google.com with ESMTPSA id h4sm2184230pat.11.2014.10.23.12.21.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 23 Oct 2014 12:21:19 -0700 (PDT)
Message-ID: <54495537.1030703@gmail.com>
Date: Fri, 24 Oct 2014 08:21:27 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Gert Doering <gert@space.net>
References: <F5C06CAF-0AD2-4225-8EE7-FC72CE9913F0@muada.com> <755DE4C3-CDDF-41AF-BA9C-E8EC5B4DFC4C@muada.com> <A7F6BEA0-BCDD-4197-B6CB-7EB8797ACA9C@delong.com> <20141016233533.1B73521A106C@rock.dv.isc.org> <CAEmG1=r7UdeStcqFjiQRO_Vt1hfR_T4oyTW5FD-eD1ATEXpc6A@mail.gmail.com> <20141017010552.9682921A4D54@rock.dv.isc.org> <CAEmG1=qi2YcBrMC8__32PFPzD6OfycTbJqeV9g_WbOs7+T14gA@mail.gmail.com> <20141023084132.GE31092@Space.Net>
In-Reply-To: <20141023084132.GE31092@Space.Net>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/v6ops/DFb9ULM_Tp0_FOUMafyP6LhMQl0
Cc: v6ops@ietf.org, grow@ietf.org
Subject: [v6ops] renumbering [was Deaggregation by large organizations]
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Oct 2014 19:21:23 -0000

Everybody,

Indeed, home networks renumber after every power cycle on the home gateway.
Homenet will ensure that also works for more complex networks.

We have a gap analysis for enterprise renumbering. Go fix the gaps if you
think they matter:
http://tools.ietf.org/html/rfc7010

  Brian

On 23/10/2014 21:41, Gert Doering wrote:
> Hi,
> 
> On Thu, Oct 16, 2014 at 06:18:34PM -0700, Matthew Petach wrote:
>> The probability of us figuring out how to scale
>> the routing table to handle 40 billion prefixes
>> is orders of magnitude more likely than solving
>> the headaches associated with dynamic host
>> renumbering.  That ship has done gone and
>> sailed, hit the proverbial iceberg, and is gathering
>> barnacles at the bottom of the ocean.
> 
> What I find scary in this statement is the underlying "one solution must
> fit all users" mentality.
> 
> I can fully see and understand Owen's point that in an *enterprise*
> environment, renumbering is truly hard, because you need to get lots of
> other people that have no real interest to renumber stuff in their config
> files - and yes, vendors of <whatever> that could handle DNS lookups and
> combinations of "get prefix from DNS, attach <localbit>, put result into
> usage" would be truly nice, but indeed, that should have been specced
> 15 years ago to be available now (maybe).
> 
> OTOH, there's the large mass of SOHO style users, where "dynamic host
> renumbering" *really* is a non-issue.  I've gone there and tested it
> in a homenet testbed with two IPv6 uplinks, so multi-homing and 
> src-based routing thrown in - it works.  It needs polishing and some
> IETF work here and there (SAS failover comes to mind, and labels-to-
> prefixes) but it works better than "IPv4 with two providers" today,
> for that particular class of users.
> 
> PI(-ish) "for everybody" is just not the right solution for non-technical-
> savy users that would just not know that these funny numbers they received
> from one of their providers are relevant, and lose them - thus, when changing
> providers, would get new ones anyway.  And what do they need static addresses
> for, anyway, as long as some sort of "register and lookup" mechanism exist
> (mDNS, DNS, SIP, ...) to find the address when needed?
> 
> No, Owen's home does not qualify for a typical "SOHO" network, and most
> likely, none of the other readers.  Ask yourself, what is needed to make
> the network on your parent's home work (assuming those are not network
> engineers).
> 
> Gert Doering
>         -- NetMaster