Re: [MEXT] Call for WG adoption of I-D: draft-korhonen-mext-mip6-altsec

Hi,

<[email protected]> writes:

> Inline:
>
> On 1/24/11 3:58 PM, "ext Arnaud Ebalard" <[email protected]> wrote:
>
>>
>>To me, what the draft describes is a patchwork based on MIPv6, ESP and
>>TLS. Instead of building on top of those protocols (read modularity and
>>interoperability), it reuses (hijacks) various blocks of associated
>>standards in a non-modular way. For instance, one has to reimplement ESP
>>in userspace to support the protocol.
>
> We are specifying an encapsulation method in the I-D. To say that one has
> to reimplement ESP in userspace is incorrect.

Then please explain how one is supposed to get the format described in
section 6.4 which is *explicitly* borrowed from RFC 4303 w/o
reimplementing it in userspace?

Or are you pushing SP and SA in order to reuse what is already
implemented in the IPsec stack?

BTW, is the packages/sources of your implementation still available
somewhere? I expected the patches to be pushed upstream at some point.

Cheers,

a+