Re: “DHCPv6, SLAAC, Static Day X - 17 year interoperability issue” 2nd issue

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 10 November 2020 21:30 UTC

Return-Path: <alexandre.petrescu@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 026503A1047; Tue, 10 Nov 2020 13:30:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.67
X-Spam-Level:
X-Spam-Status: No, score=0.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 aGJ52PKskHrd; Tue, 10 Nov 2020 13:30:44 -0800 (PST)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (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 699123A104A; Tue, 10 Nov 2020 13:30:28 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AALUJC9018420; Tue, 10 Nov 2020 22:30:19 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id A715420A6E7; Tue, 10 Nov 2020 22:30:19 +0100 (CET)
Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8C39B205422; Tue, 10 Nov 2020 22:30:19 +0100 (CET)
Received: from [10.11.240.142] ([10.11.240.142]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0AALUIoG010205; Tue, 10 Nov 2020 22:30:18 +0100
Subject: Re: “DHCPv6, SLAAC, Static Day X - 17 year interoperability issue” 2nd issue
To: Gyan Mishra <hayabusagsm@gmail.com>, draft-mishra-6man-variable-slaac@ietf.org, 6man WG <ipv6@ietf.org>, Dusan Mudric <dmudric@avaya.com>, Naveen Kottapalli <naveen.sarma@gmail.com>, Dmytro Shytyi <dmytro@shytyi.net>, Ole Troan <otroan@employees.org>, Bob Hinden <bob.hinden@gmail.com>
References: <3A94E3B6-EA5A-453A-8CB1-C11BBDF88B53@gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b8ef1bb9-b258-82d4-5aec-e7973d2ad633@gmail.com>
Date: Tue, 10 Nov 2020 22:30:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.2
MIME-Version: 1.0
In-Reply-To: <3A94E3B6-EA5A-453A-8CB1-C11BBDF88B53@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8fi61JYL8nHN4V9p7OfhXO_dlT4>
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: Tue, 10 Nov 2020 21:30:46 -0000

Le 10/11/2020 à 01:35, Gyan Mishra a écrit :
> https://www.ripe.net/publications/docs/ripe-690#4-2-4--considerations-for-cellular-operators 
> <https://www.ripe.net/publications/docs/ripe-690#4-2-4--considerations-for-cellular-operators>
> 
> 
>         4.2.4. Considerations for Cellular Operators
> 
> There is a clear exception to the rule described above when assigning 
> prefixes in a cellular network. In this case, a /64 will need to be 
> provided for each PDP context for cellular phones, whereas for LTE 
> modems/routers, i.e. in the case of broadband by means of cellular 
> access, it will still be necessary to choose a /48 or /56 in accordance 
> with the aforementioned considerations.

This is a very valid point.

That RIPE document states clearly that "a /64 will need to be
provided for each PDP context for cellular phones".

This a big issue I was not even aware of.  If someone reads that text 
then one can no longer claim that RIPE recommends non-/64s to end users 
of cellular networks.  On the contrary, RIPE recommends /64s to end 
users of cellular networks.

I wonder where was this burried up to now that we I not see it.

Or maybe it is only me who did not see it, sorry then.

Alex

> 
>