nanog mailing list archives
Re: IPv6 woes - RFC
From: JORDI PALET MARTINEZ via NANOG <nanog () nanog org>
Date: Mon, 06 Sep 2021 09:45:16 +0200
All this is resolved using IPv6-only and IPv4aaS, the same way as cellular providers are doing with 464XLAT.
This means you don't need to invest in more IPv4 addressses (at some point you can even transfer some of them to the
laggers), you still provide IPv4 service to the edge, but the access is IPv4-ignorant.
Reduced Capex and Opex in general.
El 6/9/21 9:29, "NANOG en nombre de Saku Ytti" <nanog-bounces+jordi.palet=consulintel.es () nanog org en nombre de
saku () ytti fi> escribió:
On Mon, 6 Sept 2021 at 10:20, Bjørn Mork <bjorn () mork no> wrote:
> Adding new access infrastructure of any sort (Fixed Wireless is the
> hype...)? Why would you want to continue being stupid even if you
> implemented dual-stack for all your fibre, hfc and dsl customers? You
> can save a lot by dropping dual-stack complexities in PGWs and FWA CPEs,
> even if we assume most of the fibre/hfc/dsl value chain is reused.
Can you? You need to offer IPv4 anyhow and all the complexities
related to that, i.e. some stateful box. Why would I offer in addition
to that IPv6, which is not being requested by anyone. And by anyone I
mean anyone I want as customer, as those who request it, are probably
going to be expensive to support and I need to subsidise those with my
regular customers, so I'd rather not cater to those.
--
++ytti
**********************************************
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.
Current thread:
- Re: IPv6 woes - RFC, (continued)
- Re: IPv6 woes - RFC Mark Tinka (Sep 05)
- Re: IPv6 woes - RFC Saku Ytti (Sep 05)
- Re: IPv6 woes - RFC Xavier Beaudouin via NANOG (Sep 05)
- Re: IPv6 woes - RFC Matt Palmer (Sep 06)
- Re: IPv6 woes - RFC Randy Bush (Sep 06)
- Re: IPv6 woes - RFC Mark Tinka (Sep 06)
- Re: IPv6 woes - RFC Owen DeLong via NANOG (Sep 07)
- Re: IPv6 woes - RFC Bjørn Mork (Sep 06)
- Re: IPv6 woes - RFC Saku Ytti (Sep 06)
- Re: IPv6 woes - RFC Bjørn Mork (Sep 06)
- Re: IPv6 woes - RFC JORDI PALET MARTINEZ via NANOG (Sep 06)
- Re: IPv6 woes - RFC Saku Ytti (Sep 06)
- Re: IPv6 woes - RFC JORDI PALET MARTINEZ via NANOG (Sep 06)
- Re: IPv6 woes - RFC Bjørn Mork (Sep 06)
- Re: IPv6 woes - RFC Niels Bakker (Sep 06)
- Re: IPv6 woes - RFC JORDI PALET MARTINEZ via NANOG (Sep 06)
- Re: IPv6 woes - RFC Bjørn Mork (Sep 06)
- Re: IPv6 woes - RFC JORDI PALET MARTINEZ via NANOG (Sep 06)
- Re: IPv6 woes - RFC Baldur Norddahl (Sep 06)
- Re: IPv6 woes - RFC Owen DeLong via NANOG (Sep 07)
- Re: IPv6 woes - RFC Saku Ytti (Sep 07)
