[128795] in North American Network Operators' Group
Re: BCP38 exceptions for RFC1918 space
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Mon Aug 16 09:27:07 2010
To: Joe Greco <jgreco@ns.sol.net>
In-Reply-To: Your message of "Mon, 16 Aug 2010 06:50:00 CDT."
<201008161150.o7GBo08b044855@aurora.sol.net>
From: Valdis.Kletnieks@vt.edu
Date: Mon, 16 Aug 2010 09:26:56 -0400
Cc: nanog@merit.edu
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
--==_Exmh_1281965216_5254P
Content-Type: text/plain; charset=us-ascii
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.
--==_Exmh_1281965216_5254P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iD8DBQFMaTygcC3lWbTT17ARAvqiAKC4HwPFfeBDgVZnXh7Y+J0TUDJriQCeNc8e
Bl5MjybRlfuZBTLCftB6o5k=
=1yFD
-----END PGP SIGNATURE-----
--==_Exmh_1281965216_5254P--
