RE: [Ospf-wireless-design] OSPF Flooding and Higher Mobility

"Henderson, Thomas R" <thomas.r.henderson@boeing.com> Fri, 04 November 2005 22:28 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 1EYA2l-0000xb-3B; Fri, 04 Nov 2005 17:28:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EYA2j-0000xW-FZ for ospf-wireless-design@megatron.ietf.org; Fri, 04 Nov 2005 17:28:17 -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 RAA17905 for <ospf-wireless-design@ietf.org>; Fri, 4 Nov 2005 17:27:53 -0500 (EST)
Received: from stl-smtpout-01.boeing.com ([130.76.96.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EYAHl-0004jp-DJ for ospf-wireless-design@ietf.org; Fri, 04 Nov 2005 17:43:52 -0500
Received: from stl-av-01.boeing.com ([192.76.190.6]) by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id QAA05661; Fri, 4 Nov 2005 16:28:05 -0600 (CST)
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 jA4MS4Y20962; Fri, 4 Nov 2005 16:28:04 -0600 (CST)
Received: from XCH-NW-5V1.nw.nos.boeing.com ([130.247.55.44]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 4 Nov 2005 14:28:03 -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] OSPF Flooding and Higher Mobility
Date: Fri, 04 Nov 2005 14:28:02 -0800
Message-ID: <77F357662F8BFA4CA7074B0410171B6DC9E609@XCH-NW-5V1.nw.nos.boeing.com>
Thread-Topic: [Ospf-wireless-design] OSPF Flooding and Higher Mobility
Thread-Index: AcXhg2aPTBgLniFrSWSCG8HTlCvJugACc/aQ
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: Acee Lindem <acee@cisco.com>, ospf-wireless-design@ietf.org
X-OriginalArrivalTime: 04 Nov 2005 22:28:03.0268 (UTC) FILETIME=[05230040:01C5E18F]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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

Acee, first, thanks for providing this information and (eventually) the
code. 

> 
> MPRs have the following improvements over the base provided 
> with GTNetS:
> 
>      - Smart Peering is fixed to avoid instability by running a second
>        SPF to determine if a potential peer is available via a real
>        adjacency or unsynchronized adjacency. The adjacency 
> is only suppressed
>        in the case of connectivity to the SPT via real 
> adjacencies. This
>        is discussed in the Boeing report but wasn't implemented.
> 

One potential problem that I foresee with this method is that, as
connectivity conditions change in the network, one has to go back and
re-evaluate whether previous decisions to suppress the formation of
adjacencies are still valid.  Are you addressing this issue somehow, and
if so, how?

Tom

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