Re: [coman] Device Classes?

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Fri, 04 April 2014 13:04 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: coman@ietfa.amsl.com
Delivered-To: coman@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9401A0175 for <coman@ietfa.amsl.com>; Fri, 4 Apr 2014 06:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.56
X-Spam-Level:
X-Spam-Status: No, score=-1.56 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MtnSwYxJ3AOy for <coman@ietfa.amsl.com>; Fri, 4 Apr 2014 06:04:17 -0700 (PDT)
Received: from atlas3.jacobs-university.de (atlas3.jacobs-university.de [212.201.44.18]) by ietfa.amsl.com (Postfix) with ESMTP id A74DE1A016E for <coman@ietf.org>; Fri, 4 Apr 2014 06:04:16 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas3.jacobs-university.de (Postfix) with ESMTP id DB7C4F85; Fri, 4 Apr 2014 15:04:11 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas3.jacobs-university.de ([10.70.0.220]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10030) with ESMTP id An7A3ZotIwmo; Fri, 4 Apr 2014 15:04:11 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by atlas3.jacobs-university.de (Postfix) with ESMTPS; Fri, 4 Apr 2014 15:04:11 +0200 (CEST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4F0B42002C; Fri, 4 Apr 2014 15:04:11 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id TvsVBdbMyEyh; Fri, 4 Apr 2014 15:04:11 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 59FEB2002F; Fri, 4 Apr 2014 15:04:10 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 68A4C2C25175; Fri, 4 Apr 2014 15:04:09 +0200 (CEST)
Date: Fri, 04 Apr 2014 15:04:09 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Hannes Tschofenig <hannes.tschofenig@gmx.net>
Message-ID: <20140404130409.GB81513@elstar.local>
Mail-Followup-To: Hannes Tschofenig <hannes.tschofenig@gmx.net>, Carsten Bormann <cabo@tzi.org>, "coman@ietf.org" <coman@ietf.org>
References: <533BBFB7.2000100@gmx.net> <893C4FAC-437D-4140-9832-A9ABA2D1518A@tzi.org> <533E75A9.5080003@gmx.net> <8D653B3C-E678-4A66-9798-978950977694@tzi.org> <533E9864.4060806@gmx.net> <EBDEF2B4-32C3-4B41-9CAF-C1A836CC6D7B@tzi.org> <533E9B6B.1080602@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <533E9B6B.1080602@gmx.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/coman/6U6j5IwlBmsm0N-B7kE_Xz_9PQk
Cc: "coman@ietf.org" <coman@ietf.org>, Carsten Bormann <cabo@tzi.org>
Subject: Re: [coman] Device Classes?
X-BeenThere: coman@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
List-Id: Management of Constrained Networks and Devices <coman.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/coman>, <mailto:coman-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/coman/>
List-Post: <mailto:coman@ietf.org>
List-Help: <mailto:coman-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/coman>, <mailto:coman-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 13:04:22 -0000

On Fri, Apr 04, 2014 at 01:45:47PM +0200, Hannes Tschofenig wrote:
> 
> Of course, you could replace CoAP entirely with SNMP (as Juergen had
> suggested).
> 

I did not suggest to replace CoAP with SNMP. What I said is:

1) We have done an SNMP only implementation and we know it works and
   what the resource consumption is.

2) I see potential in a RESTCONF to CoAP mapping for devices that do
   CoAP.

3) I agree with the desire to keep code down to a minimum and thus to
   keep the number of protocols needed to a minimum.

4) In our experience, the biggest chunk of code and memory goes to
   security and in particular crypto algorithms. Being able to exploit
   crypto hardware is a major plus as is using the same security and
   crypto mechanisms for all protocols supported.

It would be really nice if we would all have a common understanding of
what roughly the code and storage requirements of the various
protocols involved are. Is LWIG producing something a kind of a survey
like this? If so, this would be great I think.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>