Re: RFC4941bis: consequences of many addresses for the network

Gyan Mishra <hayabusagsm@gmail.com> Fri, 24 January 2020 23:06 UTC

Return-Path: <hayabusagsm@gmail.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 13BB4120227 for <ipv6@ietfa.amsl.com>; Fri, 24 Jan 2020 15:06:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 224U3aCArF_D for <ipv6@ietfa.amsl.com>; Fri, 24 Jan 2020 15:06:20 -0800 (PST)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 36ECA1200E9 for <ipv6@ietf.org>; Fri, 24 Jan 2020 15:06:20 -0800 (PST)
Received: by mail-io1-xd33.google.com with SMTP id i11so3626548ioi.12 for <ipv6@ietf.org>; Fri, 24 Jan 2020 15:06:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/pzZ6dL6HNRUSXh6ubvnvdcEfwbjBA4mxutD3hMq3Z0=; b=Ey2pZ0JpVNdEvtOyFLF/hKGDqgWx0gOnjtlHI//1Gy2+AZg7GcMDUzze9Yu0aYvEal J+ZHJZyzoY6U5yg7XQIhctYSe/Fh29x2nlhkPXpPwL6Mgjzh9GxFoghNx5U8hrbwtF3c e8aoZkeC5ueWowxRaZ+qVLVCl4+NkA4q0fF3aGnZF414z2B6/saHxlTs1DI+b4+fRNm+ k+XMb8Rk5C01M9gdx4QTvcAxNaxIFGpp1qZWMzAzaKxMzMhd7ZhO1dBXZX7AEDpiqWPl JpmohHVrxrMRqzcbNgcT/l86lWVDPzlTvTXHTgYW+Ic1smHl5wK6PwDa+PWLX8m4jlIp DFaQ==
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=/pzZ6dL6HNRUSXh6ubvnvdcEfwbjBA4mxutD3hMq3Z0=; b=hTWK2J7Qq/5NWiBvT0JV43V77HFE0+oEoLUgF7T39g/o3OBJUt+/Nc/D1iriWmQ5ex hGCs2HbBIquYROKBZB1vy87a86V6YNrpXAPzww9t5l47/bu8xAY8lMI2CJU7j8fSoGjt +I3oAZyMwCs8CIE7h7V1hwzsG3oItVWW0yTb2ILVH6/BZ04JnC/Ak6LBbiwxe6zXAzEC PkjeuwzGFlX0EhEbXaOtgctxgCDoLLrU3kaTN7nzwOkPcaZjyMcogrBGDbli0KYrjBVf FUJKTLP5kwd2tufUhmReLNc3ui2hrL/vUvHAzz/5HiKlPCLEivvkh0kMe1xGS+Gx2EEW WbiQ==
X-Gm-Message-State: APjAAAWYSIWAPCLSUOYVf8p/Y3So4kYXpRPniEhqdQRJO28whnNQcHhp Yo/OQRrmNL9lAmwvATo5bT1zLjfkplnTaGRbB8o=
X-Google-Smtp-Source: APXvYqyd61IHBI+Iz6PrDcTZgpQa5ee9+Xvn0enuWStiVNAhpCw8DcDk4TD7wb0eDmDK9OGu54mwjLTJB9cyqAOojSw=
X-Received: by 2002:a6b:4e13:: with SMTP id c19mr3928866iob.58.1579907179495; Fri, 24 Jan 2020 15:06:19 -0800 (PST)
MIME-Version: 1.0
References: <03C832CE-7282-4320-BF1B-4CB7167FE6BE@employees.org> <e936078e-01f9-0254-a8d0-4095455154ac@si6networks.com> <D85412DF-4B03-4790-9E39-968D50ECF86B@employees.org> <m1iuwJV-0000MAC@stereo.hq.phicoh.net> <B341FF1B-C559-4D54-B117-A58EB6A3C955@employees.org> <dfe3a236-4e61-d2be-929c-869a81994879@si6networks.com> <m1iuxwI-0000M3C@stereo.hq.phicoh.net> <CABNhwV1XcATmrosW_kRTJgrXyTSNqPe=uR4VDt=_eXtt5=H3CQ@mail.gmail.com> <431eefce-594f-b7bd-4d49-a7a7ddbcd684@si6networks.com> <CABNhwV1wA+ntT1SHzzF19VotpXED=MOD2HTbQq2hL_nhaOR3qw@mail.gmail.com> <7c65c99f-1418-eb07-b984-8ad7ff6b7a62@gmail.com> <CABNhwV0jyS+bgKzHeQe9x-3FZvsr_-BiKVm=-G_LGizC7nR=dw@mail.gmail.com>
In-Reply-To: <CABNhwV0jyS+bgKzHeQe9x-3FZvsr_-BiKVm=-G_LGizC7nR=dw@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Fri, 24 Jan 2020 18:06:08 -0500
Message-ID: <CABNhwV0w5tO-4_ixNUWjbAb81vmQvGF_iYmghmqRSuEmVR8Qtw@mail.gmail.com>
Subject: Re: RFC4941bis: consequences of many addresses for the network
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Fernando Gont <fgont@si6networks.com>, ipv6@ietf.org
Content-Type: multipart/alternative; boundary="000000000000364415059ceace80"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/QbAZYHiHP7ZrEmMKfVJvgVsiPBo>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
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: Fri, 24 Jan 2020 23:06:22 -0000

Microsoft link - forgot

On Fri, Jan 24, 2020 at 6:05 PM Gyan Mishra <hayabusagsm@gmail.com> wrote:

>
>
> On Fri, Jan 24, 2020 at 5:11 PM Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
>
>> >  I agree RFC 7217 stable address is most preferred however Microsoft
>> and Apple don’t support yet.
>
>
>   Gyan>On my IPv6 roadmap list with Microsoft.  So far no ETA.
>
>>
>> I have no idea for Apple, but afaik MS switched to pseudorandom stable
>> IIDs per interface a long time ago, before Windows 7 possibly. I haven't
>> seen a modified EUI-64 address on my laptop for a very long time. This is
>> not the same thing as RFC7217 from a privacy point of view, but for network
>> operations and neighbour cache size it seems like the same thing.
>
>
>    Gyan> I think it’s EUI-64 and not modified.
>
> I found this link from Microsoft but it does not state if modified is
> supported or not.
>

http://download.microsoft.com/download/F/D/F/FDF4CF55-5FDE-4CFF-8539-3662BB5EB7A0/TD13Basel2-43.pptx


>>
>> Anyway, I hope we're all agreed that this topic, however interesting is
>> not worth more than a small comment in RFC4941bis. Isn't it actually a
>> v6ops topic ("Operational impact of numerous addresses per host")?
>
>
>   Gyan> Agreed
>
>>
>>
>> Regards
>>    Brian
>>
>> --
>
> Gyan  Mishra
>
> Network Engineering & Technology
>
> Verizon
>
> Silver Spring, MD 20904
>
> Phone: 301 502-1347
>
> Email: gyan.s.mishra@verizon.com
>
>
>
> --

Gyan  Mishra

Network Engineering & Technology

Verizon

Silver Spring, MD 20904

Phone: 301 502-1347

Email: gyan.s.mishra@verizon.com