[34956] in North American Network Operators' Group
Re: rfc 1918?
daemon@ATHENA.MIT.EDU (John Hawkinson)
Thu Feb 22 16:32:28 2001
Date: Thu, 22 Feb 2001 16:22:07 -0500
From: John Hawkinson <jhawk@bbnplanet.com>
To: Valdis.Kletnieks@vt.edu
Cc: Chris Davis <chris.davis@computerjobs.com>,
"'nanog@merit.edu'" <nanog@merit.edu>
Message-ID: <20010222162207.W23712@jhawk-foo.bbnplanet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <200102222118.f1MLIbk30149@foo-bar-baz.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Thu, Feb 22, 2001 at 04:18:36PM -0500
Errors-To: owner-nanog-outgoing@merit.edu
> > There are good reasons to want to get those packets (traceroutes from
> > people who have numbered their networks in rfc1918 networks, f'rinstance).
>
> The original note specifically showed them as being TCP packets from
> a 10.x.x.x address going to port 80. Does that qualify as a good reason?
Err, no, but I don't think it's reasonable to expect people to filter rfc1918
packets based on specific protocols.
> > Not everyone agrees whether it is better to filter or not to filter,
> > but there are good arguments on both sides.
>
> Does anybody in the house think that these packets actually have a snowball's
> chance in Hades of getting a reply back sucessfully?
No, but that's really a thoroughly orthogonal question.
--jhawk
