1. IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN:21-07-0038-00-0000
Title: IETF Liaison Report
Date Submitted: January 18, 2007
Presented at IEEE session #18 in London
Authors or Source(s):
Yoshihiro Ohba
Abstract: This is IETF Liaison Report on January 2007

2. IEEE 802.21 presentation release statements
This document has been prepared to assist the IEEE 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
The contributor is familiar with IEEE patent policy, as outlined in Section 6.3 of the IEEE-SA Standards Board Operations Manual < and in Understanding Patent Issues During IEEE Standards Development

3. Internet-Draft on 802.21 Basic Schema
A new Internet-Draft (I-D) on Basic Schema was submitted to IETF:
draft-ohba-802dot21-basic-schema-00.txt
Why an I-D?
Basic Schema which is an RDF Schema requires a global registry maintained by IANA
Especially a persistent URL needs to be embedded in the schema definition, which currently says “URL_TO_BE_ASSIGNED”
A Specification (not a draft) is needed to register an RDF Schema with IANA
OTOH, specification will not be published until the “URL_TO_BE_ASSIGNED” part is replaced with the real URL
IANA suggested to write an Informational RFC on Basic Schema as a Specification
A possible plan:
Step 1: Keep updating the Basic Schema and the I-D until draft passes Sponsor Ballot
Step 2: Once Sponsor Ballot is passed, send a request to IESG to publish the I-D as an Informational RFC
Step 3: Once the request is approved by IESG, the required RDF Schema registry will be assigned and then the RFC will be issued
Step 4: Finally, make necessary changes to specification by replacing the entire Basic Schema definition in draft with a reference to the issued RFC

4. MIPSHOP WG MIH problem statement draft became a WG draft
draft-ietf-mipshop-mis-ps-00.txt
Design Team for MIH solution has been created
Robert Hancock (DT leader)
Srinivas Sreemanthula
Subir Das
Juan Carlos Zuniga
Telemaco Melia
Sam Xia
John Loughney (as NSIS and transport expert)

5. HOKEY (Handover Keying) WG
Two WG documents created
draft-ietf-hokey-reauth-ps-00.txt
EAP Re-authentication problem statement
draft-ietf-hokey-emsk-hierarchy-00.txt
Top-level EMSK key hierarchy
Two alternative approaches have been identified for re-authentication
Code-based approach (defining new EAP Codes)
Most optimized
Modification to EAP is needed
Modification to EAP lower-layer is needed
Type-based approach (defining a new EAP-method)
Less optimized
Modification to EAP is not needed
Modification to EAP lower-layer is not needed
A new draft to address backwards compatibility issue
draft-ohba-hokey-emu-eap-ext-00.txt
Extended EAP functionalities can be made available with still using existing EAP methods without any change
Interim meeting to be held on Jan 23 in San Jose