This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[ipv6-wg] Have we failed as IPv6 Working Group?
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Carlos Friaças
cfriacas at fccn.pt
Sun Oct 6 10:30:07 CEST 2019
Hi Alexander, All, Github is now owned by Microsoft. Someone from Microsoft reading this? Maybe Veronika from Microsoft and the UK IPv6 Council? Cisco: just saw a post from Eric Vyncke. :-)) Maybe the WG can grow the list of gaps, so they can (possibly?) start to be addressed...? Regards, Carlos On Sat, 5 Oct 2019, Alexander Koeppe wrote: > >> Am 04.10.2019 um 08:56 schrieb Carlos Friaças via ipv6-wg <ipv6-wg at 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. >
- Previous message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
- Next message (by thread): [ipv6-wg] Have we failed as IPv6 Working Group?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]