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

Acee Lindem <acee@cisco.com> Mon, 02 October 2006 17:39 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GURkz-0002QV-7U; Mon, 02 Oct 2006 13:39:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GURky-0002Oq-85 for ospf-manet@ietf.org; Mon, 02 Oct 2006 13:39:08 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GURkv-00072n-W4 for ospf-manet@ietf.org; Mon, 02 Oct 2006 13:39:08 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-1.cisco.com with ESMTP; 02 Oct 2006 10:39:06 -0700
X-IronPort-AV: i="4.09,245,1157353200"; d="scan'208"; a="44523087:sNHT50412320"
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 k92Hd5nx006792 for <ospf-manet@ietf.org>; Mon, 2 Oct 2006 13:39:05 -0400
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k92Hd5uI012521 for <ospf-manet@ietf.org>; Mon, 2 Oct 2006 13:39:05 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Oct 2006 13:39:05 -0400
Received: from [10.82.224.123] ([10.82.224.123]) by xfe-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Oct 2006 13:39:05 -0400
Message-ID: <45214EB8.5030605@cisco.com>
Date: Mon, 02 Oct 2006 13:39:04 -0400
From: Acee Lindem <acee@cisco.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
CC: ospf-manet@ietf.org
Subject: Re: [Ospf-manet] Re: Ospf-manet Digest, Vol 11, Issue 2
References: <E1GUPOB-0000FA-SD@megatron.ietf.org> <6.2.3.4.2.20061002125614.036ec290@mailserver.opnet.com>
In-Reply-To: <6.2.3.4.2.20061002125614.036ec290@mailserver.opnet.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Oct 2006 17:39:05.0560 (UTC) FILETIME=[A833B580:01C6E649]
DKIM-Signature: a=rsa-sha1; q=dns; l=1243; t=1159810745; x=1160674745; c=relaxed/simple; s=rtpdkim1001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=acee@cisco.com; z=From:Acee=20Lindem=20<acee@cisco.com> |Subject:Re=3A=20[Ospf-manet]=20Re=3A=20Ospf-manet=20Digest, =20Vol=2011, =20Issue= 202; X=v=3Dcisco.com=3B=20h=3Dd1alR2vT0d1rHILikmkbvIMYDbQ=3D; b=BAGagZXKhUVT2cOOgaHbpuHOiszACBLvjEzMKcEfV0wBbbF49vbejlnUCALi9McESMLpM16U EhHJPDCbloP+xg5vYcp+yb2AhtOWIhTcIpHuiaJXkw2SoDA/iHebsvAP;
Authentication-Results: rtp-dkim-1.cisco.com; header.From=acee@cisco.com; dkim=pass ( sig from cisco.com verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
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

Let me summarize where I think we are  - In Dallas I believe we did have
a "rough" consensus among those actively participated on the OSPF
wireless design team that the core OSPF MDR algorithm for flooding
and adjacency reduction should be the approach that we submit to the
OSPF/MANET WGs for consideration. This didn't include topology reduction
or some of the other enhancements that are confusing the discussion today.
We did vastly under estimate the arguments based on factors other than
those considered by the design team. These arguments came from
minority members of the design team including some who heretofore hadn't
participated as well as other interested individuals. These factors include
computation complexity, deployment momentum, disagreement with the
problem statement, and possibly even the reluctance or inability
to understand the MDR draft. Any others?

The question is where we go now. Independent of draft status,  it doesn't
look like we'll easily reach an agreement.Going forward with multiple 
drafts
is one option but everyone should realize that this will also impact future
optimizations which will undoubtedly be proposed for the contentious OSPF
MANET interface type.

Thanks,
Acee

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