IETF Logo Mail Archive

Re: [v6ops] Implementation Status of PREF64

Vasilenko Eduard <vasilenko.eduard@huawei.com> Mon, 11 October 2021 08:43 UTC

Return-Path: <vasilenko.eduard@huawei.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 E39F53A0C0E for <v6ops@ietfa.amsl.com>; Mon, 11 Oct 2021 01:43:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 xAhR7cbNf3XK for <v6ops@ietfa.amsl.com>; Mon, 11 Oct 2021 01:43:13 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1CE63A0C42 for <v6ops@ietf.org>; Mon, 11 Oct 2021 01:43:11 -0700 (PDT)
Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HSXKX4D1Hz687t9 for <v6ops@ietf.org>; Mon, 11 Oct 2021 16:39:44 +0800 (CST)
Received: from mscpeml500002.china.huawei.com (7.188.26.138) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Mon, 11 Oct 2021 10:43:08 +0200
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml500002.china.huawei.com (7.188.26.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Mon, 11 Oct 2021 11:43:08 +0300
Received: from mscpeml500001.china.huawei.com ([7.188.26.142]) by mscpeml500001.china.huawei.com ([7.188.26.142]) with mapi id 15.01.2308.008; Mon, 11 Oct 2021 11:43:08 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: Philip Homburg <pch-v6ops-10@u-1.phicoh.com>, "v6ops@ietf.org" <v6ops@ietf.org>
CC: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
Thread-Topic: [v6ops] Implementation Status of PREF64
Thread-Index: AQHXsWiabe9xT98knEyNpn/SXFCzFauzkUkAgABK7ICAAEb8gIAACf0AgAH4SoCAAgvogIAAROwAgAA+dACAAPFksIAAN4ew///cF4CAADh0D///620AgAE/qoCAAEymgIAAQtEAgACFcMD//87gAAADB2KAAAEo1YAAAgTGgAAMC1mAABEnE4AAAOBpgAACvIEAAAREQQAAAJLtAAACLxgAAAE9/QABFvNJgAAZYOiAAAkzk4AAA/ImAAA43DOAAHM2kdAAGZflkA==
Date: Mon, 11 Oct 2021 08:43:08 +0000
Message-ID: <51f120916e6744e3b8b0713fd98fcf3b@huawei.com>
References: <DDA36020-90CC-471B-83AD-3D98950F1164@delong.com> <CAKD1Yr0T-7t-UHbsJBMLpTjKhPAV5uUQkux6oby89TVUue7PyA@mail.gmail.com> <CO1PR11MB4881D400EA4681F1505040D2D8AA9@CO1PR11MB4881.namprd11.prod.outlook.com> <CAKD1Yr3TmqFxjKuZ57wS7VuPOf6rJvOwnvnQdFrRLQ=DkZ+CCw@mail.gmail.com> <CO1PR11MB4881F411A4D5BEA7A8479726D8AA9@CO1PR11MB4881.namprd11.prod.outlook.com> <D8AEA194-293B-43E4-BCAE-33CD81FB7D8C@delong.com> <CAKD1Yr2Tug-PFV7wAh0s6-gw8W3LcLG7wC1fD7Lu_hMZQYKdtw@mail.gmail.com> <08D2885E-B824-48E8-9703-DCA98771FA37@delong.com> <CAKD1Yr2EVsY3tYUf56R0Q1+KVrowtqh-HgwXj5vxzy4wd-vkTg@mail.gmail.com> <1A6ED87B-666E-439C-852F-2E5C904C0515@delong.com> <CAKD1Yr23fY2DJDvB-9eVFRsxnBnZQ0kZuZfYUfRUHYW=_D=enA@mail.gmail.com> <CAN-Dau1z0q0R61x7iY+Wg_cFRU0jmqr+fR0y=bSXxj+K-n722w@mail.gmail.com> <CAKD1Yr1T_mXfxJGHOrBfqZfexm6GTrUqnFi57710pTroKQK6uQ@mail.gmail.com> <702CB018-1A02-4B32-B9AA-7C7B31521F12@delong.com> <CAKD1Yr0jZR8Efzr_Y6FeiBvHYS8ATmDupx2ABTXXy-rSA_QjmA@mail.gmail.com> <1adb70a8-db0a-4ea6-f7 21-c1035343cda3@foobar.org> <DM6PR02MB69249D4F0A8003E77EC9F153C3B19@DM6PR02MB6924.namprd02.prod.outlook.com> <CAN-Dau0q7p-9NWv=9vouX51Z1Yqe_h06WwpnkMjkyj6=A7EcQw@mail.gmail.com> <m1mZfPJ-0000IoC@stereo.hq.phicoh.net>
In-Reply-To: <m1mZfPJ-0000IoC@stereo.hq.phicoh.net>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.203.200]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CNb-L-eDIPYTyzvfst_uJJ-jyZQ>
Subject: Re: [v6ops] Implementation Status of PREF64
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 Oct 2021 08:43:18 -0000

+1
The discussion is strange for me too.
I could not imagine the motivation behind "many IP addresses".

Ed/
-----Original Message-----
From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Philip Homburg
Sent: Sunday, October 10, 2021 11:27 PM
To: v6ops@ietf.org
Cc: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
Subject: Re: [v6ops] Implementation Status of PREF64

>In an effort to find a compromise that allows Android to support DHCPv6 
>and therefore the managed-assignment addressing model, I'm suggesting 
>it is reasonable for DHCPv6 clients to require the availability of more 
>than one
>IPv6 address before it enables it's IPv6 stack, and it sounds like 
>Lorenzo is at least open to discuss such a comprise.

There is one thing I don't quite understand in this discussion. For a long time it seemed to be the position of Andoid devs that only SLAAC could support the number of addresses Android needs. DHCP IA_NA was not suitable.

Now we are having a discussion whether networks should for example support
64 addresses using IA_NA.

Android is not a new operating system with many unexpected features. 
Android 12 was released recently. I don't know for how long I have had android devices connect to my network using IPv6, but it is quite a few years.

In all that time, I never noticed the android device using more than one or two IPv6 addresses.

Now obviously I'm not pushing my phone enough that I don't see it using more than, say, 10 addresses. I'm a bit curious, what are those extra addresses for? Addresses that are so special, you need them immediately when connecting to the network.

The strange thing is, my laptop has quite a few IPv4 address. Each VM with a network in bridge mode gets its own address for the guest. Addresses get added when VMs get started. And expire as stopped VMs fail to renew leases.

Why is it that android is so special, it cannot dynamically request more addresses when it needs them?


_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email