Re: [Yot] draft-veillette-core-yang-library update

Michel Veillette <Michel.Veillette@trilliantinc.com> Tue, 23 January 2018 16:51 UTC

Return-Path: <Michel.Veillette@trilliantinc.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 D2D261270B4 for <yot@ietfa.amsl.com>; Tue, 23 Jan 2018 08:51:43 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, 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 sLtItdks-aYe for <yot@ietfa.amsl.com>; Tue, 23 Jan 2018 08:51:40 -0800 (PST)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0728.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe48::728]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30BA412706D for <yot@ietf.org>; Tue, 23 Jan 2018 08:51:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Trilliant.onmicrosoft.com; s=selector1-trilliantinc-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=zm7I37/Ml6DAzHR/5wyQZXYYNdR/qdNJ61BDqaz5x5A=; b=hDfAfuelq9Mn7UGJDIpbIrDh+hJ4rKOl/E5bRLx4U8UanAS/50FwmTFplGz7rcOolCEaPETxy9HLCRQFTg+VXx1LRJ85i9hR8/sJrLtYqtwMGwe4dSWwchjTwWUsc0xVB+6ngrvw8quzYjA2eZswVzkyhtRqd1ikORbCAKxc3lM=
Received: from BN6PR06MB2308.namprd06.prod.outlook.com (10.173.19.139) by BN6PR06MB3348.namprd06.prod.outlook.com (10.174.235.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.428.17; Tue, 23 Jan 2018 16:51:36 +0000
Received: from BN6PR06MB2308.namprd06.prod.outlook.com ([10.173.19.139]) by BN6PR06MB2308.namprd06.prod.outlook.com ([10.173.19.139]) with mapi id 15.20.0428.024; Tue, 23 Jan 2018 16:51:35 +0000
From: Michel Veillette <Michel.Veillette@trilliantinc.com>
To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: "yot@ietf.org" <yot@ietf.org>
Thread-Topic: [Yot] draft-veillette-core-yang-library update
Thread-Index: AdOTvvMTvVbnOktyTea0B7WyEt05VgAENzcAACX0pFA=
Date: Tue, 23 Jan 2018 16:51:35 +0000
Message-ID: <BN6PR06MB2308F9C96037A301FBA999CFFEE30@BN6PR06MB2308.namprd06.prod.outlook.com>
References: <BN6PR06MB230845E2D1D84D15A1070728FEEC0@BN6PR06MB2308.namprd06.prod.outlook.com> <20180122222448.qmqlrgb46k6p3dui@elstar.local>
In-Reply-To: <20180122222448.qmqlrgb46k6p3dui@elstar.local>
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@trilliantinc.com;
x-originating-ip: [207.96.192.122]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR06MB3348; 7:L6JsvXlO45a3TP3RxJwtuaGM5E2MgEKCSnT5GXU1vEtDQtK6TW/2+DEIoiTRO0w2hf8eVmvycPzL/74vAUetRdZ/qZPedhwwExbi1s8vH0cG85Nv23KWi/CDIhTWWS+/U+fewRmcA5ayWwneWBImkj5gf0xNy5CmDyc2I6VTtX2UXF1NkZbWSr2f2zgY7SrkyKS6z7OXGAfATHuOgY9lzWYpB8lmjtPnnwCtZSV5j5MNjPAAy0TwU6usc3VubJXY
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: 410d1144-365a-43d6-c692-08d562819094
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(4604075)(3008032)(2017052603307)(7153060)(7193020); SRVR:BN6PR06MB3348;
x-ms-traffictypediagnostic: BN6PR06MB3348:
x-microsoft-antispam-prvs: <BN6PR06MB33487F80691197BEAC540A9DFEE30@BN6PR06MB3348.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(120809045254105)(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(5005006)(8121501046)(3231023)(2400081)(944501161)(3002001)(10201501046)(93006095)(93001095)(6041288)(20161123560045)(20161123558120)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BN6PR06MB3348; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:BN6PR06MB3348;
x-forefront-prvs: 05610E64EE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(366004)(376002)(396003)(39850400004)(346002)(13464003)(57704003)(199004)(189003)(86362001)(81166006)(81156014)(26005)(6506007)(77096007)(99286004)(8676002)(105586002)(68736007)(72206003)(966005)(575784001)(6916009)(66066001)(2950100002)(7696005)(8936002)(5660300001)(53546011)(59450400001)(76176011)(102836004)(55016002)(53936002)(4326008)(74316002)(33656002)(9686003)(15650500001)(2900100001)(305945005)(25786009)(230783001)(3660700001)(3280700002)(106356001)(97736004)(6246003)(316002)(229853002)(14454004)(6116002)(7736002)(2906002)(3846002)(6306002)(6436002)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR06MB3348; H:BN6PR06MB2308.namprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: trilliantinc.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: BA0VrOPvvFkqN9ogBeQvXRTq/dWQ8nJyBjNdj7z9/mbeqpPtPfaAxc1JTKoWidmPIe+M8DHbKF5ME9vFVRnZbw==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: trilliantinc.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 410d1144-365a-43d6-c692-08d562819094
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 Jan 2018 16:51:35.7984 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4f6fbd13-0dfb-4150-85c3-d43260c04309
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR06MB3348
Archived-At: <https://mailarchive.ietf.org/arch/msg/yot/L0SDw2weRU8UwJDkERZfx5N2tYM>
Subject: Re: [Yot] draft-veillette-core-yang-library update
X-BeenThere: yot@ietf.org
X-Mailman-Version: 2.1.22
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: Tue, 23 Jan 2018 16:51:44 -0000

Thanks for this warning Juergen

I was aware of the NMDA acronym but not about the specific impacts of this approach on protocols and on the yang library.

For now, I will just add a comment to the draft to request an alignment with NMDA and draft-ietf-netconf-rfc7895bis-03. CoMI also need to be reviewed for NMDA support. I assume that draft-dsdt-nmda-guidelines-01, draft-ietf-netconf-rfc7895bis-03 and draft-ietf-netconf-nmda-restconf-02 are the main documents to review before proceeding?

Regards,
Michel

-----Original Message-----
From: Juergen Schoenwaelder [mailto:j.schoenwaelder@jacobs-university.de] 
Sent: Monday, January 22, 2018 5:25 PM
To: Michel Veillette <Michel.Veillette@trilliantinc.com>
Cc: yot@ietf.org
Subject: Re: [Yot] draft-veillette-core-yang-library update

I assume you are aware of draft-ietf-netconf-rfc7895bis-03.txt and the discussions ongoing in NETCONF. The idea is to obsolete the old YANG library defined in RFC 7895 and to replace it with a new YANG library that supports NMDA.

/js

On Mon, Jan 22, 2018 at 08:38:29PM +0000, Michel Veillette wrote:
> Draft https://datatracker.ietf.org/doc/draft-veillette-core-yang-library/ will expire in two days.
> If you have changes to propose to this YANG module, please send them so I can update the draft accordingly.
> 
> On the Trilliant side, we propose to add support for a hash as cashing mechanism.
> The resulting 'module-set-id' will support the following datatypes.
> - uint32, local library content identifier
> - identityref, global library content identifier (i.e. SID)
> - byte string, global library content identifier (e.g. SHA2)
> 
> Do we need to support all these approaches?
> 
>   *   The local identifier is easy to manage, compact (~ 1, 2, 3 bytes) but the client need to manage device specific caches
>   *   The SID is more complex to manage (i.g. required an interaction with the SID registry), is relatively compact (~ 5 bytes) and allows the implementation of a single cache for all devices.
>   *   The hash is easy to manage but not as compact (~20 bytes)
> 
> 
> [cid:image001.jpg@01C868D8.BF0BB7E0]
> 
> Michel Veillette
> System Architecture Director
> Trilliant Inc.
> Tel: 450-531-3109
> https://trilliantinc.com/
> 
> 
> 



> _______________________________________________
> Yot mailing list
> Yot@ietf.org
> https://www.ietf.org/mailman/listinfo/yot


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