Re: [6lowpan] [Roll] draft-kelsey-intarea-mesh-link-establishment-03.txt

Abdussalam Baryun <abdussalambaryun@gmail.com> Fri, 15 June 2012 15:00 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43A9F21F87BC; Fri, 15 Jun 2012 08:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Level:
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ODjSKfkixX69; Fri, 15 Jun 2012 08:00:57 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2152421F86B8; Fri, 15 Jun 2012 08:00:57 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so1985296vbb.31 for <multiple recipients>; Fri, 15 Jun 2012 08:00:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9l8Wr5JJxfyle5NqnhTzt/LorZpz1EJ1CyFOC/EWLtM=; b=0BhMdFc9zb3s6kKzTnwq/4SEd8JjO4MwOcWJfCf2Pt2eR7OQlTIROyPpTDXAMjZGAN x4oCd+cs91Z6gYJgxIxLxIz5TUr4IPCFZkISaZmIQYuVnQrLlGw9ZiAhD+3zRipLxyLN ZgGgoLKuaAfd6H1cD0ZrJVoFYZa3g97xK0jdfabypMQiBeXCOXBHArPZAqojwRHmDE8z qUPI4pMSDBinVhVbZdmeDbt/eV30wIOJgFbWOCkNXQzuceACxskeFzzUsf7U21rZLd4n EyuN3R73LnIAEFT1CK778fl/cTbZi83GxTquUMfGDnIMjBAqY3m/l7cWm996IiUr+HWo fF5Q==
MIME-Version: 1.0
Received: by 10.220.153.80 with SMTP id j16mr3240783vcw.55.1339772448062; Fri, 15 Jun 2012 08:00:48 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Fri, 15 Jun 2012 08:00:47 -0700 (PDT)
In-Reply-To: <CC008CEF.1707C%d.sturek@att.net>
References: <6FE0075D-CB42-4FE1-A5D2-20330917542C@thomasclausen.org> <CC008CEF.1707C%d.sturek@att.net>
Date: Fri, 15 Jun 2012 16:00:47 +0100
Message-ID: <CADnDZ88+koFkMvhqeuZtvJJ19bQkbKZKhJ7dGX4ysN1p0ruwAQ@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Don Sturek <d.sturek@att.net>
Content-Type: multipart/alternative; boundary=f46d043be15ad8be8d04c284149e
Cc: roll@ietf.org, 6lowpan@ietf.org
Subject: Re: [6lowpan] [Roll] draft-kelsey-intarea-mesh-link-establishment-03.txt
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Jun 2012 15:00:58 -0000

+1

AB

On Fri, Jun 15, 2012 at 2:57 PM, Don Sturek <d.sturek@att.net> wrote:

> Hi Thomas (and Michael),
>
> I don't agree that MLE targets only RPL.  The draft was written carefully
> to avoid having a narrow focus around RPL.  That said, the deployment we
> are using this draft for uses 6LoWPAN, 6LoWPAN ND, ROLL RPL (non-storing)
> and I think many others will find the information exchanged between
> neighbors using MLE as useful.
>
> Don
>
>
>
>
>
> On 6/15/12 6:15 AM, "Thomas Heide Clausen" <ietf@thomasclausen.org> wrote:
>
> >
> >On Jun 15, 2012, at 15:12 , Michael Richardson wrote:
> >
> >>
> >>>>>>> "Thomas" == Thomas Heide Clausen <ietf@thomasclausen.org> writes:
> >>    Thomas> Not sure how fantastic (or not) it is - it is not
> >>    Thomas> immediately clear to me how tied MLE should be to RPL - if
> >>    Thomas> it truly aims at being for _MESH_ link establishment, then
> >>    Thomas> it would appear to be a much larger scope, and should not be
> >>    Thomas> tied narrowly to a special-purpose protocol's type-space (&
> >>    Thomas> conventions etc., that do not apply universally).
> >>
> >> Thomas, you will note that:
> >>  1) I suggested it go under IPv6 ICMP first, and if there was such push
> >>     back about allocating a new type, that RPL could allocate a
> >>type/code.
> >>  2) ZigBee alliance (the proposal), *IS* using RPL.
> >>
> >
> >In that case, the draft must be very narrowly scoped and written such
> >that it's clear that it's applicable _only_ to that context
> >(special-purpose deployments of a special-purpose protocol), and
> >specifically to not pretend to do general mesh link establishment.
> >
> >> I see running it over UDP very architecturally strange.
> >
> >I don't.
> >
> >Thomas
> >
> >> --
> >> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
> >> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
> >>
> >
>
>
> _______________________________________________
> 6lowpan mailing list
> 6lowpan@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowpan
>