[129023] in North American Network Operators' Group
RE: BCP38 exceptions for RFC1918 space
daemon@ATHENA.MIT.EDU (Leigh Porter)
Mon Aug 23 11:52:01 2010
Date: Mon, 23 Aug 2010 16:51:40 +0100
In-Reply-To: <4C729846.1070201@bogus.com>
From: "Leigh Porter" <leigh.porter@ukbroadband.com>
To: "Joel Jaeggli" <joelja@bogus.com>
Cc: nanog@merit.edu, Joe Greco <jgreco@ns.sol.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Oh I do, just not to my workstation ;-)
-----Original Message-----
From: Joel Jaeggli [mailto:joelja@bogus.com]=20
Sent: 23 August 2010 16:48
To: Leigh Porter
Cc: Valdis.Kletnieks@vt.edu; Joe Greco; nanog@merit.edu
Subject: Re: BCP38 exceptions for RFC1918 space
On 8/23/10 2:31 AM, Leigh Porter wrote:
> I very often see 1918 space in ICMP responses. It's quite dumb.
you wouldn't if you filtered rfc 1918 source addresses on your border.
> -----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. ;)
>>
>> 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
>=20
