Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended
Richard Ogier <ogier@earthlink.net> Tue, 14 November 2006 17:06 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gk1js-0008Cc-GU; Tue, 14 Nov 2006 12:06:24 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gk1jr-0008CX-HV for ospf@ietf.org; Tue, 14 Nov 2006 12:06:23 -0500
Received: from pop-satin.atl.sa.earthlink.net ([207.69.195.63]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gk1jp-0002Bz-6f for ospf@ietf.org; Tue, 14 Nov 2006 12:06:23 -0500
Received: from dialup-4.243.131.37.dial1.sanfrancisco1.level3.net ([4.243.131.37] helo=earthlink.net) by pop-satin.atl.sa.earthlink.net with esmtp (Exim 3.36 #1) id 1Gk1QC-0004QL-00; Tue, 14 Nov 2006 11:46:05 -0500
Message-ID: <4559F2C7.4020800@earthlink.net>
Date: Tue, 14 Nov 2006 08:45:59 -0800
From: Richard Ogier <ogier@earthlink.net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1 (emach0202)
X-Accept-Language: en-us
MIME-Version: 1.0
To: Acee Lindem <acee@cisco.com>
Subject: Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended
References: <45587A54.1090309@cisco.com> <45589EAA.6030305@earthlink.net> <4558BB03.8090501@cisco.com> <4558C236.4040709@earthlink.net> <45591561.8060101@cisco.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab
Cc: OSPF List <ospf@ietf.org>
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
Errors-To: ospf-bounces@ietf.org
Acee Lindem wrote: > Hi Richard, > Richard Ogier wrote: > >> Acee, >> >> I am not sure I understand what you mean. The MDR and OR/SP >> drafts have already been evaluated exensively via GTNetS >> simulations. INRIA's solution has not yet participated >> in any such evaluation. So if we require all the drafts >> to participate in the GTNetS evaluation (which was the >> original plan two years ago), then we *are* holding all >> drafts to the same experimental publication criteria. > > GTNetS Simulation results were presented in San Diego so I believe > MPRs have been implemented. The code should be made available for > public inspection and comparison with the other drafts. We seem to be in agreement. The question is, when will INRIA make their (up-to-date) code available to allow a fair comparison. The reason I am concerned is because I don't want to see a repeat of the MANET debate between OLSR and TBRPF, in which there was no cooperation to allow a fair comparison. (I will avoid giving the details here, since it might result in more arguing.) One of the reasons I decided to work on the MDR design is because there was a good plan for comparing the performance of the different proposals (using GTNetS). Richard > > >> >> Or, are you saying that we should give INRIA a free pass >> to avoid participating in the GTNetS evaluation? >> I really don't think this would be fair, and therefore >> seriously doubt that the consensus would agree with this. > > I agree. > >> >> I don't think the voting at the meeting clearly distinguished >> between the two options of accepting 2 versus 3 drafts. >> This distinction was not made explicit at the meeting. > > You are right that the question of 2 or 3 wasn't the primary > focus of the dialog. While we've agreed to allow for more > than one experimental draft, I don't think we should lower > our standards. I don't think anyone who was at the meeting > would disagree. > Thanks, > Acee > > >> >> Richard >> >> >> Acee Lindem wrote: >> >>> Hi Richard, >>> I think we agreed upon a process to move along and we should >>> continue to hold all the drafts to the same experimental publication >>> criteria. I guess the point was that we should not limit the number to >>> 2 if we're going to publish more than 1. Without injecting too much >>> judgment >>> on the MPR draft's maturity, did everyone at the meeting hear the >>> same message? >>> >>> Thanks, >>> Acee >>> >>> Richard Ogier wrote: >>> >>>>> Acee: Show hands on what should be done: >>>>> - Quit working on OSPF MANET: none >>>>> - Continue to drive to consensus: none >>>>> - Refine drafts and publish as experimental: 2/3's of >>>>> people >>>>> in room. To be validated on list. >>>> >>>> >>>> >>>> >>>> Acee, >>>> >>>> Correct me if I am wrong, but since the latest version of INRIA's >>>> draft was available only last week, and since previous versions did >>>> not fully specify the protocol (as pointed out by Phil Spagnolo in >>>> his 9/28/06 post to the ospf-manet list), it has not yet been decided >>>> that INRIA's draft will be published as experimental. >>>> >>>> Moreover, since INRIA has not participated in the GTNetS simulation >>>> comparison that Boeing has been conducting for the last two >>>> years, in which the MDR draft has been compared to Cisco's >>>> OR/SP drafts (results can be found at Boeing's OSPF-MANET website >>>> http://hipserver.mct.phantomworks.org/ietf/ospf/ ), >>>> it is only fair that we should do such a comparison with INRIA's draft >>>> before deciding to publish it as experimental. >>>> >>>> In fact, that has been the plan since the Dallas IETF meeting in >>>> March, >>>> and Philippe agreed to this in his message of 4/5/06: >>>> >>>> Philippe Jacquet wrote on 4/5/06: >>>> > Yes it would be great to synchronize our efforts on GTNet. >>>> > Let's see how to proceed. >>>> >>>> Now, 7 months later, INRIA has implemented their solution in GTNetS, >>>> so the next step would be for Boeing to work with INRIA to make >>>> sure the code is debugged and implemented in a manner that allows >>>> a fair comparison, just as Boeing has done with the OR/SP and >>>> MDR solutions over the last two years. Hopefully, this work can >>>> be completed by the next IETF meeting. >>>> >>>> I think it is reasonable and fair to require such a comparison >>>> to be done before INRIA's draft is accepted, especially >>>> since they promised to synchronize efforts 7 months ago. >>>> Let me know if you agree or disagree. >>>> IMO, to give INRIA a free pass and avoid such a comparison >>>> would be unfair to those of us who worked hard for the last two >>>> years on the GTNetS simulation effort. >>>> >>>> Richard >>>> >>> >>> >> > > _______________________________________________ OSPF mailing list OSPF@ietf.org https://www1.ietf.org/mailman/listinfo/ospf
- [OSPF] IETF 67 OSPF WG Meeting minutes - Correct … Acee Lindem
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Richard Ogier
- RE: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Manav Bhatia
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Acee Lindem
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Acee Lindem
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Richard Ogier
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Acee Lindem
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… U. Nilrebmorf
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Richard Ogier
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Richard Ogier
- RE: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Henderson, Thomas R
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Phil Cowburn
- RE: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Bhatia, Manav (Manav)
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… John Smith
- Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Corr… Vishwas Manral