IETF Logo Mail Archive

[netmod] Re: Yang Scalability

Kent Watsen <kent@watsen.net> Thu, 25 July 2024 20:42 UTC

Return-Path: <01000190eba1f33a-fa18710d-242f-4c8d-b4b0-cebf22299b7a-000000@amazonses.watsen.net>
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 6F891C14F705 for <netmod@ietfa.amsl.com>; Thu, 25 Jul 2024 13:42:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazonses.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rkScKvufxXRy for <netmod@ietfa.amsl.com>; Thu, 25 Jul 2024 13:42:59 -0700 (PDT)
Received: from a48-93.smtp-out.amazonses.com (a48-93.smtp-out.amazonses.com [54.240.48.93]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9492C14F6FA for <netmod@ietf.org>; Thu, 25 Jul 2024 13:42:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1721940177; h=Content-Type:Content-Transfer-Encoding:From:Mime-Version:Subject:Date:Message-Id:References:Cc:In-Reply-To:To:Feedback-ID; bh=g+TZ2aY4iEMP+qZXxpO/m0Vrr0yh0IpmwsFUlubKVWc=; b=EbYLIAbvpolA/EzoIeMZ2EG6+VTUmYL1gLjt7/gzl7dGDmryW1LZzPP9EZI1eElZ wPx2BA2/gmWrGSgm2pLZXsDM94Us2PgzckVmWZt5JdNQ84B2M6yUnBhcASunWxvyZQ6 ywc5qB+t6Bayffxf3qlrmkz3sA0J9XWTnDcR97EM=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
From: Kent Watsen <kent@watsen.net>
Mime-Version: 1.0 (1.0)
Date: Thu, 25 Jul 2024 20:42:57 +0000
Message-ID: <01000190eba1f33a-fa18710d-242f-4c8d-b4b0-cebf22299b7a-000000@email.amazonses.com>
References: <PH7PR14MB53681B1B2A6A2F41DD316DAEBBAB2@PH7PR14MB5368.namprd14.prod.outlook.com>
In-Reply-To: <PH7PR14MB53681B1B2A6A2F41DD316DAEBBAB2@PH7PR14MB5368.namprd14.prod.outlook.com>
To: Don Fedyk <dfedyk@labn.net>
X-Mailer: iPhone Mail (21E219)
Feedback-ID: ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.07.25-54.240.48.93
Message-ID-Hash: K2CVF6EPSZUVXADHUS4EOPQOECFZZ4SJ
X-Message-ID-Hash: K2CVF6EPSZUVXADHUS4EOPQOECFZZ4SJ
X-MailFrom: 01000190eba1f33a-fa18710d-242f-4c8d-b4b0-cebf22299b7a-000000@amazonses.watsen.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netmod.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "Robert Peschi (Nokia)" <robert.peschi=40nokia.com@dmarc.ietf.org>, Jürgen Schönwälder <jschoenwaelder@constructor.university>, Italo Busi <Italo.Busi=40huawei.com@dmarc.ietf.org>, netmod@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [netmod] Re: Yang Scalability
List-Id: NETMOD WG list <netmod.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/afCCakHUdXdLzx6LGc73pPxhnps>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Owner: <mailto:netmod-owner@ietf.org>
List-Post: <mailto:netmod@ietf.org>
List-Subscribe: <mailto:netmod-join@ietf.org>
List-Unsubscribe: <mailto:netmod-leave@ietf.org>

> This means to me that templating mechanism might more easily be applied to the data input versus the schema itself.

Yes, but both input and output.  That is, <get-config> would return what <edit-config> set. 

A server would advertise that it supports, e.g., via a capability, but otherwise its YANG Library would be unchanged. 

There are several proprietary implementations.  I recommend a NIST-like bake off.   Can folks submit I-Ds?

If sufficient interest, I will request an extra NETMOD session for IETF 121 dedicated to this topic.  Session requests start Aug 12. 

Kent  // NETMOD chair

v2.26.15 | Report a Bug | By Email | System Status