Re: [Roll] WorkingGroup LastCall:draft-ietf-roll-protocols-survey-02

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Tue, 09 December 2008 17:32 UTC

Return-Path: <roll-bounces@ietf.org>
X-Original-To: roll-archive@ietf.org
Delivered-To: ietfarch-roll-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 350523A6923; Tue, 9 Dec 2008 09:32:22 -0800 (PST)
X-Original-To: roll@core3.amsl.com
Delivered-To: roll@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 875673A6923 for <roll@core3.amsl.com>; Tue, 9 Dec 2008 09:32:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.404
X-Spam-Level:
X-Spam-Status: No, score=-10.404 tagged_above=-999 required=5 tests=[AWL=0.195, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nmp85aI0lJ+7 for <roll@core3.amsl.com>; Tue, 9 Dec 2008 09:32:19 -0800 (PST)
Received: from ams-iport-1.cisco.com (ams-iport-1.cisco.com [144.254.224.140]) by core3.amsl.com (Postfix) with ESMTP id 115D03A67E9 for <roll@ietf.org>; Tue, 9 Dec 2008 09:32:18 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.33,742,1220227200"; d="scan'208";a="28137412"
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 09 Dec 2008 17:32:12 +0000
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id mB9HWBCU004864; Tue, 9 Dec 2008 18:32:11 +0100
Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id mB9HWBQI008900; Tue, 9 Dec 2008 17:32:11 GMT
Received: from xmb-ams-337.cisco.com ([144.254.231.82]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 9 Dec 2008 18:32:11 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Tue, 09 Dec 2008 18:32:06 +0100
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC06ADE37A@xmb-ams-337.emea.cisco.com>
In-Reply-To: <61D43925-D96D-41A0-A73B-E87B586245E3@thomasclausen.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Roll] WorkingGroup LastCall:draft-ietf-roll-protocols-survey-02
Thread-Index: AclaEbsQ68mu7I+oQ6OfHtr5NcA9dAADWsIA
References: <7C1A2E64-C1B0-472E-B354-77F290BBC80D@cisco.com><374005f30812050849refe8122i63629f469f8ba7c8@mail.gmail.com><7471DA6B-7B09-42BB-8291-C30C83576295@cs.stanford.edu><ABE739C5ADAC9A41ACCC72DF366B719D01652699@GLKMS2100.GREENLNK.NET><E3A7879D-2DE9-49C4-9A27-15EF211E8ADA@thomasclausen.org><be8c8d780812090102y19e0183exf5ab52f95d867558@mail.gmail.com><C0F7A80F-326F-4072-B29F-524B37013405@cisco.com><be8c8d780812090354v4e60dfc0xc3454e8890837e94@mail.gmail.com><FEE327D3-70CE-4413-A366-DAC019C98BC5@cisco.com><ABE739C5ADAC9A41ACCC72DF366B719D01652A14@GLKMS2100.GREENLNK.NET><C222B5E9-FDFF-4545-A7BD-0CD5883CE2FB@cisco.com> <61D43925-D96D-41A0-A73B-E87B586245E3@thomasclausen.org>
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Thomas Heide Clausen <ietf@thomasclausen.org>, "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
X-OriginalArrivalTime: 09 Dec 2008 17:32:11.0627 (UTC) FILETIME=[1188CBB0:01C95A24]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=3717; t=1228843932; x=1229707932; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=pthubert@cisco.com; z=From:=20=22Pascal=20Thubert=20(pthubert)=22=20<pthubert@ci sco.com> |Subject:=20RE=3A=20[Roll]=20WorkingGroup=09LastCall=3Adraf t-ietf-roll-protocols-survey-02 |Sender:=20; bh=EkbMfVMAw3RHGp00Auxk0ugEuoAT+zM1+2A8QP/XumE=; b=wmCBiyY5BhMch46r0lMAe04KQsbJYb4om7+E+aGqj/ERDxtOis3p5mcgUT YmafdLDzYKdxdDkyQrv3fnhhUBm0zA/mgZwqWySuWKQ4aUyD4tuM3kch4+3g uLaT7FXjb+;
Authentication-Results: ams-dkim-1; header.From=pthubert@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
Cc: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>, Emmanuel Baccelli <emmanuel.baccelli@inria.fr>, roll@ietf.org
Subject: Re: [Roll] WorkingGroup LastCall:draft-ietf-roll-protocols-survey-02
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Sender: roll-bounces@ietf.org
Errors-To: roll-bounces@ietf.org

Hi Thomas:

Every evaluation picks criteria and applies them. This doc has been around for awhile with its own clear list of criteria, which take their source in the requirements drafts. Someone could propose another doc with another set of criteria that would make perfect sense for a different set of requirements.

We could make a moving target of this doc and pursue the quest of the perfect evaluation of life, the universe and everything. But that's not the motivation nor the best interest of this group. In any case, do we expect a perfect one-fit-it-all protocol? I guess not. We'll have to trade off and prioritize, so while the evaluation draft has mostly served its purpose, we are far from being done with the requirement drafts themselves. 

For instance, in the case of industrial, there is an emphasys on reliability vs. path cost, which *is actually* achieved in the real (non-IP) world by building graphs that tend to enable multiple forwarding solutions at each hop, with the capability to revise the forwarding decision on a frame by frame basis after a few L2 retries. 

There are deployed IP protocols that enable similar non-equal-cost path computation, for instance in the DV world with EIGRP feasible successors. There is a huge amount of reusable art in traffic engineering. There is also interesting art in academia such as Tora that might fit the bill. What we need to do is build on this experience and start the work on real solutions to figure what optimum we can actually achieve for our requirements. 

Pascal

>-----Original Message-----
>From: roll-bounces@ietf.org [mailto:roll-bounces@ietf.org] On Behalf Of Thomas Heide Clausen
>Sent: mardi 9 décembre 2008 16:21
>To: JP Vasseur (jvasseur)
>Cc: Dearlove, Christopher (UK); Emmanuel Baccelli; roll@ietf.org
>Subject: Re: [Roll] WorkingGroup LastCall:draft-ietf-roll-protocols-survey-02
>
>
>On Dec 9, 2008, at 16:13 PM, JP Vasseur wrote:
>
>>
>> On Dec 9, 2008, at 4:03 PM, Dearlove, Christopher (UK) wrote:
>>
>>>
>>>> 2- There is clearly a need for a solution *today*: look at all other
>>>> (deployed) non IP solutions out there
>>>
>>>> 4- We are not talking about a "dream protocol": again this is very
>>>> much realistic since solutions do exist today (not IP unfortunately
>>> :-( ....)
>>>
>>> Can you point me to an existing (doesn't have to be IP) protocol
>>> that passes all five of the ID's tests, without some major drawback
>>> in some other area. I for one would find it interesting and useful.
>>> (Obviously it would have to have a specification, not just a claim
>>> made about a proprietary protocol.)
>>
>> You missed my point ... I did not say that there were any of them
>> satisfying these criterion.
>> But clearly there are non IP solutions being deployed, my point
>> being that we need an
>> IP solution soon and we should make it right.
>
>I read Chris Dearlove as asking for something concrete, justifying
>that these five "criteria" that the survey I-D sets out are
>*attainable* (and without some major drawbacks on the other important
>metrics that the survey I-D is ignoring) and that we're not chasing a
>"pie in the sky".
>
>>> If one or more such protocols exist, I don't see why they aren't
>>> discussed at this stage.
>>
>> I do not think that it is in our charter to analyze *all* possible
>> protocols.
>
>No, but if a good such protocol indeed existed, IP or not, having it
>before us might just help quell skepticism.
>_______________________________________________
>Roll mailing list
>Roll@ietf.org
>https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org
https://www.ietf.org/mailman/listinfo/roll