RE: [802.21] MIH Protocol message naming
Please erase my previous email and consider this one.
-----Message d'origine-----
De : Gupta, Vivek G [mailto:vivek.g.gupta@intel.com] Envoyé : jeudi 5 janvier 2006 14:34 À : zze-Seamless PERESSE M ext RD-RESA-REN; Junghoon Jee; STDS-802-21@listserv.ieee.org Objet : RE: [802.21] MIH Protocol message naming
> -----Original Message-----
> From: stds-802-21@ieee.org [mailto:stds-802-21@ieee.org] On Behalf Of
> zze- Seamless PERESSE M ext RD-RESA-REN
> Sent: Thursday, January 05, 2006 4:58 AM
> To: Junghoon Jee; STDS-802-21@listserv.ieee.org
> Subject: RE: [802.21] MIH Protocol message naming
>
> Hi Junghoon,
>
> I agree with your statement. I guess MIH Function Message should
> simply not have a "primitive like" naming scheme, since it is confusing.
>
> However, these messages will be transmitted using other media specific
> primitives: for example, in 16g (if I understood correctly), 4
> primitives (section 6.3.2.3 in the 16g draft) are used to transmit and
> receive MIH messages (1 Request and 1 Response in both directions). Another example:
> for 11 and 3 we can use LLC primitives to send MIH message over the
> data plane. For L3 transport, I guess MIH messages can be transported
> using an implementation specific access point (e.g. socket), since
> their is no such thing as a SAP within IETF.
>
> I think we should separate interactions that deal with the local MIH
> message passing (i.e. MIH_X primitives that MIH users will use and
> Link_X primitives the MIH Function will use) from the interactions
> that deal with the MIH message transport (i.e. Media (or Transport)
> Specific facilities the MIH Function will use to transport MIH messages).
[Vivek G Gupta]
MIH protocol shall only use MIH messages and not Link layers messages (since link layer messages shall be local only).
There is a lot of similarity in naming between Table-8 and Table-13 in the draft (SAP primitives and actual MIH messages) which may not be a bad thing.
Once the actual message headers, transport options/formats and message structure is settled, this shall become clearer. A lot of this should get addressed in next meeting.
[MP] Maybe what I said was not clear. Let's take a concrete example using the MIH_Link_Up message:
- A remote MME has subscribed to receive the MIH_Link_Parameters_Change event of a terminal.
- A link parameter changes on the terminal.
- Link Layer sends a Link_Parameters_Change.indication Event to the MIH.
- The MIH sends a message "MIH_Link_Parameter_Change" to the remote MIH Function using LLC using DL_UNITDATA.request(MIH Message)
- The message is transmitted to the MME's LLC.
- The LLC delivers the MIH message to the MIH using DL_UNITDATA.indication(MIH Message)
- The MIH processes the message and invokes the MIH_Link_Parameter_Change.indication that will notify the MME's MIH User of the event.
Here there are two types of "interactions" (and thus two types of primitives):
- What I called "interactions that deal with the local MIH message passing (i.e. MIH_X primitives that MIH users will use and Link_X primitives the MIH Function will use)
-> In the example these are the Link_Parameters_Change.indication and the MIH_Link_Parameters_Change.indication
- What I called "interactions that deal with the MIH message transport (i.e. Media (or Transport) Specific facilities the MIH Function will use to transport MIH messages).
-> In the example these are DL_UNITDATA.request/response primitives.
That's why I think we should not use the same name for the primitive we described and for the MIH protocol messages.
Because the primitives we have described don't are not involved in the transport of the message.
>
>
> Regards,
>
> Mathieu
>
> -----Message d'origine-----
> De : Junghoon Jee [mailto:jhjee@ETRI.RE.KR] Envoyé : mercredi 4
> janvier 2006 14:34 À : STDS-802-21@LISTSERV.IEEE.ORG Objet : [802.21]
> MIH Protocol message naming
>
> Hello,
>
> Currently, MIH protocol messages have a very similar naming scheme
> with MIH SAP primitives, like MIH_X_Y.request/response.
>
> Don't we have to define a separate naming scheme for MIH protocol
> messages?
>
> Regards,
> Junghoon