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

Tom Herbert <tom@herbertland.com> Sat, 03 June 2017 16:03 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 BDD0D129BF5 for <ipv6@ietfa.amsl.com>; Sat, 3 Jun 2017 09:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 BxFh1T9LOH_7 for <ipv6@ietfa.amsl.com>; Sat, 3 Jun 2017 09:03:33 -0700 (PDT)
Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (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 4CD7E1242EA for <ipv6@ietf.org>; Sat, 3 Jun 2017 09:03:33 -0700 (PDT)
Received: by mail-wm0-x22c.google.com with SMTP id b84so45056907wmh.0 for <ipv6@ietf.org>; Sat, 03 Jun 2017 09:03:33 -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=fcyXyBHsQG22SFJAUC7/zR6iRblw/KjH9SjrR+r4H1w=; b=Sl2ujH16YqMt1PFMB4RCh0/oQakAPzbVG1BmJQoRdu87Ys3sbv3rNdBIeUYTdNdWC0 iqaPv+uGhhJW5VLoXMJEeMepI2prQuf9173BirjQFUPqFV27rqaEVsHh6B/kaKvyPGmL Qa9pjZR6slIaEfTuSOlwKdGRboWaCt+nGbqX9NuPa/b5dxLV8qyJFsiZT6V3TblEEv+V KrB8B/43LCRgizx9EKBPhT25uvp9Zsom43o+fHSOqtBrHDh3fstgDpPWy9xhBHJ2x4+J ecbi9jAHfxkx+8kothY6rPvdX2yXRxtmf4C/qAjJhkfHBqbkS42j0Hq9fS+ST7t0esr2 61zA==
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=fcyXyBHsQG22SFJAUC7/zR6iRblw/KjH9SjrR+r4H1w=; b=H79cByFdVSotcnFG+x4X5TakLVADNDq4Wf/854SrIWCLhwNwg+cCJR6l7C9C2TNvVS oZGgor5Qij9ImZU92cn2n17LY7QgIrD+lCBhUtK6ZfhbWo8Gw/ahpTlC4edz1LBkiz5R udbSJzBoglWlJU4QF3ziahkRMmukvuTrS1rmQocxQ4IFLgLw0f8o1XhbUhFJ+BYw/pfS X+rmu384a1uleitIKZsviFDvxhMT+TDj1WZpId0VhR29PeNSZwjHr+qasd6NKtFkzhlX IL1H8kGIMQGjPOW/fBon0XWHhssCUh3ByymEn1lH8ThazUHQE5ZfJ0GzIXTdbwCC7wDn BPfQ==
X-Gm-Message-State: AODbwcANf3A4iyA7QoFOF6eJU0sJtxJ53SkhOeuB58f04pTlLOSfCrHq TOUDwR2tjbOggG6wcaESUxI22iI7e/rj
X-Received: by 10.28.54.154 with SMTP id y26mr2247352wmh.53.1496505811754; Sat, 03 Jun 2017 09:03:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.132.135 with HTTP; Sat, 3 Jun 2017 09:03:30 -0700 (PDT)
In-Reply-To: <5932DA16.9040008@foobar.org>
References: <20170602141112.x64nleqclygz7dwd@Vurt.local> <CALx6S34y1ZS95dD6Qv5A90RnKwh2NqC=VDaZ2vSq+zpo5+NpUg@mail.gmail.com> <5932DA16.9040008@foobar.org>
From: Tom Herbert <tom@herbertland.com>
Date: Sat, 03 Jun 2017 09:03:30 -0700
Message-ID: <CALx6S35c8J5sn=VpGis-J3=yRzwXVMcntfn=Gv=tQ5k-v7r4gg@mail.gmail.com>
Subject: Re: draft-bourbaki-6man-classless-ipv6-00
To: Nick Hilliard <nick@foobar.org>
Cc: Job Snijders <job@ntt.net>, "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aj5UlkCjpfPfyKJG7100k1uBT3o>
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 16:03:35 -0000

On Sat, Jun 3, 2017 at 8:47 AM, Nick Hilliard <nick@foobar.org> wrote:
> Tom Herbert wrote:
>> Thanks for the draft. I think the case will be bolstered with some
>> real examples as to how fixed /64 interface addressing has proven to
>> be problematic. Using identifier/locator split in addresses as I
>> mentioned is one example. I suspect there are more that could be
>> documented.
>
> Tom,
>
> let's say your device is assigned a /64, e.g. either on a mobile network
> or via PD.  Your device sits between upstream and downstream devices and
> passes traffic between upstream and downstream.
>
> Forcing /64 means that your device is limited to bridging mode, because
> downstream devices would not be permitted to assign a netmask of longer
> than /64.  This could seriously adversely impact on network connectivity
> options for downstream devices.  E.g. multiple networks sitting on some
> homenet.
>
> Would this fall into the category of examples that you're talking about
> here?
>
I think this is too much a generalization trying to make it a "one
size fits all" problem. 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.

Tom



> Nick