[Netconf] draft-dsdt-netconf-restconf-nmda-00
"Susan Hares" <shares@ndzh.com> Tue, 18 July 2017 04:35 UTC
Return-Path: <shares@ndzh.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 A55EE127136; Mon, 17 Jul 2017 21:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level:
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, HTML_MESSAGE=0.001] autolearn=no 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 s2c0jApGBWZN; Mon, 17 Jul 2017 21:35:00 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E68F8126C0F; Mon, 17 Jul 2017 21:34:59 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=31.133.153.78;
From: Susan Hares <shares@ndzh.com>
To: 'Kent Watsen' <kwatsen@juniper.net>
Cc: 'Netconf' <netconf@ietf.org>, i2rs@ietf.org
Date: Tue, 18 Jul 2017 00:28:56 -0400
Message-ID: <011201d2ff7e$5fe4d480$1fae7d80$@ndzh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0113_01D2FF5C.D8D5A580"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AdL/S8SPYN+w5hc7SKqDDphMXADmkQ==
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/8y-M9Q9UgSXyUpfR9PlJXpfTlEk>
Subject: [Netconf] draft-dsdt-netconf-restconf-nmda-00
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Network Configuration WG mailing 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: Tue, 18 Jul 2017 04:35:02 -0000
Kent: I am pleased to see your progress on draft-dsdt-netconf-restconf-nmda-00txt. You asked me to suggest comments on what would be necessary in the following cases: 1) Normal, 2) Dynamic datastore 3) Ephemeral dynamic datastore #1) Normal Since the current description does not allow dynamic and ephemeral dynamic, I think this is fine. #2) Dynamic I2RS datastore which is not ephemeral These changes to restconf for the nmda-00.txt did not include the following comments from draft-hares-netconf-i2rs-restconf-02.txt: 1. I2RS Normal datastore must redefine be able to redefine a mask to the entity tag to encode <client-id> <priority-id> Section 3.5.2 of RFC8040 states: "The "ETag" header field can be used by a RESTCONF client in subsequent requests, within the "If-Match" and "If-None-Match" header fields." - This is great, because the I2RS requirements need a match on this field on the client id, the priority-id or both. Section 3.5.3 of RFC8040 states: "This entity-tag is only affected by configuration data resources and MUST NOT be updated for changes to non-configuration data." This must be revised to indicate that for dynamic datastores. any data written from any origin must be updated. Does this belong in the main document or in the I2RS ephemeral datastore definition. 2. Dynamic datastores are excluded from this draf If I2RS creates a dynamic datastore draft, should it discuss how section * "with defaults" - How RFC8040 section 3.5.4 is adapted for dynamic work, * "with validation" - How validation is normally handled, * "how client edit collisions are handled - RFC 8040 3.4 or different method 3. Ephemeral dynamic datastores are excluded from this draft If I2RS creates an dynamic ephemeral datastore draft, then it should discuss the following: . "with defaults" setting - that section 3.5.4 to not keep data after a reboot, but to provide some default setting upon being downloaded. . "entity tag" (RFC 3.5.2) - adaptation to provided client and priority, . Restriction of ephemeral dynamic datastores to exclude the "rollback I hope this helps. Sue Hares
- [Netconf] draft-dsdt-netconf-restconf-nmda-00 Susan Hares