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

"Joel M. Halpern" <joel@stevecrocker.com> Tue, 03 October 2006 16:05 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUmmE-0001GR-6s; Tue, 03 Oct 2006 12:05:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GUmmC-0001Fc-HY for ospf-manet@ietf.org; Tue, 03 Oct 2006 12:05:48 -0400
Received: from elasmtp-junco.atl.sa.earthlink.net ([209.86.89.63]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GUmmB-00063c-9a for ospf-manet@ietf.org; Tue, 03 Oct 2006 12:05:48 -0400
Received: from [71.161.34.244] (helo=JMHLap3.stevecrocker.com) by elasmtp-junco.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1GUmmA-0000Aq-Kq; Tue, 03 Oct 2006 12:05:47 -0400
Message-Id: <7.0.1.0.0.20061003120300.03364ed0@stevecrocker.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Tue, 03 Oct 2006 12:05:44 -0400
To: Richard Ogier <rich.ogier@earthlink.net>
From: "Joel M. Halpern" <joel@stevecrocker.com>
Subject: Re: [Ospf-manet] Re: Ospf-manet Digest, Vol 11, Issue 2
In-Reply-To: <452284B9.305@earthlink.net>
References: <7FB7EE0A621BA44B8B69E5F0A09DC76402999040@xmb-rtp-208.amer.cisco.com> <452284B9.305@earthlink.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-ELNK-Trace: 9f083ca8aeb2d326d5a073bfd238dd844d2b10475b571120fe5f52ac02aa33cbe83c4adfef46ee06667c3043c0873f7e350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 71.161.34.244
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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

The practice at the IETF is that such determination is made by the 
rough consensus of the working group (not the design team) when the 
data is available.

While I am not fond of "let the market decide", when the working 
group can not come to rough consensus there seems to be no 
alternative.  Proposals I have favored have ended up not being 
standardized on this basis.  (In one case I know of, the working 
group had actually standardized two solutions, and then had to 
deprecate one of them.)

Yours,
Joel M. Halpern

At 11:41 AM 10/3/2006, Richard Ogier wrote:
>>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.
>
>That may sound good, but how do we define what is "important"?
>
>As you suggest below, I agree that we should focus on technical
>discussions.  For example, that is why Aniket and I have been
>explaining why the MDR approach is a "natural extension".
>This is a very important point, since once people understand
>*why* we claim it is a "natural extension", they will understand
>the MDR approach better.
>
>Richard


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