[129019] in North American Network Operators' Group
Re: BCP38 exceptions for RFC1918 space
daemon@ATHENA.MIT.EDU (Ali)
Mon Aug 23 11:03:56 2010
In-Reply-To: <B925B320C2655641ADBBFC00B1F0B820035C55DE@ukbb3.ukbroadband.com>
From: Ali <sterbeats@gmail.com>
Date: Mon, 23 Aug 2010 08:03:11 -0700
To: Leigh Porter <leigh.porter@ukbroadband.com>
Cc: "nanog@merit.edu" <nanog@merit.edu>, Joe Greco <jgreco@ns.sol.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hahahahah=20
How do we prevent BGP loops? Hahahhaahb=20
Sent via mobile.
On Aug 23, 2010, at 2:31 AM, "Leigh Porter" <leigh.porter@ukbroadband.com> w=
rote:
> I very often see 1918 space in ICMP responses. It's quite dumb.
>=20
> -----Original Message-----
> From: Valdis.Kletnieks@vt.edu [mailto:Valdis.Kletnieks@vt.edu]=20
> Sent: 16 August 2010 14:27
> To: Joe Greco
> Cc: nanog@merit.edu
> Subject: Re: BCP38 exceptions for RFC1918 space
>=20
> On Mon, 16 Aug 2010 06:50:00 CDT, Joe Greco said:
>=20
>>> What *possible* use case would require a 1918-sourced packet to be=20
>>> traversing the public internet? We're all waiting with bated breath=20
>>> to hear this one. ;)
>>=20
>> It's great for showing in traceroutes who the heel is.
>=20
> Like I said, at that point it's name-n-shame time.
>=20
