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

Thomas Heide Clausen <ietf@thomasclausen.org> Fri, 15 June 2012 10:32 UTC

Return-Path: <ietf@thomasclausen.org>
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 07C4C21F85B6; Fri, 15 Jun 2012 03:32:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.869
X-Spam-Level:
X-Spam-Status: No, score=-0.869 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334, MIME_QP_LONG_LINE=1.396]
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 dcy4d7nMMngf; Fri, 15 Jun 2012 03:32:15 -0700 (PDT)
Received: from morbo.mail.tigertech.net (morbo.mail.tigertech.net [67.131.251.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7FD6321F85A1; Fri, 15 Jun 2012 03:32:15 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by morbo.tigertech.net (Postfix) with ESMTP id EE407557F4B; Fri, 15 Jun 2012 03:32:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 692A31C0864; Fri, 15 Jun 2012 03:32:14 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [10.129.61.101] (37-8-178-84.coucou-networks.fr [37.8.178.84]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id AFBB51C07CC; Fri, 15 Jun 2012 03:32:13 -0700 (PDT)
References: <CBFFC509.17034%d.sturek@att.net>
In-Reply-To: <CBFFC509.17034%d.sturek@att.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <2E20BD63-02D7-4275-A3C1-2E070D9BB90E@thomasclausen.org>
X-Mailer: iPad Mail (9B206)
From: Thomas Heide Clausen <ietf@thomasclausen.org>
Date: Fri, 15 Jun 2012 12:32:17 +0200
To: Don Sturek <d.sturek@att.net>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "<roll@ietf.org>" <roll@ietf.org>, "<6lowpan@ietf.org>" <6lowpan@ietf.org>, "<ipv6@ietf.org>" <ipv6@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 10:32:16 -0000

Not sure how fantastic (or not) it is - it is not immediately clear to me how tied MLE should be to RPL - if it truly aims at being for _MESH_ link establishment, then it would appear to be a much larger scope, and should not be tied narrowly to a special-purpose protocol's type-space (& conventions etc., that do not apply universally).

I guess I'm expressing some sort of support for Don's position...

-- 
Thomas Heide Clausen
http://www.thomasclausen.org/

"Any simple problem can be made insoluble if enough meetings are held to
 discuss it."
   -- Mitchell's Law of Committees


On 15 Jun 2012, at 01:43, Don Sturek <d.sturek@att.net> wrote:

> All sounds fantastic but we don't have time for all these changes so will
> opt to use MLE as written using UDP ( at least for our application....)
> 
> Don
> 
> 
> 
> On 6/14/12 1:13 PM, "Michael Richardson" <mcr+ietf@sandelman.ca> wrote:
> 
>> 
>> In draft-kelsey-intarea-mesh-link-establishment-03.txt it says that
>>  MLE messages are sent using UDP.
>> 
>> I want to suggest that MLE messages should be sent at least as IPv6
>> ICMP messages.  
>> 
>> Further, I think that it could use the RPL type 155, and RPL would
>> allocate a new "code" codepoint.
>> 
>> There would be some preference to have the general structure of MLE
>> match that of RPL, but I think that this isn't particularly a strong
>> requirement.   Allocating a new ICMP type code for MLE alone might be
>> seen as excessive, but I can not speak for the folks in 6man.
>> 
>> -- 
>> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
>> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
>> 
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
> 
> 
> _______________________________________________
> 6lowpan mailing list
> 6lowpan@ietf.org
> https://www.ietf.org/mailman/listinfo/6lowpan