On Aug 20, 2007, at 15:55, Joe Abley wrote:
On 20-Aug-2007, at 16:43, Bob Hinden wrote:
We would like to get your comments on the following two choices:
1) Deprecate RH0 as specified in <draft-ietf-ipv6-deprecate-
rh0-01.txt>.
I support this option since:
I do too, and I'd like to add to what Joe has written.
6. It seems likely that some IPv6 operators have taken the
precaution of dropping datagrams carrying RH0, and hence the zero
type might be considered effectively poisoned for use on the public
Internet. Re-use of type zero would hence only be of reliable use
within controlled networks; to be of general use, a benign source
routing option would need a new codepoint.
The way we responded to the RH0 issue in the latest release of
firmware for AirPort Extreme 802.11n base station products is to not
forward any datagrams carrying RH0 upon receiving them on any
interface. I'm pretty sure we send ICMP errors in response to them,
but that could change in the future. There is no human interface for
changing this behavior in the IPv6 router function. The filter is
always on if IPv6 routing is on.
2) Revising the draft to restrict the usage of RH0. This would
continue to require RH0 to be implemented but would restrict the
functionality of RH0. [...]
I predict a draft that describes a less restrictive policy for
handling RH0 datagrams will be ignored by everyone who has already
shipped more restrictive products.
--
james woodyatt <[EMAIL PROTECTED]>
member of technical staff, communications engineering
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
