[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Hipsec] draft-ietf-hip-native-api-09-pre
Hi,
we got an extra review to the native API from Stefan Götz. The new
preversion is here:
http://www.iki.fi/miika/docs/draft-ietf-hip-native-api-09-pre1.txt
The changes are editorial readability changes throughout the document.
Especially section 4.1 contains now more clarifications on the fields of
sockaddr_hip structure and wildcards
We'd like to move on with the document, but we have two questions for
the working group:
#1 How to future proof HITs in case we need 256 bit HITs? This is
important also from the view point of comparison of HITs (currently
draft suggests memcmp() in section 4.1. Unless, there's other
suggestions, I'd go for alternative (i):
* Alternative (i): separate sockaddr_hip structure for larger HITs
* Alternative (ii): make larger HIT structure in sockaddr_hip with
zero padding for 128 bit HITs
#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.