From:
stds-802-21@ieee.org [mailto:stds-802-21@ieee.org] On Behalf Of Kalyan Koora
Sent: Thursday, December 15, 2005
9:05 AM
To: zze-Seamless PERESSE M ext
RD-RESA-REN; STDS-802-21@listserv.ieee.org
Subject: AW: [802.21]
LINK_EVENT_SOURCE ?
This issume will become much more complex
if we think of IS primitives.
[Vivek G Gupta]
Actually IS primitives may not be that bad at all (since
there are not that many of them anyway..just a request and a response..).
like the same. I feel we have to modify
them.
[Vivek G Gupta]
May be we should have a source and destination in all
primitives and just use N/A (Not Applicable) when one of the parameter is not
relevant.
However source and destination parameters are more
applicable only for remote events/commands.
It may be getting difficult to have a generalized representation
covering all cases for events and commands.
-----Ursprüngliche
Nachricht-----
Von: zze-Seamless PERESSE M ext
RD-RESA-REN [mailto:mperesse.ext@RD.FRANCETELECOM.COM]
Gesendet: Donnerstag, 15. Dezember
2005 17:10
An: STDS-802-21@listserv.ieee.org
Betreff: [802.21] LINK_EVENT_SOURCE
?
just a clarification on the LINK_EVENT_SOURCE parameter that
is included in every Event primitive:
LINK_EVENT_SOURCE is defined as follows.
{Local Node, Remote Node}. Local and remote is referred with respect to
origination of request
What does this mean ? Is it a list composed of
"Local Node" and "Remote Node", is it an identifier, what
is the purpose of this parameter
and how is it used in event primitives ?
[Vivek G Gupta]
With regard to support for remote link events this parameter
was indicating whether the event originated at local node or remote node.
Since we are considering making all link events local only,
and have corresponding MIH events as local or remote, we could remove this
parameter from all link layer primitives.
MIH Users receiving event notifications may need to know if
a particular event originated on local MIH node or at some other remote end. From
that perspective having this parameter in there helps satisfy this need.
Also, we are currently talking about MIH capability
discovery and registration on the ML. How will link event discovery and link
event registration (primitives already in the draft) be
integrated into the overall Capability Discovery and Registration
processes respectively ?? Or will it be totally independent ?
[Vivek G Gupta]
When MIH Function receives request for MIH Capability
discovery, the MIH function may use local link layer discovery primitives to discover
appropriate link layer capabilities and send an appropriate response.