From ospf-wireless-design-bounces@ietf.org  Fri Apr  1 10:52:06 2005
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 KAA07069;
	Fri, 1 Apr 2005 10:52:06 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHOYh-0007HG-5E; Fri, 01 Apr 2005 10:59:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHOQe-00044E-P2; Fri, 01 Apr 2005 10:51:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOQd-000449-Py
	for ospf-wireless-design@megatron.ietf.org;
	Fri, 01 Apr 2005 10:51:23 -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 KAA06630
	for <ospf-wireless-design@ietf.org>;
	Fri, 1 Apr 2005 10:51:21 -0500 (EST)
Received: from rtp-iport-2.cisco.com ([64.102.122.149])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHOXz-0007EG-IC
	for ospf-wireless-design@ietf.org; Fri, 01 Apr 2005 10:59:00 -0500
Received: from rtp-core-1.cisco.com (64.102.124.12)
	by rtp-iport-2.cisco.com with ESMTP; 01 Apr 2005 10:51:14 -0500
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com
	[64.102.31.102])
	by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j31Fp01j002141; 
	Fri, 1 Apr 2005 10:51:01 -0500 (EST)
Received: from xfe-rtp-212.amer.cisco.com ([64.102.31.100]) by
	xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211);
	Fri, 1 Apr 2005 10:51:00 -0500
Received: from [10.82.225.186] ([10.82.225.186]) by xfe-rtp-212.amer.cisco.com
	with Microsoft SMTPSVC(6.0.3790.211); Fri, 1 Apr 2005 10:50:59 -0500
Message-ID: <424D6DE3.5010004@cisco.com>
Date: Fri, 01 Apr 2005 10:50:59 -0500
From: Acee Lindem <acee@cisco.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Richard Ogier <rich.ogier@earthlink.net>
Subject: Re: [Ospf-wireless-design] Synchronization requirement for including
	a	neighbor in LSA
References: <424C5AE1.5030109@earthlink.net>
In-Reply-To: <424C5AE1.5030109@earthlink.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 01 Apr 2005 15:50:59.0856 (UTC)
	FILETIME=[99A31100:01C536D2]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Content-Transfer-Encoding: 7bit
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@ietf.org
Errors-To: ospf-wireless-design-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4
Content-Transfer-Encoding: 7bit

Hi Richard,
As we discussed offline, can we call your DR/BDR the CDR/BCDR (Connected
Dominating Router/Backup ....)  or MDR/BMDR (Manet Designated 
Router/Backup ...)
as we move forward? The OSPF DR/BDR for a broadcast/NBMA has a very
well defined set of responsibilities and duties in the flooding process. 
IMHO,  the
semantics are different enough that we don't want to overload the terms 
OSPF
DR/BDR.

Also a change allowing non-adjacent neighbors to be advertised is 
somewhat beyond
the initial scope of flooding optimizations. In any case, the protocol 
mechanisms, events,
and state machines need to be very precisely defined in order to be 
evaluated.

Thanks,
Acee

Richard Ogier wrote:

> All,
>
> I want to discuss the definition of a "synchronized" neighbor
> in Section 5 of my draft, and explain why I think this is a
> good requirement for a neighbor to be included in the router LSA.
> This condition is valid for both full-topology and partial-topology
> LSAs, so the discussion below applies to either case.
>
> First, I am assuming that a set of adjacencies has been formed
> that spans the entire network, so that there exists a (suboptimal)
> path from each router to every other router via adjacent edges
> (except temporarily as new adjacencies are formed in response
> to topology changes).
>
> Each router will include, at a minimum, each fully adjacent neighbor
> in its router LSA. This will provide suboptimal routes to each
> reachable router.
>
> The question is, what other neighbors can be included in the router LSA?
>
> Suppose that node i has a non-adjacent, 2-way neighbor j, and that
> the SPF calculation has calculated a route to node j via a fully
> adjacent neighbor k. Then node i can route data packets to neighbor j
> via neighbor k. (Or, neighbor j might not be the final destination,
> but might be an intermedate node to another destination.)
> So, instead of using neighbor k as the next hop, why not take
> a shortcut and forward the data packet directly to neighbor j
> as the next hop?  This is quite reasonable, and is exactly what
> the synchronized neighbor rule says.
>
> Once neighbor j has been declared to be an acceptable next hop
> (to any destination), it can be included in node i's router LSA.
>
> Note that this is a generalization of what is allowed in an OSPF
> broadcast network, which allows a non-DR/BDR i to use another
> non-DR/BDR j as a next hop as long as both are fully adjacent to
> the DR.  In a broadcast network, there is no need for node i
> to include node j in its LSA, since the network LSA originated
> by the DR already implies this information. But when we
> generalize to a multihop network, the only way node i can
> inform other routers that it can forward packets to node j,
> is to include node j in its router LSA.
>
> A possible concern: What if, after declaring node j to be an
> acceptable next hop, there temporarily does not exist a path
> of fully adjacent edges to node j, due to topology changes?
> The above rule does not detect this and does not remove node j
> as an acceptable next hop (unless node j is no longer reachable).
>
> The answer is that the protocol will be robust enough (if designed
> properly) to maintain sufficient database synchronization even
> when topology changes cause old adjacencies to fail and require
> new adjacencies to be formed.
>
> The only case where routers may not be acceptably synchronized
> is when the network partitions, i.e., some destinations become
> temporarily unreachable.  The above rule will detect this,
> since it requires a neighbor to be reachable via a current path
> that has already been determined to be acceptable.
>
> I plan to implement the above method in the next few weeks,
> so we will see how it peforms.
>
> Richard
>
>
>
>
> _______________________________________________
> 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


