Re: Objection to draft-ietf-6man-rfc4291bis-07.txt

Alexandre Petrescu <alexandre.petrescu@gmail.com> Thu, 02 March 2017 19:15 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 0BC7D1295FF for <ipv6@ietfa.amsl.com>; Thu, 2 Mar 2017 11:15:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.353
X-Spam-Level:
X-Spam-Status: No, score=-5.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_SOFTFAIL=0.665] 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 n9ETrg9B4AgX for <ipv6@ietfa.amsl.com>; Thu, 2 Mar 2017 11:15:24 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 277061293EC for <ipv6@ietf.org>; Thu, 2 Mar 2017 11:15:23 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.15.2/8.15.2/CEAnet-Internet-out-2.4) with ESMTP id v22JFMhj029114 for <ipv6@ietf.org>; Thu, 2 Mar 2017 20:15:22 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 3A10620D2D3 for <ipv6@ietf.org>; Thu, 2 Mar 2017 20:15:22 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 305F020D2EA for <ipv6@ietf.org>; Thu, 2 Mar 2017 20:15:22 +0100 (CET)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v22JFLO2007415 for <ipv6@ietf.org>; Thu, 2 Mar 2017 20:15:22 +0100
Subject: Re: Objection to draft-ietf-6man-rfc4291bis-07.txt
To: ipv6@ietf.org
References: <20170223134026.GI5069@gir.theapt.org> <CAKD1Yr0wK8EiAbz39EZz-xZLtsSV2JROSzNECKtGo36Zc=RZ0Q@mail.gmail.com> <CAN-Dau2N-fv3o9o4807m_fbMktjC6hq28sMZhfECKg5cbb4g6Q@mail.gmail.com> <CAKD1Yr3tHm5x29w4L5KtKi7PqDHRxkPr6i9mJMtHLaPc2eM2GQ@mail.gmail.com> <20170302105206.15fc3886@echo.ms.redpill-linpro.com> <CAKD1Yr2AYaAQMuGZiKXYwKdgz1dzKs5fc5bm7hQjpuq3O_V8gQ@mail.gmail.com> <20170302121104.36ddda4e@echo.ms.redpill-linpro.com> <CAKD1Yr1cNihxMVHjY2j7mcCNU2TE0X6-0p2mDNCBVVUcUbU20Q@mail.gmail.com> <20170302153611.36506f85@envy> <CAKD1Yr1SbdE-i-oGhi2kEFBWTOi_-FzgVdMYkMWjCEtw0MRRMg@mail.gmail.com> <ee3b73b1-64fd-6fef-bc0a-53b325f0bcfd@gmail.com> <alpine.DEB.2.02.1703021902010.30226@uplift.swm.pp.se> <efe2504e-198c-36ce-c79f-be1886e5d031@gmail.com> <alpine.DEB.2.02.1703021929170.30226@uplift.swm.pp.se> <7338F75E-94D9-4330-99C5-C5A9D7B0A066@consulintel.es> <8c848dd1-ceab-887c-5348-2b1bd9920bfa@gmail.com> <367D5BA9-F588-4F2B-A783-2C8BAF9B27BF@consulintel.es>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <b6ff1b86-698c-0b8f-6a08-7d6bf8a33c8f@gmail.com>
Date: Thu, 2 Mar 2017 20:15:27 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <367D5BA9-F588-4F2B-A783-2C8BAF9B27BF@consulintel.es>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/KnSK0hR6iO6B7cdXi_I3LWJYIdM>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
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, 02 Mar 2017 19:15:26 -0000


Le 02/03/2017 à 20:06, JORDI PALET MARTINEZ a écrit :
> I guess because the lack of DHCPv6-PD support, as you already
> indicated?

But for deity's sake - DHCPv6-PD is available as open source... it's
common software.  Just download and install.  The IETF Specs suggest it,
and the 3GPP specs require it too.

There must be something else making these router equipment manufacturers
refraining from downloading and installing DHCPv6-PD.

> I think majority of the households and business customers get
> configured the CPE by means for DHCPv6-PD …

AFAIK my CPE at home does not use DHCPv6-PD, but something based on
IPv4, like 6rd.  I think it's something developped in-house at that
particular operator.

Alex

