Re: [Roll] Review and concerns (was: Re: Working Group Last Call: draft-ietf-roll-protocols-survey-02)
"Emmanuel Baccelli" <emmanuel.baccelli@gmail.com> Mon, 15 December 2008 11:23 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 5F09A3A692D; Mon, 15 Dec 2008 03:23:57 -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 0F55E3A692D for <roll@core3.amsl.com>; Mon, 15 Dec 2008 03:23:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level:
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 IZeJygyHt9bD for <roll@core3.amsl.com>; Mon, 15 Dec 2008 03:23:48 -0800 (PST)
Received: from fk-out-0910.google.com (fk-out-0910.google.com [209.85.128.186]) by core3.amsl.com (Postfix) with ESMTP id 1070B3A68D4 for <roll@ietf.org>; Mon, 15 Dec 2008 03:23:47 -0800 (PST)
Received: by fk-out-0910.google.com with SMTP id 18so1458535fkq.5 for <roll@ietf.org>; Mon, 15 Dec 2008 03:23:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=uCxCFXieI+NyKdBKevfpC9OU0jBrGzlINiCBuBWxesg=; b=efyykdKUGTDMrk9RgVgm5ZY5jFs+jIfYayO3wc3yUCedgVFPQURqZeYNifh8SmjKgR eJnXZWK43sMHqlweM1/fx5qsNbzewT6fuPEdv4WzynBdkaB3fsCsBEGRWsmxwynMsCJH ezk6Oh/baNt+xUas5wF/OqalXrK8VzLmgJNGk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=tk8QXxYtFYJhRafpp7/ZdcCKj+kkETPgBZxVYGquzt1g8ZjRe3IRwj1OZRvcPDcQML jN4dtlXX8FkLEqPsKuxqlEXweINEVwT00z15qDK+LlP6jWV4sA/Olt01ID9bsmrHeTlO 3tQh6BA1qh34CKW5Rujdmqak1VWo/Y73qw4Y4=
Received: by 10.103.229.12 with SMTP id g12mr2935476mur.16.1229340219388; Mon, 15 Dec 2008 03:23:39 -0800 (PST)
Received: by 10.103.248.12 with HTTP; Mon, 15 Dec 2008 03:23:39 -0800 (PST)
Message-ID: <be8c8d780812150323g7b7b8c88p42dc29336e34e083@mail.gmail.com>
Date: Mon, 15 Dec 2008 12:23:39 +0100
From: Emmanuel Baccelli <emmanuel.baccelli@gmail.com>
To: "David E. Culler" <culler@eecs.berkeley.edu>
In-Reply-To: <49417D7A.7060706@eecs.berkeley.edu>
MIME-Version: 1.0
References: <mailman.65.1228766406.30358.roll@ietf.org> <49417D7A.7060706@eecs.berkeley.edu>
Cc: roll@ietf.org
Subject: Re: [Roll] Review and concerns (was: Re: Working Group Last Call: 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: multipart/mixed; boundary="===============2046763895=="
Sender: roll-bounces@ietf.org
Errors-To: roll-bounces@ietf.org
On Thu, Dec 11, 2008 at 9:52 PM, David E. Culler <culler@eecs.berkeley.edu>wrote: > Emmanuel, > We discussed the list of rows in each of the IETF meetings and > associated discussions leading up to those. It sounds like you agree that > if you have some criteria for limiting the search space the discussion will > never complete. That is necessary, according to the charter, to consider > the space of solutions that might actually solve the problem. To do any > analysis there has to be something specific to analyze. You mention two > addition WGs that have done relevant work. Indeed, from the very beginning > it was stated that Roll should work in conjunction with those groups. It is > key another thing to say "this specific protocol as described by this RFC or > I-D ought to be analyzed in draft-ietf-roll-protocols-survey-03". > > Here's the NEMO list. Which are you arguing should be included and why? > Sorry to be blunt, but your charter says that DTN and NEMO are to be reviewed as well as the rest. There is not a word about either of these "fields" in the draft, why? You need to answer this question. Not me. Emmanuel > > draft-ietf-nemo-basic-support<http://tools.ietf.org/wg/nemo/draft-ietf-nemo-basic-support/> > -03 <http://tools.ietf.org/html/draft-ietf-nemo-basic-support> > 2004-06-07 RFC 3963 <http://tools.ietf.org/html/rfc3963> > draft-ietf-nemo-home-network-models<http://tools.ietf.org/wg/nemo/draft-ietf-nemo-home-network-models/> > -06 <http://tools.ietf.org/html/draft-ietf-nemo-home-network-models> > 2006-02-21 RFC 4887 <http://tools.ietf.org/html/rfc4887> > draft-ietf-nemo-multihoming-issues<http://tools.ietf.org/wg/nemo/draft-ietf-nemo-multihoming-issues/> > -07 <http://tools.ietf.org/html/draft-ietf-nemo-multihoming-issues> > 2007-02-07 RFC 4980 <http://tools.ietf.org/html/rfc4980> > draft-ietf-nemo-requirements<http://tools.ietf.org/wg/nemo/draft-ietf-nemo-requirements/> > -06 <http://tools.ietf.org/html/draft-ietf-nemo-requirements> > 2006-11-09 RFC 4886 <http://tools.ietf.org/html/rfc4886> > draft-ietf-nemo-ro-problem-statement<http://tools.ietf.org/wg/nemo/draft-ietf-nemo-ro-problem-statement/> > -03 <http://tools.ietf.org/html/draft-ietf-nemo-ro-problem-statement> > 2006-09-18 RFC 4888 <http://tools.ietf.org/html/rfc4888> > draft-ietf-nemo-ro-space-analysis<http://tools.ietf.org/wg/nemo/draft-ietf-nemo-ro-space-analysis/> > -03 <http://tools.ietf.org/html/draft-ietf-nemo-ro-space-analysis> > 2006-09-18 RFC 4889 <http://tools.ietf.org/html/rfc4889> > draft-ietf-nemo-terminology<http://tools.ietf.org/wg/nemo/draft-ietf-nemo-terminology/> > -06 <http://tools.ietf.org/html/draft-ietf-nemo-terminology> > 2006-11-09 RFC 4885 <http://tools.ietf.org/html/rfc4885> > > There are many topics that as a working group we'd like to move on to once > this process completes. Much important work has been done outside IETF > WGs. Some of it in the IRTF. Others in other places. All the more reason > to complete this well formed, bounded effort. Again, I do not hear any > suggestion that any protocol within the domain of analysis meets the > criteria. I do hear that there are protocols or modifications to protocols > that do or could. We need to complete the process on this draft so that we > can move on to consider such enhancements, candidates, or new designs. > > > On Thu, Dec 11, 2008 at 4:09 PM, Emmanuel Baccelli <emmanuel.baccelli at > gmail.com <emmanuel.baccelli%20at%20gmail.com>> wrote: > >> >> >> On Tue, Dec 9, 2008 at 11:28 PM, David E. Culler <culler at >> eecs.berkeley.edu <culler%20at%20eecs.berkeley.edu>> wrote: >>> >>> >>> Some concerns recognize that there are protocols outside the defined >>> universe that should be considered and that appear to be far better suited >>> to meeting the criteria than the set of IETF protocols that were considered >>> - since those protocols were developed without these criteria. Again, that >>> suggests that the criteria are a reasonable guide, that they do not appear >>> to be unobtainable, and that the analysis has provided a suitable guide. >>> >>> None of the comments seem to be claiming that there is a solution within >>> the universe that we were chartered to consider that meets the criteria. >>> >> > > Even admitting that the universe you defined is wide enough (a point > which is actually agued since months), we could conclude to this only if > this universe (defined in the charter) is covered entirely. Again, it is not > the case: I have seen nothing said about NEMO or DTN, so reports of > investigations in these fields need to be included in the draft anyways. > > Second, if we are not going into a long research phase, I am still > wondering what existing protocols/algorithms, IP compatible or not, are > being "hinted at" here, which could meet the "dream" criterii that are > evoked in the draft. Chris Dearlove and other people have asked this > question many times, and it is yet to be answered. > > Emmanuel > > _______________________________________________ > 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
- Re: [Roll] Review and concerns (was: Re: Working … David E. Culler
- Re: [Roll] Review and concerns (was: Re: Working … David E. Culler
- Re: [Roll] Review and concerns (was: Re: Working … Emmanuel Baccelli
- Re: [Roll] Review and concerns (was: Re: Working … Emmanuel Baccelli
- Re: [Roll] Review and concerns (was: Re: Working … Geoff Mulligan
- Re: [Roll] Review and concerns (was: Re: Working … JP Vasseur
- Re: [Roll] Review and concerns David E. Culler
- Re: [Roll] Review and concerns (was: Re: Working … Emmanuel Baccelli
- Re: [Roll] Review and concerns Geoff Mulligan
- Re: [Roll] Review and concerns JP Vasseur
- Re: [Roll] Review and concerns (was: Re: Working … Philip Levis
- Re: [Roll] Review and concerns David E. Culler
- Re: [Roll] Review and concerns (was: Re: Working … Emmanuel Baccelli
- Re: [Roll] Review and concerns Stephen Farrell
- Re: [Roll] Review and concerns (was: Re: Working … Philip Levis
- Re: [Roll] Review and concerns Philip Levis
- Re: [Roll] Review and concerns David E. Culler
- Re: [Roll] Review and concerns Philip Levis
- Re: [Roll] Review and concerns Alexandru Petrescu
- Re: [Roll] Review and concerns Alexandru Petrescu
- Re: [Roll] Review and concerns Alexandru Petrescu
- Re: [Roll] Review and concerns Thomas Heide Clausen
- Re: [Roll] Review and concerns Thomas Heide Clausen