Re: [v6ops] Update of draft-vf-v6ops-ipv6-deployment and IPv4 exhaustion

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Tue, 23 February 2021 12:41 UTC

Return-Path: <prvs=1688bbaa92=jordi.palet@consulintel.es>
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 830D93A2AF6 for <v6ops@ietfa.amsl.com>; Tue, 23 Feb 2021 04:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es
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 U8aLD3heNZ6w for <v6ops@ietfa.amsl.com>; Tue, 23 Feb 2021 04:41:16 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) by ietfa.amsl.com (Postfix) with ESMTP id B8C8E3A2ADC for <v6ops@ietf.org>; Tue, 23 Feb 2021 04:41:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1614084069; x=1614688869; i=jordi.palet@consulintel.es; q=dns/txt; h=User-Agent:Date: Subject:From:To:Message-ID:Thread-Topic:References:In-Reply-To: Mime-version:Content-type:Content-transfer-encoding; bh=G3W1mhcX FCvoiH+5btJfHZV+3ECYH16AwNDDN7rO1r0=; b=tMQmOgiqHZ8RkVgCW+5rNK4r paWDROQ0Mc3gm5kC6pT04WRiw05JBL+FsX7fZAIAgtZM7h+Qg194zxb0lRLPkMQl 1llPk9Pjmgww6anA0403qc+Bo+IMbdZjjZzn0qLv3T71FNX+MP/iZMQV5PQJyj2O rrYQHwkbdV67iKkL8kk=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Tue, 23 Feb 2021 13:41:09 +0100
X-Spam-Processed: mail.consulintel.es, Tue, 23 Feb 2021 13:41:08 +0100
Received: from [10.10.10.144] by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50000535239.msg for <v6ops@ietf.org>; Tue, 23 Feb 2021 13:41:08 +0100
X-MDRemoteIP: 2001:470:1f09:495:8cfd:f37c:544d:6d2b
X-MDHelo: [10.10.10.144]
X-MDArrival-Date: Tue, 23 Feb 2021 13:41:08 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=1688bbaa92=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/16.46.21021202
Date: Tue, 23 Feb 2021 13:41:05 +0100
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org" <v6ops@ietf.org>
Message-ID: <2CEF82A8-A2B7-4D1D-A41B-A2057596CE27@consulintel.es>
Thread-Topic: [v6ops] Update of draft-vf-v6ops-ipv6-deployment and IPv4 exhaustion
References: <d5835971a5bb429abf8cf740a824e67d@huawei.com> <26f11d42-c35c-bcc6-10a3-99b5b343f70d@gmail.com> <e9846f6259004a5d98a1eac1a61da3a1@huawei.com> <ab16a40c-2618-680f-1943-f3e03faec295@gmail.com>
In-Reply-To: <ab16a40c-2618-680f-1943-f3e03faec295@gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/j0gUvmgrwRqnEfhnKxXsHiu56Cg>
Subject: Re: [v6ops] Update of draft-vf-v6ops-ipv6-deployment and IPv4 exhaustion
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: Tue, 23 Feb 2021 12:41:25 -0000

Each RIR has its own policies, developed by the community. They are close, but not necessarily matching 100%.

In some case, you need to announce all them, or only a % of what you're using now, unless you can justify that they are being used in private networks, etc., etc. Policy can also mandate you announce it within a certain period of time.

Also remember that there is space not allocated by RIRs (legacy space), which is not necessarily subjected to those policies. Again, it depends on the region and if you have signed a contract with the relevant RIR.

Yes, private networks should use RFC1918 space, but sometimes even network 10/8 is not enough, or you can find other justifications, accepted by policies for allowing you not to announce the space.

Not so easy! Legacy space + 5 different set of policies and not all the RIRs ensuring 100% (and all the time) compliance with the policies.

Regards,
Jordi
@jordipalet
 
 

