Re: [Ospf-manet] Re: Ospf-manet Digest, Vol 11, Issue 5

Russ White <riw@cisco.com> Tue, 03 October 2006 00:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUYDI-0007Hx-Mo; Mon, 02 Oct 2006 20:32:48 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUYDH-0007Fw-KY for ospf-manet@ietf.org; Mon, 02 Oct 2006 20:32:47 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUYDC-0005BU-CC for ospf-manet@ietf.org; Mon, 02 Oct 2006 20:32:47 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 02 Oct 2006 17:32:42 -0700
X-IronPort-AV: i="4.09,246,1157353200"; d="scan'208"; a="44564783:sNHT52161340"
Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-1.cisco.com (8.12.11.20060308/8.12.11) with ESMTP id k930WgEw023415; Mon, 2 Oct 2006 20:32:42 -0400
Received: from [127.0.0.1] (rtp-ruwhite-vpn13.cisco.com [10.82.175.126]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with SMTP id k930WfuI022804; Mon, 2 Oct 2006 20:32:41 -0400 (EDT)
Message-ID: <4521AFA8.3070404@cisco.com>
Date: Mon, 02 Oct 2006 20:32:40 -0400
From: Russ White <riw@cisco.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: Aniket Desai <adesai@opnet.com>
Subject: Re: [Ospf-manet] Re: Ospf-manet Digest, Vol 11, Issue 5
References: <E1GUWT8-0002On-J2@megatron.ietf.org> <6.2.3.4.2.20061002185302.036db250@mailserver.opnet.com>
In-Reply-To: <6.2.3.4.2.20061002185302.036db250@mailserver.opnet.com>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
DKIM-Signature: a=rsa-sha1; q=dns; l=1628; t=1159835562; x=1160699562; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=riw@cisco.com; z=From:Russ=20White=20<riw@cisco.com> |Subject:Re=3A=20[Ospf-manet]=20Re=3A=20Ospf-manet=20Digest, =20Vol=2011, =20Issue= 205 |To:Aniket=20Desai=20<adesai@opnet.com>; X=v=3Dcisco.com=3B=20h=3D8XZFTs8twLCb1uaNictC/7s9Wmk=3D; b=mGanBzQgphTq33XLMpEz2a7RY4W/cFhepJm5kspAt+8+yQZ01+HZ+hPHW2rhnkUT2tELADkG 6wN7eL7/2gOUluKp/OyExkuQYtrogQ+N0TCKQ6+i2aWS5pem1zgcnDO/;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=riw@cisco.com; dkim=pass ( 27 extraneous bytes; sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Cc: ospf-manet@ietf.org
X-BeenThere: ospf-manet@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions of OSPFv3 extensions supporting MANET <ospf-manet.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf-manet>, <mailto:ospf-manet-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf-manet>
List-Post: <mailto:ospf-manet@ietf.org>
List-Help: <mailto:ospf-manet-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf-manet>, <mailto:ospf-manet-request@ietf.org?subject=subscribe>
Errors-To: ospf-manet-bounces@ietf.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


>> IMHO, it doesn't matter what you think is a "natural" and "unnatural"
>> extension to OSPF. What should matter is the requirements, and the way
>> to solve those requirements.
> 
> - Let's say OSPF-MDR is a natural way to extend OSPF's broadcast
> interface for MANET type physical medium. It should be an acceptable

Let's not use the term "natural" at all. It's completely orthogonal to
the discussion.

> If you agree that OSPF is about maintaining a connected/biconnected
> adjacency graph that is rooted towards its leaders (DR and BDR) which

I don't. There's no such thing as "leaders" in OSPF. There is such a
thing in Spanning Tree--perhaps you're mixing up ST and OSPF? Or you're
confusing the SPF tree, with it's root, with the concept of adjacencies?
DRs and BDRs are optimizations for broadcast links--OSPF would work just
fine without them. Do you know the history of p-nodes in IS-IS?

Hence, a "two hop extension" to OSPF's DR's isn't "natural" in any sense
of the term, and it's not necessarily, the best way to extend the protocol.

Again, let's get past the pejorative terms. Somehow, we've forgotten
history and context here. There's no such thing as a "natural"
extension, it doesn't matter how many times anyone repeats it on list.

:-)

Russ


- --
riw@cisco.com CCIE <>< Grace Alone

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFIa+oER27sUhU9OQRAtF5AJwP+LbvcwZJGRABFtEVcrIQnLoCtACghVLj
S3B6yIjNPjvq9Dha1KF7tCY=
=P0k+
-----END PGP SIGNATURE-----

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