> Am 04.10.2019 um 08:56 schrieb Carlos Friaças via ipv6-wg <ipv6-wg@ripe.net>:
>
> 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.
