RE: [Ospf-wireless-design] any consensus?
"Spagnolo, Phillip A" <phillip.a.spagnolo@boeing.com> Fri, 28 October 2005 22:31 UTC
Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVclH-0005hC-7o; Fri, 28 Oct 2005 18:31:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVclF-0005h7-K6 for ospf-wireless-design@megatron.ietf.org; Fri, 28 Oct 2005 18:31:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24045 for <ospf-wireless-design@ietf.org>; Fri, 28 Oct 2005 18:31:28 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVcyq-0007TQ-KT for ospf-wireless-design@ietf.org; Fri, 28 Oct 2005 18:45:52 -0400
Received: from stl-av-01.boeing.com ([192.76.190.6]) by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id PAA18505; Fri, 28 Oct 2005 15:31:21 -0700 (PDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id j9SMVLY24664; Fri, 28 Oct 2005 17:31:21 -0500 (CDT)
Received: from XCH-NW-5V2.nw.nos.boeing.com ([130.247.55.45]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 28 Oct 2005 15:31:13 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Ospf-wireless-design] any consensus?
Date: Fri, 28 Oct 2005 15:31:12 -0700
Message-ID: <08590A72DC26A54B85632FF97C2C22DA0D5052@XCH-NW-5V2.nw.nos.boeing.com>
Thread-Topic: [Ospf-wireless-design] any consensus?
Thread-Index: AcXaGy1qsC9JQPNPTryUjSIDpVdqWQB8zFRg
From: "Spagnolo, Phillip A" <phillip.a.spagnolo@boeing.com>
To: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
X-OriginalArrivalTime: 28 Oct 2005 22:31:13.0197 (UTC) FILETIME=[4D739DD0:01C5DC0F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Content-Transfer-Encoding: quoted-printable
Cc: ospf-wireless-design@ietf.org
X-BeenThere: ospf-wireless-design@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: OSPF Wireless Design Team <ospf-wireless-design.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf-wireless-design>, <mailto:ospf-wireless-design-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <https://www1.ietf.org/mailman/private/ospf-wireless-design>
List-Post: <mailto:ospf-wireless-design@lists.ietf.org>
List-Help: <mailto:ospf-wireless-design-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf-wireless-design>, <mailto:ospf-wireless-design-request@lists.ietf.org?subject=subscribe>
Sender: ospf-wireless-design-bounces@lists.ietf.org
Errors-To: ospf-wireless-design-bounces@lists.ietf.org
Emmanuel, I have instrumented our simulation to count the number of adjacencies that would be formed if adjacencies were formed between all MPRs and MPR Selectors. Richard's examples seemed to show that just having adjacencies between MPRs and MPR selectors can cause partition, but this should give a rough estimate of the set size. My first intention was to implement the OR draft in GTNetS with adjacencies only being formed between MPRs and MPR selectors. However, after looking at the work to be done, I didn't think it was possible to complete by the next meeting. See my notes below on some design issues that need to be worked out. Instead, I ran the standard ORs and I sampled the number of links that would be adjacencies every half second. This was done by counting the MPRs that a node selected without double counting nodes that selected each other. At the end of the simulation, I computed the average number of adjacencies in the network. This is an estimate of the true result because reducing the adjacencies would cause different MPRs to be selected, we don't see the result of having to remove adjacencies, etc... The OR results below are compared against the MDRs with uniconnected adjacencies. Nodes OR-adjacencies uni-MDR-adjacencies 10 11.88 11.69 20 42.04 31.04 30 77.30 40.74 40 136.87 53.09 50 193.35 63.47 As expected, it appears that more adjacencies are formed when using MPR/MPR selectors. Do you agree with the estimate? Do you still feel that this is approach is viable? Do you want the code to try yourself? Sincerely, Phil P.S. Below are "some" items that would need to be worked out before implementing the MPR/MPR selector adjacencies -When should the MPR calculation be made? In the past, it only needed to be run when a hello was sent. Now, it needs to occur whenever a neighborhood change is made. -Should the MPR and MPR selector agree on their roles before creating an adjacency or should they always accept an adjacency? -How do we remove adjacencies to get a fair comparison with MDRs? -How should full adjacency connectivity be ensured? > -----Original Message----- > From: Emmanuel Baccelli [mailto:Emmanuel.Baccelli@inria.fr] > Sent: Wednesday, October 26, 2005 3:48 AM > To: ospf-wireless-design@ietf.org > Subject: Re: [Ospf-wireless-design] any consensus? > > > > > > >On July 12, Emmanuel Baccelli from INRIA posted two reports: MPR/CDS > >stability, and on achieving partial topology in MPR-based solution. > >These reports haven't generated much discussion, and we haven't had a > >chance to look carefully at the CDS stability claims. The partial > >topology solutions recommended were to construct an MPR-CDS > or to just > >form adjacencies between MPRs and selectors, but because these > >MPR/selector relationships are not symmetric, I am guessing > that it will > >result in many more adjacencies than the CDS approach. > > > > > > Hi all, > > the trade-off in terms of partial topology is the following: if a CDS > (i.e. MDR or MPR-CDS) > backbone is used to perform reduction in topology advertizement, the > routes in the network > will suffer from a stretch factor that leads to a substantial > amount of > unnecessary retransmissions > (and hence overhead) in an ad hoc environment. We may decide to bear > with this, but we can > also consider another approach based on MPRs that does not > lead to any > route stretch, but may > yield more ajacencies (if indeed routing has to happen over > ajacencies). > I think there is a > fine trade off that remains to be evaluated between taking a > CDS or MPR > as backbone to > compute the reduction in topology advertizement. > > On the other hand, i am convinced that MPR flooding presents better > properties than CDS > flooding, in an ad hoc environment (see the stability report > we have issued > http://www.inria.fr/rrrt/rr-5609.html and experience gathered > with MPRs > in MANETs > over the years). > > Therefore taking an approach based on MPR may be the best path, as it > enables to > decouple the flooding optimization and the topology reduction > schemes. > This way, > the better properties of MPR flooding can be used, while topology > reduction can > still be either based on: > (i) MPR-CDS adjacency, which will have the same adjacency > properties than > MDR-CDS topology reduction schemes (see the partial > topology report we > have issued http://www.inria.fr/rrrt/rr-5619.html ), or based on: > (ii) MPR-selector links/adjacency. > > I guess my point is that the MDR approach should not be > favoured for its > topology > reduction abilities, since an MPR approach features at least as good > topology reduction > abilities and a better flooding scheme. > > Emmanuel > > > > _______________________________________________ > Ospf-wireless-design mailing list > Ospf-wireless-design@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/ospf-wireless-design > _______________________________________________ Ospf-wireless-design mailing list Ospf-wireless-design@lists.ietf.org https://www1.ietf.org/mailman/listinfo/ospf-wireless-design
- [Ospf-wireless-design] any consensus? Henderson, Thomas R
- Re: [Ospf-wireless-design] any consensus? Emmanuel Baccelli
- RE: [Ospf-wireless-design] any consensus? Henderson, Thomas R
- Re: [Ospf-wireless-design] any consensus? Richard Ogier
- Re: [Ospf-wireless-design] any consensus? Richard Ogier
- RE: [Ospf-wireless-design] any consensus? Spagnolo, Phillip A
- Re: [Ospf-wireless-design] any consensus? Richard Ogier
- Re: [Ospf-wireless-design] any consensus? Richard Ogier
- Re: [Ospf-wireless-design] any consensus? Richard Ogier
- RE: [Ospf-wireless-design] any consensus? Spagnolo, Phillip A
- Re: [Ospf-wireless-design] any consensus? Richard Ogier
- Re: [Ospf-wireless-design] any consensus? Richard Ogier
- Re: [Ospf-wireless-design] any consensus? Richard Ogier