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

"Chengli (Cheng Li)" <chengli13@huawei.com> Fri, 16 August 2019 03:06 UTC

Return-Path: <chengli13@huawei.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 239F8120024; Thu, 15 Aug 2019 20:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 wqLObsP8IUvA; Thu, 15 Aug 2019 20:06:15 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF6E6120013; Thu, 15 Aug 2019 20:06:14 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 8C0C9F9A0E49D8A8E8E8; Fri, 16 Aug 2019 04:06:12 +0100 (IST)
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 16 Aug 2019 04:06:04 +0100
Received: from DGGEML529-MBX.china.huawei.com ([169.254.6.253]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0439.000; Fri, 16 Aug 2019 11:05:32 +0800
From: "Chengli (Cheng Li)" <chengli13@huawei.com>
To: Brian Carpenter <brian.e.carpenter@gmail.com>, Roland Bless <roland.bless@kit.edu>
CC: "irtf-discuss@irtf.org" <irtf-discuss@irtf.org>, "6man@ietf.org" <6man@ietf.org>, IETF discussion list <ietf@ietf.org>, shyam bandyopadhyay <shyamb66@gmail.com>
Subject: RE: [irtf-discuss] Why do we need to go with 128 bits address space ?
Thread-Topic: [irtf-discuss] Why do we need to go with 128 bits address space ?
Thread-Index: AQHVUzv6frkDxDV+nEGnx5o/vYJPz6b7aqoAgAARxICAAZQfEA==
Date: Fri, 16 Aug 2019 03:05:32 +0000
Message-ID: <C7C2E1C43D652C4E9E49FE7517C236CB02668EC5@dggeml529-mbx.china.huawei.com>
References: <CAPTMOt+cGhBqHmT3yZVChv-PCMqxT-WPDcDdM3RuTc1TMfFeVg@mail.gmail.com> <cd254463-43ba-2afd-5c3c-f462a74e5c30@kit.edu> <CANMZLAat4X+Eh+fgTrbikO6dusvcvvUr5foj=3OEnbRhQtOHSw@mail.gmail.com>
In-Reply-To: <CANMZLAat4X+Eh+fgTrbikO6dusvcvvUr5foj=3OEnbRhQtOHSw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.130.185.75]
Content-Type: multipart/alternative; boundary="_000_C7C2E1C43D652C4E9E49FE7517C236CB02668EC5dggeml529mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/lGNySAjJ8JKYRBJPXaR1I4oqslo>
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, 16 Aug 2019 03:06:16 -0000

Agree.

This topic should be discussed 25 years ago, when I was a baby, and it could be discussed 15 years ago when I was a middle school student. But it SHOULD NOT be discussed now when I am a fully grown adult.

No one will make an easy decision like yes, let’s go with 128 bits, I like the number 128, cause the last number is 8!

People made this decision under enough discussion, and many people might suggest 64 at that time, but why 128 won? What happened at that time 25 years ago is even not important. Cause we cannot change it.

From technology aspect, 64 isn’t enough for the future, and this future may be very close. We won’t like to update the entire internet again to 128 bits. Think about IPv6, more than 20 years. Also, as the development of hardware, this will not a burden.(I don’t think it is a burden even now)

From business aspect, people around the world have invested a lot of money (Zillion? ) on 128 bits IPv6 address based networking. What’s the benefit to give up this and develop a new network architecture based on 64 bit address?

From history aspect, we need a time machine.

BTW, thanks to the guys who provide cool ideas in 6Lo and 6man WG, learned a lot!

Best Regards,
Cheng



From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Brian Carpenter
Sent: Thursday, August 15, 2019 6:31 PM
To: Roland Bless <roland.bless@kit.edu>
Cc: irtf-discuss@irtf.org; 6man@ietf.org; IETF discussion list <ietf@ietf.org>; shyam bandyopadhyay <shyamb66@gmail.com>
Subject: Re: [irtf-discuss] Why do we need to go with 128 bits address space ?

e) 64 isn't enough to allow lots of bits for topology plus lots of bits for privacy
f) in any case we can compress the headers in low power, low bandwidth scenarios
g) it's 25 years too late for this discussion even if we were wrong
Regards
    Brian
    (via tiny screen & keyboard)

On Thu, 15 Aug 2019, 21:27 Roland Bless, <roland.bless@kit.edu<mailto:roland.bless@kit.edu>> wrote:
Hi,

a) the address space was designed of a lifetime of 50-100 years.
b) we see how hard it is to change the core protocol
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
d) there is no problem that needs to be solved here.

Regards
 Roland

On 15.08.19 at 09:33 shyam bandyopadhyay wrote:
> To:
> The Entire IETF community
>
>     Sub: Why do we need to go with 128 bits address space if
>          whatever is been trying to achieve with the existing
>          approach of IPv6, can be achieved by 64 bits address
>          space as well?
>