Hi, Guillaume: The technical points that you have made are being investigated since the inception of the MANET networking. Probably, nearly two decades have been passed in MANET research and some of the commercial prototypes of MANETs have been implemented and their results are being published in various literatures.
My personal understanding is the, encouraged by experiences of prototype implementations of MANETs, their large-scale implementations are being followed between now and 2015 especially for military networks. And you are right, standards also need to follow hand-by-hand to obtain the fruits of MANETs in the commercial large-scale networks. In fact, it is challenges of the day going forward. The encouraging news is that MANET WG and AUTOCONFIG WG are developing the standards for MANETs in the network layer/IP layer. In directly, P2PSIP WG is also working for P2P SIP application that may be the first step which can be also be used for MANETs. However, more standard works also need to be done as follows: 1. Implications of call signaling messages for call setup/teardown/re-establishment as mobile users will move with almost randomly unpredictable speed and direction with constantly variable topology and, thereby, the needs for extensions of P2PSIP standards. 2. In MANETs, there is no such "guaranteed QOS," and thereby, new QOS standards such as "soft" QOS has been to be created. For example, IETF research group is working on "delay tolerant networking" etc. 3. The congest ions/interferences in MANETs will be pushed back to the application layer (e.g., Navy's SBIR). It means that dynamic encoding of bandwidth-intensive application like video and others with a given session. 4. Items 1, 2, and 3 indicate that there may not anything that is called layer-agnostic. That is, cross-layer mechanisms will be a part of the usual MANET networking. I do not want make the list long. The above items 1, 2, 3, and 4 reveal the fact that the days for the traditional networking are over for MANET networking. It also implies that an enormous amount of STANDARD works need to be done for full implementations of MANETs. Now to do the standard works you may need to follow as explained in my earlier email: * Wirte some drafts what works on standards need to be done related to MANETs * Suggest for extensions of P2PSIP, MANET, AUTOCONFIG, and NSIS WG for may particular standards that may be applicable for MANETs * If no existing WGs are suitable (e.g. X-layer) for any MANET topics, suggest to form new WGs writing some drafts explaining the needs and IETF management will be, I think, kind enough to provide chances for BOFs. Best regards, Radhika ----- Original Message ----- From: FORTAINE Guillaume Date: Saturday, April 5, 2008 14:01 Subject: Re: [P2PSIP] P2P SIP - Real-time Multimedia Services To: "Roy, Radhika R Dr CTR USA USAMC" Cc: [email protected], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] > Dear Mister Roy, > > You are Excellence and it's definitely an honor for me to be in > contact > with You Today > > There are various ways for P2P Networking : > > -US Army : > > DirecNet Portal > > > -DARPA : > > Home - *Delay Tolerant Networking Research Group* > > > -Open Source : > > > > > Layer-5 : > > *Real*-*time Multimedia Services Using Hybrid P2P SIP* > > > *Real-time Multimedia Services Using Hybrid P2P SIP* > Mo, Yijun; Wang, Fei; Huang, Benxiong; Luo, Fu > Communications and Information Technologies, 2006. ISCIT apos;06. > International Symposium on > Volume , Issue , Oct. 18 2006-Sept. 20 2006 Page(s):157 - 161 > Digital Object Identifier 10.1109/ISCIT.2006.339907 > *Summary:*SIP becomes one most poplar protocol in real-time > multimedia > services, but the central server becomes the single point of > failure, > While P2P becomes "killing level application" in Internet because > of its > robust and low cost. Combing P2P and SIP, we propose hybrid P2P > SIP > framework in the paper, and describe several important procedures, > such > as node registration, user registration and call procedure. But > current > P2P searching and routing arithmetic does not meet the requirement > for > low time delay in real-time multimedia applications. Then, we > present a > novel SOMCO arithmetic, which decreases the call delay and media > forwarding delay to some extend. Simulation verifies that SOMCO is > practical to support real-time multimedia services > > > > > > > > I look forward to Your Answer, > > Best Regards, > > > > Roy, Radhika R Dr CTR USA USAMC wrote: > > Hi, Fortain: > > > > I think that you can start working for all those QOS mechanisms > within the framework of P2PSIP. Let me explain as follows: > > > > 1. Mobile Ad Hoc networks need P2P networking. As result, the > applications also need to be P2P. P2PSIP WG is working for > facilitating in building of P2PSIP applications. > > > > 2. The ad hoc mobility part is primarily related to the topology > control of MANETs and MANET WG and AUTOCONFIG WG are working in > the layers 2-through 3/4. The QOS-mechanisms of the network layer > are being taken care of by those WGs. > > > > 3. The application layer QOS for SIP in peer-to-peer mode can > best be working within the framework of P2PSIP WG because, I > believe, you do not need to do anything explicitly related to > mobility assuming that the lower MAC and network layer of MANET > are being taken care of by those WGs (e.g. topology control, > routing, QOS) and we can plug those things from the application > layer to the lower network to work cooperatively. > > > > 4. It is true that we may have to do something in the P2P > application layer like P2PSIP for QOS as well as for taking care > of the ad hoc mobility, it is still not well understood by all of > us. Once the P2PSIP signaling protocol is taken care of, we will > gain more experiences what we have to do next. > > > > However, if you suggest what specific problems related to QOS > you want to address in the P2PSIP application Layer for solving > the performance problems, we can then look into those taking > Navy's QOS requirements for MANET networks. > > > > I appreciate for bringing the interesting real problems in the > P2PSIP WG mailing list. > > > > Best regards, > > Radhika > > > > > _______________________________________________ P2PSIP mailing list [email protected] https://www.ietf.org/mailman/listinfo/p2psip
