[Hipsec] feedback of hiccups-01 draft

Hi,

I have some feedback of the hiccups draft. The draft is well written and 
easy to read and understand. However, I have few questions (sorry if 
these have been asked already):

* I guess the draft assumes that data packets may be sent over HIP-aware 
overlays. I would suggest that the authors have a look at 
draft-heer-hip-middle-auth and perhaps add a pointer to the draft. 
Particularly, I would propose to make the public key mandatory and 
perhaps the middlebox extension as SHOULD? There is a new version of the 
draft coming up very soon. Feel free to ask Tobias for a preview if you 
are interested.

* The justification for the seq/ack mechanism is a bit unclear. Is it 
only about replay protection?

* I just implemented minimal support for HIP_DATA in HIPL. Now the 
implementation should be able to respond with an R1 to a HIPL_DATA 
packet. Now we need to test it for interoperability :) I would suggest 
that OpenHIP folks also implemented this feature because it should be 
only few lines of code.

* Second paragraph in section 5 explain about the issues with 
fragmentation. Implementation wise, shouldn't this problem be just 
solved by lowering the MTU of the tunnel device by the size of HIP 
header, [HOST_ID], payload HMAC and HIP_SIGNATURE?
_______________________________________________
Hipsec mailing list
Hipsec@ietf.org
https://www.ietf.org/mailman/listinfo/hipsec