1. IEEE 802.21 MEDIA INDEPENDENT HANDOVER DCN: 21-09-0114-00-0000
Title: Minor Issues on – 2008 Specification
Date Submitted: July , 2009
Presented at IEEE session #33 in San Francisco
Authors or Source(s):
Yoshihiro Ohba (Toshiba)
Abstract: This contribution describes minor technical issues on IEEE – 2008 standard that have been found as of the submission date of the contribution. It is expected that a new revision of IEEE specification address these issues.

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 stated in Section 6 of the IEEE-SA Standards Board bylaws < and in Understanding Patent Issues During IEEE Standards Development

3. Inconsistency in LINK_PARAM
LINK_PARAM is derived from
SEQUENCE(
LINK_PARAM_TYPE,
CHOICE(LINK_PARAM_VAL,
QOS_PARAM_VAL))
LINK_PARAM_VAL is derived from UNSIGNED_INT(2)
However, when LINK_PARAM_GEN is chosen as LINK_PARAM_TYPE, Signal Strength is one parameter type in LINK_PARAM_GEN and its type of SIG_STRENGTH which is derived from CHOICE(INTEGER(1), PERCENTAGE)
There can be other parameter types that does not fit UNSIGNED_INT(2)

4. Location CELL_ID
p237 Location "CELL_ID" (UNSIGNED_INT(4)) is not unique
LOCATION: CHOICE(
CIVIC_LOC,
GEO_LOC,
CELL_ID)
Should be revised to:
3GPP_2G_CELL_ID,
3GPP_3G_CELL_ID)
Similar change is needed for the corresponding property in the RDF schema

5. PICS
When one implements only CS, i.e., Link_Configure_Threshold is implemented, then it won't be able to get the corresponding Link_Parameters_Report
Detailed conditioning is needed

6. MIH_Net_HO_Candidate_Query
Is MIH_N2N_HO_Query_Resources required after MIH_Net_HO_Candidate_Query?
“ General” says its required
But in "Effect on receipt” there is no text to invoke MIH_N2N_HO_Query_Resources

7. TLV Length Field The image and the text is not consistent.
“length of LENGTH” in Figure 19 should be revised to “length of LENGTH minus one” to be consistent with the following description: “The MSB of the first octet of the Length field is set to the value ‘1’ and the remaining seven bits of the first octet indicate the number of octets that are appended further”

8. RDF Schema
The schema is currently under review in IETF for allocation of persistent URI for the schema
draft-ohba-802dot21-basic-schema
Internet AD Jari Arkko is shepherding the Internet-Draft
Several issues with basic schema were found and already addressed in the latest revision of I-D
Several new issues with data types have been found (see next slide)
The issues should be reflected to basic schema as well
Once an informational RFC is published for the I-D, Annex H of the basic schema should be replaced with the reference to RFC

9. Issues with Data Types
NET_CAPS Bit 0 (Security) the definition “Indicates that some level of security is supported when set” is very weak
It should say “Indicates link-layer ciphering is used when set”
TYPE_EXT (of type OCTET_STRING) needs allocation policy for the extended network types. It was suggested to have IANA allocation
NETWORK_ID content for is unclear while NET_AUX_ID content for is clear (HESSID)
Either specify that NETWORK_ID content for is SSID, or explicitly state that NETWORK_ID content can be any string
Input from WG members is needed for these issues to answer to the shepherding AD of the basic schema I-D

10. Annex C
In Annex C (informative) handover procedures, the Figure C.1 - Mobile-initiated handover procedure depicts the traffic sequence for Resource release. (page 191)
However, the message from Candidate network 1 PoS-C1: MIH_N2N_HO_Complete request, is sent directly to Serving network MIH user, instead of PoS-S. And the subsequent steps are also incorrect