[180321] in North American Network Operators' Group
Re: AWS Elastic IP architecture
daemon@ATHENA.MIT.EDU (Owen DeLong)
Sun May 31 21:08:37 2015
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <D190F68B.52B0E%wesley.george@twcable.com>
Date: Sun, 31 May 2015 18:07:03 -0700
To: "George, Wes" <wesley.george@twcable.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
As I said before:
Host Virtual (vr.org <http://vr.org/>)
Softlayer (softlayer.com <http://softlayer.com/>)
Linode (Linode.com <http://linode.com/>)
All have full dual-stack support.
I=E2=80=99m sure there are others.
Owen
> On May 31, 2015, at 2:49 PM, George, Wes <wesley.george@twcable.com> =
wrote:
>=20
>=20
> On 5/31/15, 3:11 PM, "Owen DeLong" <owen@delong.com> wrote:
>=20
>> if they said =E2=80=9CWe have a plan, and it will take X amount of =
time=E2=80=9D, I would
>> respect that.
>>=20
>> If they said =E2=80=9CWe have a plan and we=E2=80=99re not sure how =
long it will take=E2=80=9D, I
>> would continue to poke
>> them about sooner is better than later and having a target date helps
>> people to plan.
>>=20
>> =E2=80=9CWe don=E2=80=99t think IPv6 matters and we aren=E2=80=99t =
announcing any plans to get it
>> implemented or any
>> date by which it will be available=E2=80=9D, on the other hand, being =
what they
>> have actually repeatedly
>> said to me until very recently, not so much.
>>=20
>> Now, they=E2=80=99re saying (essentially) =E2=80=9CWe think IPv6 =
might matter, but we
>> aren=E2=80=99t announcing
>> any plans to get it implemented or any date by which it will be
>> available=E2=80=9D . To me, this
>> is still a problematic situation for their customers.
>=20
> At the risk of feeding the troll...
>=20
> This isn't just an AWS problem.
>=20
> "All Compute Engine networks use the IPv4 protocol. Compute Engine
> currently does not support IPv6. However, Google is a major advocate =
of
> IPv6 and it is an important future direction."
> https://cloud.google.com/compute/docs/networking
>=20
>=20
> "The foundational work to enable IPv6 in the Azure environment is well
> underway. However, we are unable to share a date when IPv6 support =
will be
> generally available at this time."
>=20
> http://azure.microsoft.com/en-us/pricing/faq/
>=20
>=20
> This is only marginally better, as it acknowledges that it's =
important,
> but still has no actual committed timeline and doesn't even reference =
any
> available ELB hacks.
>=20
> Anyone else want to either name and shame, or highlight cloud =
providers
> that actually *support* IPv6 as an alternative to these so that one =
might
> be able to vote with one's wallet?
>=20
>=20
> This E-mail and any of its attachments may contain Time Warner Cable =
proprietary information, which is privileged, confidential, or subject =
to copyright belonging to Time Warner Cable. This E-mail is intended =
solely for the use of the individual or entity to which it is addressed. =
If you are not the intended recipient of this E-mail, you are hereby =
notified that any dissemination, distribution, copying, or action taken =
in relation to the contents of and attachments to this E-mail is =
strictly prohibited and may be unlawful. If you have received this =
E-mail in error, please notify the sender immediately and permanently =
delete the original and any copy of this E-mail and any printout.
