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

["Henderson, Thomas R" <thomas.r.henderson at boeing.com>]

> #2 How should the socket calls react to only-hip wildcard. Currently 
> section 4.1.1 describes:
> 
>     With the HIP_HIT_ANY address,
>     the underlying system allows only HIP-based data flows with the
>     corresponding socket.  For incoming packets, the system 
> transparently
>     discards all other traffic arriving at the socket than 
> HIP related.
>     For outgoing packets, the system returns -1 in the socket call and
>     sets errno to ECOMM when the system failed to deliver the 
> packet over
>     a HIP-based data channel.

I would like to suggest these changes to the above paragraph:

    With the HIP_HIT_ANY address,
    the underlying system allows only HIP-based data flows with the
    corresponding socket.  For incoming packets, the system
    discards all non-HIP-related traffic arriving at the socket.
    For outgoing packets, the system returns -1 in the socket call and
    sets errno to an appropriate error type when the system failed to
deliver the packet over
    a HIP-based data channel.

rationale:
1) for incoming datagrams, "discards" rather than "transparently
discards" is a policy issue that is not related to the API (e.g. whether
a system returns some type of ICMP error is out of scope for the API
specification)
2) for outgoing packets, different systems appear to specify different
errnos under different circumstances, so it probably is too restrictive
to specify ECOMM here.  ECOMM, for instance, does not appear to be an
error type returned by Linux as a failure code for connect().

Tom