Re: [Yot] comi.space maintenance

Michel Veillette <Michel.Veillette@trilliant.com> Thu, 13 September 2018 16:21 UTC

Return-Path: <Michel.Veillette@trilliant.com>
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 48B51130E04 for <yot@ietfa.amsl.com>; Thu, 13 Sep 2018 09:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=trilliant.onmicrosoft.com
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 vWMpEYmrHBcP for <yot@ietfa.amsl.com>; Thu, 13 Sep 2018 09:20:59 -0700 (PDT)
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (mail-eopbgr730121.outbound.protection.outlook.com [40.107.73.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16366130DFF for <yot@ietf.org>; Thu, 13 Sep 2018 09:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-Trilliant-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EI133ymquRjXIRqdwkVikrK+zflJQ5U4Ca172s3P1Yg=; b=FI+E2m+EANa1/ziI/JJyjvoYVzHZ3qzpQgyxnpkVO4mga85BzSgDb3arHYP/9poPjIz3gdeTLT1Dxsb7UMKNw16XMtBtNvBzLpwwcl/lJSFLB0gkl4Iy6JR9X36Bfqjkm0YMybBiO+UC+vHvqR/delN0ORfe8SfnW+nveXxtbf0=
Received: from DM5PR06MB2777.namprd06.prod.outlook.com (10.175.107.139) by DM5PR06MB3148.namprd06.prod.outlook.com (10.174.240.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1122.17; Thu, 13 Sep 2018 16:20:53 +0000
Received: from DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::85c4:bc9b:dc0e:19e8]) by DM5PR06MB2777.namprd06.prod.outlook.com ([fe80::85c4:bc9b:dc0e:19e8%3]) with mapi id 15.20.1122.019; Thu, 13 Sep 2018 16:20:53 +0000
From: Michel Veillette <Michel.Veillette@trilliant.com>
To: Alexander Pelov <a@ackl.io>, "consultancy@vanderstok.org" <consultancy@vanderstok.org>, Carsten Bormann <cabo@tzi.org>
CC: "yot@ietf.org" <yot@ietf.org>
Thread-Topic: comi.space maintenance
Thread-Index: AQHUSq2G956uuL28GUCttAXFuFin0KTuVQmAgAAO8bA=
Date: Thu, 13 Sep 2018 16:20:53 +0000
Message-ID: <DM5PR06MB2777A3B8E15F4A1B7348BFC59A1A0@DM5PR06MB2777.namprd06.prod.outlook.com>
References: <d2fed114dc7a5db157a9509a317ee8e0@bbhmail.nl> <CACQW0ErK=6gSaxXio79AxvqAfmtFWnMeYLYZA5zF7NEdo3U6Bg@mail.gmail.com>
In-Reply-To: <CACQW0ErK=6gSaxXio79AxvqAfmtFWnMeYLYZA5zF7NEdo3U6Bg@mail.gmail.com>
Accept-Language: fr-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Michel.Veillette@trilliant.com;
x-originating-ip: [207.96.192.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR06MB3148; 6:Ka+EdLDWCvs/MASKNeJ95DiBNMRTMKC1x5bojiCHtbqxq9X+iA/b5j48tLaZ3474j1KE1FyYPQ/QQYc4Z/UWio54C0gmgeHuqMc7iVsM7vAU3t/Uxgm1xBowyfyFWeO2QQr5cAM+CavslJV8O6FS+CTHeqBmTg2eAkL93sM5DmEd2m95g85JG1aXLFsH8h1/Efp7ePHqRTYR8AQByIFvfPhj9Kpg34gcnwHB3DMSYniMatn8i+MRR6gxjh7G3nvvMSHtgCtbJ5R5N9Z8V38oRXYJ40qAb0wsIFsmvNQcslpJj8U6JnujmDWfWs25GYhxrML7dbI2P2xD+oBYMk6AKdtNDlHeTCPhLqPAKI9EzSCan+gzzwM1tlynpioNDEUKlhmM2kxkegcTscU7DG05NudgHD2aA9E4/B0Up2BhO5r6VJ6AN14qrToMS7U10QSCAlvu5x5SRW3bKCgIM69NBg==; 5:XvrXAi344Ngd97RtFlcA5VwIH79Yn3xcRohm2DwjtkMxln3HN+l/sePW2XeRDk14hyPPDIG8J3mDJqQu46IsyhoLfpPSVb0xgm0QSBCHef62b7cCRiQJqtKMVvzS6ZQQQKGQfpbFmxy/xXiQSJbtiQloMSXywAGyBJ4MyMgA3XE=; 7:B03t5FaRx7HauosbKHexcFBTKAbYfQ/izAm+fxb7m05BdzQRLPFowTTwsWp0TxXBlN7fFTHimjuugyZEosB1kh64dby1j323f2vGfZokPjIiQLOWd+v/wea7LXQRXN6bCP90XrS19Y2rN0R+FwSr6raMe5YD0Net4YAHDCGdItU2pQT0FuoybNcA3az8LcU2yyZh8DdCcfe3fXgKcr+uCRXWL9QpLRucNwdIIgn+B5x/YteBSpV25aWfpmBKagHp
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: 121b1f08-e9a8-41f0-7a6d-08d61994e0a0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989137)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(5600074)(711020)(2017052603328)(7153060)(7193020); SRVR:DM5PR06MB3148;
x-ms-traffictypediagnostic: DM5PR06MB3148:
x-microsoft-antispam-prvs: <DM5PR06MB314837422FF8A0DA28D581469A1A0@DM5PR06MB3148.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(95692535739014)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231311)(944501410)(52105095)(3002001)(10201501046)(149027)(150027)(6041310)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123558120)(201708071742011)(7699050); SRVR:DM5PR06MB3148; BCL:0; PCL:0; RULEID:; SRVR:DM5PR06MB3148;
x-forefront-prvs: 07943272E1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400003)(396003)(346002)(366004)(376002)(136003)(199004)(189003)(66066001)(33656002)(14454004)(606006)(5660300001)(2900100001)(8676002)(68736007)(74316002)(7736002)(478600001)(11346002)(9686003)(6436002)(55016002)(316002)(110136005)(6306002)(446003)(53546011)(72206003)(97736004)(102836004)(6506007)(476003)(790700001)(3846002)(6116002)(256004)(2906002)(76176011)(2501003)(229853002)(106356001)(236005)(7696005)(14444005)(5250100002)(53936002)(86362001)(105586002)(81156014)(186003)(53386004)(486006)(4326008)(19609705001)(6246003)(26005)(54896002)(3480700004)(8936002)(81166006)(99286004)(25786009)(781001); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR06MB3148; H:DM5PR06MB2777.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: trilliant.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: bWKLzExUAEd4uFqeKHZw5w3Bhl0lnE1YhzXMIg+ti+V4BFe7GgY5Rsv0AGeavfkO6L985uS++VrkBYKBcNm4lDCyumwBfnJY0DkhRJetbmeuNHyjK42mRYTi8+Qj/bMJQhSAAuoX9sWdPIRULd34UGQTnbN9+2ZbPh04QH5gwV0Ri1zGkOZ/1Upvxw6dcEcdGx3tUDlUNdLVQWr6N7YUHw1SjXaNGS5lLkkmM7UWPLajCcb7H9tbCDR9TEOQ4FY7ogtbCVhm6xOpNXoKTT7puESjNohL5cUw5jHySCSJJenQiB1RKolOc8f6fLPe+b2tnstFJoD6thwAexVXpXSu67RQna0bqaCG7PNAXi9cjHc=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR06MB2777A3B8E15F4A1B7348BFC59A1A0DM5PR06MB2777namp_"
MIME-Version: 1.0
X-OriginatorOrg: Trilliant.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 121b1f08-e9a8-41f0-7a6d-08d61994e0a0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Sep 2018 16:20:53.2565 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR06MB3148
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/161kOY0zKmxJIKtBh1diuEcDBk0>
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:21:02 -0000

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?