From ospf-wireless-design-bounces@ietf.org  Fri Apr  1 11:33:08 2005
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 LAA12333;
	Fri, 1 Apr 2005 11:33:07 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHPCQ-0000sC-72; Fri, 01 Apr 2005 11:40:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHOyE-0001XW-LE; Fri, 01 Apr 2005 11:26:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHOyD-0001XR-AW
	for ospf-wireless-design@megatron.ietf.org;
	Fri, 01 Apr 2005 11:26:05 -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 LAA10729
	for <ospf-wireless-design@ietf.org>;
	Fri, 1 Apr 2005 11:26:02 -0500 (EST)
Received: from pop-a065c10.pas.sa.earthlink.net ([207.217.121.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHP5X-0000HZ-BM
	for ospf-wireless-design@ietf.org; Fri, 01 Apr 2005 11:33:41 -0500
Received: from dialup-4.243.134.61.dial1.sanfrancisco1.level3.net
	([4.243.134.61] helo=earthlink.net)
	by pop-a065c10.pas.sa.earthlink.net with esmtp (Exim 3.36 #10)
	id 1DHOy8-0002VX-00; Fri, 01 Apr 2005 08:26:00 -0800
Message-ID: <424D7618.7010609@earthlink.net>
Date: Fri, 01 Apr 2005 08:26:00 -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: Acee Lindem <acee@cisco.com>
Subject: Re: [Ospf-wireless-design] Synchronization requirement for including
	a	neighbor in LSA
References: <424C5AE1.5030109@earthlink.net> <424D6DE3.5010004@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b22590c27682ace61775ee7b453b40d3
Content-Transfer-Encoding: 7bit
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@ietf.org
Errors-To: ospf-wireless-design-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Content-Transfer-Encoding: 7bit

Hi Acee,

Acee Lindem wrote:

> Hi Richard,
> As we discussed offline, can we call your DR/BDR the CDR/BCDR (Connected
> Dominating Router/Backup ....)  or MDR/BMDR (Manet Designated 
> Router/Backup ...)
> as we move forward? The OSPF DR/BDR for a broadcast/NBMA has a very
> well defined set of responsibilities and duties in the flooding 
> process. IMHO,  the
> semantics are different enough that we don't want to overload the 
> terms OSPF
> DR/BDR. 

OK.  I prefer MDR/BMDR.

>
>
> Also a change allowing non-adjacent neighbors to be advertised is 
> somewhat beyond
> the initial scope of flooding optimizations. In any case, the protocol 
> mechanisms, events,
> and state machines need to be very precisely defined in order to be 
> evaluated.

If the initial scope of flooding optimizations does not
allow non-adjacent neighbors to be advertised, then it may
prevent an efficient solution. I guess the scope can be
changed if it is found to be necessary. But I think the
fact that OSPF already allows a non-adjacent neighbor
to be a next hop (in a broadcast network), and the fact
that this information is implied by the network LSA originated
by the DR, implies that the inclusion of a non-adjacent neighbor
in an LSA is simply a necessary generalization to multi-hop
networks, since a network LSA cannot be used in such networks.

Once the protocol is implemented in GTNetS (in the next
few weeks), it will be precisely defined.

Richard


>
>
> Thanks,
> Acee
>
> Richard Ogier wrote:
>
>> All,
>>
>> I want to discuss the definition of a "synchronized" neighbor
>> in Section 5 of my draft, and explain why I think this is a
>> good requirement for a neighbor to be included in the router LSA.
>> This condition is valid for both full-topology and partial-topology
>> LSAs, so the discussion below applies to either case.
>>
>> First, I am assuming that a set of adjacencies has been formed
>> that spans the entire network, so that there exists a (suboptimal)
>> path from each router to every other router via adjacent edges
>> (except temporarily as new adjacencies are formed in response
>> to topology changes).
>>
>> Each router will include, at a minimum, each fully adjacent neighbor
>> in its router LSA. This will provide suboptimal routes to each
>> reachable router.
>>
>> The question is, what other neighbors can be included in the router LSA?
>>
>> Suppose that node i has a non-adjacent, 2-way neighbor j, and that
>> the SPF calculation has calculated a route to node j via a fully
>> adjacent neighbor k. Then node i can route data packets to neighbor j
>> via neighbor k. (Or, neighbor j might not be the final destination,
>> but might be an intermedate node to another destination.)
>> So, instead of using neighbor k as the next hop, why not take
>> a shortcut and forward the data packet directly to neighbor j
>> as the next hop?  This is quite reasonable, and is exactly what
>> the synchronized neighbor rule says.
>>
>> Once neighbor j has been declared to be an acceptable next hop
>> (to any destination), it can be included in node i's router LSA.
>>
>> Note that this is a generalization of what is allowed in an OSPF
>> broadcast network, which allows a non-DR/BDR i to use another
>> non-DR/BDR j as a next hop as long as both are fully adjacent to
>> the DR.  In a broadcast network, there is no need for node i
>> to include node j in its LSA, since the network LSA originated
>> by the DR already implies this information. But when we
>> generalize to a multihop network, the only way node i can
>> inform other routers that it can forward packets to node j,
>> is to include node j in its router LSA.
>>
>> A possible concern: What if, after declaring node j to be an
>> acceptable next hop, there temporarily does not exist a path
>> of fully adjacent edges to node j, due to topology changes?
>> The above rule does not detect this and does not remove node j
>> as an acceptable next hop (unless node j is no longer reachable).
>>
>> The answer is that the protocol will be robust enough (if designed
>> properly) to maintain sufficient database synchronization even
>> when topology changes cause old adjacencies to fail and require
>> new adjacencies to be formed.
>>
>> The only case where routers may not be acceptably synchronized
>> is when the network partitions, i.e., some destinations become
>> temporarily unreachable.  The above rule will detect this,
>> since it requires a neighbor to be reachable via a current path
>> that has already been determined to be acceptable.
>>
>> I plan to implement the above method in the next few weeks,
>> so we will see how it peforms.
>>
>> Richard
>>
>>
>>
>>
>> _______________________________________________
>> 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


From ospf-wireless-design-bounces@ietf.org  Tue Apr  5 15:59:46 2005
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 PAA04413;
	Tue, 5 Apr 2005 15:59:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIuLR-0001Wv-Kg; Tue, 05 Apr 2005 16:08:17 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIu5C-0004xE-19; Tue, 05 Apr 2005 15:51:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIu5A-0004wu-QY
	for ospf-wireless-design@megatron.ietf.org;
	Tue, 05 Apr 2005 15:51:28 -0400
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 PAA01005
	for <ospf-wireless-design@ietf.org>;
	Tue, 5 Apr 2005 15:51:26 -0400 (EDT)
Received: from rtp-iport-1.cisco.com ([64.102.122.148])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIuDM-00009q-O9
	for ospf-wireless-design@ietf.org; Tue, 05 Apr 2005 15:59:58 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13)
	by rtp-iport-1.cisco.com with ESMTP; 05 Apr 2005 16:12:29 -0400
X-IronPort-AV: i="3.91,152,1110171600"; 
	d="scan'208"; a="43263633:sNHT1344882288"
Received: from mchandra-u10.cisco.com (mchandra-u10.cisco.com [64.102.48.252])
	by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id
	j35JpFjI016932; Tue, 5 Apr 2005 15:51:16 -0400 (EDT)
Received: (mchandra@localhost) by mchandra-u10.cisco.com (8.11.2/CISCO.WS.1.2)
	id j35JpFx20502; Tue, 5 Apr 2005 15:51:15 -0400 (EDT)
Date: Tue, 5 Apr 2005 15:51:15 -0400
From: "Madhavi W. Chandra" <mchandra@cisco.com>
To: Richard Ogier <rich.ogier@earthlink.net>
Subject: Re: [Ospf-wireless-design] Another example for self-selected MPRs
Message-ID: <20050405195115.GA20498@cisco.com>
References: <424A0B78.1010203@earthlink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <424A0B78.1010203@earthlink.net>
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
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@ietf.org
Errors-To: ospf-wireless-design-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b

On Tue, Mar 29, 2005 at 06:14:16PM -0800, Richard Ogier wrote:
> 
> 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.

Actually, the backup Overlapping Relays (node 2) will go into action 
since it wouldn't have received node 4's ACK.  This will happen at 
(Pushbacktimer + jitter), which is latest by 
(RxmtInterval/2 - propagatation delays).  Even taking
the default RxmtInterval of 5 seconds, puts this time on par, if not
sooner, with the 2second Hello time example.  So, the rest of the example 
of Node 2 knowing it is an Active Overlapping Relay at time 6 is moot.  
Jitter is used for backups to avoid multiple backups firing at the same 
time.  

Please keep in mind that the backup mechanism in Overlapping Relays is 
a powerful yet simple feature and integral to the operation, and should 
not be overlooked.

Thanks,
Madhavi
 
> 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

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


From ospf-wireless-design-bounces@ietf.org  Tue Apr  5 18:40:57 2005
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 SAA27130;
	Tue, 5 Apr 2005 18:40:56 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIwrS-0001gd-HT; Tue, 05 Apr 2005 18:49:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIwiF-0004Ep-Df; Tue, 05 Apr 2005 18:39:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIwiD-0004Ek-KH
	for ospf-wireless-design@megatron.ietf.org;
	Tue, 05 Apr 2005 18:39:57 -0400
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 SAA27062
	for <ospf-wireless-design@ietf.org>;
	Tue, 5 Apr 2005 18:39:54 -0400 (EDT)
Received: from pop-a065b10.pas.sa.earthlink.net ([207.217.121.170])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DIwqR-0001fm-I6
	for ospf-wireless-design@ietf.org; Tue, 05 Apr 2005 18:48:27 -0400
Received: from dialup-4.243.134.210.dial1.sanfrancisco1.level3.net
	([4.243.134.210] helo=earthlink.net)
	by pop-a065b10.pas.sa.earthlink.net with esmtp (Exim 3.36 #10)
	id 1DIwiA-00018b-00; Tue, 05 Apr 2005 15:39:54 -0700
Message-ID: <425313A1.6040109@earthlink.net>
Date: Tue, 05 Apr 2005 15:39:29 -0700
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: "Madhavi W. Chandra" <mchandra@cisco.com>
Subject: Re: [Ospf-wireless-design] Another example for self-selected MPRs
References: <424A0B78.1010203@earthlink.net> <20050405195115.GA20498@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Content-Transfer-Encoding: 7bit
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@ietf.org
Errors-To: ospf-wireless-design-bounces@ietf.org
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Content-Transfer-Encoding: 7bit

Madhavi W. Chandra wrote:

>On Tue, Mar 29, 2005 at 06:14:16PM -0800, Richard Ogier wrote:
>
>>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.
>>
>
>Actually, the backup Overlapping Relays (node 2) will go into action 
>since it wouldn't have received node 4's ACK.  This will happen at 
>(Pushbacktimer + jitter), which is latest by 
>(RxmtInterval/2 - propagatation delays).  Even taking
>the default RxmtInterval of 5 seconds, puts this time on par, if not
>sooner, with the 2second Hello time example.  So, the rest of the example 
>of Node 2 knowing it is an Active Overlapping Relay at time 6 is moot.  
>Jitter is used for backups to avoid multiple backups firing at the same 
>time.
>

There are still some differences. For example, for the 6 seconds it
may take to select another MPR, *every* LSA will suffer the
PushbackInterval + jitter delay, whereas once a self-selected MPR
selects itself, it will forward new LSAs immediately. Also, the use
of PushbackInterval imposes a more strict constraint on AckInterval
(the maximum time to send a delayed ACK), i.e., AckInterval must be
less than (RxmtInterval/2 - propagation delays). What concerns me
most is scalability. In a very dense network, there could be a large
number of backup Overlapping Relays, and even with jitter the
probability of multiple backups forwarding the LSA becomes
significant. (Of course, backup MPRs are not as desirable as active
MPRs - otherwise there would be no need to select active MPRs.)

But I consider the above to be minor compared to the other advantages
of self-selected MDRs, which have been discussed.
I think simulations will be most useful in comparing the
two approaches.

Richard


>
>
>Please keep in mind that the backup mechanism in Overlapping Relays is 
>a powerful yet simple feature and integral to the operation, and should 
>not be overlooked.
>
>Thanks,
>Madhavi
> 
>
>>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
>>
>
>



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


From ospf-wireless-design-bounces@ietf.org  Tue Apr  5 19:23:55 2005
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 TAA29913;
	Tue, 5 Apr 2005 19:23:55 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIxX3-00032k-Gx; Tue, 05 Apr 2005 19:32:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIxHO-0003xJ-1Z; Tue, 05 Apr 2005 19:16:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIxHM-0003xE-QZ
	for ospf-wireless-design@megatron.ietf.org;
	Tue, 05 Apr 2005 19:16:16 -0400
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 TAA29406
	for <ospf-wireless-design@ietf.org>;
	Tue, 5 Apr 2005 19:16:13 -0400 (EDT)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIxPZ-0002mD-Jg
	for ospf-wireless-design@ietf.org; Tue, 05 Apr 2005 19:24:47 -0400
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-2.cisco.com with ESMTP; 05 Apr 2005 16:16:05 -0700
Received: from [10.32.9.51] ([10.32.9.51])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j35NFqDr000537;
	Tue, 5 Apr 2005 16:15:52 -0700 (PDT)
Message-ID: <42531C3A.5000903@cisco.com>
Date: Tue, 05 Apr 2005 16:16:10 -0700
From: Padma Pillay-Esnault <ppe@cisco.com>
User-Agent: Mozilla Thunderbird 0.9 (Macintosh/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ospf-wireless-design@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-PMX-Version: 4.7.0.111621
X-from-outside-Cisco: [10.32.9.51]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit
Subject: [Ospf-wireless-design] Algorithms and optimizations
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: 0.0 (/)
X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793
Content-Transfer-Encoding: 7bit


Looking at the multiple threads lately, it seems that the discussions 
are drifting to evaluating the optimizations
of one proposal as an argument versus another. We think that we should 
bear in mind that it is the base algorithm that is of prime importance.

While some optimizations are required for scalability, they can be 
applied to both base algorithms and hence they should have a limited 
weight on evaluation of a proposal.

Another essential foundation is OSPFv3, changes that impact the basic 
protocol have to be evaluated.
In the real world, existing stacks will need to be changed to 
incorporate wireless interface. How much
of these changes can it really absorb and still function correctly? The 
extent of change has to be evaluated carefully so as not to jeopardise 
stability and  uncover  corner cases that have a nagging habit of popping
up pretty late in the game. We think that changes should be limited to 
what is really essential for manet to
perform.

Most of the optimizations are applicable to both base algorithms and 
including them only adds more
parameters that blur what should really be evaluated. Some optimizations 
can be palliatives and hence
they cannot be used to validate the base algorithms.

IMHO, evaluation should be done thru a number of clearly defined 
criteria. A first attempt
could look like the following
- Comparison of base algorithm without any optimization.
- Evaluation of the changes required to the OSPFv3 protocol , bearing in 
mind extensive changes
usually spell instability and newly discovered corner cases.
- Leverage of existing proven mechanisms of the OSPFv3 protocol.
- Clearly define in which circumstances the optimizations that really 
make sense. For instance, limiting adjacencies is an interesting concept 
only if there is a high number of nodes potentially going out of range. 
However, it adds unnecessary complexity if the nodes have a wide range 
and less likely to drop out. In other words, do these scenarios really 
matter or are they unlikely in the particular nework we are addressing.  
Also, optimizations should retain their optional character.
- Last but not the least, identify the sector most likely to deployment 
of this technology and tackle their specific
problems and perks first.


Padma

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


From ospf-wireless-design-bounces@ietf.org  Wed Apr  6 20:05:23 2005
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 UAA24152;
	Wed, 6 Apr 2005 20:05:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJKex-0002vo-9B; Wed, 06 Apr 2005 20:14:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJKWQ-0005OI-8h; Wed, 06 Apr 2005 20:05:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJKWO-0005Ks-Tu
	for ospf-wireless-design@megatron.ietf.org;
	Wed, 06 Apr 2005 20:05:20 -0400
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 UAA24139
	for <ospf-wireless-design@ietf.org>;
	Wed, 6 Apr 2005 20:05:17 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJKep-0002vD-Le
	for ospf-wireless-design@ietf.org; Wed, 06 Apr 2005 20:14:05 -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
	RAA10839; Wed, 6 Apr 2005 17:05:09 -0700 (PDT)
Received: from XCH-NWBH-02.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
	j37057724782; Wed, 6 Apr 2005 19:05:08 -0500 (CDT)
Received: from XCH-NW-27.nw.nos.boeing.com ([192.48.4.101]) by
	XCH-NWBH-02.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 6 Apr 2005 17:05:04 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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] Algorithms and optimizations
Date: Wed, 6 Apr 2005 17:05:04 -0700
Message-ID: <6938661A6EDA8A4EA8D1419BCE46F24C04060AF0@xch-nw-27.nw.nos.boeing.com>
Thread-Topic: [Ospf-wireless-design] Algorithms and optimizations
Thread-Index: AcU6NosO+MBToCsuSp6/eDOgNxX7ZgAzhOEQ
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Padma Pillay-Esnault" <ppe@cisco.com>, <ospf-wireless-design@ietf.org>
X-OriginalArrivalTime: 07 Apr 2005 00:05:05.0090 (UTC)
	FILETIME=[73A38A20:01C53B05]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08e48e05374109708c00c6208b534009
Content-Transfer-Encoding: quoted-printable
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: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: quoted-printable

Padma, thanks for your observations.  I will try to account for them in
our next simulation release.  We are presently trying to compare basic
operation in an apples-to-apples comparison (as best we can).  We are
also trying to implement things in a modular way so that we can turn
features on and off (for example, running with/without differential
hellos).=20

Tom

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


From ospf-wireless-design-bounces@ietf.org  Wed Apr  6 23:51:09 2005
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 XAA09617;
	Wed, 6 Apr 2005 23:51:09 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DJOBS-0007OQ-J1; Wed, 06 Apr 2005 23:59:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DJO1X-0000FM-Jz; Wed, 06 Apr 2005 23:49:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DJO1V-0000FH-Mh
	for ospf-wireless-design@megatron.ietf.org;
	Wed, 06 Apr 2005 23:49:41 -0400
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 XAA09595
	for <ospf-wireless-design@ietf.org>;
	Wed, 6 Apr 2005 23:49:38 -0400 (EDT)
Received: from pop-a065c28.pas.sa.earthlink.net ([207.217.121.205])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DJO9z-0007NY-Cf
	for ospf-wireless-design@ietf.org; Wed, 06 Apr 2005 23:58:27 -0400
Received: from dialup-4.243.140.248.dial1.sanfrancisco1.level3.net
	([4.243.140.248] helo=earthlink.net)
	by pop-a065c28.pas.sa.earthlink.net with esmtp (Exim 3.36 #10)
	id 1DJO1O-0001rm-00; Wed, 06 Apr 2005 20:49:35 -0700
Message-ID: <4254ADCE.3010706@earthlink.net>
Date: Wed, 06 Apr 2005 20:49:34 -0700
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: Padma Pillay-Esnault <ppe@cisco.com>
Subject: Re: [Ospf-wireless-design] Algorithms and optimizations
References: <42531C3A.5000903@cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 2.9 (++)
X-Scan-Signature: c83ccb5cc10e751496398f1233ca9c3a
Content-Transfer-Encoding: 7bit
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@ietf.org
Errors-To: ospf-wireless-design-bounces@ietf.org
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2
Content-Transfer-Encoding: 7bit

Padma,

A given technique (or optimization) may be more beneficial to one
approach than to another approach. For example, if you want to compare
using a jet versus using a propeller on aircraft, it would be foolish
to insist that both aircraft use the same body. A body that works well
with a propeller might break apart if a jet were used, and the design
team might come to the false conclusion that propellers are superior
to jets.

Regarding OSPF extensions, both approaches are actually optimizations
of OSPF, so when you say to compare the approaches without any
optimizations, it might not be easy to define what that means.

The technique of reducing the set of adjacencies is an example of a
technique that *might* work better in the MDR (Manet Designated Router)
approach than the MPR approach.  In fact, reducing the number of
adjacencies is one of the main design goals of the MPR approach.
So, if we are forced to compare the two approaches assuming that all
neighbors are adjacent (which could result in more than 2000
adjacencies in a dense 100-node network), the overhead due to forming
adjacencies might dominate the total overhead, and one might conclude
that both methods perform about the same. On the other hand, if we
allow both approaches to employ whatever technique it can to reduce
the number of adjacencies, the two approaches might perform quite
differently.

> - Clearly define in which circumstances the optimizations that really 
> make sense. For instance, limiting adjacencies is an interesting 
> concept only if there is a high number of nodes potentially going out 
> of range. However, it adds unnecessary complexity if the nodes have a 
> wide range and less likely to drop out. In other words, do these 
> scenarios really matter or are they unlikely in the particular nework 
> we are addressing.  Also, optimizations should retain their optional 
> character.


Limiting adjacencies is interesting even if all nodes are always in
range of each other. In fact, that is the reason why adjacencies are
limited in an OSPF broadcast network. Instead of n(n-1) adjacencies,
there are only 2n - 3 adjacencies, since each router is adjacent only
to the DR and BDR. The main idea of the MDR approach is to generalize
this technique to multi-hop networks.

However, I agree that (in most cases) optimizations should be optional.

Richard




Padma Pillay-Esnault wrote:

>
> Looking at the multiple threads lately, it seems that the discussions 
> are drifting to evaluating the optimizations
> of one proposal as an argument versus another. We think that we should 
> bear in mind that it is the base algorithm that is of prime importance.
>
> While some optimizations are required for scalability, they can be 
> applied to both base algorithms and hence they should have a limited 
> weight on evaluation of a proposal.
>
> Another essential foundation is OSPFv3, changes that impact the basic 
> protocol have to be evaluated.
> In the real world, existing stacks will need to be changed to 
> incorporate wireless interface. How much
> of these changes can it really absorb and still function correctly? 
> The extent of change has to be evaluated carefully so as not to 
> jeopardise stability and  uncover  corner cases that have a nagging 
> habit of popping
> up pretty late in the game. We think that changes should be limited to 
> what is really essential for manet to
> perform.
>
> Most of the optimizations are applicable to both base algorithms and 
> including them only adds more
> parameters that blur what should really be evaluated. Some 
> optimizations can be palliatives and hence
> they cannot be used to validate the base algorithms.
>
> IMHO, evaluation should be done thru a number of clearly defined 
> criteria. A first attempt
> could look like the following
> - Comparison of base algorithm without any optimization.
> - Evaluation of the changes required to the OSPFv3 protocol , bearing 
> in mind extensive changes
> usually spell instability and newly discovered corner cases.
> - Leverage of existing proven mechanisms of the OSPFv3 protocol.
> - Clearly define in which circumstances the optimizations that really 
> make sense. For instance, limiting adjacencies is an interesting 
> concept only if there is a high number of nodes potentially going out 
> of range. However, it adds unnecessary complexity if the nodes have a 
> wide range and less likely to drop out. In other words, do these 
> scenarios really matter or are they unlikely in the particular nework 
> we are addressing.  Also, optimizations should retain their optional 
> character.
> - Last but not the least, identify the sector most likely to 
> deployment of this technology and tackle their specific
> problems and perks first.
>
>
> Padma
>
> _______________________________________________
> 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


From ospf-wireless-design-bounces@ietf.org  Tue Apr 12 12:47:10 2005
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 MAA14510;
	Tue, 12 Apr 2005 12:47:10 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLOhJ-0006We-5u; Tue, 12 Apr 2005 12:57:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLOUa-0003sw-Jg; Tue, 12 Apr 2005 12:44:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLOUY-0003nh-Tv
	for ospf-wireless-design@megatron.ietf.org;
	Tue, 12 Apr 2005 12:43:58 -0400
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 MAA14000
	for <ospf-wireless-design@ietf.org>;
	Tue, 12 Apr 2005 12:43:34 -0400 (EDT)
Received: from pop-a065c32.pas.sa.earthlink.net ([207.217.121.247])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLOdp-0006ML-4J
	for ospf-wireless-design@ietf.org; Tue, 12 Apr 2005 12:53:34 -0400
Received: from dialup-4.243.131.232.dial1.sanfrancisco1.level3.net
	([4.243.131.232] helo=earthlink.net)
	by pop-a065c32.pas.sa.earthlink.net with esmtp (Exim 3.36 #10)
	id 1DLOU9-0001et-00
	for ospf-wireless-design@ietf.org; Tue, 12 Apr 2005 09:43:34 -0700
Message-ID: <425BFAB0.5040006@earthlink.net>
Date: Tue, 12 Apr 2005 09:43:28 -0700
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
Subject: Re: [Ospf-wireless-design] Another example for self-selected MPRs
References: <424A0B78.1010203@earthlink.net> <20050405195115.GA20498@cisco.com>
	<425313A1.6040109@earthlink.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit
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: 0.1 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Content-Transfer-Encoding: 7bit

I want to mention another design goal of of the MDR/BMDR flooding
procedure.  I wanted it to be useful for other MANET applications
that do not require reliable flooding and therefore do not use ACKs.
Thus, I designed the flooding procedure so that it provides redundancy
(via the BMDRs) to improve the delivery ratio even if ACKs are not used.
Thus, a BMDR forwards an LSA not based on ACKs, but based on
whether the neighboring relays that transmitted the LSA cover
all neighbors.  Thus, the flooding procedure is separate from
the reliability procedure (ACKs and retransmissions).

Non-active overlapping relays (NAORs) require that ACKs be
used, since all NAORs will eventually forward each LSA if it
is never ACKed.  (If we disable the NAORs in applications that
do not use ACKs, so that only active MPRs forward LSAs, then
reliability will be poor, especially if it can take 6 seconds
to select a new MPR following a link failure.)

Also, the use of Hellos instead of router LSAs to learn 2-hop neighbor
information makes the flooding protocol more modular (since it
does not depend on LSAs), allowing it to be used for other
MANET applications.

Another design goal is scalability. I wanted the overhead to increase
linearly with the number of nodes for a fixed network diameter,
i.e., to increase linearly with the density (average node degree).
This is true for MDR flooding whether we consider 100 nodes, 1000 nodes,
or 10,000 nodes. MPRs are also scalable, since the average number of
MPRs per node is roughly constant as the node degree increases.
But this is not true for non-active overlapping relays (NAORs).
There must be a time interval DELTA such that if two NAORs
decide to forward the same LSA within time DELTA of each other,
then both will forward the LSA. Therefore, if the node degree
is large enough, so that the number of NAORs is large enough,
then the number of NAORs that decide to forward a given LSA
will increase linearly with the node degree. This will cause
the total number of LSA transmissions to increase quadratically
with the network density, which is something I wanted to avoid.

(Even though the NAORs are triggered only when MPRs are temporarily
unavailable following topology changes, this will be some percentage
of time depending on the degree of mobility, and in any case
the resulting quadratic term will dominate the total overhead
for a sufficently dense network.)

Richard





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


From ospf-wireless-design-bounces@ietf.org  Wed Apr 13 00:34:00 2005
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 AAA16920;
	Wed, 13 Apr 2005 00:34:00 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLZjR-0002ig-PR; Wed, 13 Apr 2005 00:44:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLZWw-0001M7-DL; Wed, 13 Apr 2005 00:31:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLZWv-0001LX-9w
	for ospf-wireless-design@megatron.ietf.org;
	Wed, 13 Apr 2005 00:31:09 -0400
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 AAA16470
	for <ospf-wireless-design@ietf.org>;
	Wed, 13 Apr 2005 00:30:57 -0400 (EDT)
Received: from nez-perce.inria.fr ([192.93.2.78])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLZgT-0002eH-Q7
	for ospf-wireless-design@ietf.org; Wed, 13 Apr 2005 00:41:03 -0400
Received: from yamacraw.inria.fr (yamacraw.inria.fr [128.93.24.137])
	by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j3D4UjIY030193
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 13 Apr 2005 06:30:46 +0200
Received: from yamacraw.inria.fr (localhost [127.0.0.1])
	by yamacraw.inria.fr (8.13.0/8.13.0) with ESMTP id j3D4UjNQ028432;
	Wed, 13 Apr 2005 06:30:45 +0200
Received: (from apache@localhost)
	by yamacraw.inria.fr (8.13.0/8.12.10/Submit) id j3D4UjvA028431;
	Wed, 13 Apr 2005 06:30:45 +0200
X-Authentication-Warning: yamacraw.inria.fr: apache set sender to
	Emmanuel.Baccelli@inria.fr using -f
Received: from px2.hitachi.co.jp (px2.hitachi.co.jp [202.246.252.97]) 
	by pops-rocq.inria.fr (IMP) with HTTP 
	for <ebaccell@yamacraw.inria.fr>; Wed, 13 Apr 2005 06:30:45 +0200
Message-ID: <1113366645.425ca07537550@pops-rocq.inria.fr>
Date: Wed, 13 Apr 2005 06:30:45 +0200
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
To: ospf-wireless-design@ietf.org
Subject: Re: [Ospf-wireless-design] Another example for self-selected MPRs
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Originating-IP: 202.246.252.97
X-Miltered: at nez-perce with ID 425CA075.001 by Joe's j-chkmail
	(http://j-chkmail.ensmp.fr)!
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Content-Transfer-Encoding: 8bit
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: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Content-Transfer-Encoding: 8bit


See comments bellow...

Richard Ogier wrote:

> I want to mention another design goal of of the MDR/BMDR flooding
> procedure.  I wanted it to be useful for other MANET applications
> that do not require reliable flooding and therefore do not use ACKs.
> Thus, I designed the flooding procedure so that it provides redundancy
> (via the BMDRs) to improve the delivery ratio even if ACKs are not used.
> Thus, a BMDR forwards an LSA not based on ACKs, but based on
> whether the neighboring relays that transmitted the LSA cover
> all neighbors.  Thus, the flooding procedure is separate from
> the reliability procedure (ACKs and retransmissions).
>
> Non-active overlapping relays (NAORs) require that ACKs be
> used, since all NAORs will eventually forward each LSA if it
> is never ACKed.  (If we disable the NAORs in applications that
> do not use ACKs, so that only active MPRs forward LSAs, then
> reliability will be poor, especially if it can take 6 seconds
> to select a new MPR following a link failure.)
>


The way i see it is that Overlapping Relays are largely based on 
MPRs. The difference between them is enssentially that Overlapping Relays 
also make use of OSPF Acks as an additionnal signalling mechanism to 
trigger some re-transmissions if needed. That is, if LSAs are not generated
frequently enough to provide reliability through periodicity.

This said, i think it remains to be seen wether MPRs are more, or less 
reliable than a source independent approach in case of dense networks or 
networks with a "sufficient" link failure rates.

Actually, having MPRs should be an advantage in such cases: if a node X 
fails to re-transmit a broadcast, some neighbor node Y should receive it 
from an mpr selector (instead of from X) and will thus retransmit, 
naturally covering up X's failure. Whereas with a source independent
approach, if node X fails to emit, then basically nobody will.

Having some backup (basically doubling up the CDS) helps a little to go in the 
direction of the MPR approach, but the generalization of the backing-up in a
decentralized environment like an ad-hoc network may indeed be much better off
with MPRs.

I think some real experience needs to be gathered with source-independent
approaches, in order to compare it fairly with the real experience that 
has been gathered over the years and on the field with ad-hoc networking with
MPRs. 

Until then, we can also compare simulations. I am curious to see some results 
comparing, say, the delivery rate in case of mobility (i.e. "sufficient"
link failure rates) for an MPR approach and a source independent approach?


Emmanuel


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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


From ospf-wireless-design-bounces@ietf.org  Wed Apr 13 13:31:46 2005
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 NAA16303;
	Wed, 13 Apr 2005 13:31:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLlsF-0005hF-8a; Wed, 13 Apr 2005 13:41:59 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLld8-0001bS-CW; Wed, 13 Apr 2005 13:26:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLld6-0001bF-VF
	for ospf-wireless-design@megatron.ietf.org;
	Wed, 13 Apr 2005 13:26:21 -0400
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 NAA16001
	for <ospf-wireless-design@ietf.org>;
	Wed, 13 Apr 2005 13:26:09 -0400 (EDT)
Received: from blv-smtpout-01.boeing.com ([130.76.32.69])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLlmo-0005Yk-3h
	for ospf-wireless-design@ietf.org; Wed, 13 Apr 2005 13:36:22 -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
	KAA27922; Wed, 13 Apr 2005 10:25:55 -0700 (PDT)
Received: from XCH-NWBH-02.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
	j3DHPsm00241; Wed, 13 Apr 2005 12:25:54 -0500 (CDT)
Received: from XCH-NW-27.nw.nos.boeing.com ([192.48.4.101]) by
	XCH-NWBH-02.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); 
	Wed, 13 Apr 2005 10:25:49 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.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] Another example for self-selected MPRs
Date: Wed, 13 Apr 2005 10:25:49 -0700
Message-ID: <6938661A6EDA8A4EA8D1419BCE46F24C04060B04@xch-nw-27.nw.nos.boeing.com>
Thread-Topic: [Ospf-wireless-design] Another example for self-selected MPRs
Thread-Index: AcU/4gD9iPtblsRiRc+/DBtWfS56mAAXFt4w
From: "Henderson, Thomas R" <thomas.r.henderson@boeing.com>
To: "Emmanuel Baccelli" <Emmanuel.Baccelli@inria.fr>,
        <ospf-wireless-design@ietf.org>
X-OriginalArrivalTime: 13 Apr 2005 17:25:49.0649 (UTC)
	FILETIME=[D5F99410:01C5404D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: quoted-printable
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: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: quoted-printable

=20

> -----Original Message-----
> From: Emmanuel Baccelli [mailto:Emmanuel.Baccelli@inria.fr]=20
> Sent: Tuesday, April 12, 2005 9:31 PM
> To: ospf-wireless-design@ietf.org
> Subject: Re: [Ospf-wireless-design] Another example for=20
> self-selected MPRs
>=20
>=20
> This said, i think it remains to be seen wether MPRs are=20
> more, or less reliable than a source independent approach in=20
> case of dense networks or networks with a "sufficient" link=20
> failure rates.
>=20
> Actually, having MPRs should be an advantage in such cases:=20
> if a node X fails to re-transmit a broadcast, some neighbor=20
> node Y should receive it from an mpr selector (instead of=20
> from X) and will thus retransmit, naturally covering up X's=20
> failure. Whereas with a source independent approach, if node=20
> X fails to emit, then basically nobody will.
>=20

I don't think the last statement accurately depicts the situation with
the approach proposed by Richard.   There are two related mechanisms at
work:  flooding, and retransmissions along adjacencies.  MDRs and MBDRs
are used during the initial flood (with MBDRs waiting for a short
backoff interval to flood, while suppressing if the MDRs are sensed to
have done their job).  These LSAs are also put on the retransmission
list and retransmitted if needed.  The adjacencies in Richard's proposal
also line up with the MDRs and MBDRs for convenience, although fuller
topologies are possible.  So an LSA is flooded by DRs, the flood is
backed up by BDR, and retransmissions along adjacencies back up those
floods.  If for some reason the floods fail and the adjacencies fail
simultaneously, the receiver will form new adjacencies and recover the
LSA via synchronization.

Tom

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


From ospf-wireless-design-bounces@ietf.org  Thu Apr 14 01:58:40 2005
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 BAA14206;
	Thu, 14 Apr 2005 01:58:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLxX7-0000r8-UK; Thu, 14 Apr 2005 02:08:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLxK0-0005w8-GD; Thu, 14 Apr 2005 01:55:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLxJs-0005us-2d
	for ospf-wireless-design@megatron.ietf.org;
	Thu, 14 Apr 2005 01:55:16 -0400
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 BAA13948
	for <ospf-wireless-design@ietf.org>;
	Thu, 14 Apr 2005 01:55:07 -0400 (EDT)
Received: from nez-perce.inria.fr ([192.93.2.78])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLxTf-0000lD-Tp
	for ospf-wireless-design@ietf.org; Thu, 14 Apr 2005 02:05:24 -0400
Received: from yamacraw.inria.fr (yamacraw.inria.fr [128.93.24.137])
	by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j3E5ssRm000750
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <ospf-wireless-design@ietf.org>; Thu, 14 Apr 2005 07:54:54 +0200
Received: from yamacraw.inria.fr (localhost [127.0.0.1])
	by yamacraw.inria.fr (8.13.0/8.13.0) with ESMTP id j3E5srR0027326
	for <ospf-wireless-design@ietf.org>; Thu, 14 Apr 2005 07:54:53 +0200
Received: (from apache@localhost)
	by yamacraw.inria.fr (8.13.0/8.12.10/Submit) id j3E5sqPD027323
	for ospf-wireless-design@ietf.org; Thu, 14 Apr 2005 07:54:52 +0200
X-Authentication-Warning: yamacraw.inria.fr: apache set sender to
	Emmanuel.Baccelli@inria.fr using -f
Received: from px2.hitachi.co.jp (px2.hitachi.co.jp [202.246.252.97]) 
	by pops-rocq.inria.fr (IMP) with HTTP 
	for <ebaccell@yamacraw.inria.fr>; Thu, 14 Apr 2005 07:54:52 +0200
Message-ID: <1113458092.425e05acc569a@pops-rocq.inria.fr>
Date: Thu, 14 Apr 2005 07:54:52 +0200
From: Emmanuel Baccelli <Emmanuel.Baccelli@inria.fr>
To: ospf-wireless-design@ietf.org
Subject: Re: [Ospf-wireless-design] Another example for self-selected MPRs
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.2.2
X-Originating-IP: 202.246.252.97
X-Miltered: at nez-perce with ID 425E05AE.000 by Joe's j-chkmail
	(http://j-chkmail.ensmp.fr)!
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
Content-Transfer-Encoding: 8bit
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: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Content-Transfer-Encoding: 8bit


Comments in below


Henderson, Thomas R wrote:

> 
>
>>-----Original Message-----
>>From: Emmanuel Baccelli [mailto:Emmanuel.Baccelli@inria.fr] 
>>Sent: Tuesday, April 12, 2005 9:31 PM
>>To: ospf-wireless-design@ietf.org
>>Subject: Re: [Ospf-wireless-design] Another example for 
>>self-selected MPRs
>>
>>
>>This said, i think it remains to be seen wether MPRs are 
>>more, or less reliable than a source independent approach in 
>>case of dense networks or networks with a "sufficient" link 
>>failure rates.
>>
>>Actually, having MPRs should be an advantage in such cases: 
>>if a node X fails to re-transmit a broadcast, some neighbor 
>>node Y should receive it from an mpr selector (instead of 
>>from X) and will thus retransmit, naturally covering up X's 
>>failure. Whereas with a source independent approach, if node 
>>X fails to emit, then basically nobody will.
>>
>
>I don't think the last statement accurately depicts the situation with
>the approach proposed by Richard.   There are two related mechanisms at
>work:  flooding, and retransmissions along adjacencies.  MDRs and MBDRs
>are used during the initial flood (with MBDRs waiting for a short
>backoff interval to flood, while suppressing if the MDRs are sensed to
>have done their job).  These LSAs are also put on the retransmission
>list and retransmitted if needed.  The adjacencies in Richard's proposal
>also line up with the MDRs and MBDRs for convenience, although fuller
>topologies are possible.  So an LSA is flooded by DRs, the flood is
>backed up by BDR, and retransmissions along adjacencies back up those
>floods.  If for some reason the floods fail and the adjacencies fail
>simultaneously, the receiver will form new adjacencies and recover the
>LSA via synchronization.
>
>Tom
>
>


Yes. I was talking about the base algorithms (CDS, MPR) behind the specific
mechanisms proposed by Richard and by Cisco for the purpose of OSPF on
wireless. 



Emmanuel


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

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


