Re: draft-bourbaki-6man-classless-ipv6-00

Tom Herbert <tom@herbertland.com> Sat, 03 June 2017 18:41 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D07412EB9A for <ipv6@ietfa.amsl.com>; Sat, 3 Jun 2017 11:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=herbertland-com.20150623.gappssmtp.com
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 lCmRfx6ekaTt for <ipv6@ietfa.amsl.com>; Sat, 3 Jun 2017 11:41:18 -0700 (PDT)
Received: from mail-wm0-x231.google.com (mail-wm0-x231.google.com [IPv6:2a00:1450:400c:c09::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 651A712EB97 for <ipv6@ietf.org>; Sat, 3 Jun 2017 11:41:18 -0700 (PDT)
Received: by mail-wm0-x231.google.com with SMTP id d127so48320365wmf.0 for <ipv6@ietf.org>; Sat, 03 Jun 2017 11:41:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kQ8wIEjoFC+nXwV6RfEdUxMLMW3bHqPONQWxg465zOo=; b=bzf4eP3gBh0sB+so0c7Qhv3DbDWTqk32h/n09y2/vCf/3i63U/Yl1W0eE4+Rs/7rno Bp/zGNc+L+rj8IV7XfyodFa5RUZB8l5EQsoj2fZSc1U58vNstTCHKL9EXpAwudfGjOhM BPuVhDirPI4neZ8vUAqGdgkDBcZFlfBIy0Do1DLR7kvWStcR25AT+ra++WWRo8S/e6Bj tAzCMHPAwqAq2pdcNVrtXpKejxqHbKqoRFCqrVzwYz3+rrIjWEp63WjdKG47z4yvLdEN skpAzQgaUjeh7KoU1s1w+P72OVkPNG29KJpJo1jVZ1EYYdnbqTnwvyJzHLaR/ZO4Yk3J e0iQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kQ8wIEjoFC+nXwV6RfEdUxMLMW3bHqPONQWxg465zOo=; b=pPibyQ9wR6V57/pg5Q+6GHKTlg7E04koZ8YpV39IJg18VaF9MopGz42o/xuCxv2LuP IIj7aj+81VmGPFX65FE6BkqSQYucAFcbKMxcUbXJbYuEzw2iD+4SJpNqknx2xhK6CqXB IeWsNPcoc9fQbVxfZxkJMKVO9lgoABa4ZeKWjd94DgakTS0FTCBpzOAFi1fpPuGjAkQd 3SabcCx9+quf0N14lNUxjoRyxmRq7KbRMk90RVGFJpx3M5po1J28ChfIHurGA/rhZjU4 dtiSuIvDry7mWjIy/Rhlfs4keqarPymmbtQlmGmZdenpbcgQ3n3tVf/0mqFZQaNSO5Bf rZCw==
X-Gm-Message-State: AODbwcBGIo96tyBPiYgGsyS75iTZfrs7u9PseUkDXgQM2ALmYsnDCBSb FNUIJMYPprDyrXvn+yqKW1HZEOxcja6k
X-Received: by 10.28.229.144 with SMTP id c138mr2876742wmh.60.1496515276776; Sat, 03 Jun 2017 11:41:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.132.135 with HTTP; Sat, 3 Jun 2017 11:41:15 -0700 (PDT)
Received: by 10.223.132.135 with HTTP; Sat, 3 Jun 2017 11:41:15 -0700 (PDT)
In-Reply-To: <715E81C1-6A48-4507-8C50-C94D1D68B842@thehobsons.co.uk>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <CALx6S34y1ZS95dD6Qv5A90RnKwh2NqC=VDaZ2vSq+zpo5+NpUg@mail.gmail.com> <5932DA16.9040008@foobar.org> <CALx6S35c8J5sn=VpGis-J3=yRzwXVMcntfn=Gv=tQ5k-v7r4gg@mail.gmail.com> <715E81C1-6A48-4507-8C50-C94D1D68B842@thehobsons.co.uk>
From: Tom Herbert <tom@herbertland.com>
Date: Sat, 03 Jun 2017 11:41:15 -0700
Message-ID: <CALx6S36hu5-65Xg11ZyJwkh04epiQDjONudxRbvv-Psyh4ONZA@mail.gmail.com>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: Simon Hobson <linux@thehobsons.co.uk>
Cc: ipv6@ietf.org
Content-Type: multipart/alternative; boundary="001a11471eb279437a0551129d1f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6UNfJvJreWci4U39igi0I7rqQT0>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jun 2017 18:41:21 -0000

On Jun 3, 2017 2:16 PM, "Simon Hobson" <linux@thehobsons.co.uk> wrote:

Tom Herbert <tom@herbertland.com> wrote:

> I'm not going to use my phone as a router into
> my enterprise network, I don't see any reason to have it delegate some
> complex network hierarchy. We need the ability to tether a small
> number of devices, anything more than we are talking about a different
> type of device.


OK, what about a situation where something that looks like a phone to the
network, but happens to not have much by way of telephony bits built into
it, is being used ? It really doesn't change the discussion that the box is
black, has no display, and is called a router - it's still doing exactly
the same thing as a phone doing tethering for downstream devices.


But that does change the discussion significantly. Those are different
devices, not smart phone I'm using to type this message. This does not need
a /64 assignment, I will never use it for any more than tethering a few
devices. What I do need is seamless mobility for my applications which is a
problem IPv6 should be able to help solve.

And at work, we have customers doing just that - connecting an entire
network (OK, not complex network) to the internet either as a temporary
measure until their proper connection gets installed, or in some cases as a
permanent measure as it's not worth getting a fibre circuit installed for a
temporary site (where temporary is typically in the order of 2-4 years for
a civil engineering project).


That's anecdotal. For every case like that, how many user devices are out
there that don't even turn tethering ever and are only using one address,
much less need 2**64 of them?

Thanks,
Tom




Roger Jørgensen <rogerj@gmail.com> wrote:

> But I guess the none technical side are a lost case for most IETF'ers.

In reality the world is run by non-technical people - often derogatorily
referred to as bean counters. While not applicable here, I firmly believe
that one of the reasons for the slow adoption of IPv6 is it's perceived
complexity (and hence cost) on the part of the bean counters who ultimately
must sign off on any project in a business.

> Not to mention that we remove one of the thing so many I've spoken to
over the years think is great - the standard LAN size.

I'm inclined to agree there.
At first I had to admit that I just couldn't bring myself to think
positively about what seems to be profligate wastage of address space -
having "cut my teeth" with IPv4 addressing. Now I'm getting my head around
it though it's taking some effort to adjust in many ways.
As a thought, will there be discussions at some point in the future when it
turns out that some vendors have decided that nothing other than a /64
exists and so their kit doesn't support (say) a /56 ?

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------