Re: [6lo] Focusing the charter

Geoff Mulligan <geoff.ietf@mulligan.com> Fri, 14 June 2013 21:49 UTC

Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3ACF421E8083 for <6lo@ietfa.amsl.com>; Fri, 14 Jun 2013 14:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 FFZDCAoyqMeE for <6lo@ietfa.amsl.com>; Fri, 14 Jun 2013 14:49:08 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 65B3721F99F8 for <6lo@ietf.org>; Fri, 14 Jun 2013 14:49:04 -0700 (PDT)
Received: from [192.168.1.4] (unknown [192.168.1.4]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id E723D5F74E; Fri, 14 Jun 2013 15:49:00 -0600 (MDT)
Message-ID: <51BB8FCC.3050608@mulligan.com>
Date: Fri, 14 Jun 2013 15:49:00 -0600
From: Geoff Mulligan <geoff.ietf@mulligan.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130510 Thunderbird/17.0.6
MIME-Version: 1.0
To: Ulrich Herberg <ulrich@herberg.name>
References: <DFF38ACA-5099-4EC0-B1BA-4FA977CC246F@tzi.org> <A13EB629-B1AC-4AA8-9DDB-EDAC691921FE@tzi.org> <CAK=bVC-pSY9qSbMew30HghQttTFuDc4B1hgO10Xsr9AnMtSdhA@mail.gmail.com> <6805.1371231731@sandelman.ca> <51BB5D82.5030602@mulligan.com> <CAK=bVC_uhbtnzc5EooJiZyX3ySrafYzdPZGCWsPL95NeHfJcPA@mail.gmail.com>
In-Reply-To: <CAK=bVC_uhbtnzc5EooJiZyX3ySrafYzdPZGCWsPL95NeHfJcPA@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: 6lo@ietf.org
Subject: Re: [6lo] Focusing the charter
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discussion of a WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lo>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Jun 2013 21:49:13 -0000

On 06/14/2013 12:21 PM, Ulrich Herberg wrote:
> Geoff,
>
> On Fri, Jun 14, 2013 at 11:14 AM, Geoff Mulligan
> <geoff.ietf@mulligan.com> wrote:
>> Ulrich: Why can't SNMP be used over 6lowpans?  I don't see what would
>> technically stop it from being used or from working.
> That is an interesting question that (I think) was part of a
> to-be-done gap analysis in the COMAN draft. The main question would be
> if SNMP has too much overhead for constrained devices and networks
> (both in terms of payload and stack size). Has anyone deployed SNMP in
> such networks and on constrained devices?
>
> Best regards
> Ulrich
In my experience with implementing SNMP and also working with folks that 
have done an SNMP like protocol, it is certainly doable to implement and 
use it with constrained devices and networks.  In my implementation I 
did not provide a full ASN.1 compliant system, but instead only 
implemented a limited set of BER to improve stack size and I elided some 
of the OID to improve payload efficiency.

NXP's JennetIP implements a protocol that is similar to SNMP.

So, no I don't think that SNMP would have too much overhead for these 
devices and networks and I'm still interested in pursuing this.

     geoff