Re: [Hipsec] HIP parameters critical flag

Hi, 

Just one clarification:
The suggestion that the HIH and the HI should be close in the packet comes from the fact that the HIH only makes sense in packets that contain the HI (e.g., to check the HI-HIT relation). Therefore, they are closely related and it might be useful to keep both together.

Tobias

> 
> I looked at the parameter numbers and I would suggest number 715 because is located behind 705/Host_ID and it is therefore close to it in the actual HIP control packet.
> 
> I checked the following things for all active HIP drafts and documents that are accessible from the HIP WG status page:
> * There is no mentioning of the parameter number 715
> * The next parameter higher than 705/HOST_ID is 768/Cert (RFC5201 and draft-ietf-hip-cert-02.txt)
>  - there won't be any parameter between HOST_ID and HIH
>  - there is sufficient space between HIH and Cert to introduce new parameters
> 
> I checked the following files:
> 
> rfc4423.txt
> rfc5201.txt
> rfc5202.txt
> rfc5203.txt
> rfc5204.txt
> rfc5205.txt
> rfc5206.txt
> rfc5338.txt
> draft-ietf-hip-bone-03.txt
> draft-ietf-hip-cert-02.txt
> draft-ietf-hip-hiccups-00.txt
> draft-ietf-hip-nat-traversal-09.txt
> draft-ietf-hip-native-api-11.txt
> 
> Any more to check? HIP RG documents?
> 
> 
> =================================================================
> 
> And Miika proposes:
> 
> I would say that it should be before the ESP_INFO parameter. 63?
> 
> 
> 
> http://www.iana.org/assignments/hip-parameters/hip-parameters.xhtml
> 
> 
> ====================================================================
> 
> So a hum is requested:
> 
> 715?
> 63?
> 
> Other?
> 
> 
> 
> _______________________________________________
> Hipsec mailing list
> Hipsec@ietf.org
> https://www.ietf.org/mailman/listinfo/hipsec

--  

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group 
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer