Jeroen Massar

As performed in France, what happens is that some copyright owner
contacts the ISP that IP address a.b.c.d had accessed/served copyright
infringing data at date/time dd-mm-yyyy HH:mm providing some kind of
detail on how they figured that out.

That report is a 'strike' and gets forwarded to the user.

If that then happens 6 times they are blocked.

The ISP as such does not do any content inspection.

It is though assumed that some ISPs simply count bytes and that they do
some investigation themselves when you reach a certain bandwidth
threshold (it seems to correlate that copyright infringers are
downloading a lot more than normal webbrowsing users...)

Greets,
Jeroen

Hi folks,

For quite a few folks here on the list travel is a common thing, going
into foreign wireless networks is too. Likely your laptop/tablet comes
with IPv6 enabled per default, it is 2012 after all almost going 2013.

And then you get to a silly hotspot and it does not work as the
connection fails (or you get the website you host on your laptop and go
'huh?' ;).

Thus you check and you see:
8<------------------------------------------------------------------------
$ dig securelogin.arubanetworks.com aaaa

; <<>> DiG 9.8.3-P1 <<>> securelogin.arubanetworks.com aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25608
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;securelogin.arubanetworks.com.    IN    AAAA

;; ANSWER SECTION:
securelogin.arubanetworks.com. 5 IN    AAAA    ::1

;; Query time: 19 msec
;; SERVER: 66.28.0.45#53(66.28.0.45)
;; WHEN: Tue Dec  4 10:12:33 2012
;; MSG SIZE  rcvd: 75
------------------------------------------------------------------------>8

I am fairly sure somebody technical and high enough up at Aruba knows
how to get this resolved, sooner or later... thus please do, it will
start hurting more and more people every day.

Oh, and btw, it has an A record too, but even though Happy Eyeballs
exists in a magical form inside OSX, ::1 is a very close route thus will
always win over the IPv4 address.

Of course, temp disabling IPv6 on the link is a way to circumvent it,
but heck, why is that DNS server publishing ::1 at all!?

Greets,
Jeroen

Japan and South Korea are doing quite well indeed and China has CERNET
of course which is doing mostly IPv6.

There are some ISPs in various other Asian countries doing IPv6, but I
guess indeed that they don't push that much traffic, but counting that
is hard to tell anyway.

Can you divulge some of these hurdles? Would be interesting to know what
they are running into.

Greets,
Jeroen