[128745] in North American Network Operators' Group
Re: BCP38 exceptions for RFC1918 space
daemon@ATHENA.MIT.EDU (Florian Weimer)
Sun Aug 15 13:15:24 2010
From: Florian Weimer <fw@deneb.enyo.de>
To: Michael J Wise <mjwise@kapu.net>
Date: Sun, 15 Aug 2010 19:15:11 +0200
In-Reply-To: <040D7E72-DF20-4C85-843A-D621B73A52B3@kapu.net> (Michael
J. Wise's message of "Sun, 15 Aug 2010 09:47:35 -0700")
Cc: nanog@merit.edu
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
* Michael J. Wise:
> On Aug 15, 2010, at 9:14 AM, Florian Weimer wrote:
>
>> What's the current consensus on exempting private network space from
>> source address validation?
>
> BCP38-land MUST *never* see RFC1918-space traffic. Ever.
> Unless you're using a border router as a NAT device, of course....
>
> The only way your question makes sense is if someone who should know
> better is intending to announce some chunk of RFC1918-space via BGP.
>
> Please tell us that is not your intent.
It's not. It's not even about my or my employer's network, that's why
I need to exercise extra caution before handing out advice. 8-)