HIPIG Minutes for May 2011

Total Page:16

File Type:pdf, Size:1020Kb

HIPIG Minutes for May 2011

五月, 2011 IEEE P802.15-15-11-0393-00-0hip IEEE P802.15 Wireless Personal Area Networks

Project IEEE P802.15 Working Group for Wireless Personal Area Networks (WPANs)

Title HIPIG Minutes for May 2011

Date 13 May, 2011 Submitted

Source [Robert Moskowitz] Voice: [+1-248-219-2059] [Verizon] Fax: [+1-248-968-2824] E-mail: [ [email protected] consult.com ] Re: HIPIG Minutes for May 2011

Abstract HIPIG Minutes for May 2011

Purpose Official Minutes

Notice This document has been prepared to assist the IEEE P802.15. It is offered as a basis for discussion and is not binding on the contributing individual(s) or organization(s). The material in this document is subject to change in form and content after further study. The contributor(s) reserve(s) the right to add, amend or withdraw material contained herein.

Release The contributor acknowledges and accepts that this contribution becomes the property of IEEE and may be made publicly available by P802.15.

Submission Page 1 Robert Moskowitz, Verizon 五月, 2011 IEEE P802.15-15-11-0393-00-0hip

Attendance:

Robert Moskowitz – Verizon Cao Zhen – China Mobile Paul Lambert – Marvell

IPR:

Certicom has submitted IPR on IETF ID 5201-bis (HIP-BEX): https://datatracker.ietf.org/ipr/1541/

It is not known at this time if similar claims will be made on HIP-DEX.

Also it needs to be clarified what their claims are and if they are valid as HIP with RSA identities predates the patents and anyone 'conversant in the arts' sees the logical use of ECDSA as well.

Post meeting update:

The first listed patent DOES impact HIP-DEX and can be avoided by explicitly requiring Elliptic Curves the a co-factor of 1. Even though the curves currently defined in both 5201-bis and HIP-DEX all have co-factors of 1, this requirement MUST be explicit in the standard.

Compared Moskowitz presentation using 4e Multipurpose Frames to Cao presentation using modifed ASSOCIATE Frames. Selected Multipurpose Frames as they work, also support HIP UPDATE frames, other KMPs, and will be easier to get WG approval.

Submission Page 2 Robert Moskowitz, Verizon 五月, 2011 IEEE P802.15-15-11-0393-00-0hip Agreed that work is on KMP for .15.4 and not just HIP KMP. HIP would be the default KMP.

Discussed KMP packet length compared to 15.4 MTU. Although 15.4g adds larger MTU support, providing a mechanism to 'chain' a number of Multipurpose Frames together in a shim layer between the MAC and KMP provides additional flexibility.

Discussed how the KMP SHOULD provide the Short addresses as soon as possible. The HIT COULD be truncated to do this, much as 6lowpan uses Ipv6 addresses, as the HIT IS an IPv6 address.

Cao presented a hash chain algorithm for VERY lightweight keying. This will be further investigated. It may either become a exchange mode in HIP or its own KMP.

Single-hop and Multi-hop security was discussed. 15.4 does NOT provide a Multi-hop forwarding mechanism so a 15.4 KMP could only provide single- hop keying. Multi-hop should be done in the IETF either in core or roll.

Between now and the July meeting a paper will be produced expanding on all these points along with a draft PAR and 5-part. The goal for the July meeting will be to accept a specific framework for KMP, move the HIP IG to a KMP SG, and 1st reading of the PAR with November approval in mind.

Submission Page 3 Robert Moskowitz, Verizon

Recommended publications