[52723] in North American Network Operators' Group
Re: Who does source address validation? (was Re: what's that smell?)
daemon@ATHENA.MIT.EDU (Joe Abley)
Wed Oct 9 13:12:48 2002
Date: Wed, 9 Oct 2002 13:12:12 -0400
Cc: "Greg A. Woods" <woods@weird.com>,
Sean Donelan <sean@donelan.com>, nanog@merit.edu
To: "Stephen J. Wilcox" <steve@telecomplete.co.uk>
From: Joe Abley <jabley@isc.org>
In-Reply-To: <Pine.LNX.4.21.0210091633560.21213-100000@MrServer>
Errors-To: owner-nanog-outgoing@merit.edu
On Wednesday, Oct 9, 2002, at 11:36 Canada/Eastern, Stephen J. Wilcox
wrote:
> On Tue, 8 Oct 2002, Greg A. Woods wrote:
>
>> Such things REALLY _NEEED_ to be broken, and the sooner the better as
>> then perhaps the offenders will fix such things sooner too, because
>> they
>> are by definition already broken and in violation of RFC 1918 and good
>> common sense.
>
> Ok but real world calling. I have tried this and when customers find
> something
> doesnt work on your network but it does on your competitor you make it
> work even
> if that means breaking rules.
What services require transport of packets with RFC1918 source
addresses across the public network?
I can think of esoteric examples of things it would be possible to do,
but nothing that a real-world user might need (or have occasion to
complain about).
Do you have experience of such breakage from your own customers? It
would be interesting to hear details.
Joe
