RE: Link-layer Triggers Protocol draft

Hi Alper,


>The generator of the L2 trigger cannot assess whether this is interesting
>or not. It's up-to the consumer of the trigger to assess this. You are
>right,
>not all L2 events result in a L3 event. But this is not up-to the servers
>to decide...


The only information that the clients get as part of the triggers is the l2 address of the "other end". How can they use this information to make sure it is an L3 event?. The host would probably need some mapping(l2-l3) or protocol to find out if this is a l3 event.

>In either case, L2 address is the address of the "other end" of the link.
>For example, if trigger is received by the access router, the "other end"
>of the link is "access device" of the wireless client.

I understand the client aspect, how about the server?. How is it supposed to know it is servicing a host client or access router client?. This would entail that we have a version of host server and access router server since the servers need to provide different information in the trigger data.



Mohammed 

**********************Confidentiality Note**********************
Privileged/Confidential Information may be contained in this e-mail and any
attachment to it and may be covered by existing non-disclosure or
confidentiality agreements.
If you are not the addressee (or authorized to receive for the addressee),
you may not use, copy or disclose to anyone any information contained in
this e-mail.  If you have received this e-mail in error, please notify the
sender immediately by reply e-mail and delete it from your system.
Thank you very much.
*************************************************************


_______________________________________________
pilc mailing list
[email protected]
https://www1.ietf.org/mailman/listinfo/pilc
http://www.ietf.org/html.charters/pilc-charter.html
http://pilc.grc.nasa.gov/