Mailing List Archive

Re: SixXS shutting down 2017-06-06
Hi,

On 23 Mar 2017, at 15:25, Pim van Pelt <pim@ipng.nl<mailto:pim@ipng.nl>> wrote:


On Thu, Mar 23, 2017 at 4:19 PM, Thomas Schäfer <thomas@cis.uni-muenchen.de<mailto:thomas@cis.uni-muenchen.de>> wrote:
https://www.root.cz/clanky/sixxs-vypne-ipv6-tunely-sluzby-ukonci-6-cervna/

The article sums it up quite well, and the author understood I think the rationale quite well. I've asked them to change the link at the top of their article from a WIP document that I had sent to the SixXS admin community this week, and instead point folks at https://www.sixxs.net/sunset/ which contains the rationale (also in Josh' forward upthread).

Obviously many users will be asking questions, or simply saying thanks over the next few days. I intend to engage with the IPv6 community next week, although my thoughts are kind of wrapped up in the sunset rationale here. Do let me know if you have thoughts or further discussion points. Would be happy to collate them from *NOG, ipv6-* and publish those as well.

I think SiXXS and tunnel broker.net<http://broker.net> have both been excellent services over the (many) years, and certainly good value for money for the users :) Many thanks for providing it!

I understand the rationale. I’ve generally been a tunnelbroker.net<http://tunnelbroker.net> guy, but now rarely use it as I’m finding IPv6 more widely available, and have had it natively at home in the UK for a few years now. I think your observation of "SixXS is no longer able to contribute to the solution, and is hampering its own goals of facilitating the migration of consumers to native IPv6” rings true.

All the best Pim (and Jeroen!)

Tim
Re: SixXS shutting down 2017-06-06 [ In reply to ]
Hi,

On Thu, Mar 23, 2017 at 03:38:58PM +0000, Tim Chown wrote:
> I think SiXXS and tunnel broker.net<http://broker.net> have both been excellent services over the (many) years, and certainly good value for money for the users :) Many thanks for providing it!
>
> I understand the rationale. I???ve generally been a tunnelbroker.net<http://tunnelbroker.net> guy, but now rarely use it as I???m finding IPv6 more widely available, and have had it natively at home in the UK for a few years now. I think your observation of "SixXS is no longer able to contribute to the solution, and is hampering its own goals of facilitating the migration of consumers to native IPv6??? rings true.
>
> All the best Pim (and Jeroen!)

What Tim said. Thanks, sixxs folks.

Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?

SpaceNet AG Vorstand: Sebastian v. Bomhard
Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann
D-80807 Muenchen HRB: 136055 (AG Muenchen)
Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279
Re: SixXS shutting down 2017-06-06 [ In reply to ]
* Pim van Pelt

> Our webservers aren't going anywhere, but it may take a little while
> to piece out the ULA bits from the other database activity we have,
> and it's my intention to destroy the PII (ie the database) after the
> sunset. I'll make a note of coming back to this after the dust
> settles.

Regardless of what will happen to the ULA registry, I presume that all
the personal data you've gathered during the years of SixXS operation
(whois database, user accounts, backups of those, etc etc etc) will be
deleted?

(IANAL, but it'd surprise me if anything else would conform to the
various data protection laws and regulations in most civilised
countries.)

In any case, many thanks for your contribution to IPv6 deployment!

Tore - inactive SixXS user
Re: SixXS shutting down 2017-06-06 [ In reply to ]
On 2017-03-23 17:07, Tore Anderson wrote:
> * Pim van Pelt
>
>> Our webservers aren't going anywhere, but it may take a little while
>> to piece out the ULA bits from the other database activity we have,
>> and it's my intention to destroy the PII (ie the database) after the
>> sunset. I'll make a note of coming back to this after the dust
>> settles.
>
> Regardless of what will happen to the ULA registry, I presume that all
> the personal data you've gathered during the years of SixXS operation
> (whois database, user accounts, backups of those, etc etc etc) will be
> deleted?
>
> (IANAL, but it'd surprise me if anything else would conform to the
> various data protection laws and regulations in most civilised
> countries.)

See FAQ of https://www.sixxs.net/sunset/ that answers the question.

We are quite responsible :)

Greets,
Jeroen
Re: SixXS shutting down 2017-06-06 [ In reply to ]
On 3/23/17 12:24 PM, Jeroen Massar wrote:

> See FAQ of https://www.sixxs.net/sunset/ that answers the question.
>
> We are quite responsible :)

But can I trade in my 1,480 ISK for karma or other goods?

Thanks for the work you guys have done, RIP SixXS.

