Re: [ipv6-wg] Clear Guidance for Enterprises

2023-05-31 Thread Alexander Koeppe via ipv6-wg
Hi

> The civil servants were concerned that adding an IPv6 requirement would 
> further reduce competition and make managing cost more difficult.

And this is - in my opinion -  just a reflection of the typical 
counter-argument coming from these IT consultants being reluctant getting their 
hands dirty with IPv6 and postulate "why should I need IPv6, everything works 
with IPv4 though".


Alexander Koeppe




This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, you 
must not copy this message or attachment or disclose the contents to any other 
person. If you have received this transmission in error, please notify the 
sender immediately and delete the message and any attachment from your system. 
Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept 
liability for any omissions or errors in this message which may arise as a 
result of E-Mail-transmission or for damages resulting from any unauthorized 
changes of the content of this message and any attachment thereto. Merck KGaA, 
Darmstadt, Germany and any of its subsidiaries do not guarantee that this 
message is free of viruses and does not accept liability for any damages caused 
by any virus transmitted therewith.



Click 
merckgroup.com/disclaimer<https://www.merckgroup.com/en/legal-disclaimer/mail-disclaimer.html>
 to access the German, French, Spanish, Portuguese, Turkish, Polish and Slovak 
versions of this disclaimer.



Please find our Privacy Statement information by clicking here: 
merckgroup.com/privacy-statements-by-location<https://www.merckgroup.com/en/privacy-statement/privacy-statements-by-location.html>

-- 

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


Re: [ipv6-wg] Clear Guidance for Enterprises

2023-05-31 Thread Alexander Koeppe via ipv6-wg
Hi Wilhelm

Me being a network engineer in an enterprise and an IPv6 enthusiast can say, 
that it even fails within the IT.
Many IT workers, from server administrators over network consultants to 
application / solution designers still ignore IPv6 as an avoidable burden.

Every time I talk vendor for a new product, they wince when I ask for IPv6 
support - even today. And IPv6 support doesn't mean that all aspects are 
covered.
Even in the space of network vendors, you feel the difference of maturity for 
IPv6 related support compared to the IPv4 related aspects of the solution when 
you try to thoroughly set it up for IPv6.
The same goes on when going towards application space.

With these constraints it's hard to encourage our own IT folks to just roll it 
out.

>From my opinion, without companies being forced from top-down with a language 
>managers understand (money or complaints), the move to IPv6 will remain at the 
>micro-steps enthusiasts like me can afford and support.

Alexander Koeppe




This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, you 
must not copy this message or attachment or disclose the contents to any other 
person. If you have received this transmission in error, please notify the 
sender immediately and delete the message and any attachment from your system. 
Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept 
liability for any omissions or errors in this message which may arise as a 
result of E-Mail-transmission or for damages resulting from any unauthorized 
changes of the content of this message and any attachment thereto. Merck KGaA, 
Darmstadt, Germany and any of its subsidiaries do not guarantee that this 
message is free of viruses and does not accept liability for any damages caused 
by any virus transmitted therewith.



Click 
merckgroup.com/disclaimer<https://www.merckgroup.com/en/legal-disclaimer/mail-disclaimer.html>
 to access the German, French, Spanish, Portuguese, Turkish, Polish and Slovak 
versions of this disclaimer.



Please find our Privacy Statement information by clicking here: 
merckgroup.com/privacy-statements-by-location<https://www.merckgroup.com/en/privacy-statement/privacy-statements-by-location.html>

-- 

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


Re: [ipv6-wg] Have we failed as IPv6 Working Group?

2019-10-05 Thread Alexander Koeppe

> Am 04.10.2019 um 08:56 schrieb Carlos Friaças via ipv6-wg :
>
> Some years ago i also did a local test by removing the IPv4 address from my 
> laptop to see if i could bear with a full day of work without it. I couldn't. 
> After two hours i placed it back, but at the time i already had a list of 
> "things to fix", with stuff which was only accessible by IPv4. If you have 
> the time, i recommend you to do it. It's also a way of advancing IPv6 
> deployment, if you have the time/patience.

Same thing I’ve also tried several weeks ago
The problem comes when trying to fix issues outside your reach.

For example: try to access Github.
Even Cisco Website. Try to login. The intermediate step of the Pingfed solution 
doing the SSO login is IPv4-only.

This is very frustrating. The biggest network vendor isn’t fully reachable via 
IPv6-only.

 - Alex


This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, you 
must not copy this message or attachment or disclose the contents to any other 
person. If you have received this transmission in error, please notify the 
sender immediately and delete the message and any attachment from your system. 
Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept 
liability for any omissions or errors in this message which may arise as a 
result of E-Mail-transmission or for damages resulting from any unauthorized 
changes of the content of this message and any attachment thereto. Merck KGaA, 
Darmstadt, Germany and any of its subsidiaries do not guarantee that this 
message is free of viruses and does not accept liability for any damages caused 
by any virus transmitted therewith.



Click http://www.merckgroup.com/disclaimer to access the German, French, 
Spanish and Portuguese versions of this disclaimer.


Re: [ipv6-wg] Disband IPv6 WG

2019-10-04 Thread Alexander Koeppe


Am 04.10.2019 um 00:22 schrieb Kai 'wusel' Siering 
mailto:wusel...@uu.org>>:


So, why not make ripe.net v6-only by 2020-01-01, as RIPE NCC's 
IPv4 pool will have run dry by then anyway?



I like this idea.



This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, you 
must not copy this message or attachment or disclose the contents to any other 
person. If you have received this transmission in error, please notify the 
sender immediately and delete the message and any attachment from your system. 
Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept 
liability for any omissions or errors in this message which may arise as a 
result of E-Mail-transmission or for damages resulting from any unauthorized 
changes of the content of this message and any attachment thereto. Merck KGaA, 
Darmstadt, Germany and any of its subsidiaries do not guarantee that this 
message is free of viruses and does not accept liability for any damages caused 
by any virus transmitted therewith.



Click http://www.merckgroup.com/disclaimer to access the German, French, 
Spanish and Portuguese versions of this disclaimer.