[172341] in North American Network Operators' Group
Re: routing issues to AWS via 2914(NTT)
daemon@ATHENA.MIT.EDU (joel jaeggli)
Fri Jun 13 22:29:43 2014
X-Original-To: nanog@nanog.org
Date: Fri, 13 Jun 2014 19:29:37 -0700
From: joel jaeggli <joelja@bogus.com>
To: nanog@nanog.org
In-Reply-To: <20140613212829.GY8158@hezmatt.org>
Errors-To: nanog-bounces@nanog.org
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--U1ejvPB3l6A6hL39KTMAfTNeIfcfoET54
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 6/13/14, 2:28 PM, Matt Palmer wrote:
> On Fri, Jun 13, 2014 at 11:44:51AM +0000, Paul WALL wrote:
>> Amazon peers at many key exchanges, with dozens of hosting shops
>> (where customers might share mutual infrastructure) like yours:
>>
>> https://www.peeringdb.com/view.php?asn=3D16509
>>
>> Rather than play the blame game with third-party transit providers,
>> why not hit them up for some sessions?
>=20
> That'll only get you peering connectivity into the local region. To ge=
t
> fully-peered with AWS, and be able to avoid third-party transit provide=
rs
> entirely, you're going to have to be in a *lot* of places.
>=20
> Not saying that AWS is a bad peer (from experience, I know they're fine=
to
> deal with) but it isn't as cut-and-dried as saying "don't blame transit=
> providers, just peer!".
just peer in IAD, SEA and SJC, and AMS, and SIN. problem solved, yup.
> - Matt
>=20
--U1ejvPB3l6A6hL39KTMAfTNeIfcfoET54
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlObs5EACgkQ8AA1q7Z/VrI0QgCdH1rhoOYCroLLC+wfDnQKbsmz
NaMAnjeSiQSgAjy+22vGqkhp9KLiAljM
=eS6b
-----END PGP SIGNATURE-----
--U1ejvPB3l6A6hL39KTMAfTNeIfcfoET54--
