Re: Extensions to OSPF to Support Mobile Ad Hoc Networking
Russ White <ruwhite@CISCO.COM> Mon, 23 February 2004 19:31 UTC
Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14391 for <ospf-archive@LISTS.IETF.ORG>; Mon, 23 Feb 2004 14:31:11 -0500 (EST)
Received: from PEAR.EASE.LSOFT.COM (209.119.0.19) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <16.00CFFAF3@cherry.ease.lsoft.com>; Mon, 23 Feb 2004 14:31:02 -0500
Received: from PEACH.EASE.LSOFT.COM by PEACH.EASE.LSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 3589406 for OSPF@PEACH.EASE.LSOFT.COM; Mon, 23 Feb 2004 14:30:57 -0500
Received: from 64.102.122.148 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0i) with TCP; Mon, 23 Feb 2004 14:30:57 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 23 Feb 2004 11:33:24 -0800
Received: from cisco.com (shako.cisco.com [64.102.17.78]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i1NJUrT4011269 for <OSPF@PEACH.EASE.LSOFT.COM>; Mon, 23 Feb 2004 14:30:53 -0500 (EST)
Received: from localhost (rtp-vpn3-305.cisco.com [10.82.217.51]) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id OAA25166 for <OSPF@PEACH.EASE.LSOFT.COM>; Mon, 23 Feb 2004 14:30:52 -0500 (EST)
References: <6938661A6EDA8A4EA8D1419BCE46F24C020AC2DE@xch-nw-27.nw.nos.boeing.com>
X-X-Sender: ruwhite@shako.cisco.com
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Message-ID: <Pine.WNT.4.53.0402231427040.4016@russpc.Whitehouse.intra>
Date: Mon, 23 Feb 2004 14:30:52 -0500
Reply-To: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
Sender: Mailing List <OSPF@PEACH.EASE.LSOFT.COM>
From: Russ White <ruwhite@CISCO.COM>
Subject: Re: Extensions to OSPF to Support Mobile Ad Hoc Networking
To: OSPF@PEACH.EASE.LSOFT.COM
In-Reply-To: <6938661A6EDA8A4EA8D1419BCE46F24C020AC2DE@xch-nw-27.nw.nos.boeing.com>
Precedence: list
> - at the end of page 4, there was discussion about the fact that too many > neighbors will cause scalability problems. This was also discussed in > Fred Baker's MANET draft from 2002. Do you intend to introduce > mechanisms for minimizing the number of neighbors that a router tries to > become adjacent with, or is that outside the scope of this proposal? The direction we're going on in this area is to reduce the cost of becoming adjacent, rather than preventing adjacencies in the first place--at least at this point. > - could you please explain why LLS extensions are preferable to defining > a new packet type (such as Incremental Hello)? If there is no advantage, > LLS seems a more roundabout way to do it. Because it doesn't impact backwards compatibility. The LLS extensions will be quietly ignored if the router doesn't know how to support it, which allows us to continue and build a "normal" OSPF adjacency with that neighbor. If we use some other packet type, we either need to send those packets plus hello's, to maintain backwards compatibility, or only send this new placket type, which would break backwards compatability. > - do you foresee additional significant extensions beyond use of MPRs/ack > strategy for flooding and use of incremental Hellos? Yes, possibly. There are other uses within OSPF, as well, so it's a generic extension that's useful for a lot of other things, not just MANET. Flexibility is good. :-) :-) Russ __________________________________ riw@cisco.com CCIE <>< Grace Alone
- Extensions to OSPF to Support Mobile Ad Hoc Netwo… Russ White
- Re: Extensions to OSPF to Support Mobile Ad Hoc N… Henderson, Thomas R
- Re: Extensions to OSPF to Support Mobile Ad Hoc N… Russ White
- Re: Extensions to OSPF to Support Mobile Ad Hoc N… Richard Ogier
- Re: Extensions to OSPF to Support Mobile Ad Hoc N… Spagnolo, Phillip A
- Re: Extensions to OSPF to Support Mobile Ad Hoc N… Madhavi Chandra
- Re: Extensions to OSPF to Support Mobile Ad Hoc N… Henderson, Thomas R
- Re: Extensions to OSPF to Support Mobile Ad Hoc N… Russ White
- Re: Extensions to OSPF to Support Mobile Ad Hoc N… Madhavi Chandra