Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended

"U. Nilrebmorf" <nilrebmorfunam@googlemail.com> Tue, 14 November 2006 02:07 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gjni4-0006CE-NJ; Mon, 13 Nov 2006 21:07:36 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GjnhL-0005xJ-AK for ospf@ietf.org; Mon, 13 Nov 2006 21:06:51 -0500
Received: from py-out-1112.google.com ([64.233.166.176]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GjnZi-0007yr-NA for ospf@ietf.org; Mon, 13 Nov 2006 20:59:00 -0500
Received: by py-out-1112.google.com with SMTP id f31so822957pyh for <ospf@ietf.org>; Mon, 13 Nov 2006 17:58:58 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=UYQiRsDYFCMKpGfI19CwUE4nWLIJpJBewL5JCyFn4N5pGxbUiYleAW3pxqnJIwGhCQQio3gYq9CxZNikark4d85mPKnt5tKi35bKarhZpM7oAqF6VycKSiXgg4CzXz8pgMDgW0Mt575woEYA/Fv6u1PKuh3ZQliLagIktZhLZIU=
Received: by 10.35.49.1 with SMTP id b1mr639633pyk.1163469531651; Mon, 13 Nov 2006 17:58:51 -0800 (PST)
Received: by 10.35.106.5 with HTTP; Mon, 13 Nov 2006 17:58:51 -0800 (PST)
Message-ID: <96a9156a0611131758s7f281111y3eeb0fd309bce47d@mail.gmail.com>
Date: Tue, 14 Nov 2006 02:58:51 +0100
From: "U. Nilrebmorf" <nilrebmorfunam@googlemail.com>
To: ospf@ietf.org
Subject: Re: [OSPF] IETF 67 OSPF WG Meeting minutes - Correct file appended
In-Reply-To: <4558C236.4040709@earthlink.net>
MIME-Version: 1.0
References: <45587A54.1090309@cisco.com> <45589EAA.6030305@earthlink.net> <4558BB03.8090501@cisco.com> <4558C236.4040709@earthlink.net>
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 3971661e40967acfc35f708dd5f33760
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>
Content-Type: multipart/mixed; boundary="===============0636349981=="
Errors-To: ospf-bounces@ietf.org

Hi Richard,

I was at the meeting. The consensus was that since simulations are not
sufficient to decide for one solution over another, simulations are also not
sufficient to exclude one solution. So it was decided to move on with 3
experimental. If I am not mistaken, it is read in the minutes from the
meeting:

"Acee: all authors have been attentive to comments. The 3 I-Ds should move
forward to draft-ietf-ospf to go experimental."

That's what the working group decided in the end. If you had been there
maybe it would be clearer to you?

Hope to see you at the next meeting.

Nilreb



On 11/13/06, Richard Ogier <ogier@earthlink.net> 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.
>
> 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 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.
>
> 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 mailing list
OSPF@ietf.org
https://www1.ietf.org/mailman/listinfo/ospf