Re: [Hipsec] I-D Action: draft-ietf-hip-rfc4423-bis-09.txt

2014-10-20 Thread Miika Komu
Protocol Working Group of the IETF. Title : Host Identity Protocol Architecture Authors : Robert Moskowitz Miika Komu Filename: draft-ietf-hip-rfc4423-bis-09.txt Pages : 39 Date: 2014-10

Re: [Hipsec] HIP draft updates

2014-07-30 Thread Miika Komu
Hi Tom, On 07/29/2014 01:09 AM, Tom Henderson wrote: For RFC5202bis, the main issue is the recommendation of NULL encryption as a MUST to implement (issue 43). This has been discussed on the saag list and on this list, and I don't think it is yet resolved although I would like to again

Re: [Hipsec] transition from CLOSING state to state I1-SENT

2014-07-30 Thread Miika Komu
Hi, On 07/29/2014 01:14 AM, Tom Henderson wrote: This issue with RFC5201-bis is being tracked as issue 48: http://trac.tools.ietf.org/wg/hip/trac/ticket/48 When a HIP association is in state CLOSING and new data arrives to send to the peer, Table 7 states to send another I1 but stay in

Re: [Hipsec] RFC5201-bis: Stephen Farrell's DISCUSS questions

2014-07-30 Thread Miika Komu
Hi, On 07/22/2014 01:50 AM, Tom Henderson wrote: Also - there are no counter modes, is that wise? HIP DEX defines AES-128-CTR for HIP_CIPHER [3]. However, I just realized that it does not specify its use for the ENCRYPTED parameter. Instead, the specification focuses on the special-purpose

Re: [Hipsec] NULL encryption mode in RFC 5202-bis

2014-07-08 Thread Miika Komu
Hi, On 07/08/2014 07:54 AM, Tom Henderson wrote: Hi all, Apologies for cross-posting, but Stephen Farrell raised a DISCUSS (seconded by Kathleen Moriarty) in the IESG evaluation of RFC 5202-bis: Using the Encapsulating Security Payload (ESP) Transport Format with the Host Identity Protocol

Re: [Hipsec] processing review comments on RFC 5201-bis

2014-07-02 Thread Miika Komu
Hi, On 06/30/2014 08:46 PM, Tom Taylor wrote: 3) Section 5.2.18: given the strict ordering of HIP parameters, the initial plaintext for the Encrypted content (type and length of initial parameter) may be fairly easily guessed. This opens up the minor possibility of a known plaintext attack.

Re: [Hipsec] processing review comments on RFC 5201-bis

2014-07-02 Thread Miika Komu
Hi, On 07/02/2014 05:26 PM, Miika Komu wrote: Hi, On 06/30/2014 08:46 PM, Tom Taylor wrote: 3) Section 5.2.18: given the strict ordering of HIP parameters, the initial plaintext for the Encrypted content (type and length of initial parameter) may be fairly easily guessed. This opens up

Re: [Hipsec] ESP in clientVPN tunnel mode - what is needed in exchange

2014-05-19 Thread Miika Komu
Hi, On 05/19/2014 09:08 PM, Robert Moskowitz wrote: I have a real need to provide ESP tunnel mode from a HIP client to a gateway. The world just won't go as nicely as I would have wanted it to. location-based security is old fashioned :( At the application layer, tunnel mode may have some

Re: [Hipsec] Unsticking HIP from 1st gear

2014-05-02 Thread Miika Komu
Hi, On 05/02/2014 01:29 AM, Robert Moskowitz wrote: On 04/30/2014 02:18 PM, Robert Moskowitz wrote: Automotive analogy because right now I have been dragged back to my automotive history to work on the Connected Car security... I am working on multiple HIP projects. Real vendors with real

[Hipsec] HIP in a cloud testbed to analyze CERN data

2014-04-17 Thread Miika Komu
FYI, HIP for Linux is now utilized in a testbed cloud deployment that is used for analyzing CMS (Compact Muon Solenoid) data from CERN. The HIP protocol provides secure connectivity and connection management capabilities for the OpenStack based cloud. Thanks to Salman Toor, Juhani Toivonen and

Re: [Hipsec] WGLC: draft-ietf-hip-rfc4423-bis

2014-04-08 Thread Miika Komu
Hi, sure thing, thanks Tom for comments! On 04/08/2014 01:25 PM, Gonzalo Camarillo wrote: Hi Tom, thanks for your comments. Authors, could you please look into this? Thanks, Gonzalo On 07/04/2014 12:08 AM, Henderson, Thomas R wrote: Hi, we WGLCed this draft some time ago, but we are

Re: [Hipsec] Feedback for 4423bis

2013-12-18 Thread Miika Komu
Hi, I have fixed some typos in the latest version of architecture draft (draft-ietf-hip-rfc4423-bis-07). I'd suggest to move it to last call unless there are more quick comments. ___ Hipsec mailing list Hipsec@ietf.org

Re: [Hipsec] additional comments on latest RFC5201-bis draft

2013-11-09 Thread Miika Komu
FYI, On 09/26/2013 11:45 PM, Henderson, Thomas R wrote: I'll try to wrap up the inputs and post a revision over the weekend, if no further comments. Please see inline below. Xin Gu implemented HIPv2 (sponsored by Aalto university) and the code is now available in the HIPL trunk:

Re: [Hipsec] Feedback for 4423bis

2012-10-18 Thread Miika Komu
Hi, On 10/10/2012 10:05 PM, Sasu Tarkoma wrote: Hi all, I read the latest HIP architecture draft (4423bis-05) and it looks very good. Below you will find some observations that I made when reading the draft. looks good to me too but I have also some suggestions for improvement. Here's the

Re: [Hipsec] WGLCs: 4423bis and 5201bis

2012-10-17 Thread Miika Komu
Hi, On 10/17/2012 06:36 AM, Henderson, Thomas R wrote: 5.1. HIP Control Packets: The HIP header and parameters follow the conventions of [RFC5201] with the exception that the HIP header checksum MUST be zero. Authors, can we get rid of the pseudo header or are we stuck with it? Or can we

Re: [Hipsec] WGLCs: 4423bis and 5201bis

2012-09-13 Thread Miika Komu
Hi, On 09/13/2012 11:11 AM, Gonzalo Camarillo wrote: Folks, I would like to start the WGLCs on the following two drafts. These WGLCs will end on September 30th. https://datatracker.ietf.org/doc/draft-ietf-hip-rfc4423-bis/ https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5201-bis/ In

<    1   2