> > Hi Kamala, > > Our goal is to keep the AP-SAI have as much common modeling as the current > SAI .. > > however, the biggest difference (new SAI IF enhancement) would be modeling > the wireless interface (802.11) on such SOCs ... > e.g. > Phy, > RF channel, > hwmode, > htmode, > chanbw, > txpower, > antenna-tilt, > DFS, > beacon, > MCS settings, > BSSID, > SSID-name, > > Beyond that different Wi-Fi SoC providers have various level of > capabilities exposed through custom APIs .. e.g Broadcom supports > > frambursts, maxassociation (# of clients), slottime etc. > > As you can see, all of the above should be modeled as a new "api_type" for > SAI ; > > While we can reuse other API types like modeling Tunnel types etc.. > > > At least that is my initial thought process .. but then i am sure this > will change as we progress work .. > > > > BR > Rajat Ghai > CTO > Benu Networks > > > > > On Thu, Mar 24, 2016 at 12:22 PM, Kamala Subramaniam < > kasu...@microsoft.com> wrote: > >> Hi Rajat, >> >> >> >> When you mean branch off of SAI are you planning on using SAI like >> objects/APIs/attributes like the CRUD model? The abstraction you are >> working on will be different from actually abstracting a pipeline for >> switching ASICs. However if you plan on modeling it like the current SAI, >> in the future I think we can start to benefit from the ecosystem that will >> form around having similar APIs such as telemetry, etc. >> >> >> >> I would like to be involved in the initial stages to see if there is a >> way SAI and AP-SAI can benefit each other. >> >> >> >> Thanks, >> >> Kamala >> >> >> >> *From:* opencompute-networking-boun...@lists.opencompute.org [mailto: >> opencompute-networking-boun...@lists.opencompute.org] *On Behalf Of *Paul, >> Devashish >> *Sent:* Tuesday, March 22, 2016 12:49 PM >> *To:* Carlos Cardenas <car...@cumulusnetworks.com>; Rajat Ghai < >> rajatg...@gmail.com> >> *Cc:* ocp-tel...@lists.opencompute.org; Rajat Ghai <rg...@benunets.com>; >> Craig White <craig.white....@gmail.com>; opencompute-networking < >> opencompute-networking@lists.opencompute.org> >> *Subject:* Re: [Opencompute-networking] Work Item proposal for OCP Wi-Fi >> AP >> >> >> >> Carlos, >> >> >> >> That’s is correct. Starting broad and then target to specific >> applications is fine. I just wanted people to be aware that the Telco >> charter which is being edited by the leads (as we speak) is broad enough to >> cover this use case. >> >> >> >> Dev >> >> >> >> *From:* Carlos Cardenas [mailto:car...@cumulusnetworks.com >> <car...@cumulusnetworks.com>] >> *Sent:* Tuesday, March 22, 2016 10:49 AM >> *To:* Paul, Devashish; Rajat Ghai >> *Cc:* ocp-tel...@lists.opencompute.org; Jeff Catlin; Craig White; Rajat >> Ghai; Ayham Ereksousi; opencompute-networking >> *Subject:* Re: [Opencompute-networking] Work Item proposal for OCP Wi-Fi >> AP >> >> >> >> Dev, >> >> >> >> Thank you for your interest in this new endeavor for open networking. >> >> >> >> The access / branch / campus networking piece will stay in the networking >> group but all is welcome to contribute to it. >> >> >> >> Once the ecosystem has been established, we expect the Telco group to >> take what we have and focus it to their needs (like what they do for OCP >> servers and switches today); this is the same model the HPC group that you >> lead does as well, correct? >> >> >> >> It's easier to start broad and focus later than the other way around >> wouldn't you agree? >> >> >> >> +--+ >> Carlos >> >> *From:*devashish.p...@idt.com >> >> *Sent:*March 22, 2016 7:04 AM >> >> *To:*rajatg...@gmail.com >> >> *Cc:*jeff_cat...@edge-core.com; ayham.erekso...@gmail.com; >> car...@cumulusnetworks.com; craig.white....@gmail.com; >> opencompute-networking@lists.opencompute.org; rg...@benunets.com; >> ocp-tel...@lists.opencompute.org >> >> *Subject:*RE: [Opencompute-networking] Work Item proposal for OCP Wi-Fi >> AP >> >> >> >> Rajat, the charter for OCP Telco is currently in definition/being >> written. From what I recall the framework that Craig White and Bill Carter >> have discussed would not exclude that. Perhaps one of them will have a >> chance to comment since I missed a few of the meetings/discussion at the >> Summit. >> >> >> >> Dev >> >> >> >> *From:* Rajat Ghai [mailto:rajatg...@gmail.com <rajatg...@gmail.com>] >> *Sent:* Tuesday, March 22, 2016 9:59 AM >> *To:* Paul, Devashish >> *Cc:* Jeff Catlin; Ayham Ereksousi; Carlos Cardenas; Craig White; >> opencompute-networking@lists.opencompute.org; Rajat Ghai; >> ocp-tel...@lists.opencompute.org >> *Subject:* Re: [Opencompute-networking] Work Item proposal for OCP Wi-Fi >> AP >> >> >> >> Hi Paul, >> >> >> >> Sorry i haven't yet participated in the OCP Telco group. But, this work >> can/does apply to Telco/SPs as well. >> >> >> >> Having said that, the goal of this OCP-Networking proposal / sub-group is >> *not* only to create requirements but contribute working code as well ; >> (hopefully from many participants including ourselves). >> >> >> >> Does OCP-Telco plan to to host/provide 'working reference code ' as part >> of its charter ? >> >> >> >> BR >> Rajat Ghai >> >> CTO >> >> Benu Networks >> >> >> >> >> >> On Tue, Mar 22, 2016 at 8:24 AM, Paul, Devashish <devashish.p...@idt.com> >> wrote: >> >> Hey guys, >> >> >> >> The OCP Telco group is formulating its charter and it includes >> technologies for the access network. While not typical wireless or >> wireline access network, there may be a better fit over there to cover >> WIFI. Perhaps Craig White who is holding the lead can comment. >> >> >> >> Dev >> >> >> >> *From:* opencompute-networking-boun...@lists.opencompute.org [mailto: >> opencompute-networking-boun...@lists.opencompute.org] *On Behalf Of *Jeff >> Catlin >> *Sent:* Tuesday, March 22, 2016 7:30 AM >> *To:* Ayham Ereksousi; Carlos Cardenas >> *Cc:* Rajat Ghai; opencompute-networking@lists.opencompute.org >> >> >> *Subject:* Re: [Opencompute-networking] Work Item proposal for OCP Wi-Fi >> AP >> >> >> >> Obviously we would be interested in participating as well J >> >> >> >> Jeffrey D Catlin >> >> Associate Vice President of Technology >> >> Accton Technology Corporation >> >> jeff_cat...@accton.com >> >> 603-531-1286 >> >> >> >> *From:* Ayham Ereksousi [mailto:ayham.erekso...@gmail.com >> <ayham.erekso...@gmail.com>] >> *Sent:* Monday, March 21, 2016 10:19 PM >> *To:* Carlos Cardenas >> *Cc:* Rajat Ghai; opencompute-networking@lists.opencompute.org; Jeff >> Catlin; Rajat Ghai >> *Subject:* Re: [Opencompute-networking] Work Item proposal for OCP Wi-Fi >> AP >> >> >> >> I'm interested in Wi-Fi subgroup. >> >> >> >> Ayham >> >> >> >> On Mon, Mar 21, 2016 at 8:09 PM, Carlos Cardenas < >> car...@cumulusnetworks.com> wrote: >> >> Hey Rajat, >> >> >> >> I don't think you're jumping the gun (carpe diem and such). >> >> >> >> As one the few members that have expertise in this field, would y'all >> mind assist in steering this 'sub-group'? >> >> >> >> Is there any interest from others willing to participate in the wireless >> subgroup? >> >> >> +--+ >> >> Carlos >> >> >> >> On Mon, Mar 21, 2016 at 4:55 PM, Rajat Ghai <rajatg...@gmail.com> wrote: >> >> Hi, >> >> >> >> I might be jumping the gun here a little bit , however we @ Benu Networks >> are very interested in pursuing, facilitating & participating in Open >> Branch platforms (specially an Open Wi-Fi AP). >> >> >> >> We believe that open desegregated Wi-Fi AP can kickstart a new wave of >> innovation that can radically disrupt the branch office / SMB , similar to >> what is already been happening to OCP based Data Center Switching. >> >> >> >> We would love to open up a discussion in the group and see if we can find >> fellow travelers to join us. As a starting point we'd like to offer a high >> level proposal the looks like the one shown below : >> >> >> >> >> >> >> Wi-Fi APs are not your typical switches as 802.11 has big WLAN (RF) >> component that needs a whole different class of management e.g. >> >> >> >> - ICM : Interference Counter Measure (Ability to automate interference >> mitigation) >> >> - 802.1r fast mobility (Ability to provide fast handovers from one AP to >> another) , >> >> - 802.11k handoff steering (Ability to interact with user >> devices for AP attach) >> >> - Band steering policies (2.4 Ghz v/s 5 GHz) >> >> - Network (SSID) steering policies (Virtual SSID scenarios) >> >> - Other Network policies like MCS threshold settings for better QoE & >> Service discovery >> >> - Wi-Fi Telemetry, >> >> >> >> Apart from WLAN specific interface, the Wi-Fi AP also has networking >> setup (bridges, tunnels etc.) >> >> that are also common to non-Wi-Fi capable branch switches . >> >> >> >> Finally, Wi-Fi APs also require to have a branch IP router capability >> that includes other networking stacks that are not present in DC switches >> e.g. UPnP (DLNA), PCP etc. >> >> >> >> We could create a SAI equivalent for Branch {in this case i have called >> it *A-SAI i.e. AP SAI*) ; Such SAI would be common to all Wi-Fi SoCs >> e.g. from Broadcom , Qualcomm, Intel etc. >> >> >> >> If the group agrees to move it forward, we (Benu) would be happy to >> facilitate the process as well as contribute user land components mentioned >> above. >> >> >> >> BR >> >> Rajat Ghai >> >> CTO >> >> Benu Networks >> >> >> _______________________________________________ >> opencompute-networking mailing list >> Unsubscribe: >> http://lists.opencompute.org/mailman/options/opencompute-networking >> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.opencompute.org%2fmailman%2foptions%2fopencompute-networking&data=01%7c01%7ckasubra%40microsoft.com%7c831d6435059f49acfd2a08d3528d82fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=DUOzaAGCGt1BPsBTbX%2bwMxqLgbcXd%2fSfzfKivXa2uXM%3d> >> >> opencompute-networking@lists.opencompute.org >> http://lists.opencompute.org/mailman/listinfo/opencompute-networking >> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.opencompute.org%2fmailman%2flistinfo%2fopencompute-networking&data=01%7c01%7ckasubra%40microsoft.com%7c831d6435059f49acfd2a08d3528d82fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=VKOR7bYbpNbDEnscldrGYTgbHvHb6SqJHXpFBor8JnY%3d> >> >> >> >> >> _______________________________________________ >> opencompute-networking mailing list >> Unsubscribe: >> http://lists.opencompute.org/mailman/options/opencompute-networking >> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.opencompute.org%2fmailman%2foptions%2fopencompute-networking&data=01%7c01%7ckasubra%40microsoft.com%7c831d6435059f49acfd2a08d3528d82fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=DUOzaAGCGt1BPsBTbX%2bwMxqLgbcXd%2fSfzfKivXa2uXM%3d> >> >> opencompute-networking@lists.opencompute.org >> http://lists.opencompute.org/mailman/listinfo/opencompute-networking >> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2flists.opencompute.org%2fmailman%2flistinfo%2fopencompute-networking&data=01%7c01%7ckasubra%40microsoft.com%7c831d6435059f49acfd2a08d3528d82fb%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=VKOR7bYbpNbDEnscldrGYTgbHvHb6SqJHXpFBor8JnY%3d> >> >> >> > > > > -- > Best Regards > Rajat Ghai > CTO > Benu Networks (www.benunets.com) > > >
_______________________________________________ opencompute-networking mailing list Unsubscribe: http://lists.opencompute.org/mailman/options/opencompute-networking
opencompute-networking@lists.opencompute.org http://lists.opencompute.org/mailman/listinfo/opencompute-networking