El 23/2/21 13:20, "v6ops en nombre de Alexandre Petrescu" <v6ops-bounces@ietf.org en nombre de alexandre.petrescu@gmail.com> escribió:



    Le 23/02/2021 à 11:24, Paolo Volpato a écrit :
    > Hi Alexandre,
    > 
    > It seems that those addresses were already allocated in the past but they are simply unadvertised.
    > As you mentioned, a possible reason for that is related to their use or transfer in the future.
    > Further pieces of information would be needed to have a better understanding.

    In that sense, maybe there is a rule at RIRs that mandate the ISPs that 
    received IPv4 blocks to actually use them right away?  Or are RIRs 
    allowing ISPs to not use the IP blocks immediately?

    Alex

    > 
    > BR
    > Paolo
    > 
    > -----Original Message-----
    > From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Alexandre Petrescu
    > Sent: Tuesday, February 23, 2021 10:43 AM
    > To: v6ops@ietf.org
    > Subject: Re: [v6ops] Update of draft-vf-v6ops-ipv6-deployment and IPv4 exhaustion
    > 
    > 
    > 
    > Le 22/02/2021 à 15:46, Paolo Volpato a écrit :
    >> Dear WG,
    >>
    >> We have just submitted a new version of draft-vf-v6ops-ipv6-deployment
    >> (https://datatracker.ietf.org/doc/draft-vf-v6ops-ipv6-deployment/
    >> <https://datatracker.ietf.org/doc/draft-vf-v6ops-ipv6-deployment/>),
    >> where we included more sections about IPv6 deployment.
    >>
    >> Specifically, we added considerations on IPv6 for enterprises,
    >> industrial Internet and cloud providers. We also updated the
    >> statistics on the use of IPv6, as of Dec 2020.
    >>
    >> There is also a new section, at the beginning of the draft, related to
    >> the exhaustion of the IPv4 address space, in this regard we used some
    >> of the references shared by Fred on this mailing list.
    >>
    >> While writing this section, we noticed that the total remaining IPv4
    >> address pool, as reported by the five RIRs at the end of 2020, has a
    >> bit more than 18 million addresses (either available or reserved).
    >> This data is summarized for example in
    >> https://www.potaroo.net/ispcol/2021-01/addr2020.html
    >> <https://www.potaroo.net/ispcol/2021-01/addr2020.html>.
    >>
    >> However, from the same article, it appears that the pool of
    >> unadvertised addresses has grown in the past few years. From 2018 to
    >> the end of 2020 this pool rose to around 50 /8s that were unadvertised
    >> in the public Internet.
    >>
    >> On the one hand this seems a good sign for IPv6 deployment. On the
    >> other, one may think that the IPv4 addresses are more than expected.
    >>
    >> This is a good point for discussion within the working group. Any
    >> opinion on this?
    > 
    > I would like to ask whether these unadvertised addresses are up for allocation by RIRs to operators?  Or is it just it has been observed that they are not advertised in the network?
    > 
    > Maybe these IPv4 addresses are not advertised in the network but are set apart by their owners for use at a later time?
    > 
    > Alex
    > 
    >>
    >> Comments and suggestions to the draft are always welcome.
    >>
    >> BR
    >>
    >> Paolo
    >>
    >> *Paolo Volpato***
    >>
    >> Senior IP Product Manager
    >>
    >> Europe Standardization & Industry Development Dept [2012 Labs]
    >>
    >> cid:image001.jpg@01D241B1.C3AC46F0
    >>
    >> ______________________________________________________________________
    >> ______
    >>
    >>
    >>
    > *Huawei Technologies Italia S.r.l.*
    >>
    >> Address: via Lorenteggio 240, Torre A, 20147 Milano Italy
    >>
    >> Mobile: +39 344 019 7606
    >>
    >> E-mail: paolo.volpato@huawei.com
    >>
    >> ______________________________________________________________________
    >> _______
    >>
    >>
    >>
    > Huawei Technologies Italia S.r.l. is a company registered in Italy
    >> at the Company Registration Office of Milan, with registered number
    >> 04501190963 and equity capital €3,000,000 fully paid up, whose
    >> registered office is in Milan, Via Lorenteggio 257, Tower B, 20152
    >> Milan. Huawei Technologies Italia S.r.l. is 100% owned by Huawei
    >> Technologies Cooperatief U.A
    >>
    >> ______________________________________________________________________
    >> _______
    >>
    >>
    >>
    > This e-mail and its attachments contain confidential information
    >> from HUAWEI, which is intended only for the person or entity whose
    >> address is listed above. Any use of the information contained herein
    >> in any way (including, but not limited to, total or partial
    >> disclosure, reproduction, or dissemination) by persons other than the
    >> intended recipient(s) is prohibited. If you receive this e-mail in
    >> error, please notify the sender by phone or email immediately and
    >> delete it!
    >>
    >> /---------------------------------------------------------------------
    >> ----------------------------------------------------------------------
    >> ----------------------------------------------------------------------
    >> -----------/
    >>
    >>
    >>
    > */PRIVACY NOTICE:/*/Pursuant to Art. 13 of Legislative Decree
    >> 196/03, so called "Data Protection Code", Huawei Technologies Italia
    >> Srl. informs you that the personal data provided by you will be
    >> treated for the acquisition of information preliminary to the
    >> conclusion of contracts, for the definition and formalization of
    >> contractual relationship with you as well as for their management and
    >> for the fulfillment of legal requirements related to civil, tax and
    >> accounting law. Data are processed both through computer or paper in a
    >> lawful and correct manner and in compliance with the Decree.
    >> Personal data and its processing are necessary for business
    >> negotiation and will not be subject to disclosure and spread out the
    >> circumstances permitted by law, on the same you can exercise your
    >> rights under art. 7 of the above mentioned decree. The Data Controller
    >> is Huawei Technologies Italia Srl, which has appointed Data
    >> Processors, the list of which is available at
    >> //dataprotection@huawei.com <mailto:dataprotection@huawei.com>//./
    >>
    >>
    >> _______________________________________________ v6ops mailing list
    >> v6ops@ietf.org https://www.ietf.org/mailman/listinfo/v6ops
    >>
    > 
    > _______________________________________________
    > v6ops mailing list
    > v6ops@ietf.org
    > https://www.ietf.org/mailman/listinfo/v6ops
    > 

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



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.theipv6company.com
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.