Re: [105attendees] Why do we need to go for 128 bits address space?
Brian E Carpenter <brian.e.carpenter@gmail.com> Sat, 27 July 2019 21:56 UTC
Return-Path: <brian.e.carpenter@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 06DE112008C
for <ipv6@ietfa.amsl.com>; Sat, 27 Jul 2019 14:56:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, 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 8mQ8MMmT1Mzb for <ipv6@ietfa.amsl.com>;
Sat, 27 Jul 2019 14:56:31 -0700 (PDT)
Received: from mail-io1-xd41.google.com (mail-io1-xd41.google.com
[IPv6:2607:f8b0:4864:20::d41])
(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 A4F8412007A
for <6man@ietf.org>; Sat, 27 Jul 2019 14:56:31 -0700 (PDT)
Received: by mail-io1-xd41.google.com with SMTP id k20so112030951ios.10
for <6man@ietf.org>; Sat, 27 Jul 2019 14:56:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=subject:to:cc:references:from:message-id:date:user-agent
:mime-version:in-reply-to:content-language:content-transfer-encoding;
bh=XJ6gD7yNRIwsdBMzp+kjz5m3HWOMtcF8q/GBpSt39nw=;
b=BI8SmyUBaIak5MasDIab6/2CvX87OyBVpTlnpoUQb+cWf7E281pk3Nl231pvCxdo2X
uUdsMXRiSwIucZev97jeAKsYerrIEGbwiqR7NcDOTTTDXz8Mi7YaaU9YZa5QJgKhz3M0
rTXuEbBa1FMhS+okLswA9Wy/dichzuYQRgWUAafQf4kglQXmJMKazBQuyKtWydSra9on
bgA7UgSYCNSozvOZyQgFjP+Vw00x+zxaCOLUoXcpDmyn13le0ljxrh+fSOzikn0ngjoA
m1tAIsqPEP8UYYF5dMZaHOZDH4Rp0QbIAtSDuyI/2yjyj0rY1pGoinAkZXuZ14wlswLr
6KKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:subject:to:cc:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-language
:content-transfer-encoding;
bh=XJ6gD7yNRIwsdBMzp+kjz5m3HWOMtcF8q/GBpSt39nw=;
b=Fa9uaCfuNHKviObFIzxgM+W2VCmIGezBfpkkYBkwNd4XCSRsT3bz1MAFVypOBwkLue
2SDj6Razma/a8Oz0fbi68rPEoWwsQ3vPBe7MI7gj3sETbNFzDI35AubrpIpV9oDuOj+n
FfUN1H/reGUM03L867ZxdP+Vi39+fJbDz/mGHsgQwtdWWxYSucdscS9QNuWmRewpHneu
sf7m8SkSqZCkg2i8y96Z1Z0O5jTr9zdin+rNMZeCFGfrx3UJOIRRFgzmqXBObM9NgTG1
mInpR35no6ayraBm03UIUORNx1RRj+KFc1/SjKUV0udLyh8K2R1kLY2bdS+LwWjZYoDp
bGaw==
X-Gm-Message-State: APjAAAXUncFiD8ly4s6d7GZI8Ut/a77h4aI2Kvd+gh9tY4PDr16DGluN
JnGUvhYhSN1pOOOWf7uOofrY+Y7F
X-Google-Smtp-Source: APXvYqz1qQ9vls6cJ0OW99lU39Ji9bdGEF/w7J3u33rKJyIHOFpqDX6SNSrsMNGy6OA4omqrf8Z3sg==
X-Received: by 2002:a02:3f0a:: with SMTP id d10mr30739442jaa.23.1564264590785;
Sat, 27 Jul 2019 14:56:30 -0700 (PDT)
Received: from [10.255.242.196] ([207.164.22.35])
by smtp.gmail.com with ESMTPSA id c11sm31719727ioi.72.2019.07.27.14.56.29
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Sat, 27 Jul 2019 14:56:30 -0700 (PDT)
Subject: Re: [105attendees] Why do we need to go for 128 bits address space?
To: John Day <jeanjour@comcast.net>, Simon Hobson <linux@thehobsons.co.uk>
Cc: 6man@ietf.org
References: <CAPTMOtLOHDPvA3Tfky79idNS7CMZctsUCB4M8hB0urSU9u2JQQ@mail.gmail.com>
<46BD2180-BCC7-4D38-BF43-F913251357F5@kaloom.com>
<CAPTMOt+BRCGZR9XQmZXTrN9j3-YA-voyUsOEXRv=TDR4ozGMiw@mail.gmail.com>
<563D8720-F79C-4A41-9DED-C50BAADC5A4B@thehobsons.co.uk>
<8A5CCAFA-6650-42E7-975C-E1D250C12E48@comcast.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <89cc2e88-bafe-c4ad-11e0-631187048507@gmail.com>
Date: Sun, 28 Jul 2019 09:56:30 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101
Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <8A5CCAFA-6650-42E7-975C-E1D250C12E48@comcast.net>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6fwxvFZMH-IOn52Qtzk4fe92DIs>
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: Sat, 27 Jul 2019 21:56:34 -0000
On 28-Jul-19 09:34, John Day wrote:
> All of this talk of backward compatibility is pretty rich, considering the strong backward compatibility between IPv4 and IPv6.
To be clear, backward compatibility in the strict sense was *never* a goal for IPng, because of the lack of address extensibility in RFC791. The goal was co-existence from the start, which led inevitably to the dual-stack model and to one form or other of NAT64.
Deploying IPv6 to the point where by some measurements it exceeds 25% of traffic has taken 25 years. So I don't think anybody will be investing in another such effort any time soon.
Brian
>
>
> John
>
>> On Jul 27, 2019, at 17:26, Simon Hobson <linux@thehobsons.co.uk> wrote:
>>
>> shyam bandyopadhyay <shyamb66@gmail.com> wrote:
>>
>>> I am thankful to you because you are the only one who came up
>>> with all the queries earlier. I am attaching a text version of the mail that I
>>> had sent which contains answers to your questions (in case
>>> you failed to open the attachment that I had already sent).
>>
>> All you have come up with in that text is "most of that can be done in 64 bits" - but you haven't stated any case for WHY only 64 bits would be significantly better. There are few (and getting fewer) systems/situations where the extra bits needed for storage and transmission are going to be a significant issue - and many systems where it could be an issue (deep space probes ?) tend to use custom protocols anyway. What's more, the case for the change would have to be very VERY compelling given that we've now had a couple of decades of design, development, and implementations of IPv6 protocols using 128 bit addresses.
>> To change it now would be VERY problematic - a 64bit version would be incompatible with what's already been implemented by hundred or thousands of vendors across thousands or even millions of networks. So there would be all the problems that are being discussed & solved in migrating from IPv4 to IPv6 without a "global big bang day" - but (AFAICS) really no compelling case for making the change at all. You'd effectively be saying "lets forget about that 128bit IPv6 everyone has been working on, and do an IPv8 instead with only 64 bit addresses" !
>>
>> I think you need to realise that this train left the station a couple of decades ago (that's when address length was discussed and decided upon), and its' not coming back,
>>
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
- Re: [105attendees] Why do we need to go for 128 b… Suresh Krishnan
- Re: [105attendees] Why do we need to go for 128 b… JORDI PALET MARTINEZ
- Re: [105attendees] Why do we need to go for 128 b… shyam bandyopadhyay
- Re: [105attendees] Why do we need to go for 128 b… Ted Lemon
- Re: [105attendees] Why do we need to go for 128 b… Simon Hobson
- Re: [105attendees] Why do we need to go for 128 b… John Day
- Re: [105attendees] Why do we need to go for 128 b… Brian E Carpenter
- Re: [105attendees] Why do we need to go for 128 b… Fred Baker
- Re: [105attendees] Why do we need to go for 128 b… Mark Smith
- Re: [105attendees] Why do we need to go for 128 b… Gyan Mishra
- Re: [105attendees] Why do we need to go for 128 b… Alexandre Petrescu