Pekka, Leakage in the payload (i.e. a referral) is problem we will have anyway, e.g. if the referred address is inside a firewall. I think that problem is unavoidable. It's true that with a fully registered PI, diagnosis is easier.
Brian Pekka Savola wrote: > > On Sun, 9 Nov 2003, Brian E Carpenter wrote: > [...] > > > As I explain in a previous message, this last property is not verified > > > by the hinden/haberman draft, as when those addresses leak, > > > they would create untraceable problems, very similar to the one > > > caused by RFC1918 leaks today. > > > > Q: Who is to blame and likely to be a victim? > > > > A: any ISP without ingress filtering. > > > > To misquote Pekka, why exactly should we care if ISP X's operations > > break because it fails to implement ingress filtering? > > Uhh, but isn't the pain felt by everyone, especially if the leakage is > more subtle than source/destination address? E.g., leakage in the > payload... > > -- > Pekka Savola "You each name yourselves king, yet the > Netcore Oy kingdom bleeds." > Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
