Re: [v6ops] Fwd: I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt

Mark Smith <markzzzsmith@gmail.com> Fri, 04 August 2017 02:40 UTC

Return-Path: <markzzzsmith@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11D04129B2A for <v6ops@ietfa.amsl.com>; Thu, 3 Aug 2017 19:40:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.498
X-Spam-Level:
X-Spam-Status: No, score=-1.498 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, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 PJcElbV_9v1l for <v6ops@ietfa.amsl.com>; Thu, 3 Aug 2017 19:40:12 -0700 (PDT)
Received: from mail-vk0-x236.google.com (mail-vk0-x236.google.com [IPv6:2607:f8b0:400c:c05::236]) (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 0B47313146C for <v6ops@ietf.org>; Thu, 3 Aug 2017 19:40:12 -0700 (PDT)
Received: by mail-vk0-x236.google.com with SMTP id u133so1489610vke.3 for <v6ops@ietf.org>; Thu, 03 Aug 2017 19:40:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=dDygyrh+O1cZn7XyQm2EhJtvCKX7JvS4uwkstunzzVE=; b=OD++KQAeL3GSiE45xf2A9RALpUFmdFyluoVB+MydQlB9Ycek3kiRcNbxQOsop22hJ8 t1fG7glUs+SPW50wKm7QOVYjZL/B5dq/bZXNz5C8Rx9zFl8UqqVrHyIpkgUQkXtDsGBL ZwCwy802/lxOPZGSZYPFx37g+s7e5XwY9lPjvlASZcrpLiwlFdlr4Hhbo2Fhr+I9nU7T lTkamg8RIp7wgqtH/XGO9GWe3t7n3RqFqecHVk0moRjHz4wcGxgOnMrMjKk6awZUZWsN tSTnHvQXgZYUxq5gG5d5pxk9wrhtzXtjUtLt5jlwS9pt2xb/oQXIb4YRZqF2Ty5d6Uji OaWw==
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:content-transfer-encoding; bh=dDygyrh+O1cZn7XyQm2EhJtvCKX7JvS4uwkstunzzVE=; b=BfSxTBNtJsApFwk3Xcuqe6WcfKRdZQdWRyGuDfQIRIS5ltdIEs549FWJiwewFV8Ibc DQGmA/p4ODxOpTq7UxF3NpbNeuh7TRrzLJZaNtU3FxVbTCT9qV70DAoWY8qSBX3yM/41 ykej8uF001pzhhekt4erqg46/uT0QwWSqVZ+B7DeAu/s4/62rxIq9B68CW6V+srfIYKV uqmilAWxV8vZBdZyGYxqo40uMoTMb4ZvoM1FTd3joxjAUzCv4DhnaP4F3XTri6X3wCeQ h6Gz4MS0R2duT9qU9g9U3tTj0OmEBy+Kpezz0ryzVkjYeKE9MXN0htv7Bed3OcOTG0T9 BWeg==
X-Gm-Message-State: AHYfb5iZh0OFwK8BnNMPb8lHz/Z01DDGhjxC9T8RLBdUhOitsAdxp9Iu s0itXNYYk3To0bi9dAcQoUvBnQ3HpQ==
X-Received: by 10.31.59.69 with SMTP id i66mr464027vka.105.1501814411133; Thu, 03 Aug 2017 19:40:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.18.105 with HTTP; Thu, 3 Aug 2017 19:39:40 -0700 (PDT)
In-Reply-To: <E6AC9174-3D6E-4FAD-B84B-B7E58FB149BC@gmail.com>
References: <150148445751.17707.15424999122129322815@ietfa.amsl.com> <E6AC9174-3D6E-4FAD-B84B-B7E58FB149BC@gmail.com>
From: Mark Smith <markzzzsmith@gmail.com>
Date: Fri, 04 Aug 2017 12:39:40 +1000
Message-ID: <CAO42Z2xEs6RauD6Oo_NbqOh+FRVAu3NuveewSvRx7g1hS2-ToQ@mail.gmail.com>
To: DY Kim <dykim6@gmail.com>
Cc: v6ops list <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/BovSL4XWC_6371xzLi0BxQwhVc4>
Subject: Re: [v6ops] Fwd: I-D Action: draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 04 Aug 2017 02:40:13 -0000

On 4 August 2017 at 11:53, DY Kim <dykim6@gmail.com> wrote:
> In the 2nd para of Sec. 4, it reads:
>
> “… a Unique IPv6 prefix (currently a /64 prefix)…”
>
> Assuming that there’d be at some place upwards where a /48 prefix would be
> present, which prefix length is up to a common practice for ISPs in
> assigning a prefix to a site, does the above spec means:
>
> o the maximum number of devices that the proposed scenario can accommodate
> is 64K (2**16; 64 - 48 = 16)?
>

(Not speaking on the authors behalf)

If you only received a /48 for your site, then yes, that would be the
upper limit on how many devices this method supported.

However, the scenario being described is one of a service provider,
and they will get at least a /32 from their RIR, meaning in theory the
maximum number of hosts they can support is 4 billion (!). They could
get larger than /32 if they needed to if it became too small.

In this scenario a "site" is really the individual host, rather than a
boundary of a group of subnets at a site. /48 or /56 are common
aggregation boundaries for a multi-subnet site, so they don't really
apply here. The service provider could internally aggregate the /64s
at any where they need to between e.g. /32 and /63 to suit their
routing protocol scaling.

So in short, /48 is not constraining this solution because /48 doesn't apply.

Regards,
Mark.