[Top] [All Lists]

Re: Adding of destination options in IPv6

To: stefan.schlott@xxxxxxxxxxxxxxxxxx (Stefan Schlott)
Subject: Re: Adding of destination options in IPv6
From: kuznet@xxxxxxxxxxxxx
Date: Wed, 12 Jul 2000 20:13:12 +0400 (MSK DST)
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20000711221316.A1386@xxxxxxxxxxxxxxxxxxxxxxxxxxx> from "Stefan Schlott" at Jul 11, 0 10:13:16 pm
Sender: owner-netdev@xxxxxxxxxxx

> new ext_header_len. As a second step, I do my modifications in ip6_xmit/
> ip6_build_xmit.
> A general interface for this work would be ugly, but at least there would
> be an interface ;-)
> Any comments?

Comment is that it is right direction.

Only it is not so straightforward. Such adjustments violate existing
locking hierarchy, so that you have to design thing, which does not exist
now. Namely, message queue for relaible feedback from lower layers
to upper ones. It is for mobile IPv6.

And it still will not work with IPsec, because you cannot send anything
not-encrypted, while the information trips back to sender. So, direct
surgery inside TCP is required in any case.

Reserving space is much simpler and seems not to hurt anyone.
Surgeons wait, while terapeutics helps. 8)


<Prev in Thread] Current Thread [Next in Thread>