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

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

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUUrb-0008QQ-6C; Mon, 02 Oct 2006 16:58:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUUra-0008QL-5N for ospf-manet@ietf.org; Mon, 02 Oct 2006 16:58:10 -0400
Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUUrX-0007vd-LP for ospf-manet@ietf.org; Mon, 02 Oct 2006 16:58:10 -0400
Received: from rtp-dkim-1.cisco.com ([64.102.121.158]) by rtp-iport-2.cisco.com with ESMTP; 02 Oct 2006 16:58:07 -0400
X-IronPort-AV: i="4.09,245,1157342400"; d="scan'208"; a="105429898:sNHT339873736"
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 k92Kw7OI015092; Mon, 2 Oct 2006 16:58:07 -0400
Received: from xbh-rtp-211.amer.cisco.com (xbh-rtp-211.cisco.com [64.102.31.102]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k92Kw7uI004938; Mon, 2 Oct 2006 16:58:07 -0400 (EDT)
Received: from xfe-rtp-201.amer.cisco.com ([64.102.31.38]) by xbh-rtp-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 2 Oct 2006 16:58:06 -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 16:58:06 -0400
Message-ID: <45217D5D.5060007@cisco.com>
Date: Mon, 02 Oct 2006 16:58:05 -0400
From: Acee Lindem <acee@cisco.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
MIME-Version: 1.0
To: "Joel M. Halpern" <joel@stevecrocker.com>
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> <45214EB8.5030605@cisco.com> <45216D6C.7020401@earthlink.net> <7.0.1.0.0.20061002162346.036b1f10@stevecrocker.com>
In-Reply-To: <7.0.1.0.0.20061002162346.036b1f10@stevecrocker.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 02 Oct 2006 20:58:06.0570 (UTC) FILETIME=[75993CA0:01C6E665]
DKIM-Signature: a=rsa-sha1; q=dns; l=2215; t=1159822687; x=1160686687; 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 |To:=22Joel=20M.=20Halpern=22=20<joel@stevecrocker.com>; X=v=3Dcisco.com=3B=20h=3Dd1alR2vT0d1rHILikmkbvIMYDbQ=3D; b=BHPLd0gDV8kSkpONfDGKDBglLaplyZs1tYzwREg4RbzDreVpJ7gHb4ziOc00QpLBAK+19uKE SI40h7/tqEERoh92+ywcwUbsKCJXejoiCJpS9VusG3TSQXstftNJV+No;
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: 4d87d2aa806f79fed918a62e834505ca
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

Richard,

I'd have to agree with Joel. Addiitonally, reaching consensus on the 
criteria
and who has the mandate to make the decision may be as difficult as agreeing
on an approach.  So, we could bring in others, e.g. the routing ADs or 
members of the
routing directorate, but this may not bring us any closer to concensus.

Thanks,
Acee
Joel M. Halpern wrote:
> Why must the teams agree on a methodology?
> The point of experimental publication is to get the definitions out 
> there so that people can implement and use them.
> If it does not get used, then there is no need to move anything to 
> Proposed Standard.
> If one gets used, and the others do not, then that one ends up on the 
> standards track.  Probably with improvements from the implementation 
> and deployment experience.
> If several get implemented and deployed, then we hope to learn things 
> from that deployment.  We may discover that factors that never 
> occurred to the working group will turn out to be important.  It may 
> be that factors the working group thought important turn out to be 
> irrelevant.
>
> The IETF has almost never agreed on criteria for moving from 
> experimental to proposed standard, other than "lets see what happens."
> And I would be amazed at the IETF giving significant weight to 
> simulation experience for that transition.
>
> Yours,
> Joel M. Halpern
>
> PS: When this has been done in the past, it has been with the view 
> that it was intended to get real world deployment experience.  And 
> that such experience was what mattered for any possible eventual move 
> from experimental to standards track status.
>
> At 03:50 PM 10/2/2006, Richard Ogier wrote:
>> I think that if we decide to go forward with multiple experimental
>> drafts, then we MUST first agree on a methodology for comparing the
>> proposals, and all participants MUST agree to cooperate with this
>> methodology.  (E.g., if one team refuses to implement their solution
>> in GTNetS, then they will be disqualified.)
>
>
> _______________________________________________
> Ospf-manet mailing list
> Ospf-manet@ietf.org
> https://www1.ietf.org/mailman/listinfo/ospf-manet
>

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