Re: [v6ops] IETF109:: IPv6-only adoption challenges and standardization requirements

Fernando Gont <fgont@si6networks.com> Mon, 30 November 2020 19:22 UTC

Return-Path: <fgont@si6networks.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 797813A109A for <v6ops@ietfa.amsl.com>; Mon, 30 Nov 2020 11:22:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-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 mAD2bq_yaeXj for <v6ops@ietfa.amsl.com>; Mon, 30 Nov 2020 11:22:44 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 56ED93A1084 for <v6ops@ietf.org>; Mon, 30 Nov 2020 11:22:36 -0800 (PST)
Received: from [IPv6:2800:810:464:8164:2a:4307:16da:8e67] (unknown [IPv6:2800:810:464:8164:2a:4307:16da:8e67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id C7E64283C5B; Mon, 30 Nov 2020 19:22:33 +0000 (UTC)
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>, v6ops@ietf.org
References: <DM6PR05MB634846E24826EF244B6AD4B8AEF50@DM6PR05MB6348.namprd05.prod.outlook.com> <38cb7e50-a44f-0fa8-dd70-8caa7846cb78@gmail.com>
From: Fernando Gont <fgont@si6networks.com>
Message-ID: <0c7c442e-a128-2ed4-4ef0-b1a56411990c@si6networks.com>
Date: Mon, 30 Nov 2020 15:54:03 -0300
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <38cb7e50-a44f-0fa8-dd70-8caa7846cb78@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/3ut_SLJhGt5HgxjchbxkhwF2hXk>
Subject: Re: [v6ops] IETF109:: IPv6-only adoption challenges and standardization requirements
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, 30 Nov 2020 19:22:47 -0000

On 30/11/20 14:47, Alexandre Petrescu wrote:
[....]
> 
> I wanted to get confirmation that is the way that it is?
> 
> UEs getting IPv6-only is a great step forward.
> 
> But the /64 prefix for an UE might be a relatively limiting aspect if 
> considering mobile hotspots.

That's already the case for e.g. many fixed-line (e.g. Cable) ISPs. 
e.g., I get a /64 from my ISP.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492