IETF Logo Mail Archive

Re: [netconf] RFC8040 inquiries

Anton Snitser <antons@sedonasys.com> Mon, 07 October 2019 11:28 UTC

Return-Path: <antons@sedonasys.com>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DCA012007A for <netconf@ietfa.amsl.com>; Mon, 7 Oct 2019 04:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 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, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sedonasys.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 vlhdtWttS7Z1 for <netconf@ietfa.amsl.com>; Mon, 7 Oct 2019 04:28:39 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-eopbgr130122.outbound.protection.outlook.com [40.107.13.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6B07120052 for <netconf@ietf.org>; Mon, 7 Oct 2019 04:28:38 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=f/rSizDkVILftPSYWX52C0CFUm4R2ARfcFaG4FKkE2b+Y5PLmxC+vOzolkrQnS7j2o9ZLIfuCCWWZmfw5c96aM39pqk0GB9svqx5xyvLvKOoJLOs0giwXC2XeV+SITwyruyjzRZWgfcdJKuhtybrjNecyxdV5EEj1/jls2N4qUBcVyVw+uHdMvz65UhZgJPiHSvXER9a8Ql3yoAic/LugLPOcGL9nX4A6K767pazSROpJ2d6ZMFNueFbfPj+8xT6kPx/jtnep8FFQy02S5ghd+QOPoeTo7mub1/hh3HRH0qW1M7RaVAxD6cpgtKlI/pW02BuXPGyGE+nJ7gZZGcXYQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fORZPhiE9FDyTokrHor2cy52e0drKbjQN5w8HBxBo2c=; b=Bd3EbM0sK2lMufy4FXrVYpZhSWk2oJix09UcBbcMOH3UqtUi3XYxlXDo9Kv3VYmYNSeUES5ZFK+WeprwrYuqmGarn5U27bKO3gQ1yrhdl9COHgHqZJTczM2VBitsT6NEjHcr2WR135HWZipDkGiXd9+U+q6oFRI/H9VXsx9UBipPsJeN9gZzEinh9pRsnddkjOYjM25llYSvMPszbqEzP4A9v+w15ES8bDvlql4jJFoCLJuayxxBQAMoXtKD9zcEPS496SNYntl5DOIH57hWC6xQ/qteK5VwTjtpCy4A4hZb+5kmzvVng1DNrpNse5AXTQ8UuNxbShKqhLj1vRS+fw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=sedonasys.com; dmarc=pass action=none header.from=sedonasys.com; dkim=pass header.d=sedonasys.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sedonasys.onmicrosoft.com; s=selector2-sedonasys-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fORZPhiE9FDyTokrHor2cy52e0drKbjQN5w8HBxBo2c=; b=fwdNz/iZUXmanY+exxb/X/+UNMFKuqVkQWXYJahOk8UDKBlvOyPF/UkJKlhfGrP4tVCYoqjuGeg2TEPcd5WexHcwNJd5RVuClQpDzqGozhlKCfNnv61Grp2Gq+/TerRBnVNBNsJI/7ZRfhqmPtqz/OqYgRrb39SCWv+NvruhGbw=
Received: from DB8PR10MB3387.EURPRD10.PROD.OUTLOOK.COM (10.255.17.204) by DB8PR10MB2764.EURPRD10.PROD.OUTLOOK.COM (20.179.9.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2327.24; Mon, 7 Oct 2019 11:28:35 +0000
Received: from DB8PR10MB3387.EURPRD10.PROD.OUTLOOK.COM ([fe80::f97f:fdcb:cd01:c7b5]) by DB8PR10MB3387.EURPRD10.PROD.OUTLOOK.COM ([fe80::f97f:fdcb:cd01:c7b5%7]) with mapi id 15.20.2327.023; Mon, 7 Oct 2019 11:28:35 +0000
From: Anton Snitser <antons@sedonasys.com>
To: "andy@yumaworks.com" <andy@yumaworks.com>, "mbj@tail-f.com" <mbj@tail-f.com>, "kwatsen@juniper.net" <kwatsen@juniper.net>, "netconf@ietf.org" <netconf@ietf.org>
CC: Liviu Cohen <liviuc@sedonasys.com>
Thread-Topic: RFC8040 inquiries
Thread-Index: AQHVePX19zmZMGveE0a2YmIbFCjzPadPNFAA
Date: Mon, 07 Oct 2019 11:28:35 +0000
Message-ID: <85070ED8-38A7-4C0D-B9C5-BC53252AB800@sedonasys.com>
References: <DCDA4768-5366-4D1B-88CC-0F60333591A3@sedonasys.com>
In-Reply-To: <DCDA4768-5366-4D1B-88CC-0F60333591A3@sedonasys.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=antons@sedonasys.com;
x-originating-ip: [37.142.40.85]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6d4e3f3a-72c2-4cd8-592c-08d74b197e28
x-ms-traffictypediagnostic: DB8PR10MB2764:
x-ms-exchange-purlcount: 2
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <DB8PR10MB2764822AC2E00C4E9D767B3CD79B0@DB8PR10MB2764.EURPRD10.PROD.OUTLOOK.COM>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01834E39B7
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400003)(396003)(136003)(346002)(366004)(376002)(53754006)(199004)(189003)(66946007)(256004)(555904003)(66066001)(186003)(7116003)(6436002)(7066003)(606006)(66556008)(64756008)(66616009)(66476007)(66446008)(229853002)(76116006)(91956017)(14454004)(71190400001)(71200400001)(25786009)(316002)(6486002)(33656002)(6246003)(36756003)(107886003)(45080400002)(99286004)(3846002)(790700001)(236005)(6116002)(6506007)(81166006)(81156014)(2201001)(486006)(8676002)(54896002)(6306002)(5660300002)(102836004)(6512007)(733005)(508600001)(446003)(11346002)(26005)(1941001)(4326008)(99936001)(2501003)(2906002)(9326002)(8936002)(476003)(86362001)(7736002)(2616005)(76176011)(110136005)(36394004); DIR:OUT; SFP:1102; SCL:1; SRVR:DB8PR10MB2764; H:DB8PR10MB3387.EURPRD10.PROD.OUTLOOK.COM; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: sedonasys.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: Tqf4aoE5+h5q2/OJEJVEbxgx70iEg7JZAlQ/bvQCBXHCC5bofYi7PKtUjSUs0sKWSzRDhJhaaTnJWbho7G2oBsKMlrEpTwKgis5jCARdinoBVzpLDqEotabPZRIFkdUR1sclDLLYOSWotcC/WtTTQ91ii4IIC78fEe2teZZfvz4z/Ww37xUVzsxVjz4OjU/oWXAFYV+GurLlDXw2NyPqLAALHqGYuXfopyOL+a9qgTL6+Px/tGUtrKgJCQfivFXT2oyOmxti9UEZH4S7iOHGV/XXUr7l5YtYkbsqiPd4M2oBBwY6Kj/lpt7e1aCs/R8OJNkFmhjkU6YMLVA7MRMfrcRos5gro6BUU4DI+Gg3XLhswaZk1UQQPqBLvXKnOCCa5KICMk7BDKaCsiPR7Nl3E+1hS1K1ln1vR6IKYAOxanqkc+Z6YHHCxPlMJ68Is9ZSaUl1BfWmlsQztlKopxR6sg==
Content-Type: multipart/related; boundary="_004_85070ED838A74C0DB9C5BC53252AB800sedonasyscom_"; type="multipart/alternative"
MIME-Version: 1.0
X-OriginatorOrg: sedonasys.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6d4e3f3a-72c2-4cd8-592c-08d74b197e28
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Oct 2019 11:28:35.8234 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d7c5624d-c76e-473e-9a79-91d374431ce8
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: W2Syt7vNxu15wH7XRgaRj5dXiEbNUUVxjpjdXaz8/pKQgmVoncS8jPq6yznkARHL3CL4PoS9uamzDbfrPND6Eg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR10MB2764
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/1qFmm5Rp4eFKb3JnMgEjhmKJZi8>
Subject: Re: [netconf] RFC8040 inquiries
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>, <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>, <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Oct 2019 11:28:41 -0000

Hello Everyone,

My name Is Anton Snizar, I am a System engineer working for Sedona Systems.

I have a foundational question regarding the RESTCONF specification. I have not seen anywhere in the document whether it is required to provide a synchronous or asynchronous interface? Or maybe you have left it for the implementor to decide?

For Non-NMDA (unified datastore) RESTCONF (RFC 8040) it is stated that only a 201 created status code will valid to be used when new objects are created/configured. With that in mind, should one treat this as an implicit definition to make the interface synchronous? E.g., only upon resource creation in the network will a 201 be sent to the NBI client?

At the moment we implement a synchronous RESTCONF interface but at the same time wondering support for async for some optimization considerations. As were wondering whether it would still be compliant to the standard or not.. Any clarification would be helpful.

Hanks,
Best regards

[id:image001.png@01D3D4EC.AFD81260]
Anton Snizar | Systems Engineer

m: +972-504042744
e: antons@sedonasys.com<mailto:antons@sedonasys.com>
w: sedonasys.com<https://sedonasys.com/>
l: Linkedin<http://linkedin.com/in/anton-snizar-4aa57646/>

v2.23.0 | Report a Bug | By Email