Hi Fred, The below comment from you made me thinking. I must admit I'm not much familiar with Aero, have not seen its references in CDMA, WiMAX, CableLabs, WLAN or LTE architectures. But, if it has all the mobility features and you believe this can conclude the WG, I thought I will explore this a bit. I started reviewing the charts that you sent and started browsing some of the specs. Few high-level questions, if you can answer or point me to some documents, it will be great.
1.) What is the interface between the Aero Server and the client ? Is it just DHCPv6 ? There is no other signaling interface ? 2.) What is the service authorization model for a Aero client ? How is the client identified by the server ? What is the security model ? 3.) Can the Aero solution support IP nodes that do not have Aero client stack ? 4.) If a mobile or a cable SP deploys Aero, where is their point of control ? Where can they do Accounting, Lawful interception ? 5.) I assume Aero client can be IPv4 or an IPv6 device ? For an IPv4-only legacy device, is the interface DHCPv4 ? 6.) Can an operator enable location-based services for a Aero client ? 7.) How can an operator enable IP Flow Mobility type features in an Aero system ? 8.) Taking a mobile router scenario, how does Aero client support multi-tenancy ? Is there a single tunnel between the client and the server ? Regards Sri On 9/10/14 11:43 AM, "Templin, Fred L" <fred.l.temp...@boeing.com> wrote: >Hi Jouni, > >I'd like to propose a slightly different charter: > > "AERO already solves distributed mobility management and provides a > a comprehensive mobility solution for any mobile device. AERO should > therefore be approved as the mobility management solution for DMM. > Publication of AERO will therefore conclude the working group's > activity." > >Can we have this on the agenda? > >Thanks - Fred >fred.l.temp...@boeing.com > >> -----Original Message----- >> From: dmm [mailto:dmm-boun...@ietf.org] On Behalf Of Jouni Korhonen >> Sent: Wednesday, September 10, 2014 11:37 AM >> To: sarik...@ieee.org >> Cc: Dapeng Liu; dmm@ietf.org >> Subject: Re: [DMM] DMM Interim call #2 - agenda forming >> >> >> What do you mean by no agenda? To me it clearly says we use the call #2 >> for setting up the work split. >> >> - Jouni >> >> 9/10/2014 9:06 PM, Behcet Sarikaya kirjoitti: >> > Jouni, why don't we cancel this one (#2) and do the next one (#3) with >> > an agenda? >> > I hope Alper can attend :-) >> > >> > Regards, >> > >> > Behcet >> > >> > On Wed, Sep 10, 2014 at 1:02 PM, Jouni Korhonen >><jouni.nos...@gmail.com> wrote: >> >> >> >> It seems I sent this to a wrong receiver.. that explains why it did >>not >> >> appear on the list. >> >> >> >> - Jouni >> >> >> >> -------- Alkuperäinen viesti / Orig.Msg. -------- >> >> Aihe: DMM Interim call #2 - agenda forming >> >> Päiväys: Mon, 08 Sep 2014 23:43:24 +0300 >> >> Lähettäjä: Jouni Korhonen <jouni.nos...@gmail.com> >> >> Vastaanottaja: dmm-...@tools.ietf.org >> >> CC: jouni.nos...@gmail.com, Dapeng Liu <liudap...@chinamobile.com> >> >> >> >> Folks, >> >> >> >> The next interim is close. Assuming there are no overwhelming amount >>of >> >> comments to the re-charter text, we are ready to start setting up the >> >> work split on the solution space! Remember the discussion and the >> >> minutes from the IETF#90 Friday session. No other agenda items are >> >> planned for the next interim. >> >> >> >> - Jouni & Dapeng >> >> >> >> >> >> _______________________________________________ >> >> dmm mailing list >> >> dmm@ietf.org >> >> https://www.ietf.org/mailman/listinfo/dmm >> >> _______________________________________________ >> dmm mailing list >> dmm@ietf.org >> https://www.ietf.org/mailman/listinfo/dmm >_______________________________________________ >dmm mailing list >dmm@ietf.org >https://www.ietf.org/mailman/listinfo/dmm _______________________________________________ dmm mailing list dmm@ietf.org https://www.ietf.org/mailman/listinfo/dmm