AlanC
Re: SixXS shutting down 2017-06-06 [ In reply to ]
On 2017-03-23 18:28, David Farmer wrote:
>
>
> On Thu, Mar 23, 2017 at 10:46 AM, Brian E Carpenter
> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote
>
>
> One detail not mentioned in the /sunset page. Will you leave the
> ULA tool and registry in place (https://www.sixxs.net/tools/grh/ula/
> <https://www.sixxs.net/tools/grh/ula/>) ?
> I believe some people like that.
>
> Brian
>
>
> I'd be interested in some data on the use of the ULA tool and registry,
> I'd especially be interested in use over time. Is use of the ULA
> registry increasing or decreasing over the last few years?

That is an easy question to answer:

$ SELECT YEAR(ula_date) AS Year, COUNT(*) AS Count FROM grh_ulas GROUP
BY YEAR(ula_date);
+------+-------+
| Year | Count |
+------+-------+
| 2007 | 63 |
| 2008 | 140 |
| 2009 | 321 |
| 2010 | 611 |
| 2011 | 835 |
| 2012 | 742 |
| 2013 | 724 |
| 2014 | 1096 |
| 2015 | 1303 |
| 2016 | 640 |
| 2017 | 143 |
+------+-------+
11 rows in set (0.00 sec)

I would say that it is going down if we look at that count ;)

> Basically,
> is there an argument for further or new work within the IPv6 community
> on this front?

>From my POV not really. It is extremely simple to get a prefix from one
of the RIRs. Yes, it costs some money, which is something that should be
addressed IMHO. (routing gear etc costs money too though).

Also, more importantly, ULA is random per definition, and the chance of
collisions is extremely low. (unless one does not use randomness).

> Or, should this service just be sustained as-is, maybe
> finding a new home or new support over the long-term? Or, should this
> service also be sunset, maybe not on the same timeframe as the other
> SixXS services?
>
> Personally, if anything, I like to see some new work here, but I'd like
> to drive what that is or should be with some data.

Like with many things, I first would ask: what are the
requirements/usecases/etc.

> Finally, many thanks to SixXS for their years of service to the IPv6
> community! And, kudos for planning an orderly sunset, rather than
> decaying into oblivion.

We have been warning people since December 2015. Hopefully since then
they actually called their ISP or changed to ones that support IPv6.

Greets,
Jeroen
Re: SixXS shutting down 2017-06-06 [ In reply to ]
Below...

On 24/03/2017 06:39, Jeroen Massar wrote:
> On 2017-03-23 18:28, David Farmer wrote:
>>
>>
>> On Thu, Mar 23, 2017 at 10:46 AM, Brian E Carpenter
>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> wrote
>>
>>
>> One detail not mentioned in the /sunset page. Will you leave the
>> ULA tool and registry in place (https://www.sixxs.net/tools/grh/ula/
>> <https://www.sixxs.net/tools/grh/ula/>) ?
>> I believe some people like that.
>>
>> Brian
>>
>>
>> I'd be interested in some data on the use of the ULA tool and registry,
>> I'd especially be interested in use over time. Is use of the ULA
>> registry increasing or decreasing over the last few years?
>
> That is an easy question to answer:
>
> $ SELECT YEAR(ula_date) AS Year, COUNT(*) AS Count FROM grh_ulas GROUP
> BY YEAR(ula_date);
> +------+-------+
> | Year | Count |
> +------+-------+
> | 2007 | 63 |
> | 2008 | 140 |
> | 2009 | 321 |
> | 2010 | 611 |
> | 2011 | 835 |
> | 2012 | 742 |
> | 2013 | 724 |
> | 2014 | 1096 |
> | 2015 | 1303 |
> | 2016 | 640 |
> | 2017 | 143 |
> +------+-------+
> 11 rows in set (0.00 sec)
>
> I would say that it is going down if we look at that count ;)
>
>> Basically,
>> is there an argument for further or new work within the IPv6 community
>> on this front?
>
>>From my POV not really. It is extremely simple to get a prefix from one
> of the RIRs. Yes, it costs some money, which is something that should be
> addressed IMHO. (routing gear etc costs money too though).
>
> Also, more importantly, ULA is random per definition, and the chance of
> collisions is extremely low. (unless one does not use randomness).

I agree. I have never thought that ULA registration was useful. But
apparently some people were worried enough about collisions to use
the registry. In any case the little tool to generate a ULA prefix
is of value, so I hope you can leave that available.

Brian

>
>> Or, should this service just be sustained as-is, maybe
>> finding a new home or new support over the long-term? Or, should this
>> service also be sunset, maybe not on the same timeframe as the other
>> SixXS services?
>>
>> Personally, if anything, I like to see some new work here, but I'd like
>> to drive what that is or should be with some data.
>
> Like with many things, I first would ask: what are the
> requirements/usecases/etc.
>
>> Finally, many thanks to SixXS for their years of service to the IPv6
>> community! And, kudos for planning an orderly sunset, rather than
>> decaying into oblivion.
>
> We have been warning people since December 2015. Hopefully since then
> they actually called their ISP or changed to ones that support IPv6.
>
> Greets,
> Jeroen
>
>
>
Re: SixXS shutting down 2017-06-06 [ In reply to ]
>
> But can I trade in my 1,480 ISK for karma or other goods?
>
> Thanks for the work you guys have done, RIP SixXS.
>
> AlanC
>

Trade for bitcoins I thought it was?


Seriously, thanks for all the years of hard work guys. All the best.

Cheers,

Dunc