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

AW: [802.21] LINK_EVENT_SOURCE ?



Title: Nachricht
Hi Mathieu,
 
as far as I understood, it is the source ID from where the link event is generated.
 
I still have a feeling that there should be source and destination ID in all the primitivies.
Well, in some cases some IDs may not be needed, but i feel this is good to have.
This issume will become much more complex if we think of IS primitives.
Just a note: all the general primitivies of ES, CS, IS (not in section 7) look
like the same. I feel we have to modify them.
 
regards,
Kalyan
-----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 ?

Hi all,
 
just a clarification on the LINK_EVENT_SOURCE parameter that is included in every Event primitive:
 
From the draft:
 
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 ?
 
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 ?
 
 
 
Thanks a lot!
 
 
Mathieu.