On 8-mei-2007, at 21:00, Tim Enos wrote:
I would also prefer that RH0 be silently dropped but could live
with an ICMPv6 error message being sent back to the sending host
Why is everyone so in love with silently dropping?
This only makes troubleshooting harder.
See RFC 2460 and imagine that type 0 is not recognized:
If, while processing a received packet, a node encounters a Routing
header with an unrecognized Routing Type value, the required
behavior
of the node depends on the value of the Segments Left field, as
follows:
If Segments Left is zero, the node must ignore the Routing header
and proceed to process the next header in the packet, whose type
is identified by the Next Header field in the Routing header.
If Segments Left is non-zero, the node must discard the packet
and
send an ICMP Parameter Problem, Code 0, message to the packet's
Source Address, pointing to the unrecognized Routing Type.
Additionally, it would be helpful if we could separate the issues on
the table. There are many of them, and not all solutions apply to all
of them:
- source routing can be used for amplification
- IPv6 source routing is enabled by default on most implementations
- IPv6 source routing can't be disabled on some implementations
- BSD will _forward_ IPv6 source routed packets even when IPv6
forwarding is disabled
- apparently, there is no check whether the same addresses appear
multiple time in many implementations
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
