IETF Logo Mail Archive

Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt

Alexandre PETRESCU <alexandre.petrescu@cea.fr> Thu, 05 November 2020 20:38 UTC

Return-Path: <alexandre.petrescu@cea.fr>
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 3552F3A1A32; Thu, 5 Nov 2020 12:38:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.144
X-Spam-Level:
X-Spam-Status: No, score=-2.144 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.247, 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 5eUdH0LmApr2; Thu, 5 Nov 2020 12:38:18 -0800 (PST)
Received: from oxalide-smtp-out.extra.cea.fr (oxalide-smtp-out.extra.cea.fr [132.168.224.13]) (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 1ADF33A19D4; Thu, 5 Nov 2020 12:38:16 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A5KcDcY000907; Thu, 5 Nov 2020 21:38:13 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3747E209AE1; Thu, 5 Nov 2020 21:38:13 +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 24494209A85; Thu, 5 Nov 2020 21:38:13 +0100 (CET)
Received: from [10.11.242.214] ([10.11.242.214]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 0A5KcBga009549; Thu, 5 Nov 2020 21:38:12 +0100
Subject: Re: I-D Action: draft-mishra-6man-variable-slaac-01.txt
To: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Cc: draft-mishra-6man-variable-slaac@ietf.org
References: <160409741426.1448.16934303750885888002@ietfa.amsl.com> <3c1c3ab5-5726-b141-e7ed-618984bbbdb1@gmail.com> <CABNhwV1zoZpZNjb54rEys4+49H3vpebZW2g9JbO1_58eR+WnQg@mail.gmail.com> <CAKD1Yr0vvyQnTGRoSh4qa4He1gq5HXXRaKU3pVLtCtDUzcwL_w@mail.gmail.com> <CAD6AjGQPatbg5=OaMzxJXy5mGZai1bqLfg8f+9SUnfg=s1kADg@mail.gmail.com> <e55a9fbf-a93c-a96f-7991-f0c3aad8ce16@gmail.com> <CAD6AjGSTQjKQuY1+0DNm5NRgTRkWUQ=eRhnvyKCXvKc3Kvy9TQ@mail.gmail.com> <CAKD1Yr3h_Jypxx49-e-PUFvtX0y7DaXf-XvBgK4-oQAjEe8vvA@mail.gmail.com> <23631B74-1870-4F53-9CC1-F884505E61D8@gmail.com>
From: Alexandre PETRESCU <alexandre.petrescu@cea.fr>
Organization: CEA
Message-ID: <b9670467-b89b-27b4-4dbc-08c91fc7e74e@cea.fr>
Date: Thu, 05 Nov 2020 21:38:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0
MIME-Version: 1.0
In-Reply-To: <23631B74-1870-4F53-9CC1-F884505E61D8@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms030801080709040103060404"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6LGvuwcewpScLaAdKJQLMXw0zLU>
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: Thu, 05 Nov 2020 20:38:20 -0000


--
Alexandre Petrescu
alexandre.petrescu@cea.fr, tél 0169089223

Le 05/11/2020 à 19:28, Bob Hinden a écrit :
> Hi,
> 
>> Mobile providers have not deployed dhcp pd in the last 10 years.
>> 
>> As a mobile provider, my bet is the next 10 years may be no
>> better.
>> 
>> Yet, rfc 7278 is deployed in many places in mobile
>> 
> 
> If mobile providers have not implemented DHCP PD in the last 10
> years, why would anyone expect them to implement some new mechanism
> with the similar functionality.   It seems to me that they don’t want
> to support functionality like this.

If we run SLAAC-GUA with a plen 65 and IID 63 _behind_ the Mobile 
Router, not on its 3GPP interface, then the operator is not concerned by 
this solution.

In other words, the mobile operator could continue to do SLAAC-64, or 
DHCPv6-PD if it so wishes, and the 3GPP modem manufacturer continue to 
do 64 and block multicast.  But the SLAAC-65 and IID-63len on the 
Ethernet interface would allow to make that 'hotspot' work.

Alex

> 
> Bob
> 
>

v2.23.0 | Report a Bug | By Email