NBMA loss of DR

John Moy <jmoy@proteon.com> Thu, 27 May 1993 19:28 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11687; 27 May 93 15:28 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11683; 27 May 93 15:28 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa22148; 27 May 93 15:28 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11663; 27 May 93 15:28 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11659; 27 May 93 15:27 EDT
Received: from monk.proteon.com by CNRI.Reston.VA.US id aa22125; 27 May 93 15:27 EDT
Received: from starsky.proteon.com by monk.proteon.com (5.65/1.8) id AA16952; Thu, 27 May 93 15:29:35 -0400
Received: by starsky.proteon.com (4.1/SMI-4.1) id AA16278; Thu, 27 May 93 15:27:53 EDT
Date: Thu, 27 May 1993 15:27:53 -0400
X-Orig-Sender: iplpdn-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John Moy <jmoy@proteon.com>
Message-Id: <9305271927.AA16278@starsky.proteon.com>
To: telenet!killians!snaudus@uunet.uu.net
Cc: iplpdn@CNRI.Reston.VA.US
In-Reply-To: Stanley Naudus's message of Thu, 27 May 93 14:24:27 EDT <9305271824.AA01665@killians.telenet.com>
Subject: NBMA loss of DR

Stan-

You could make a case for making OSPF routers automatically detect NBMA
topologies that are not completely connected, and to then try to split
them into separate NBMAs accordingly. This is not as easy as you think
though -- you need a reliable means to detect whether a single PVC is
down, or whether the router's entire Frame relay interface is down.
(The latter seems much more likely, and is handled fine by OSPF). And
when you split up an NBMA, you probably also want to reassign some of
the IP addresses...

As I said in the last paragraph of the note you are replying to
(although it was on the OSPF list, so I guess the iplpdn people didn't
see it), if this is an operational issue you just need to configure
the failure-prone PVCs as their own IP subnets, ala the Internet Draft
draft-ietf-ospf-guidelines-frn-00.txt.

John