[129022] in North American Network Operators' Group
Re: BCP38 exceptions for RFC1918 space
daemon@ATHENA.MIT.EDU (Joel Jaeggli)
Mon Aug 23 11:49:00 2010
Date: Mon, 23 Aug 2010 08:48:22 -0700
From: Joel Jaeggli <joelja@bogus.com>
To: Leigh Porter <leigh.porter@ukbroadband.com>
In-Reply-To: <B925B320C2655641ADBBFC00B1F0B820035C55DE@ukbb3.ukbroadband.com>
Cc: nanog@merit.edu, Joe Greco <jgreco@ns.sol.net>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
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]
> Sent: 16 August 2010 14:27
> To: Joe Greco
> Cc: nanog@merit.edu
> Subject: Re: BCP38 exceptions for RFC1918 space
>
> On Mon, 16 Aug 2010 06:50:00 CDT, Joe Greco said:
>
>>> What *possible* use case would require a 1918-sourced packet to be
>>> traversing the public internet? We're all waiting with bated breath
>>> to hear this one. ;)
>>
>> It's great for showing in traceroutes who the heel is.
>
> Like I said, at that point it's name-n-shame time.
>
>
