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 ]

Dave Taht dave.taht at gmail.com
Mon Oct 7 18:37:04 CEST 2019

On Mon, Oct 7, 2019 at 9:23 AM <bob.sleigh at bt.com> wrote:
>
> Congratulations on your contribution to success Dave!
>
> Regards
>
> Bob
>
> Sent from my local coffee shop - using my EE Mobile over native IPv6

Yea! thank you! That cheers me up a lot. I hadn't found a single coffee shop yet
that had it. But my request was that someone go to their local coffee
shop and *make* it work when it didn't
already.

Care to go for 2/2? Test for bufferbloat via dslreports.com and/or
flent's rrul test?

> -----Original Message-----
> From: ipv6-wg <ipv6-wg-bounces at ripe.net> On Behalf Of Dave Taht
> Sent: 07 October 2019 17:04
> To: Bjoern Buerger <b.buerger at penguin.de>
> Cc: ipv6-wg at ripe.net IPv6 <ipv6-wg at ripe.net>
> Subject: Re: [ipv6-wg] Have we failed as IPv6 Working Group?
>
> 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.
>


-- 

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740

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 ]