Re: [Yot] comi.space maintenance

Carsten Bormann <cabo@tzi.org> Thu, 13 September 2018 16:41 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: yot@ietfa.amsl.com
Delivered-To: yot@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCACA12F1A5 for <yot@ietfa.amsl.com>; Thu, 13 Sep 2018 09:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=0.001] 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 CesdUH8LIUQ9 for <yot@ietfa.amsl.com>; Thu, 13 Sep 2018 09:41:06 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AAC11294D0 for <yot@ietf.org>; Thu, 13 Sep 2018 09:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w8DGf2q5023027; Thu, 13 Sep 2018 18:41:02 +0200 (CEST)
Received: from client-0156.vpn.uni-bremen.de (client-0156.vpn.uni-bremen.de [134.102.107.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 42B4Cd6sXDzDWRF; Thu, 13 Sep 2018 18:41:01 +0200 (CEST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <DM5PR06MB2777A3B8E15F4A1B7348BFC59A1A0@DM5PR06MB2777.namprd06.prod.outlook.com>
Date: Thu, 13 Sep 2018 18:41:01 +0200
Cc: Alexander Pelov <a@ackl.io>, peter van der Stok <consultancy@vanderstok.org>, "yot@ietf.org" <yot@ietf.org>
X-Mao-Original-Outgoing-Id: 558549659.450042-828051b24392a4968c78b4c0a624f71b
Content-Transfer-Encoding: quoted-printable
Message-Id: <8E99BCF3-DBC2-40D7-B7CF-5ABE880A3D47@tzi.org>
References: <d2fed114dc7a5db157a9509a317ee8e0@bbhmail.nl> <CACQW0ErK=6gSaxXio79AxvqAfmtFWnMeYLYZA5zF7NEdo3U6Bg@mail.gmail.com> <DM5PR06MB2777A3B8E15F4A1B7348BFC59A1A0@DM5PR06MB2777.namprd06.prod.outlook.com>
To: Michel Veillette <Michel.Veillette@trilliant.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/xvaOQX48i9PhH1j3KpAH8BTdPss>
Subject: Re: [Yot] comi.space maintenance
X-BeenThere: yot@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Yang of Things <yot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/yot>, <mailto:yot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/yot/>
List-Post: <mailto:yot@ietf.org>
List-Help: <mailto:yot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yot>, <mailto:yot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2018 16:41:08 -0000


> On Sep 13, 2018, at 18:20, Michel Veillette <Michel.Veillette@trilliant.com> wrote:
> 
> Hi Alexander, Hi Peter, Hi Carsten
>  
> I'm currently updating "draft-ietf-core-comi".
>  
> What should I do about the name?
> Should I change CoMI to CORECONF in the entire document?
> Or should I keep the draft the way it is?
>  
> What was the resolution on this subject at the last IETF?

The resolution was that we want to call the whole thing Coreconf, just as the XML message thing is called Netconf and the HTTP-based thing is called RESTCONF.

We did want to keep the name COMI around (to honor Peter’s substantial contributions, but also for people who have found that name somewhere and want to google things).  The idea was to continue to call the binding of Coreconf to CoAP COMI, i.e., what is in draft-ietf-core-comi right now.  So YANG-CBOR + COMI + SID management + (maybe a few specific modules) = Coreconf.   But that was a bit less firm, so if there is a reason to revisit this, we should.

Grüße, Carsten