[Ospf-wireless-design] Another example for self-selected MPRs

Richard Ogier <rich.ogier@earthlink.net> Wed, 30 March 2005 02:14 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24347; Tue, 29 Mar 2005 21:14:54 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGSqF-0000WI-Np; Tue, 29 Mar 2005 21:21:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DGSis-0002pb-Hz; Tue, 29 Mar 2005 21:14:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DGSiq-0002pT-Tg for ospf-wireless-design@megatron.ietf.org; Tue, 29 Mar 2005 21:14:20 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24243 for <ospf-wireless-design@ietf.org>; Tue, 29 Mar 2005 21:14:19 -0500 (EST)
Received: from pop-a065c28.pas.sa.earthlink.net ([207.217.121.205]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DGSpf-0000U6-VT for ospf-wireless-design@ietf.org; Tue, 29 Mar 2005 21:21:24 -0500
Received: from dialup-4.243.137.114.dial1.sanfrancisco1.level3.net ([4.243.137.114] helo=earthlink.net) by pop-a065c28.pas.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1DGSio-00066x-00 for ospf-wireless-design@ietf.org; Tue, 29 Mar 2005 18:14:18 -0800
Message-ID: <424A0B78.1010203@earthlink.net>
Date: Tue, 29 Mar 2005 18:14:16 -0800
From: Richard Ogier <rich.ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 (emach0202)
X-Accept-Language: en-us
MIME-Version: 1.0
To: ospf-wireless-design@ietf.org
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.9 (++)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Subject: [Ospf-wireless-design] Another example for self-selected MPRs
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@ietf.org
Errors-To: ospf-wireless-design-bounces@ietf.org
X-Spam-Score: 2.9 (++)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

To help understand how my proposed solution uses Hellos to learn
2-hop neighbor information and to update self-selected MPRs (or MDRs),
I would like to present another example.

Let's assume that (differential) Hellos must be used to learn
2-hop neighbor information, e.g., so that partial-topology
LSAs can be generated.  Also, assume that Hellos are sent
every 2 seconds, and that no early Hellos are sent.

First, I want to point out that, for self-selected MPRs/MDRs, only
DRs and BDRs need to advertise their full neighborhood (periodically)
in Hellos. This is an additional benefit of using self-selected MPRs,
because they are in the "middle of the action", i.e., they can directly
see both the upstream neighbors and the downstream neighbors.
However, for this example, I will assume that all nodes periodically
advertise their full neighborhood in Hellos.

       1
      / \
     /   \
    2 --- 3
     \   /
      \ /
       4


Assume that initially node 3 is an MPR, either self-selected, or
neighbor-selected by node 1.

Now assume that node 4 detects the failure of its link to node 3 at
time 0, either from a link-layer failure notification, or from
not hearing Hellos from node 3 for RouterDeadInterval.

Then node 4 will send a Hello at time 2 (worst case) that indicates
node 3 is no longer a neighbor. Assume that node 3 can still hear
Hellos from node 4, so both nodes 2 and 3 will receive the Hello.

If MPRs are self-selected, then node 2 will select itself as an MPR
at time 2, when it receives the Hello from node 4.

If MPRs are neighbor-selected, then node 3 will send a Hello at
time 4 (worst case) indicating that node 4 is no longer a neighbor.
When node 1 receives this Hello, it will select node 2 as an MPR,
and will send a Hello at time 6 including the updated MPR.
Node 2 will then know it is an MPR at time 6, compared to time 2
for self-selected MPRs.

(I know that non-active overlapping relays will forward MPRs
during this recovery period, but with an added delay of
PushbackInterval, and possibly additional overhead if
mutiple non-active relays flood the LSA at nearly the same time,
a real possibility if the number of non-active relays is large.)

Richard




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