Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

RE: How to transport MIH information from client to server

 

 

From: stds-802-21@ieee.org [mailto:stds-802-21@ieee.org] On Behalf Of Parameshwar Hegde
Sent: Monday, December 19, 2005 4:59 AM
To: STDS-802-21@listserv.ieee.org
Subject: How to transport MIH information from client to server

 

Hi,

 

I am new to this forum. Please give me pointers to email/document, if these questions are already addressed or please let me know if these topics are not in the scope of this forum.

[Vivek G Gupta]

Please refer to the current version of the 802.21 draft for more details. However currently the draft is restricted to 802.21 members only.

These topics are very much in scope of this forum.

 

My questions are,

 

  1. How do I transport MIH headers and parameters from handset to server and vice-versa.

[Vivek G Gupta]

Discussions are currently underway in 802.21 and even in other industry bodies like IETF regarding this.

If you end up using L3 transport between handset and server, the IETF MIPSHOP group is looking into defining a L3 protocol for supporting MIH services.

For L2 transport we have an initial definition of MIH protocol that can be encapsulated in L2 data frames of specific link layer technologies.

Please look into section 8 of current 802.21 draft for more details.

 

  1. Also does 802.21 recommends which protocol to use (like SIP etc) to transport MIH information between handset and server.

[Vivek G Gupta]

SIP is a higher layer mobility management type protocol. For transferring MIH messages between peer entities (at L3) a different protocol (based on current work at IETF) is likely to be used. The MIH protocol and transport is independent of SIP or any other mobility management protocol.

 

  1. Let us say if  SIP is used as protocol between handset and server, does 802.21 spec mandates how should this MIH information (header and parameters) should be transported, like what is the content type. Xml VS binary payload?.

[Vivek G Gupta]

For Information Service, we currently support both TLV type binary encoding and XML as well. This part is still under further development and we are expecting significant updates/progress in Jan meeting. Other MIH services are represented as binary payload between peer MIHF entities.

 

Thanks in advance

[Vivek G Gupta]

Thanx for your interesting questions and we look forward to your continued participation in 802.21.

 

--Parameshwar