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 ]
Job Snijders
job at instituut.net
Mon Oct 7 18:16:38 CEST 2019
Dear Dave, On Mon, Oct 7, 2019 at 4:04 PM Dave Taht <dave.taht at gmail.com> wrote: > If I can get *one* person in this working group to go down to their > local coffee shop and make ipv6 work by whatever means necessary (and > also fix their bufferbloat) - I'll consider my participation in this > thread a success. That may be how you measure success yourself, however I measure differently: I consider your input in this thread insightful and valuable, regardless of the coffee shop's connectivity. Influencing the connectivity of any public place (bar, coffee shop, or mall) who don't consider their internet access service their core business, can be really tricky. Any anecdotal data gleaned from that experience is just that, anecdotal. Kind regards, Job
- 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 ]