On 11-May-2007, at 17:18, David Malone wrote:
This is why I think someone might want to turn RH0 back on again (to get this feature on their own network). They can filter at the border to prevent external abuse, and use the usual procedures to deal with internal abuse. This is also the sort of feature that ordinary users are not likely to use, which is why I think it is reasonable to have it off by default.
There seem to be many daily examples of very large numbers of client machines being controlled remotely to participate in activities that the owner/operators of those machines aren't aware of. If there's a hook available to turn RH0 processing back on, and RH0 is useful to the kind of people who control botnets today, then I think it's a fair bet that RH0 will be turned back on regardless of the default setting is.
If RH0 is not a useful mechanism to facilitate wide-scale network abuse, then I would not expect this to happen (but then, if RH0 is so benign, why are we talking? :-)
Joe -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
