Hi Satoru, Thanks a lot for your review and proposal.
For the difference of split mac and Local Mac, it's all of matter of either 802.11 or 802.3 over CAPWAP Ctrl/Data Tunnel. For Local Mac, all functions will be based on AC, because 802.11 will be terminated at AC other than AP. This is the reason in our current PS draft to only define Split MAC function scope. Most of above has been stated by previous CAPWAP RFCs. For us, we have both of them deployed, it depends on the operators's strategy. If there is a problem about how Local MAC has Interop issue, this PS draft would be happy to include them, the draft is still open. I am think that AP pass all 802.11 to ACs, it may not have an issue, because 802.11 is a standard. Other problems described in current PS draft are not tighted with either Split MAC or Local MAC. thanks a lot for your review and discussion. Best regards, -Hui 2012/10/20 Satoru Matsushima <[email protected]> > Zhen, Rong, > > On Fri, Oct 19, 2012 at 6:47 PM, <[email protected]> wrote: > > > > Hello Satoru, > > > > If you kind help to start the survey, we can support you as well. > > > > I think I can help you anything what I can do. But if you want to > achieve your goal, you need much more support from the community. I > believe that the first step should be more clear problem statement. > One of my idea as ToC of the PS doc is following: > > 1. Why CAPWAP > 2. What is Split-MAC and Local-MAC in CAPWAP > 3. A clarification of use case of both Split-MAC and Local-MAC > 4. Problem statement > 5. A survey of current implementation of CAPWAP > 4.1. Supported mode and function > 4.2. Interoperability > 4.3. Scalability > 6. Goal of CAPWAP improvement > > > > By the way, network architecture of AP-AC-AAA has been proved good for > wifi > > handover performance, > > > > I think that you may answer in the document for how much improved > performance should be your target. > > 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
