Re: [Ospf-wireless-design] OSPF Wireless Design Team Minutes

"Madhavi W. Chandra" <mchandra@cisco.com> Thu, 24 March 2005 15:20 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 KAA22345; Thu, 24 Mar 2005 10:20:49 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DEUEO-0006pS-RP; Thu, 24 Mar 2005 10:26:45 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DEU80-0005bC-He; Thu, 24 Mar 2005 10:20:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DEU7z-0005b7-77 for ospf-wireless-design@megatron.ietf.org; Thu, 24 Mar 2005 10:20:07 -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 KAA22233 for <ospf-wireless-design@ietf.org>; Thu, 24 Mar 2005 10:20:05 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DEUDg-0006nv-Mo for ospf-wireless-design@ietf.org; Thu, 24 Mar 2005 10:26:00 -0500
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 24 Mar 2005 10:38:25 -0500
X-IronPort-AV: i="3.91,119,1110171600"; d="scan'208"; a="41748695:sNHT55758252538"
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 j2OFJOjI017189; Thu, 24 Mar 2005 10:19:24 -0500 (EST)
Received: (mchandra@localhost) by mchandra-u10.cisco.com (8.11.2/CISCO.WS.1.2) id j2OFJOT15730; Thu, 24 Mar 2005 10:19:24 -0500 (EST)
Date: Thu, 24 Mar 2005 10:19:23 -0500
From: "Madhavi W. Chandra" <mchandra@cisco.com>
To: Acee Lindem <acee@cisco.com>
Subject: Re: [Ospf-wireless-design] OSPF Wireless Design Team Minutes
Message-ID: <20050324151923.GC15716@cisco.com>
References: <422F4539.5070108@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <422F4539.5070108@cisco.com>
User-Agent: Mutt/1.4i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
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: 5a9a1bd6c2d06a21d748b7d0070ddcb8

Hi All,

On Wed, Mar 09, 2005 at 01:49:29PM -0500, Acee Lindem wrote:
> All,
> 
> Yesterday morning Tom Henderson, Thomas Clausen, Joe Macker, Emmanuel 
> Baccelli,
> and I got together to design team issues, progress, and actions. This 
> E-mail includes my
> notes from the meeting. Please feel free to add comments and corrections.
> 
> One of the first things we discussed was how to handle the evolution of 
> requirements.
> All of us agreed that if we were going to make any progress we needed to 
> stick to the
> original charter of the design. Joe reiterated that the MANET WG is 
> actively pursing
> protocols optimized to MANET environments including reactive protocols. 
> I added
> that it would be interesting to see how either the protocols and/or 
> concepts could
> be seamlessly integrated with OSPF (however, that also is not within the 
> scope
> of the design team).

I agree that this is not within the scope of the DT right now.  However,
we must be cognizant of this fact.  Meaning, the DT should minimize the
changes to OSPF and the optimized flooding scheme, realizing that the
MANET WG may come out with a different flooding scheme down the line that
may need to be adopted.   As we all decided in the DT charter, we
should minimize the changes to OSPF, and any changes should be able to
work with standard OSPF nodes.

This is the approach that we (Cisco) have taken in our Overlapping Relays.  
The Overlapping Relays reduce the overhead in flooding as compared to 
standard OSPF (I will share some internal scalability testing that we did
in another email), without much changes to the way flooding works in OSPF.  
Essentially, Overlapping Relays suppresses redundant transmissions by 
neighbors without compromising reliability.  It uses timers and 
knowledge of 2-hop neighborhood which is already available in LSAs (this 
can also be done via Hellos if necessary), without modifying/affecting 
adjacencies, data plane, etc.  At most, it slightly delays flooding, but 
within the retransmission time.  Studies on packet delivery ratio and
throughput have shown favorable results (again, I will share our
scalability testing in another email.)

We have been receiving very positive feedback on its behavior *and* 
simplicity/compatability from our customers that have been using code 
drops of our implementation.

Thanks,
Madhavi

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