Re: [Hipsec] HIP parameters critical flag

Since I suggested it, it makes sense to vote for it:

715

Tobias

Am 12.01.2010 um 16:58 schrieb Robert Moskowitz:

> Tobias and I have been working away on 5201-bis and of course one new thing is the HIH parameter that needs a number...
> 
> -------- Original Message --------
> Subject: 	Fwd: HIP parameters critical flag
> Date: 	Tue, 12 Jan 2010 11:49:51 +0100
> From: 	Tobias Heer <tobias.heer@gmx.de>
> To: 	Robert Moskowitz <rgm@htt-consult.com>
> 
> 
> 
> Hello Bob,
> 
>> Am 11.01.2010 um 21:54 schrieb Robert Moskowitz:
>> 
>>> So for defining the new HIH parmeter, I am looking at 5.2.1 and it talks about the critical flag.  Oops, of course HIH is critical.  So I search for critical in the other parameters and NONE mention being critical.
>>> 
>>> What am I missing here???
>>> 
>> 
>> the C bit is the lowest order bit of the parameter number. All parameters with odd numbers (e.g. Puzzle, Solution, DH ...) are critical.
> 
> We are going to clearify this in 5201-bis and explicitly state what is a critical parameter.
> 
>>> Also what is the type value for HIH to get it in the 'right' place in the parameters?
>>> 
>> The HIH definitely needs to be in the signed part of the packet. I would consider it a parameter that is related to the BEX. The appropriate parameter range would be 0-1023. We probably need to check the HIP extensions to find a free number in this range. I'll do this tomorrow.
>> 
> 
> 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