[180387] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: AWS Elastic IP architecture

daemon@ATHENA.MIT.EDU (Hugo Slabbert)
Mon Jun 1 18:41:22 2015

X-Original-To: nanog@nanog.org
Date: Mon, 1 Jun 2015 15:41:19 -0700
From: Hugo Slabbert <hugo@slabnet.com>
To: Matt Palmer <mpalmer@hezmatt.org>
In-Reply-To: <20150601221741.GW724@hezmatt.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org


--4Ckj6UjgE2iN1+kY
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

>The question that Matthew Kaufman proposed was specifically asking about=
=20
>app architecture deployments, so what Facebook is choosing to do is=20
>entirely germane.

I'd lean more on the "ipv6 evangelism" side of the discussion, but:

Facebook controls the whole stack and can require buy-in from their apps=20
people to push IPv6 first.  If that costs them dev time to patch some OSS=
=20
to handle it gracefully, that's their business decision.  In the "cloud=20
host" domain, you're dealing with a much more heterogeneous environment=20
where the provider doesn't control the whole stack up to the apps.  Making=
=20
the platform as frictionless as possible for customers is key; customer X=
=20
is not going like your platform much if widget Y doesn't run properly=20
"because IPv6".  Sure, widget Y should get its excrement together and=20
handle it, but all customer X sees is "widget Y fails on provider A, but=20
runs fine on provider B" where provider A was v6-only internal but provider=
=20
B is either v4-only or dual stack.  Guess where customer X spends their=20
dollars now?

I'm on your side, here: I run my own stuff v6-first wherever possible and=
=20
have filed bug reports, submitted workarounds/patches, etc.  We need people=
=20
doing that to push things forward.

On this given point, though: Facebook -ne generic hosting platform

--=20
Hugo

--4Ckj6UjgE2iN1+kY
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVbN+PAAoJEJqxD/2xeDE+STcP/03NahitjCxql4U6VtW4kvV4
CgUThR24mxBguHiK+q0oh/I7uJunfRnMZ4g5s6O73QhvMHVvpv9mHImipZLKKFbk
Cx24Ou31P0HWwH4kzZf8A21olyYLFa/j2NmAOJ9iDaSTijzJZlacq6dKaImqK3sU
pekwD7VsF44a9d9PXnH5FyEg8Ql5Cd3taZZh6Vc3QGjP4fye0LncqiPr63oEhfLR
ekFrBQxhCkfc4liY3ucx5bFuJHtT7IK/aQaTmtVa9I7KFGx+46MXT6aOVJJHAe+o
0zeLemJ0BK/zwvNOBkMmhhlkAUBFFDVvk3uJDT1R/EJLa7RB7HKSul+jEAXWNtS/
g2k8rvosbahkyrUrfD6CLcV1Jn2X8TieVvGLJgQUB/N5FqZ75SpugpEfWDzPPcua
LdZ4wmWKvmH9nK2Vuh5wfkkTWDjAYzgFgv63WAw8G+F4j2IUziTFwBRIaUx5xuMq
EV2otlaryVE/LbQJbQlXgTVYcRk3HZWrECeOvqHs4trj586heeXCD50rfH+OlXQG
+wPKty6/pQv7fRLgXEx6RAkUa+jOEGrgGqiSFcs2DrwNusuM9avMzL9Wg7f3kQZ8
NDCW956DVZZGOrg3OtP7xoOIONXtg78Rmo/j8yCvAZCqQzQP2sQ0P36rXEuxlBfZ
0vhsAsFpI3Ji0pa+JHwF
=WHJX
-----END PGP SIGNATURE-----

--4Ckj6UjgE2iN1+kY--

home help back first fref pref prev next nref lref last post