Re: [Roll] mixture of storing and non-storing nodes

Abdussalam Baryun <abdussalambaryun@gmail.com> Sun, 09 September 2012 21:55 UTC

MIME-Version: 1.0
In-Reply-To: <A48E3E6B-C1BC-4D94-84FB-126992B70990@cs.stanford.edu>
References: <CAErDfUQV2E5H66k9YjRSGF8RmA=xhQzrDwpyTRBJ8WQUZh3diw@mail.gmail.com> <B7828579-4864-4CBA-A999-808F394D543F@cisco.com> <BD04C41F-0368-4AEB-8E23-EA3043298599@etri.re.kr> <952CC507-2BA2-4005-B44A-0E40308E15AF@cisco.com> <1EEC52C7-5B67-459D-A579-D809F5426BD0@cs.stanford.edu> <CADnDZ8_zVK=ueFQ9BRA2SQggUkrC32_Qvi0RTSmV4d4puwQVCg@mail.gmail.com> <A48E3E6B-C1BC-4D94-84FB-126992B70990@cs.stanford.edu>
Date: Sun, 09 Sep 2012 23:55:48 +0200
Message-ID: <CADnDZ88nmQjYBTfA=AddTfQ+fweC=zx9tJJvhUdBDw3rVGCfaQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Philip Levis <pal@cs.stanford.edu>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: roll WG <roll@ietf.org>
Subject: Re: [Roll] mixture of storing and non-storing nodes
Precedence: list

On 9/4/12, Philip Levis <pal@cs.stanford.edu> wrote:
>
> On Sep 4, 2012, at 3:04 AM, Abdussalam Baryun wrote:
>> I also think that RPL is complicated, for good reasons, but not always
>> complicated protocols should not be optimized or assisted by others.
>> However, new ideas and drafts are always recommended.
>
> As an academic, I agree wholeheartedly. Also as an academic, I'd argue that
> new ideas which do not have a strong application pull are the province of
> research, not standardization. Our goal here is to standardize practice for
> interoperability, not come up with new ideas. But that's just my 2 cents.
>

I disagree that we only "standardize practice for interoperability",
but we also standard to solve problems that face LLNs and RPL, by new
ideas/protocols. For example, RPL is an IETF standard but still not
fully in practice, yet was a good idea to standard. Furthermore, there
are many deployment results not shown in IETF, but used by researchers
or companies elsewhere. I am working on a new protocol to be standard
by IETF because it will solve an important LLN routing problem.

AB

Re: [Roll] mixture of storing and non-storing nod… JeongGil Ko
[Roll] mixture of storing and non-storing nodes Omprakash Gnawali
Re: [Roll] mixture of storing and non-storing nod… Abdussalam Baryun
Re: [Roll] mixture of storing and non-storing nod… Abdussalam Baryun
Re: [Roll] mixture of storing and non-storing nod… Omprakash Gnawali
Re: [Roll] mixture of storing and non-storing nod… 정종수
Re: [Roll] mixture of storing and non-storing nod… JP Vasseur (jvasseur)
Re: [Roll] mixture of storing and non-storing nod… Abdussalam Baryun
Re: [Roll] mixture of storing and non-storing nod… JP Vasseur (jvasseur)
Re: [Roll] mixture of storing and non-storing nod… Michael Richardson
Re: [Roll] mixture of storing and non-storing nod… 정종수
Re: [Roll] mixture of storing and non-storing nod… JeongGil Ko
Re: [Roll] mixture of storing and non-storing nod… Philip Levis
Re: [Roll] mixture of storing and non-storing nod… Abdussalam Baryun
Re: [Roll] mixture of storing and non-storing nod… Philip Levis
Re: [Roll] mixture of storing and non-storing nod… JeongGil Ko
Re: [Roll] mixture of storing and non-storing nod… Philip Levis
Re: [Roll] mixture of storing and non-storing nod… JeongGil Ko
Re: [Roll] mixture of storing and non-storing nod… JP Vasseur (jvasseur)
Re: [Roll] mixture of storing and non-storing nod… JeongGil Ko
Re: [Roll] mixture of storing and non-storing nod… Abdussalam Baryun
Re: [Roll] mixture of storing and non-storing nod… JeongGil Ko