Re: [core] CoMI Cool draft splits

Carsten Bormann <cabo@tzi.org> Fri, 20 November 2015 06:36 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 260C21A8847 for <core@ietfa.amsl.com>; Thu, 19 Nov 2015 22:36:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 sEUu5uu86YVf for <core@ietfa.amsl.com>; Thu, 19 Nov 2015 22:36:00 -0800 (PST)
Received: from relay4-d.mail.gandi.net (relay4-d.mail.gandi.net [IPv6:2001:4b98:c:538::196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E8B91A8849 for <core@ietf.org>; Thu, 19 Nov 2015 22:36:00 -0800 (PST)
Received: from mfilter28-d.gandi.net (mfilter28-d.gandi.net [217.70.178.159]) by relay4-d.mail.gandi.net (Postfix) with ESMTP id 4C64617209D; Fri, 20 Nov 2015 07:35:59 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter28-d.gandi.net
Received: from relay4-d.mail.gandi.net ([IPv6:::ffff:217.70.183.196]) by mfilter28-d.gandi.net (mfilter28-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id tXH6u5zVmmQv; Fri, 20 Nov 2015 07:35:57 +0100 (CET)
X-Originating-IP: 93.199.254.229
Received: from nar.local (p5DC7FEE5.dip0.t-ipconnect.de [93.199.254.229]) (Authenticated sender: cabo@cabo.im) by relay4-d.mail.gandi.net (Postfix) with ESMTPSA id C5D311720A3; Fri, 20 Nov 2015 07:35:55 +0100 (CET)
Message-ID: <564EBF4A.8010405@tzi.org>
Date: Fri, 20 Nov 2015 07:35:54 +0100
From: Carsten Bormann <cabo@tzi.org>
User-Agent: Postbox 4.0.8 (Macintosh/20151105)
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>
References: <0559fa310f26530d1c1e89c1ed64b7aa@xs4all.nl> <BN1PR04MB424BAAB4D9E771D891BD06F921D0@BN1PR04MB424.namprd04.prod.outlook.com> <CABCOCHQ8QQArhVUVT4FkYOYnYny4osGMeY4F6jvNjZ0v9Pa3bg@mail.gmail.com> <cf7b132ec85a3781bf4e3a28cda4cb97@xs4all.nl> <0E9A48AB39AF3547ACD28A6DE3E2906A0F1AC492@ATBRAGMSX02.itiso.net> <CABCOCHROWZtR3jZ431ZK_rxZR-giAr9qzGcANzYSD-a85dSyHQ@mail.gmail.com> <0E9A48AB39AF3547ACD28A6DE3E2906A0F1ACE72@ATBRAGMSX02.itiso.net> <CABCOCHTQ6h6zAzL+OyrMT_xKcOzk1=Z7DtaSniQTO2PTOuDW9w@mail.gmail.com> <564DFAD7.1000800@tzi.org> <CABCOCHRU2S9TBMLtEfA_jqHa1+jVC4Sk8hZG0OiVi5q6mP+yXg@mail.gmail.com>
In-Reply-To: <CABCOCHRU2S9TBMLtEfA_jqHa1+jVC4Sk8hZG0OiVi5q6mP+yXg@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/Yhoyy5vzFUvMaI98a6S5hIa2AsE>
Cc: Core <core@ietf.org>
Subject: Re: [core] CoMI Cool draft splits
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 20 Nov 2015 06:36:02 -0000

Andy Bierman wrote:
> [...] IMO constrained nodes
> will never be using the same modules that are written for networking
> equipment.

Is that so?  Why wouldn't I use a couple of items from, say, RFC 7317
(or 7277) in my constrained node?  In the end these are just resources
that I add to my resource tree.  Of course, cherry-picking may require
some form of subsetting that may not yet be part of the NETCONF approach.

Grüße, Carsten