Re: [ipv6-wg] contents of ipv6-wg Digest, Vol 135, Issue 10
Hi Wilhelm, all, I am also really interested in this topic, really suspect it’s not broken for the most enterprises so why invest into what’s a whole new re architecture, skills in-house may also not exist. expensive in people and technology and high risk migration. Gsma announced this year global IOT devices surpassed SIMs this year, both now at 2bn + so change is already coming from the networks. I would really like to contribute however I can, Clodagh.durkan@ucdconnect.ie or gmail above Best regards, Clodagh On Thu 15 Jun 2023 at 11:00, <ipv6-wg-request@ripe.net> wrote:
Send ipv6-wg mailing list submissions to ipv6-wg@ripe.net
To subscribe or unsubscribe via the World Wide Web, visit https://lists.ripe.net/mailman/listinfo/ipv6-wg or, via email, send a message with subject or body 'help' to ipv6-wg-request@ripe.net
You can reach the person managing the list at ipv6-wg-owner@ripe.net
When replying, please edit your Subject line so it is more specific than "Re: Contents of ipv6-wg digest..."
Today's Topics:
1. Re: Clear Guidance for Enterprises (Paolo Volpato)
----------------------------------------------------------------------
Message: 1 Date: Wed, 14 Jun 2023 16:08:22 +0000 From: Paolo Volpato <paolo.volpato@huawei.com> To: Wilhelm Boeddinghaus <wilhelm@boeddinghaus.de> Cc: "ipv6-wg@ripe.net" <ipv6-wg@ripe.net> Subject: Re: [ipv6-wg] Clear Guidance for Enterprises Message-ID: <2164ac90f1b34e908d39fe008217be7c@huawei.com> Content-Type: text/plain; charset="utf-8"
Hi Wilhelm, All,
I have noticed that some people would be happy to cooperate to your idea of a paper for IPv6 in enterprises (me included :-) Wonder if you have thought of any rough plan to start and organize the work.
Many thanks Paolo
-----Original Message----- From: Wilhelm Boeddinghaus <wilhelm@boeddinghaus.de> Sent: Thursday, June 1, 2023 4:20 PM To: Paolo Volpato <paolo.volpato@huawei.com> Cc: ipv6-wg@ripe.net Subject: Re: [ipv6-wg] Clear Guidance for Enterprises
Hi Paolo,
thanks for your help with this project.
Lack of budget is of course a problem. But if the IT departments could at least quantify the budget, this would help. If they have no idea how to start the project, a budget eastimation is not possible.
Best,
Wilhelm
Hi Wilhelm,
In addition, I would add that they also lack the budget to consider deploying IPv6, meaning that enterprises don't consider IPv6 as a priority. At least, this is what we found during the editing of RFC 9386 on IPv6 deployment status.
I would be happy to contribute to this effort.
Best regards Paolo
-----Original Message----- From: ipv6-wg <ipv6-wg-bounces@ripe.net> On Behalf Of Wilhelm Boeddinghaus Sent: Tuesday, May 30, 2023 6:06 PM To: ipv6-wg@ripe.net Subject: [ipv6-wg] Clear Guidance for Enterprises
Hi,
at the end of my talk during the RIPE86 IPv6 working group I promised to start work on a paper with clear guidance for enterprises to migrate their networks to IPv6.
We have often wondere why enterprises do not migrate to IPv6. One
Am 31.05.2023 um 08:42 schrieb Paolo Volpato via ipv6-wg: possible answer is: They have no time and they lack knowledge. Many IT departments don't have any spare time for reading RFCs.
From my understanding these IT departments don't need papers
explaining the many possibilites to choose from. They need very clear guidance and examples.
I am looking for 3 to 4 people who would like to start working on this
with me.
Peter Hessler contacted me during the meeting and he offered his help,
time and expertise for this project. Thank you, Peter.
Best,
Wilhelm
------------------------------
Subject: Digest Footer
--
To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://lists.ripe.net/mailman/listinfo/ipv6-wg
------------------------------
End of ipv6-wg Digest, Vol 135, Issue 10 ****************************************
Hi, On Mon, Jun 26, 2023 at 01:16:02PM +0100, Clodagh Durkan wrote:
I am also really interested in this topic, really suspect it???s not broken for the most enterprises so why invest into what???s a whole new re architecture, skills in-house may also not exist.
If you have ever looked at (large) enterprise IPv4 networks, you know that you do not need to "suspect". It's broken beyond any imagination, usually, with lots of internal NAT44, duplicate use of RFC1918 segments ("every kubernetes cluster has the same 10.x.0.0/16 subnet, because that's how automated deploymet works - and besides, it's the only /16 available out of 10/8!"). Going from there to IPv6 would bring immense benefits in the medium to long term - but in the short term, it's "extra work!" and "nobody has time!", and also "nobody cares, these are costs that people have become used to" (and that's the worst bit of all). Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Hi, Yup yup, l I was being generous, no use whinging about how every new architecture just grabbed easiest from what they googled, there’s a lot of new space and enterprises are looking for help. (At least some in the organisations who are looking at forecasting future projects) it’s a great opportunity to start renewed. Easiest may be to not agonise over how much legacy to bring forward and just start fresh and make the old have to update Imho RIPE, while I believe their position is they are not the enforcers for every implementor or and don’t fall subject to new eu critical infrastructure regulation as global, still hold a lot of advisory kudos in this space. Will be an interesting study / paper. Clodagh On Mon 26 Jun 2023 at 13:21, Gert Doering <gert@space.net> wrote:
Hi,
On Mon, Jun 26, 2023 at 01:16:02PM +0100, Clodagh Durkan wrote:
I am also really interested in this topic, really suspect it???s not broken for the most enterprises so why invest into what???s a whole new re architecture, skills in-house may also not exist.
If you have ever looked at (large) enterprise IPv4 networks, you know that you do not need to "suspect". It's broken beyond any imagination, usually, with lots of internal NAT44, duplicate use of RFC1918 segments ("every kubernetes cluster has the same 10.x.0.0/16 subnet, because that's how automated deploymet works - and besides, it's the only /16 available out of 10/8!").
Going from there to IPv6 would bring immense benefits in the medium to long term - but in the short term, it's "extra work!" and "nobody has time!", and also "nobody cares, these are costs that people have become used to" (and that's the worst bit of all).
Gert Doering -- NetMaster -- have you enabled IPv6 on something today...?
SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
participants (2)
-
Clodagh Durkan -
Gert Doering