IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Data Type Encoding Date Submitted: April 27, 2007 Presented at IEEE session #20 in Montreal Authors or Source(s): Yoshihiro Ohba, Subir Das, Yuu-Heng Alice Cheng, Miriam Tauil, Kenichi Taniuchi Abstract: This document describes problem with data type encoding in

IEEE 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 Section 6.3 of the IEEE-SA Standards Board Operations Manualhttp://standards.ieee.org/guides/opman/sect6.html#6.3

Issues Some value encoding rules for some TLVs are defined in IE definition (e.g., Link Type and QoS Parameters TLV values are defined in Section 6) and while others are defined in TLV definition in Section 8 There are a lot of duplicate value assignment in primitive definition and TLV definition (e.g, SupportMIHCommandList bitmap assignment in Sections 7 and 8) In Section 8.6, TLV type space is not unique across multiple messages This could make MIH protocol difficult to implement Requires 4 pieces of information (SID, Opcode, AID, TLV Type) to determine the actual “TLV Type” In Section 8.6, multiple TLVs in the same message point to the same TLV definition OldLinkIdentifer and NewLinkIdentifer in Section point to Link Identifier TLV that has floating Type value assignment –Notation Problem Nested TLV encoding can be redundant E.g., Link Identifier encoding

A Possible Approach Define data types and their encoding rule in a common place A general idea is to move Table 22 to a normative Annex with adding encoding rule. Define IEs, TLVs and primitives using the data types Advantage: Duplicate format definition can be avoided The specification can be more readable (detailed type definitions are not in the main sections)

Data Type Table Example Data TypeDescriptionValid RangeEncoding Rule BITMAP(size)A bitmap of the specified size.…Each bit of a BITMAP(N) value [N=8*i, i=1, 2, …] is encoded as an N/8-octet value in order of significance. INTEGER(size)An integer of the specified size in number of octets. …Each octet of an INTEGER(N) value [N=1,2,..] is encoded in network-byte order into an N-octet field. LINK_TYPELINK_TYPE is derived form INTEGER(4) to represent a type of link …See Table X1 [currently Table 9] REVISIONREVISION is derived from BITMAP(64) to represent the release version of the standard. …See Table X1 [currently Table 9] LINK_IDA identifier of a link as defined by IEEE Consisting of: 1) link type, and 2) MAC address of MN. …See Table X2 [see below] TRANSPORT ADDRESS……… ……… AttributeTypeDescription Link TypeLINK_TYPEType of the link. MN MAC AddressTRANSPORT_ADDRESSA Mobile Node’s MAC address of the link. Table X2: LINK_ID Parameters

IE / TLV Value Definition Example General form: IE Example: Section Network Type TLV Example: Section Link Identifier Type=TYPE_IE_* or TYPE_TLV_*Length=length Value Name [DATATYPE] (Additional description) … Type=TYPE_IE_NETWORK_TYPELength=Variable Type [LINK_TYPE] Revision [REVISION] Type=TYPE_TLV_NETWORK_TYPELength=Variable Link Identifier [LINK_ID] Note that IE and TLV have different lengths in Type field.

Primitive Definition Example General form: PRIMITIVE_NAME.{request,indication,response,confirm} ( ParameterName1 [DATATYPE] (mandatory/optional), ParameterName2 [DATATYPE] (mandatory/optional), … ) Note: Parameter table is not needed.

TLV Type definition Example Type NameType ValueValue Type TYPE_TLV_LINK_ID1LINK_ID TYPE_TLV_OLD_LINK_ID2LINK_ID TYPE_TLV_NEW_LINK_ID3LINK_ID TYPE_TLV_MIH_EVENT_LIST4MIH_EVENT_LIST ………

Discussion There may be three options to take: Option 1: Ignore this proposal Option 2: Adopt this proposal Option 3: Think about use of ASN.1