IPv6 was Re: www.irtf.org unreachable?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Carsten

https://www.akamai.com/uk/en/about/our-thinking/state-of-the-internet-report/state-of-the-internet-ipv6-adoption-visualization.jsp


claims that Australian adoption of IPv6 is at 15% - behind
even New Zealand. I suspect that's optimistic, given that
the measurements will be biased towards the core.

I am not expecting to receive plug and play IPv6
anytime soon.

But perhaps another World IPv6 Day will finally make
a difference!


regards

 
Lloyd Wood lloyd.wood@xxxxxxxxxxx http://about.me/lloydwood



________________________________
From: Carsten Bormann <cabo@xxxxxxx>
To: Lloyd Wood <lloyd.wood@xxxxxxxxxxx> 
Cc: IETF Discussion Mailing List <ietf@xxxxxxxx>
Sent: Saturday, 10 November 2018, 11:37
Subject: Re: www.irtf.org unreachable?



On Nov 10, 2018, at 06:35, Lloyd Wood <lloyd.wood=40yahoo.co.uk@xxxxxxxxxxxxxx> wrote:
[..]

> (over IPv4. Haven’t tried IPv6, which noone uses...)

If you cared to acquire more knowledge about this (e.g., [1].[2],[3]), you would be surprised.
(In this case, I am too lazy to find out whether www.irtf.org came via a stagecoach or via today’s IP.)

Grüße, Carsten

[1]: http://www.worldipv6launch.org/major-mobile-us-networks-pass-50-ipv6-threshold/
[2]: https://www.google.com/intl/en/ipv6/statistics.html#tab=ipv6-adoption
[3]: https://www.google.com/intl/en/ipv6/statistics.html#tab=per-country-ipv6-adoption


OBTW, $ curl -I www.irtf.org
HTTP/1.1 301 Moved Permanently
Date: Sat, 10 Nov 2018 00:23:23 GMT
Server: Apache
Strict-Transport-Security: max-age=16070400; includeSubDomains
Location: https://www.irtf.org/
Cache-Control: max-age=0
Expires: Sat, 10 Nov 2018 00:23:23 GMT
Content-Type: text/html; charset=iso-8859-1

So we do “have” it, but of course it redirects to https.

And then:

$ /usr/bin/curl -I https://www.irtf.org/
HTTP/1.1 301 Moved Permanently
Date: Sat, 10 Nov 2018 00:27:46 GMT
Server: Apache
Location: http://irtf.org/
Content-Type: text/html; charset=iso-8859-1

As it should be.  (Except that the copy of curl at hand doesn’t accept the cert chain, so I have to switch to another copy. Standard fare.)





[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux