IETF Logo Mail Archive

Re: OSPF WG Charter Proposal

Rohit Dube <rohit@XEBEO.COM> Tue, 29 October 2002 18:48 UTC

Received: from cherry.ease.lsoft.com (cherry.ease.lsoft.com [209.119.0.109]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19081 for <ospf-archive@LISTS.IETF.ORG>; Tue, 29 Oct 2002 13:48:47 -0500 (EST)
Received: from walnut (209.119.0.61) by cherry.ease.lsoft.com (LSMTP for Digital Unix v1.1b) with SMTP id <5.007998FA@cherry.ease.lsoft.com>; Tue, 29 Oct 2002 13:51:09 -0500
Received: from DISCUSS.MICROSOFT.COM by DISCUSS.MICROSOFT.COM (LISTSERV-TCP/IP release 1.8e) with spool id 355976 for OSPF@DISCUSS.MICROSOFT.COM; Tue, 29 Oct 2002 13:51:09 -0500
Received: from 204.192.44.242 by WALNUT.EASE.LSOFT.COM (SMTPL release 1.0f) with TCP; Tue, 29 Oct 2002 13:51:09 -0400
Received: (qmail 2444 invoked from network); 29 Oct 2002 18:51:08 -0000
Received: from bigbird.xebeo.com (192.168.0.21) by lxmail.xebeo.com with SMTP; 29 Oct 2002 18:51:08 -0000
Received: from bigbird.xebeo.com (localhost.localdomain [127.0.0.1]) by bigbird.xebeo.com (8.9.3/8.9.3) with ESMTP id NAA04737 for <OSPF@DISCUSS.MICROSOFT.COM>; Tue, 29 Oct 2002 13:51:08 -0500
X-Mailer: exmh version 2.1.1 10/15/1999
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID: <200210291851.NAA04737@bigbird.xebeo.com>
Date: Tue, 29 Oct 2002 13:51:08 -0500
Reply-To: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
Sender: Mailing List <OSPF@DISCUSS.MICROSOFT.COM>
From: Rohit Dube <rohit@XEBEO.COM>
Subject: Re: OSPF WG Charter Proposal
To: OSPF@DISCUSS.MICROSOFT.COM
In-Reply-To: Message from "Manral, Vishwas" <VishwasM@NETPLANE.COM> of "Tue, 29 Oct 2002 08:22:54 EST." <E7E13AAF2F3ED41197C100508BD6A328791918@india_exch.hyderabad.mindspeed.com>
Precedence: list

On Tue, 29 Oct 2002 08:22:54 -0500 "Manral, Vishwas" writes:
=>Hi Rohit/Acee,
=>
=>>Is anybody running OSPF networks hitting this problem with no workarounds
=>in sight?
=>I am not sure about this statement exactly, however I do think it can be
=>helpful in a few cases. A recent paper by Aman Shaikh/Albert Greenberg
=>et.al. about analyzing OSPF for Enterprise is one such case. One of our
=>drafts "Congestion Avoidance and Control for OSPF networks" talks about
=>problems that have been caused by flooding overload in production networks.
[snip]

Vishwas,

I am familiar with Aman's work. The problem identified there was
that of (a) sub-optimal network/ospf configuration and (b) broken router.
This does not ofcourse justify building new protocol mechanisms, thereby
complicating the protocol.

I will look at the congestion again to see if/why it concludes otherwise.

Regards,
--rohit.

v2.23.0 | Report a Bug | By Email