Re: [core] COMI: Basic Operations

Carsten Bormann <cabo@tzi.org> Wed, 22 June 2016 10:50 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AADF12B035 for <core@ietfa.amsl.com>; Wed, 22 Jun 2016 03:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 Cy7WiwPmJE_1 for <core@ietfa.amsl.com>; Wed, 22 Jun 2016 03:50:16 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3384D12B004 for <core@ietf.org>; Wed, 22 Jun 2016 03:50:16 -0700 (PDT)
Received: from mfilter32-d.gandi.net (mfilter32-d.gandi.net [217.70.178.163]) by relay2-d.mail.gandi.net (Postfix) with ESMTP id B44B1C5A8B; Wed, 22 Jun 2016 12:50:14 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter32-d.gandi.net
Received: from relay2-d.mail.gandi.net ([IPv6:::ffff:217.70.183.194]) by mfilter32-d.gandi.net (mfilter32-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id 1T41EAWtUOAG; Wed, 22 Jun 2016 12:50:13 +0200 (CEST)
X-Originating-IP: 93.199.242.26
Received: from nar-3.local (p5DC7F21A.dip0.t-ipconnect.de [93.199.242.26]) (Authenticated sender: cabo@cabo.im) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 9AF2DC5A65; Wed, 22 Jun 2016 12:50:12 +0200 (CEST)
Message-ID: <576A6D62.9010107@tzi.org>
Date: Wed, 22 Jun 2016 12:50:10 +0200
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: consultancy@vanderstok.org
References: <5768F53B.6010109@gmx.net> <576918EB.7000205@tzi.org> <FEEAFFBA-7042-4BF5-AD54-83DE64C02922@ericsson.com> <67cb9ead467f3bbe24515a7b255fabc2@xs4all.nl>
In-Reply-To: <67cb9ead467f3bbe24515a7b255fabc2@xs4all.nl>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/XJkW7Fm7MmdhBfahE4057WWuBc0>
Cc: "core@ietf.org WG" <core@ietf.org>
Subject: Re: [core] COMI: Basic Operations
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jun 2016 10:50:18 -0000

I think that the question how COMI and LWM2M could converge in the long
run is very much a research question.  But I would encourage people to
think about possible ways of getting there, because eventually we will
have situations in which a combination of both YANG models and the
media-type based specifications from LWM2M will be useful.

Grüße, Carsten