On 26.06.2013, at 11:58, René Hummen <[email protected]> wrote:
[...] > Regarding 5202-bis: > ---------------------------- > There is currently no reference to the TRANSPORT_FORMAT_LIST parameter in > this document. Here, we need to specify the transform format type for IPsec > ESP. I suggest to add the following new section to the document [7]: > "4.1.1 IPsec ESP Transport Format Type > The HIP handshake signals the TRANSPORT_FORMAT_LIST parameter in the R1 and > I2 messages. This parameter contains a list of the supported HIP transport > formats of the sending host in the order of preference. The transport format > type for IPsec ESP is X (TBD)." According to 5201-bis, the transport format type is defined as [1]: "The TF type numbers correspond to the HIP parameter type numbers of the respective transform parameters." Hence, the last sentence of my suggested text should rather read as follows: "The transport format type for IPsec ESP is the type number of the ESP_TRANSFORM parameter, i.e., 4095." BR René [1] http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-11#section-5.2.11 -- Dipl.-Inform. Rene Hummen, Ph.D. Student Chair of Communication and Distributed Systems RWTH Aachen University, Germany tel: +49 241 80 21429 web: http://www.comsys.rwth-aachen.de/team/rene-hummen/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Hipsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/hipsec
