> Regarding using Ad Hoc networks as transit networks is very important > discussion, and the views in industry are mixed. I personally believe > this must be supported for emergency preparedness reasons and I can come > up with many others, and that the IETF community needs to develop Ad Hoc > network specs, ops views, etc that include viewing Ad Hoc nets as > transit providers. This will have much debate is my guess.
I would separate this into two cases, one being an AHN that is a transit to another AHN, which I would be interested in (or more generally, AHNs which collectively are a stub, but individually may be transit networks), the other being an AHN with multiple connections to the fixed Internet (or any other network with significantly greater stability, reliability and/or - usually and - bandwidth) the AHN acting as a transit for the other network. The latter I'd be happy to exclude. I'd postpone considering the former too if it helped the process along (or include it if that helped the proces along, but that seems less likely). [Incidentally I take your point about there being a logical difference between MANETs and AHNs and have used the latter above. However in practice the distinction blurs, I've presented results from a real network which had non-mobile nodes, but was a non-static network - and that was before allowing nodes to fail. I think what you really want are protocols that can be adapted - or better yet adapt themeselves - to the range of conditions, and I hope at least some of this will come out in Standards Track routing protocols. But that's off the point here I think, hence the brackets.] ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ Int-area mailing list [email protected] https://www1.ietf.org/mailman/listinfo/int-area
