On 30 May 2023, at 18:50, Michael Richardson <mcr+ietf@sandelman.ca> wrote:


Wilhelm Boeddinghaus <wilhelm@boeddinghaus.de> wrote:
We have often wondere why enterprises do not migrate to IPv6. One
possible answer is: They have no time and they lack knowledge. Many IT
departments don't have any spare time for reading RFCs.

They have no management mandate on spending their time on it.

From my understanding these IT departments don't need papers explaining
the many possibilites to choose from. They need very clear guidance and
examples.

It's true that they need clear guidance, but since one size does not fit all,
that doesn't help much.

I am looking for 3 to 4 people who would like to start working on this
with me.

I suggest in order to be successful, one really needs an iterative approach.
One needs to include actual IT departments, take their feedback, and iterate.


Hello, here is some work the Swedish Post and Telecom Authority have done. In Swedish but by Google Translate here.


I have deployed IPv6 or been involved in many municpalities and enterprise since many years and I may help you with a short guide.
My own reflections over the years is
- keep it simple
- Don’t build the most advanced, complex and handsome address plan 
- It isn’t a long project, often it’s about a few days to be done
- Always dual stack so the staff have some thing to refer or fall back to 
- Main problem isn’t the internal network, it’s broken IPv6 services outside where Happy Eyeball don’t help you


In some cases I have had training for the staff when we activate IPv6 in some segments. 

/Tobbe





--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
-= IPv6 IoT consulting =-                      *I*LIKE*TRAINS*



--

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