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] broken-v6only

Previous message (by thread): [ipv6-wg] broken-v6only
Next message (by thread): [ipv6-wg] Call for presentations for RIPE 83

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Olivier MJ Crépin-Leblond ocl at gih.com
Mon Oct 25 14:46:29 CEST 2021

At this point in time, in 2021, one wonders whether some of these 
"choices" are political. It's now been so many years, why would the 
vendors still have problems rolling out a v6 only version? Or are these 
specific case scenarios that *require* v4 as part of their DNA?
Kindest regards,

Olivier

On 23/10/2021 17:49, Jens Link wrote:
> Hi,
>
> just ran into this on twitter:
>
> https://github.com/buraglio/broken-v6only
>
> ---
> A running list of applications and processes that just do not work with
> the total absence of IPv4 on on a host. Contributions welcome and encouraged.
> ---
>
> Maybe the RIPE community can give more input.
>
> Jens
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/ipv6-wg/attachments/20211025/4c4cc27d/attachment.html>

Previous message (by thread): [ipv6-wg] broken-v6only
Next message (by thread): [ipv6-wg] Call for presentations for RIPE 83

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ ipv6-wg Archives ]