Hi Sri, Sure, that diagram could be redrawn with airplanes instead of automobiles. But, consider also the case where the airplane is a mobile router that connects into a home network provided by an aeronautical Internet service provider. Then, the passenger devices are also mobile routers with their own home networks. That would represent a single mobile-router-within-mobile-router nesting, but a "nested NEMO" case nonetheless.
We also care about use cases outside of just commercial aviation. Unmanned Air Systems, Unmanned Underwater Vehicles, MANETs, disaster relief networks, search and rescue networks, space-based systems etc. About tunnels within tunnels, we should be able to nest them to infinite levels of recursion where each level sees at least a 1500 MTU. None of this 1460 reduced to 1420 reduced to 1380, etc. until we run out of space - there should be a solid 1500 at every level with the ability to go bigger if the path MTU can support it. Thanks - Fred From: Sri Gundavelli (sgundave) [mailto:[email protected]] Sent: Wednesday, September 24, 2014 3:26 PM To: Templin, Fred L; [email protected] Subject: Re: Signaling Message Fragmentation Hi Fred, > I can think of use cases related to my industry, for example when a first > airplane provides an access link to a second airplane, the second airplane > provides an access link to a third airplane, etc. Seems to match the below use-case. I do not know the Boeing's or the broader Airline industry requirement, but personally I've not seen much interest for this. [cid:[email protected]] > In any case, however, whenever there is a fixed or mobile node connected to > an access link provided by a mobility anchor there is nothing stopping the > node from setting up a tunnel. Agree. That's there today; A MR on cellular access link, brings up a tunnel, which is on a transport tunnel. Regards Sri On 9/24/14 1:50 PM, "Templin, Fred L" <[email protected]<mailto:[email protected]>> wrote: Hi Sri, I remember the nested NEMO discussions, but at least for mobile network use-cases I have not seen any real deployment use-cases for that requirement. But, it will be good to have some discussions on that topic. I am thinking about the case when a mobile router A provides an access link for a mobile router B, which provides an access link for a mobile router C, which provides an access link for a mobile router D, etc. Each mobile router would coordinate with their home networks so that there would be tunnels-within-tunnels-within-tunnels-etc. I can think of use cases related to my industry, for example when a first airplane provides an access link to a second airplane, the second airplane provides an access link to a third airplane, etc. I think this might come up also for certain mobile ad-hoc scenarios. In any case, however, whenever there is a fixed or mobile node connected to an access link provided by a mobility anchor there is nothing stopping the node from setting up a tunnel. Then, there will be at least one tunnel-within-tunnel nesting. Thanks - Fred [email protected]<mailto:[email protected]>
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
