Re: [Hipsec] draft-ietf-hip-native-api-09-pre

["Ahrenholz, Jeffrey M" <jeffrey.m.ahrenholz at boeing.com>]

Miika,

> section 4.1. I also wrote the ship_len explicitly to the 
> structure since we were discussing on size issues.

In section 7 you might mention using the optional ship_len field (maybe
instead of flags and prefix.) 

> Both the sockaddr_is_srcaddr() and sockaddr_is_hit() function 
> take care of the wildcards currently as follows:
> 
>     The function returns also
>     returns -1 on a sockaddr_hip structure containing a 
> HIP_ENDPOINT_ANY
>     or HIP_HIT_ANY_* wildcard.

This is good since the wildcards aren't HITs.

> Jeff and Andrew, please comment on the mailing if you are 
> satisfied with 
> the changes so that I can publish the final version of the draft.

Just a couple of nits:

Section 4.5
s/Application can call/Applications can call/
s/function returns also returns -1/function also returns -1/

Section 7
s/to indicate that can support/to indicate that it can support/
s/instead directly using/instead of directly using/

-Jeff