From david.freedman at uk.clara.net  Sun Jul  5 01:08:45 2009
From: david.freedman at uk.clara.net (David Freedman)
Date: Sun, 5 Jul 2009 00:08:45 +0100
Subject: IPv6 Contact at ATT AS7018
Message-ID: <7B8B0D6F623C3A40A0D0A80A66756E2B0D7D43@EXVS01.claranet.local>

If anybody has a good IPv6 contact there (or indeed, if they are on-list), would appreciate being passed their details (concerning a routing issue)

Regards,

------------------------------------------------
David Freedman
Group Network Engineering 
Claranet Limited
http://www.clara.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.cluenet.de/pipermail/ipv6-ops/attachments/20090705/c3393d38/attachment.html 

From ipv6-ops at arbitraryconstant.com  Thu Jul 16 20:57:16 2009
From: ipv6-ops at arbitraryconstant.com (Anthony Roberts)
Date: Thu, 16 Jul 2009 12:57:16 -0600
Subject: Factors, actions influencing the possibility/timing of IDR for
	IPv6-basedrouting =?UTF-8?Q?domains=3F?=
In-Reply-To: <2e8c64260906241513h41030fb0g929b1a1e7324c118@mail.gmail.com>
References: <04BBB069-AF1B-4B20-8A0B-1B94F528147C@pch.net>
	<3E8BEB47BAAC4480A53CE6AF3D3FDC08@tedsdesk>
	<DBFE2B4E-032E-4EB5-9108-BF1D8F1FE28F@pch.net>
	<F910D18AF8C04992A1435594CAEF15CA@tedsdesk>
	<2e8c64260906191832nb0d4b0ma457e017673a1347@mail.gmail.com>
	<39bd4837e6e9a4bf5aef9bf1c4697bdd@localhost>
	<2e8c64260906241513h41030fb0g929b1a1e7324c118@mail.gmail.com>
Message-ID: <58392f46212236d841023b0edd1a9777@smtp.arbitraryconstant.com>

Good point. I don't think all v6 hosts are getting Google's AAAAs yet, but
I imagine that's going to improve with time as v6 networks become better
connected with each other.

I've been following the BEHAVE NAT64 mailing list -- they've now got a
draft to allow hosts to learn the NAT64 translation prefix and take
appropriate action internally for situations like this where DNS
translation can't occur. Google cache links aren't the only use case that
may be impacted. That won't work for "legacy" v6 hosts that don't support
this, but moving forward at least there's a better developed set of tools
to mitigate these sorts of issues. "Foo is broken in v6" is much worse than
"You need Windows N+1 SP2 to use foo in v6".

-Anthony

On Wed, 24 Jun 2009 15:13:01 -0700, Erik Kline <ek at google.com> wrote:
>> The thing I find encouraging are the NAT64 drafts, as they explicitly
>> acknowledge and address the fact that v4 may be with us for some time to
>> come. That may cause a problem for Google cache links though; you'll see
>> v4
>> connections, and send back links with v4 IPs, but the clients will be
>> relying on DNS translation that won't happen for web links with raw IPs.
>> Good times. :)
> 
> I'm not sure of this being a real problem, at least not the situation
> you describe.  In your example a client has IPv6-only, and gets to
> IPv4 via NAT64 at some point in the network path.  I think in this
> scenario we would just serve AAAAs to these IPv6-only networks and
> side-step the whole issue.

From nicolas.braudsantoni at gmail.com  Fri Jul 17 15:44:56 2009
From: nicolas.braudsantoni at gmail.com (Nicolas Braud-Santoni)
Date: Fri, 17 Jul 2009 15:44:56 +0200
Subject: Factors, actions influencing the possibility/timing of IDR for 
	IPv6-basedrouting domains?
In-Reply-To: <58392f46212236d841023b0edd1a9777@smtp.arbitraryconstant.com>
References: <04BBB069-AF1B-4B20-8A0B-1B94F528147C@pch.net>
	<3E8BEB47BAAC4480A53CE6AF3D3FDC08@tedsdesk>
	<DBFE2B4E-032E-4EB5-9108-BF1D8F1FE28F@pch.net>
	<F910D18AF8C04992A1435594CAEF15CA@tedsdesk>
	<2e8c64260906191832nb0d4b0ma457e017673a1347@mail.gmail.com>
	<39bd4837e6e9a4bf5aef9bf1c4697bdd@localhost>
	<2e8c64260906241513h41030fb0g929b1a1e7324c118@mail.gmail.com>
	<58392f46212236d841023b0edd1a9777@smtp.arbitraryconstant.com>
Message-ID: <738b3a5e0907170644r4faba7dw5917451338c8e8e7@mail.gmail.com>

2009/7/16 Anthony Roberts <ipv6-ops at arbitraryconstant.com>:
> Good point. I don't think all v6 hosts are getting Google's AAAAs yet, but
> I imagine that's going to improve with time as v6 networks become better
> connected with each other.

Hello Antony,
Google authoritative DNS won't give you the AAAA records unless they
recognize the IPv4 address of your DNS resolver as an IPv6 compliant
host (they just lookup a list of hosts that requested to get the AAAA
records).
More information here : http://www.google.com/intl/en/ipv6/

> I've been following the BEHAVE NAT64 mailing list -- they've now got a
> draft to allow hosts to learn the NAT64 translation prefix and take
> appropriate action internally for situations like this where DNS
> translation can't occur. Google cache links aren't the only use case that
> may be impacted. That won't work for "legacy" v6 hosts that don't support
> this, but moving forward at least there's a better developed set of tools
> to mitigate these sorts of issues. "Foo is broken in v6" is much worse than
> "You need Windows N+1 SP2 to use foo in v6".