IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN:21-07-0052-00-0000 Title: IETF Liaison Report Date Submitted: March 15, 2007 Presented at IEEE 802.21 session #19 in Orlando Authors or Source(s): Yoshihiro Ohba Abstract: This is IETF Liaison Report on March 2007 21-07-0052-00-0000

IEEE 802.21 presentation release statements This document has been prepared to assist the IEEE 802.21 Working Group. 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. The contributor grants a free, irrevocable license to the IEEE to incorporate material contained in this contribution, and any modifications thereof, in the creation of an IEEE Standards publication; to copyright in the IEEE’s name any IEEE Standards publication even though it may include portions of this contribution; and at the IEEE’s sole discretion to permit others to reproduce in whole or in part the resulting IEEE Standards publication. The contributor also acknowledges and accepts that this contribution may be made public by IEEE 802.21. The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual <http://standards.ieee.org/guides/opman/sect6.html#6.3> and in Understanding Patent Issues During IEEE Standards Development http://standards.ieee.org/board/pat/guide.html>  21-07-0052-00-0000

MIPSHOP WG WG Last Call on MIH problem statement draft has issued http://www.ietf.org/internet-drafts/draft-ietf-mipshop-mis-ps-00.txt 802.21 WG members are strongly encouraged to read the draft and send feedback to yohba@tari.toshiba.com or to the MIPSHOP Mailing List From 802.21 perspective, it is important to make sure that general transport requirements described in the MIPSHOP draft cover the MIH protocol transport requirements The WG Last Call expires on April 2, 2007 Design Team will present something IETF68 next week 21-07-0052-00-0000

HOKEY (Handover Keying) WG Interim Meeting in January 23 After Interim Meeting there is a consensus call, which created a lot of discussions Re-authentication will be based on “Code-based” approach (defining new EAP Codes to support re-auth) Most optimized Modification to EAP is needed Modification to EAP lower-layer is needed Discussion on top-level key hierarchy Most plausible solution: EMSK  (DSRK, USRK, DUSRK) EMSK: Extended Master Session Key DSRK: Domain-Specific Root Key USRK: Usage-Specific Root Key 3-party key distribution issue was raised and being discussed In EAP keying framework, security properties of MSK key distribution heavily depends on deployment of a AAA protocol Some people want to have a true 3-party key distribution protocol for HOKEY 21-07-0052-00-0000