Re: [Hipsec] ROUTE_VIA and _DST support for HIP native API

[Miika Komu <[e-mail]>]

Ari Keranen wrote:

Hi,

> Hi,
> 
> Sorry that this comes a bit late in the process, but I think it would 
> make sense to have support for the source routing & route recording 
> ROUTE_DST and ROUTE_VIA parameters [1] in the HIP native API. They are 
> needed for HIP BONE but likely they have use also in other contexts and 
> then an application would need an API for using them.
> 
> Maybe the API that RFC 2292 [2] defines for IPv6 routing header could be 
> re-used for this purpose.
> 
> 
> Cheers,
> Ari
> 
> [1] http://tools.ietf.org/html/draft-camarillo-hip-via-00
> [2] http://tools.ietf.org/html/rfc2292#section-8

I had a brief look a the routing header options and I think this would 
require a lot more work. I think we just can't tell "use IPv6 routing 
header for route recording" because we need to dig out the differences 
with orchid vs. IPv6 routing and flesh out all the details. The current 
time schedule is quite tight for this too.

Currently, the native API draft defines "Basic Socket Interface 
Extensions for Host Identity Protocol (HIP)". I believe the hiccups 
extensions belong to the category of "advanced" and the reference to [2] 
is also "Advanced Sockets API for IPv6".

I would propose that we'd introduce another document for orchid routing 
or add them to the VIA draft. Please comment this proposal ASAP so that 
I'll have more time to hack this over the night if people want to see 
the changes in the native API.