Re: [DNA-BOF] AP5: cataloguing L2 Hints for DNA.

[Greg Daley <greg.daley@eng.monash.edu.au>]

Hi Daniel,

I've got two quick points.

* we shouldn't be using the word trigger in the document

* we're looking at existing procedures, which don't
   modify L2.

Further work in the future which co-operates with
link-layer authorities may provide guidelines
for L2 systems.

We have to see what we can get as hints today from
deployed systems.

Greg



Soohong Daniel Park wrote:
> Hi all
> 
> At this stage, I am wondering below issue can be discussed
> at DNA for L2 Hint issues.
> 
> Could you let me know your view on this ?
> 
> I am trying to write a brief mention as follows
> 
> 1. Problem statement
> 
> The L2 trigger in WLAN might be based on the change between
> APs. But a change of AP on the same subnet does not require
> a change of AR since AR is L2 reachable from the MN connected
> to any APs. It should be required for the MN to know whether it
> changes AP or AR. However, in the existing mechanism, the MN
> could not know whether it changes AP or AR. Thus, when the MN
> changes AP without change of AR, there are some redundant
> traffics. These redundant traffics might be remarkable when there
> are many MNs that are now connecting to the PAR.
> 
> 2. Solution statement
> 
> The beacon message given by AP is defined newly by adding the
> ARID (AR's Identity) to the reserved field. Other fields in the beacon
> messages are not affected since the existing reserved field is used
> for.
> 
> 
> 
> Thanks in advance.
> 
> 
> Daniel (Soohong Daniel Park)
> Mobile Platform Lab,SAMSUNG Electronics
>