Hi Satoru, Inline please.
On Thu, Oct 18, 2012 at 11:47 PM, Satoru Matsushima < [email protected]> wrote: > Hui, > > On Thu, Oct 18, 2012 at 11:21 PM, Hui Deng <[email protected]> wrote: > > Hello Satoru, > > > > Thanks a lot for your comments, > > > > I guess it is not clear in our document, because chapter says. > > 3. Supporting EAP authencation in Wifi network . . . . . . . . . . 3 > > 3.1. Scenario Description . . . . . . . . . . . . . . . . . . . 3 > > 4. The scope of definition of split MAC mode . . . . . . . . . . . 4 > > Section 4 could lead people think that we are only working on the split > MAC, > > actually the local MAC don't need define the scope, > > > > Thanks your clarification. In addition, split-mac mode is also assumed > in section 3. > > > we specify both split and local MAC. > > > > My question is why local-mac couldn't solve your problem. As far as I > know, any local-mac mode AP needs to encapsulate EAP packet into > neither CAPWAP-DATA nor CTL as far as i understand, the local-mac mode will encapsulate the CAPWAP message into 802.3 header. +-+wireless frames +-+ 802.3 frames +-+ | |----------------| |--------------| | | | | | | | | |----------------| |--------------| | | |wireless PHY/ | | CAPWAP | | | | MAC sublayer | | | | +-+ +-+ +-+ STA WTP AC > because AP send messages to AAA server as > EAP authenticator. > This way, when UE handover between different AP, the security session cannot be switched to the new AP. --cz > > cheers, > --satoru > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg >
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
