[113878] in North American Network Operators' Group
Re: IPv4 Anycast?
daemon@ATHENA.MIT.EDU (Jeroen Massar)
Wed Apr 22 17:27:11 2009
Date: Wed, 22 Apr 2009 23:27:03 +0200
From: Jeroen Massar <jeroen@unfix.org>
To: Kevin Loch <kloch@kl.net>
In-Reply-To: <49EF8ACB.8000604@kl.net>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig6F877829FB89C0A6BECB997F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Kevin Loch wrote:
> Patrick W. Gilmore wrote:
>> On Apr 22, 2009, at 4:35 PM, Jack Bates wrote:
>>> Zhenkai Zhu wrote:
>>>> I just want to make sure if I understand correctly. You mean that
>>>> the anycasted address space can be announced in different places yet=
>>>> with the same origin AS?
>>>
>>> Yes, and it is commonly done.
>>
>> I was under the impression anycast services with homogeneous origin AS=
>> was far more common than the heterogeneous. Almost all the instances
>> I know of use homogeneous origin AS.
>>
>> I'd be interested in statistics either way.
>=20
> 192.88.99.0/24, 2002::/16, and 2001::/32 are some
> notable examples of heterogeneous origin AS.
And those prefixes (6to4 & Teredo) all come with annoying problems as
one never knows which relay is really being used and it is hard to debug
how the packets really flow.
Greets,
Jeroen
--------------enig6F877829FB89C0A6BECB997F
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.4.7 (MingW32)
iD8DBQFJ74unKaooUjM+fCMRArjFAKCZizkoeC6qywz4DSXPK3bjBMSsJACdH9E6
yqoFUPL1co3vgbxc2pPMD+c=
=Pm0G
-----END PGP SIGNATURE-----
--------------enig6F877829FB89C0A6BECB997F--
