Re: [irtf-discuss] Why do we need to go with 128 bits address space ?

Tom Herbert <tom@herbertland.com> Thu, 15 August 2019 23:26 UTC

Return-Path: <tom@herbertland.com>
X-Original-To: irtf-discuss@ietfa.amsl.com
Delivered-To: irtf-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 623E31200FA for <irtf-discuss@ietfa.amsl.com>; Thu, 15 Aug 2019 16:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 ZTsKEd9AdzOh for <irtf-discuss@ietfa.amsl.com>; Thu, 15 Aug 2019 16:26:19 -0700 (PDT)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 2FAD11200F1 for <irtf-discuss@irtf.org>; Thu, 15 Aug 2019 16:26:19 -0700 (PDT)
Received: by mail-ed1-x52a.google.com with SMTP id a21so3584622edt.11 for <irtf-discuss@irtf.org>; Thu, 15 Aug 2019 16:26:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=herbertland-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DZZpud6MjVc+E/WJqJqcAG13jk/Z+KPswdoaAt3RTfc=; b=uCRAAtnL4x5PCZY7BkIsFajDwKg1UjueeZNeuAnxDUWncx1/8be2P0iaG8JrUaYW3w qNrRx3t70cV/H0H2R4iF3g01ejchyotRa0+r3rtKCw7NzQyyGB2FDxqiBm1xFP9j0DAI wrT0AYOUkpW+sM14lqb4vGemVs2blmEi2RX4E5GzxJLmdRr4d0Rb2ei+pduZZjFgfuXd yXxpAdw9L1kTn1SzgP43aiQUHGWI44omlqhecvAl6fXLu7EN6yKbSY98BcSeVcJwnXeQ fTOt7uwo3+i9QDF9JA/6VU/qdwgRDVenLajEouCjaxetu6/BQ44cZ2WtnRCJ6SB1ySlj ogqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=DZZpud6MjVc+E/WJqJqcAG13jk/Z+KPswdoaAt3RTfc=; b=Un9RfQ8AtH07K8ksYpi0+Cwk7b18rJrVRvEZ8pLMzFlme2DgaAuBhyJjYHtKnepAVO MwRBbEKtKG48EMCEYCEiyQg7wTI63XifY0KndPNGdr/w42QqzdkM5fRFiHs0eSsL6aEN 2UCBE23v+5spoS3yqEcf9S4Dnp+qIcO3y54+KjqApjoZdH2bv/8sh+Xe58rhCjIs2vRX JUo5ccY3jZ0US4yLUOJEIKaKohBp7YCNbPAa/G2529+8gLxGf2rbr2vsgsCwXuExCZ53 bHO4ZTxV/9R2C395akk2q79u80i/b08rqVMD38b4iAjriqXpqTFLe7/+FkxGXz67VYf1 sO8Q==
X-Gm-Message-State: APjAAAXDM4ubWzYC7clX+YcOEXOTt67uATiv++NRhFoJ9H43CotEMcRV VTUbrXj2gW77cqKcv58u0wILZK+7fhW4JvlIx405Uw==
X-Google-Smtp-Source: APXvYqzCIKPbet0D75WSbiF65YjOCuqbhbpx3OJVzGaN1EmQWiZEzbf0Eie6R91OMK0OSudulSYsVCi2HNRxpNeIx9Q=
X-Received: by 2002:a17:906:5806:: with SMTP id m6mr6737105ejq.80.1565911577519; Thu, 15 Aug 2019 16:26:17 -0700 (PDT)
MIME-Version: 1.0
References: <CAPTMOt+cGhBqHmT3yZVChv-PCMqxT-WPDcDdM3RuTc1TMfFeVg@mail.gmail.com> <cd254463-43ba-2afd-5c3c-f462a74e5c30@kit.edu> <374d84e5-e20a-e89f-d235-703581db1f00@si6networks.com>
In-Reply-To: <374d84e5-e20a-e89f-d235-703581db1f00@si6networks.com>
From: Tom Herbert <tom@herbertland.com>
Date: Thu, 15 Aug 2019 16:26:06 -0700
Message-ID: <CALx6S36N2F+EDDdnR7omQJoH9LKZQuK5wB+02jFB0T9ZOKEo_w@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
Cc: Roland Bless <roland.bless@kit.edu>, shyam bandyopadhyay <shyamb66@gmail.com>, IETF-Discussion <ietf@ietf.org>, irtf-discuss@irtf.org, 6MAN <6man@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-discuss/D1xlSaY8YeACoLQg6sxssLJjydE>
Subject: Re: [irtf-discuss] Why do we need to go with 128 bits address space ?
X-BeenThere: irtf-discuss@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IRTF general and new-work discussion list <irtf-discuss.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-discuss/>
List-Post: <mailto:irtf-discuss@irtf.org>
List-Help: <mailto:irtf-discuss-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-discuss>, <mailto:irtf-discuss-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Aug 2019 23:26:21 -0000

On Thu, Aug 15, 2019 at 3:48 PM Fernando Gont <fgont@si6networks.com> wrote:
>
> On 15/8/19 12:27, Roland Bless wrote:
> [....]
> > c) given the increasing number of virtual machines and IoT devices 64
> > bit isn't sufficient, see also the discussion of new MAC address lengths
> [...]
>
> The MAC addresses should have never been embedded in the IID. In fact,
> that's no longer the recommended way to generate IPv6 IIDs. See RFC8064.
>
It's not the number of addressed nodes that exhausts an address space,
it's the various levels of hierarchy to people split the space into
(eventually someone will claim 128 bits isn't enough!).

There is one relevant implication in this discussion. It's undeniable
that IPv6 addresses are four times larger than IPv4 addresses and in
some contexts that is an overhead burden. I believe this is being
addressed. For instance, 6lopan has a method to compress IPv6
addresses and the header, and there are active drafts that would
reduce the overhead in segment routing header which carries lists of
IPv6 addresses.

Tom


> Thanks,
> --
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------