RE: [Ospf-wireless-design] Re: consensus

"Spagnolo, Phillip A" <phillip.a.spagnolo@boeing.com> Fri, 04 November 2005 14:48 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 1EY2s1-0002Ix-2v; Fri, 04 Nov 2005 09:48:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EY2ry-0002Ii-Jk for ospf-wireless-design@megatron.ietf.org; Fri, 04 Nov 2005 09:48:43 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA23810 for <ospf-wireless-design@ietf.org>; Fri, 4 Nov 2005 09:48:18 -0500 (EST)
Received: from blv-smtpout-01.boeing.com ([130.76.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EY36v-0000VU-T3 for ospf-wireless-design@ietf.org; Fri, 04 Nov 2005 10:04:13 -0500
Received: from blv-av-01.boeing.com ([192.42.227.216]) by blv-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id GAA06292; Fri, 4 Nov 2005 06:48:18 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id jA4EmHH29761; Fri, 4 Nov 2005 06:48:18 -0800 (PST)
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, 4 Nov 2005 06:48:15 -0800
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] Re: consensus
Date: Fri, 04 Nov 2005 06:48:14 -0800
Message-ID: <08590A72DC26A54B85632FF97C2C22DA0D506A@XCH-NW-5V2.nw.nos.boeing.com>
Thread-Topic: [Ospf-wireless-design] Re: consensus
Thread-Index: AcXhKq0vcJJ1ybMJR+eglvJQvyyhNQAIn93A
From: "Spagnolo, Phillip A" <phillip.a.spagnolo@boeing.com>
To: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>, ospf-wireless-design@ietf.org
X-OriginalArrivalTime: 04 Nov 2005 14:48:15.0637 (UTC) FILETIME=[C9A09450:01C5E14E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: quoted-printable
Cc:
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,

You have stated the following on several occasions.

> One thing that must be considered though, is the stretch 
> factor that is 
> implied by the topology reduction scheme going
> with MDRs. We are currently at INRIA running some simulations to 
> evaluate this stretch factor. It seems it may be
> quite substantial, and this should be taken into account in 
> the design, 
> as route stretching introduces an overhead that
> is proportional to the data traffic. On the other hand using 
> MPR/MPRselector adjacencies does yield more adjacencies,
> but no route stretching whatsoever. So here (in the topology 
> reduction 
> design) there is a trade-off that was not yet fully
> discussed in my opinion.

Why do you say that MDRs require much longer routing stretch?  It has
been pointed out several times that when using MDR Full or Min-hop LSAs
then route stretch is minimized in OSPF-MDR.  

For some reason, it seems that you want to force data packets and ospf
packets over the same path.  

Are the simulations that you are running forcing data packets over the
CDS backbone?  If they are then your comparison does not seem to be on a
level playing field.

Let me know if I am confused in some way, or I don't have all the
information.  

Sincerely,
Phil

_______________________________________________
Ospf-wireless-design mailing list
Ospf-wireless-design@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/ospf-wireless-design