In your previous mail you wrote:
I have the impression that a lot of the complexity in these chained
extension headers is caused by the way Source Routing is specified.
If Source Routing would be a hop-by-hop extension and the IPv6
destination was always the final destination the header mess wouldn't be
that big
=> hop-by-hop means to be processed by each router on the path...
What you propose in fact is to kill the routing header facility
(as it was for IPv4 in the real world) but I am sorry but the routing
header is useful, for instance for mobility (routing optimization needs it)
and policy routing.
(the disadvantage being that Loose Source Routed packets need
additional procesing in non-fixed hops,
=> IPv6 routing header type 0 (other types are not used) is *loose* source
routing.
but who is using Source Routing anyhow?).
=> see before.
[EMAIL PROTECTED]
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
