[Netconf] Does NMDA support synchronous configuration operation?
Henry Yu <hyu2010b@gmail.com> Fri, 22 June 2018 20:33 UTC
Return-Path: <hyu2010b@gmail.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 DC7B2130EEE for <netconf@ietfa.amsl.com>; Fri, 22 Jun 2018 13:33:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qVGZjd2gphms for <netconf@ietfa.amsl.com>; Fri, 22 Jun 2018 13:33:17 -0700 (PDT)
Received: from mail-ed1-x52c.google.com (mail-ed1-x52c.google.com [IPv6:2a00:1450:4864:20::52c]) (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 AB3AE130EE8 for <netconf@ietf.org>; Fri, 22 Jun 2018 13:33:16 -0700 (PDT)
Received: by mail-ed1-x52c.google.com with SMTP id b12-v6so1840103edt.8 for <netconf@ietf.org>; Fri, 22 Jun 2018 13:33:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=uEYWA9j0ueXTlajBHpE3oy0LbzIi+W36GX82DHb6YLw=; b=SKES3VZiQQJ8nx9GgPZIuph6LQMpZQI2280/v6glN/PNpvPc6FJYTprNCqvG64JH7o uhRxpYOFfc5GWFsyv91JSosrv7vcoL0rOIIteukjqkv2J/rhJiZoAS94UXNSGfkL5HAh Kc7TyNW61rOqUPzPfjbW2mNqLGART7qlZUucC602nGi6Q4q3RTG+4FtiY8qRFgwGzEzP sMxZ4QCTl8DCmbtzfgPQCVFh8uxsSDdeT9Ea+07uk4/z0RgA9rOkAwlq53Tj+D4BOHD+ 3hAruTOHH2npHpcOwZkVTZxRZXY4vHoDQ4WAIwEpsWCnMYvu+NWlwNENOXphIF9vxcCU pLxg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=uEYWA9j0ueXTlajBHpE3oy0LbzIi+W36GX82DHb6YLw=; b=fHJE1KXocw5l02symw6JNHvVdMM2fmAUknjRwJxrqwjkHkg+JeOdEFu0KpruRU4EvR hC5MUvjnH/jTMFQm24xjcNr/HUADC5ybev4vovSkD9C4IN3RVDmRcd42ITJg0PFsRpDi /1Yr3GSgIqdx1Kk/YiBVkmSOHD1el1FYJFvncMuOa8PtsP6w3KhE0A2asSNs58ZVD9Gb 3wIwsv/jNxWXhE6PT1V1GfYg0739R8/3TyrVGTnwe1vl9T4e/OEU8MDoCbJ6tb4FyFoF ydV3DF26/2OP2NEPZlNSeH4Xn6/7Fh10CelXzUMCaEHR/3qUeF4ij6vjiVMLJEPwVNtF Zx8g==
X-Gm-Message-State: APt69E26Nf7JSYg71xTPLdZQEL7o598ZuiToPs2t26UhnUKoC9ABDzfk l7X2sGNr86Qiehe8WHS0abT4IvzyDl14WGtPZHmw1Q==
X-Google-Smtp-Source: ADUXVKKSpNLFWJzIp/DGSP4DjlkRUQimfSJGolOswOykMl4vTKwPnEJUV33u+SyuWypHwLDvIw9Nq+WxNFHh0YkZZAc=
X-Received: by 2002:a50:b18d:: with SMTP id m13-v6mr2949798edd.66.1529699594991; Fri, 22 Jun 2018 13:33:14 -0700 (PDT)
MIME-Version: 1.0
From: Henry Yu <hyu2010b@gmail.com>
Date: Fri, 22 Jun 2018 16:33:04 -0400
Message-ID: <CAFsbzLmF+=x7Uiru8mT_17gGxmPwaLn_k735JMDVyo3OTumZRQ@mail.gmail.com>
To: netconf@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/iBArxZXEAxKL3Ss4W6VgfqRUgSI>
Subject: [Netconf] Does NMDA support synchronous configuration operation?
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.26
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: Fri, 22 Jun 2018 20:33:19 -0000
Hi all, Does NMDA (RFC 8341) support the synchronous configuration operation, defined in [draft-ietf-netmod-opstate-reqs-04]? [draft-ietf-netmod-opstate-reqs-04] and its solution [draft-kwatsen-netmod-opstate-02] have been replaced by RFC 8341. However, it seems that RFC 8341 only requires asynchronous config operations. i.e., When an intended configuration is received by the sever, it is written to <intended> once it passes the schematic validation, and applying the configuration to devices is a separate action. Is that a correct understanding? (I read some discussions [3] from the archive, but I am still not quite certain. Any clarification is appreciated.) Thanks, Henry [draft-ietf-netmod-opstate-reqs-04] https://tools.ietf.org/html/draft-ietf-netmod-opstate-reqs-04 [draft-kwatsen-netmod-opstate-02] https://www.ietf.org/archive/id/draft-kwatsen-netmod-opstate-02.txt [3] https://www.ietf.org/mail-archive/web/netmod/current/msg15113.html
- Re: [Netconf] Does NMDA support synchronous confi… Henry Yu
- Re: [Netconf] Does NMDA support synchronous confi… Juergen Schoenwaelder
- Re: [Netconf] Does NMDA support synchronous confi… Henry Yu
- Re: [Netconf] Does NMDA support synchronous confi… Henry Yu
- Re: [Netconf] Does NMDA support synchronous confi… Juergen Schoenwaelder
- Re: [Netconf] Does NMDA support synchronous confi… Henry Yu
- [Netconf] Does NMDA support synchronous configura… Henry Yu
- Re: [Netconf] Does NMDA support synchronous confi… Juergen Schoenwaelder
- Re: [Netconf] Does NMDA support synchronous confi… Juergen Schoenwaelder
- Re: [Netconf] Does NMDA support synchronous confi… Juergen Schoenwaelder
- Re: [Netconf] Does NMDA support synchronous confi… Ladislav Lhotka
- Re: [Netconf] Does NMDA support synchronous confi… Kent Watsen