:48 PM
To: Tony Hain
Cc: joel jaeggli; valdis.kletni...@vt.edu; NANOG List
Subject: Re: NAT64 and matching identities
So one has to wonder how those names made it into the top 100 list if
it's supposed to be a top 100 web sites, since they are obviously not
web
sites.
(at least
Lee Howard wrote:
...
There is obviously a long tail of ip4 destinations, but nearly all
of 500 of the Alexa global 500 have ip6 listeners,
Do you have a data source for that? I see no indication of IPv6
listeners on 85% of the top sites.
A slightly different metric, 44% of USA
I question how one can have a top 100 website without an A record.
I am inclined to believe there is a bug in there somewhere.
Owen
On Nov 22, 2013, at 10:18 AM, Tony Hain alh-i...@tndh.net wrote:
Lee Howard wrote:
...
There is obviously a long tail of ip4 destinations, but nearly all
of
On Fri, 22 Nov 2013 10:18:27 -0800, Tony Hain said:
The top 100 websites: records and IPv6 connectivity
count with A: 98 ( 98.000%)
count with : 30 ( 30.000%)
Of the 30 hosts with records, testing connectivity to TCP/80:
count with IPv6
On 11/22/13, 12:01 PM, valdis.kletni...@vt.edu wrote:
On Fri, 22 Nov 2013 10:18:27 -0800, Tony Hain said:
The top 100 websites: records and IPv6 connectivity
count with A: 98 ( 98.000%)
count with : 30 ( 30.000%)
Of the 30 hosts with records,
It would be way more than 2 if it were CNAME, methinks.
Owen
On Nov 22, 2013, at 12:12 PM, joel jaeggli joe...@bogus.com wrote:
On 11/22/13, 12:01 PM, valdis.kletni...@vt.edu wrote:
On Fri, 22 Nov 2013 10:18:27 -0800, Tony Hain said:
The top 100 websites: records and IPv6 connectivity
-Original Message-
From: Owen DeLong [mailto:o...@delong.com]
Sent: Friday, November 22, 2013 12:16 PM
To: joel jaeggli
Cc: valdis.kletni...@vt.edu; Tony Hain; NANOG List
Subject: Re: NAT64 and matching identities
It would be way more than 2 if it were CNAME, methinks.
Owen
On Nov 22
-Original Message-
From: Owen DeLong [mailto:o...@delong.com]
Sent: Friday, November 22, 2013 12:16 PM
To: joel jaeggli
Cc: valdis.kletni...@vt.edu; Tony Hain; NANOG List
Subject: Re: NAT64 and matching identities
It would be way more than 2 if it were CNAME, methinks.
Owen
On Nov
; NANOG List
Subject: Re: NAT64 and matching identities
So one has to wonder how those names made it into the top 100 list if it's
supposed to be a top 100 web sites, since they are obviously not web
sites.
(at least in the case of the two in the top 100)
Owen
On Nov 22, 2013, at 1:28 PM
On Wed, Nov 20, 2013 at 1:30 PM, Gary E. Miller g...@rellim.com wrote:
Yo Lee!
On Wed, 20 Nov 2013 16:14:47 -0500
Lee Howard l...@asgard.org wrote:
There is obviously a long tail of ip4 destinations, but nearly all
of 500 of the Alexa global 500 have ip6 listeners,
Do you have a data
It was a stale DNS entry. Now fixed (modulo TTLs and such), thanks.
That said, your troubleshooting was troubleshooting a different
problem, not your browser's inability to retrieve the page. The way
the browser sends the request is something like this (note the HTTP
version and the host
Leaving out stuff . . .
On 11/19/13 6:53 PM, Ian Smith i.sm...@f5.com wrote:
There is obviously a long tail of ip4 destinations, but nearly all of 500
of the Alexa global 500 have ip6 listeners,
Do you have a data source for that? I see no indication of IPv6 listeners
on 85% of the top sites.
Yo Lee!
On Wed, 20 Nov 2013 16:14:47 -0500
Lee Howard l...@asgard.org wrote:
There is obviously a long tail of ip4 destinations, but nearly all
of 500 of the Alexa global 500 have ip6 listeners,
Do you have a data source for that? I see no indication of IPv6
listeners on 85% of the top
On 11/20/13 4:30 PM, Gary E. Miller g...@rellim.com wrote:
Yo Lee!
On Wed, 20 Nov 2013 16:14:47 -0500
Lee Howard l...@asgard.org wrote:
There is obviously a long tail of ip4 destinations, but nearly all
of 500 of the Alexa global 500 have ip6 listeners,
Do you have a data source for
On 11/18/13 3:06 PM, Justin M. Streiner strei...@cluebyfour.org wrote:
It's looking more and more like NAT64 will be in our future. One of the
valid concerns for NAT64 - much like NAT44 - is being able to determine
the identity of a given user through the NAT at a given point in time.
Bulk
On Mon, Nov 18, 2013 at 03:06:52PM -0500, Justin M. Streiner wrote:
Other IPv6 transition mechanisms appear to be no less thorny than
NAT64 for a variety of reasons.
Some of us who worked on the NAT64/DNS64 combination were content that
it was a long way from the perfect solution. The idea I
From: Justin M. Streiner [mailto:strei...@cluebyfour.org]
It's looking more and more like NAT64 will be in our future.
One of the valid concerns for NAT64 - much like NAT44 - is being
able to determine the identity of a given user through the NAT
at a given point in time.
How feasible this is
On Nov 19, 2013, at 8:36 AM, Andrew Sullivan asulli...@dyn.com wrote:
On Mon, Nov 18, 2013 at 03:06:52PM -0500, Justin M. Streiner wrote:
Other IPv6 transition mechanisms appear to be no less thorny than
NAT64 for a variety of reasons.
Some of us who worked on the NAT64/DNS64 combination
It depends on what direction your are translating to:
IPv6-only host to IPv4 Internet: This isn't a problem if you are dual-stack at
the host, but if you really do have ip6 only hosts, you aren't looking at any
requirement that is different than LSN44 or providing a IPv6 tunnel broker
service
On Tue, 19 Nov 2013, Ian Smith wrote:
It depends on what direction your are translating to:
IPv6-only host to IPv4 Internet: This isn't a problem if you are
dual-stack at the host, but if you really do have ip6 only hosts, you
aren't looking at any requirement that is different than LSN44
On 18/11/2013 3:06 PM, Justin M. Streiner wrote:
It's looking more and more like NAT64 will be in our future. One of the
valid concerns for NAT64 - much like NAT44 - is being able to determine
the identity of a given user through the NAT at a given point in time.
How feasible this is depends
MSOs logging subscriber flows, what could possibly go wrong?
Drive slow, like a Sandvine under load,
Paul Wall
On Mon, Nov 18, 2013 at 8:03 PM, Tom Taylor tom.taylor.s...@gmail.comwrote:
On 18/11/2013 3:06 PM, Justin M. Streiner wrote:
It's looking more and more like NAT64 will be in our
22 matches
Mail list logo
