Re: [netmod] system configuration sync mechanism
Andy Bierman <andy@yumaworks.com> Tue, 17 August 2021 23:35 UTC
Return-Path: <andy@yumaworks.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76F2E3A12F8 for <netmod@ietfa.amsl.com>; Tue, 17 Aug 2021 16:35:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.887
X-Spam-Level:
X-Spam-Status: No, score=-1.887 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yumaworks-com.20150623.gappssmtp.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 bvls92woD1QQ for <netmod@ietfa.amsl.com>; Tue, 17 Aug 2021 16:35:09 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 76A0B3A12C6 for <netmod@ietf.org>; Tue, 17 Aug 2021 16:35:09 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id k5so565622lfu.4 for <netmod@ietf.org>; Tue, 17 Aug 2021 16:35:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+ADnZOodgD/xsxQN+l5RFNiYZlRhF0/HkUnTZhWrHFE=; b=i3B1/YzlOIvQ9Fnb1vGQUqYwZHrdQ4oq9Xg5G9LhhAPFwp6O84ec1LNuvhgD5N6LRx akNExsQiXh+G00IBYRcDR6ne+KfFp2qQfhiPru17hn5uvtz//BNUcgjdhTCyixbbPQxe k61WMcQvHkyksnQ93ZyaLK/d4UVckE8Av7KiVYhPek5FnMuPYRRKIQB1nO6XoG5k5V7y sfMWBSh9IqPCGYymjGEWrVWQYlVkZ9pg0mmouNrm3VhT6cL8axN2JBY5xtEAkGDY4Cfm OGpX3b/RysPVj26VZGNVskFWD1v0K311qNh0qqY6R2T1ypvwY6TIsGJuF7ZX8K4cfjCt 9Hmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+ADnZOodgD/xsxQN+l5RFNiYZlRhF0/HkUnTZhWrHFE=; b=CRvjyE3AakKMxxSj0fPZ4fmCstPm1zdyz11+Wh/VOh2f5B8UV/aO3dKWzjsQg394qA ik26xFuYiZEIxmO+MXyIxTlX/OIkOueJUZ5XFIHkFiL2zD6T/WyVu91PpJ+RSskA3FHX 1+GnySe3hYtRD/CaZBffNrfyR6fh/Yq1CjpiH4D4jVmi/veml99F/KoTVKz4zru9SolB +Crhtr6HyCxBOqPNvdpoG6OAM8kxnBb+7Z/dXnlCK/6Yy0fnBQpdqbOrJx9Vmbhsyg17 Z6jQcUjvuWLasreF5O/08ZwG0X6IYwAUJLwFeGSagY+Dxp5qfJBRKowHihawWn9HiKIH ogzw==
X-Gm-Message-State: AOAM531PDKwcDYlN4nhtP2QhSTsvMYNei9L87xKGBURajYZdioIPPuYk oLbPLoDafJhtXRooVa0CG0pP27fqMGuvOA15mAqEeg==
X-Google-Smtp-Source: ABdhPJxJNsZAaXdoANMInwf3ATkXXH97qpG7Uhu5JA38ZgNXS+Py+PicDbW4+487LNHBlPFhSuQkqECIotIsiUT+mv4=
X-Received: by 2002:a19:4f1a:: with SMTP id d26mr4009026lfb.377.1629243305593; Tue, 17 Aug 2021 16:35:05 -0700 (PDT)
MIME-Version: 1.0
References: <ad7ec21e0d3d477b91bebdfdeec01303@huawei.com> <0100017b5558ab9d-43cdec2f-59c4-4ff0-97e2-3b90cfca869d-000000@email.amazonses.com>
In-Reply-To: <0100017b5558ab9d-43cdec2f-59c4-4ff0-97e2-3b90cfca869d-000000@email.amazonses.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Tue, 17 Aug 2021 16:34:54 -0700
Message-ID: <CABCOCHQkJWtJLaGQGOiK73KOFdQJY4PGy5daZSj4ToZPqPubZQ@mail.gmail.com>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: Qin Wu <bill.wu@huawei.com>, "netmod@ietf.org" <netmod@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007ba4ee05c9c9c4c0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/g8caKcDtp7WM4ENhbUgwaT8GBVo>
Subject: Re: [netmod] system configuration sync mechanism
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Aug 2021 23:35:25 -0000
Hi, I guess I do not agree with the premise of the draft, which is that the client needs to take over control of the system-controlled configuration. I will wait for a draft update and see if that helps understand it better. Andy On Tue, Aug 17, 2021 at 11:21 AM Kent Watsen <kent+ietf@watsen.net> wrote: > > >IMO this draft overlaps the factory-default datastore. > >Unfortunately, RFC 8808 does not document NMDA, Appendix A3 details > >https://datatracker.ietf.org/doc/html/rfc8342#appendix-A.3 > >It does not say if <factory-default> datastore feeds into <running> or > into <intended>. > >It is not clear how <system> would interact with other datastores. > [Qin]: As described in Appendix-A.3, two ways to interact with other > datastore are discussed, one is interact implicitly, the other is to use > RPC to trigger application of the datastore's data, in factory default > setting case, <factory-reset> rpc will reset the contents of all relevant > datastores to factory default state. > The extreme case of factory default state is no configuration at all for > each datastore. > > > Right. Also, the word “flow” doesn’t seem quite right…at least in my > mind, it suggests an ongoing relationship, whereas <factory-default> is > really for one-time initializations. > > From https://datatracker.ietf.org/doc/html/rfc8808#section-3: > > Management operations: The contents of the datastore is set by the > server in an implementation-dependent manner. The contents cannot > be changed by management operations via the Network Configuration > Protocol (NETCONF), RESTCONF, the CLI, etc., unless specialized, > dedicated operations are provided. The datastore can be read > using the standard NETCONF/RESTCONF protocol operations. The > "factory-reset" operation copies the factory default contents to > <running> and, if present, <startup> and/or <candidate>. The > contents of these datastores is then propagated automatically to > any other read-only datastores, e.g., <intended> and > <operational>. > > > > >It is not clear why it is even needed since <factory-default> contains > only system settings. > [Qin]: I agree <factory-default> could have system setting. But > unspecified for some reasons. > Based on earlier discussion on factory default, what content is included > in <factory-default> and how to format this content, e.g., YANG instance > file format > Have been ruled out of the scope. See the diff in v-07 > https://www.ietf.org/rfcdiff?url2=draft-ietf-netmod-factory-default-07.txt > > > > Regardless, <factory-default> cannot be used for immutable “system" > defined objects, since it’s contents initialize client-editable datastores. > > > K. > > >
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism maqiufang (A)
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism maqiufang (A)
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism maqiufang (A)
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism maqiufang (A)
- Re: [netmod] system configuration sync mechanism Balázs Lengyel
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Kent Watsen
- [netmod] 答复: system configuration sync mechanism Fengchong (frank)
- Re: [netmod] 答复: system configuration sync mechan… Jürgen Schönwälder
- [netmod] 答复: 答复: system configuration sync mechan… Fengchong (frank)
- Re: [netmod] 答复: 答复: system configuration sync me… Jürgen Schönwälder
- Re: [netmod] 答复: system configuration sync mechan… Andy Bierman
- [netmod] 答复: 答复: system configuration sync mechan… Fengchong (frank)
- Re: [netmod] system configuration sync mechanism maqiufang (A)
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Jürgen Schönwälder
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Sterne, Jason (Nokia - CA/Ottawa)
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism Sterne, Jason (Nokia - CA/Ottawa)
- Re: [netmod] system configuration sync mechanism Sterne, Jason (Nokia - CA/Ottawa)
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Qin Wu
- Re: [netmod] system configuration sync mechanism Kent Watsen
- Re: [netmod] system configuration sync mechanism Andy Bierman
- Re: [netmod] system configuration sync mechanism Jan Lindblad (jlindbla)
- Re: [netmod] system configuration sync mechanism Sterne, Jason (Nokia - CA/Ottawa)
- Re: [netmod] system configuration sync mechanism Sterne, Jason (Nokia - CA/Ottawa)
- Re: [netmod] system configuration sync mechanism Sterne, Jason (Nokia - CA/Ottawa)