>
> Saludos, Jordi
>
>
> -----Mensaje original----- De: ipv6 <ipv6-bounces@ietf.org>; en
> nombre de Alexandre Petrescu <alexandre.petrescu@gmail.com>; Responder
> a: <alexandre.petrescu@gmail.com>; Fecha: jueves, 2 de marzo de 2017,
> 20:02 Para: <ipv6@ietf.org>; Asunto: Re: Objection to
> draft-ietf-6man-rfc4291bis-07.txt
>
>
>
> Le 02/03/2017 à 19:54, JORDI PALET MARTINEZ a écrit :
>> Actually, is not correct that most use /56 for residential.
>>
>>> From my last review of the survey, worldwide, 22% use /48, 35%
>>> use /56, but there is a lot of ISPs (33%) doing it wrong and
>>> using /64, which of course, we are explaining them that is
>>> wrong. 10% use “other” sizes.
>
> So how comes that households can get /56s but smartphones no?
>
> Really there must be something there hidden.
>
> Alex
>
>>
>> Full details at:
>>
>> https://labs.ripe.net/Members/jordipaletm/results-of-the-ipv6-deployment-survey
>
>>
>>
>
>> Saludos, Jordi
>>
>>
>> -----Mensaje original----- De: ipv6 <ipv6-bounces@ietf.org>; en
>> nombre de Mikael Abrahamsson <swmike@swm.pp.se>; Organización:
>> People's Front Against WWW Responder a: <swmike@swm.pp.se>; Fecha:
>> jueves, 2 de marzo de 2017, 19:33 Para: Alexandre Petrescu
>> <alexandre.petrescu@gmail.com>; CC: <ipv6@ietf.org>; Asunto: Re:
>> Objection to draft-ietf-6man-rfc4291bis-07.txt
>>
>> On Thu, 2 Mar 2017, Alexandre Petrescu wrote:
>>
>>> YEs yes, but how much of that /44 is covering the end-users and
>>> how much is reserved for interconnnections?
>>
>> Nothing. It's /44 to the GGSN/SPGW.
>>
>>> Ah great, but I guess few cellular operators (if any?) are LIRs.
>>>  Or maybe that's true and I didnt know.
>>
>> You don't know.
>>
>>> If all this were that simple and clearcut - there are enough /64s
>>> out there - then why operators only assign one per one end user?
>>
>> Because DHCPv6-PD hasn't been implemented in mobile networks yet
>> (that I know of). So that's all they can do per 3GPP standards.
>>
>> Residential rollouts, most use /56 per customer.
>>
>>> From the RIRs, you can without further justification get /48 per
>>>  "site",
>> so if you show up to RIR and you're LIR and you say "hello, I have
>> 40 million customers and I want to give each customer a /48" then
>> they'll give you a /22 most likely. You're perfectly within your
>> right as an operator to deploy /48 per customer per current RIR
>> rules that I am aware of.
>>
>> -- Mikael Abrahamsson    email: swmike@swm.pp.se
>>
>> --------------------------------------------------------------------
>
>>
>>
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>>
>>
>
>>
>>
>>
>>
>> ********************************************** IPv4 is over Are you
>> ready for the new Internet ? http://www.consulintel.es The IPv6
>> Company
>>
>> This electronic message contains information which may be
>> privileged or confidential. The information is intended to be for
>> the use of the individual(s) named above. If you are not the
>> intended recipient be aware that any disclosure, copying,
>> distribution or use of the contents of this information, including
>> attached files, is prohibited.
>>
>>
>>
>> --------------------------------------------------------------------
>
>>
>>
> IETF IPv6 working group mailing list ipv6@ietf.org Administrative
>> Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>
>>
>>
>
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>
>
>
> ********************************************** IPv4 is over Are you
> ready for the new Internet ? http://www.consulintel.es The IPv6
> Company
>
> This electronic message contains information which may be privileged
> or confidential. The information is intended to be for the use of
> the individual(s) named above. If you are not the intended recipient
> be aware that any disclosure, copying, distribution or use of the
> contents of this information, including attached files, is
> prohibited.
>
>
>
> --------------------------------------------------------------------
>  IETF IPv6 working group mailing list ipv6@ietf.org Administrative
> Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>