* Brian E. Carpenter:
> Common practice in network monitoring and in QoS technologies
> is to identify a flow of packets by the 5-tuple
> {source address, dest address, source port, dest port, protocol #}.
> This is relatively trivial at line speed in IPv4 since
> these things are at fixed locations in the header.
Only if you ignore IP options. Of course, IP options have been
operationally deprecated and are typically not forwarded across the
public Internet.
> But in IPv6, the protocol number is at the end of a linked list of
> "next headers." Even if the normal case is only one item in the
> linked list, any implementation (hardware or software) that extracts
> the 5-tuple has to follow the linked list to the end.
As far as I can tell, all extension headers except fragmentation are
deprecated, similar to IP options in IPv4 land. This should make
extraction much simpler.
> What do people think?
>From today's perspective, the IPv6 header design is complete crap.
Maybe it was optimized for software forwarding on in-order CPUs, but
that's distant history now.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