Regards,
Michel

From: Alexander Pelov <a@ackl.io>
Sent: Thursday, September 13, 2018 11:20 AM
To: consultancy@vanderstok.org
Cc: Michel Veillette <Michel.Veillette@trilliant.com>; Michael Richardson <mcr@sandelman.ca>; Panos Kampanakis (pkampana) <pkampana@cisco.com>
Subject: Re: comi.space maintenance

Hi Peter,

Thanks for reaching out!
Yes, I think you are right that we should have a plan for the maintenance of comi.space

Let's discuss this before the next IETF?
(currently I'm in the US for a couple of days, maybe beginning of October?)

Alexander

On Wed, 12 Sep 2018, 08:30 Peter van der Stok <stokcons@bbhmail.nl<mailto:stokcons@bbhmail.nl>> wrote:
Hi Alexander,

We use com.space to allocate SID values to the fields of the voucher specified in our yang files .
See anima-constrained-voucher for details.

Currently, we experience a problem with the version of the pyang tools prepared by Michel.
Michel has been kind enough to provide use with all necessary information and the supporting files.
Michael Richardson tries to debug the python code and may come up with a a solution.

That will remove our problems for the time being, but we risk that other people may use a different version of the pyang tools because Michel seems to have a limited time to occupy himself with the maintenance of the pyang tool.

Do you have suggestions, or are already procedures in place, to assure the continued maintenance of comi.space also after Michel may become unavailable (other job, health problems, and what not).

May be I worry over a non existing problem.
If not, it would be nice if we could discuss this on the Core ML, where all the work originated.

Greetings, thanks for your answer,

Peter
--
Peter van der Stok
vanderstok consultancy
mailto: consultancy@vanderstok.org<mailto:consultancy@vanderstok.org>, stokcons@bbhmail.nl<mailto:stokcons@bbhmail.nl>
www: www.vanderstok.org<http://www.vanderstok.org>
tel NL: +31(0)492474673     F: +33(0)966015248