Hi Behcet, How do you mean to submit it as a solution draft to dmm? That is essentially what I am already proposing.
Thanks - Fred From: Behcet Sarikaya [mailto:[email protected]] Sent: Monday, March 17, 2014 5:37 PM To: Templin, Fred L Cc: Jouni Korhonen; [email protected]; [email protected] Subject: Re: [DMM] DMM WG next steps Hi Fred, Why don't you submit it as a solution draft to dmm? Then you can push for your draft instead of arguing for something that we don't know what. Regards, Behcet On Mon, Mar 17, 2014 at 1:31 PM, Templin, Fred L <[email protected]<mailto:[email protected]>> wrote: Hi Jouni, > -----Original Message----- > From: Jouni Korhonen > [mailto:[email protected]<mailto:[email protected]>] > Sent: Saturday, March 15, 2014 9:04 PM > To: Templin, Fred L > Cc: [email protected]<mailto:[email protected]>; > [email protected]<mailto:[email protected]> > Subject: Re: [DMM] DMM WG next steps > > Fred, > > On Mar 11, 2014, at 11:48 PM, "Templin, Fred L" > <[email protected]<mailto:[email protected]>> wrote: > > > Hi Jouni, > > > > I think AERO fits paragraph 3 of the proposed new charter. AERO is a > > mobility solution for IPv6, where each node gets at least a /64. It > > has in-built route optimization, and can run over either IPv6 or IPv4 > > networks as a "link layer" for mobility. AERO expects a distributed > > mobility management environment, where a network of servers and > > relays keeps track of mobile node locations without single point > > of failure concerns. > > > > AERO is somewhat like MIPv6, but differs in that it treats the > > underlying network as a link-layer for IPv6 using a non-broadcast > > multiple access (NBMA) interface model. AERO uses IPv6 ND messaging > > and the IPv6 neighbor cache on the AERO "link" instead of MIPv6 > > mechanisms, and uses DHCPv6 PD exchanges instead of RS/RA for mobile > > node coordinations. The mobile nodes can therefore act as mobile > > routers and can provide stable network access for their connected > > networks (where each mobile node and its connected networks is > > a "site"). > > > > Here is a pointer to the spec. Please have a look and let me know > > what you think, > > There has been zero prior discussion or activity on this > topic in DMM that I recall. Furthermore, the current draft > seems to be a bis of RFC6707, driven by a single individual > and quite far in the preparation so I do not see a reason > involving this into the WG work. AERO is about mobility in general and distributed mobility management in particular. It also provides a solution to the route optimization problem cited in RFC5522 (which came from MEXT). AERO should be of interest to anyone interested in network mobilitiy, route optimization and distributed mobility management. IMHO, it is a better way of doing things than prior methods and this group would do well to consider it. Thanks - Fred [email protected]<mailto:[email protected]> > - JOuni > > > > > > https://datatracker.ietf.org/doc/draft-templin-aerolink/ > > > > Thanks - Fred > > [email protected]<mailto:[email protected]> > > > >> -----Original Message----- > >> From: dmm [mailto:[email protected]<mailto:[email protected]>] On > >> Behalf Of Jouni Korhonen > >> Sent: Wednesday, March 05, 2014 2:10 AM > >> To: [email protected]<mailto:[email protected]> > >> Cc: [email protected]<mailto:[email protected]> > >> Subject: [DMM] DMM WG next steps > >> > >> Folks, > >> > >> DMM WG has done some progress lately. The requirements document has > >> already left the building and the gap analysis is heading to WGLC as > >> we speak. It is about the time to think what we should do next now > >> that we have grown out of the infancy. > >> > >> A smaller group of mobility enthusiasts have been discussing about > >> possible next steps and how the possible new charter would look like. > >> The current very draft text template can be found here: > >> https://github.com/jounikor/dmm-re-charter > >> > >> As you can see, we are still in early stages and all input it welcome. > >> Obviously, possible re-chartering depends on many things. For example, > >> things like getting the gap analysis out of the WG and what the IESG > >> says. Nothing has been fixed or decided yet. Anyhow, we will start the > >> discussion on re-chartering with the expectation that the DMM WG will > >> re-charter and continue developing new solutions and/or enhancements > >> in the IP mobility space. > >> > >> - Jouni & Dapeng > >> > >> _______________________________________________ > >> dmm mailing list > >> [email protected]<mailto:[email protected]> > >> https://www.ietf.org/mailman/listinfo/dmm _______________________________________________ dmm mailing list [email protected]<mailto:[email protected]> https://www.ietf.org/mailman/listinfo/dmm
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
