[netmod] Re: Yang Scalability

Kent Watsen <kent@watsen.net> Fri, 26 July 2024 05:25 UTC

Return-Path: <01000190ed7ff4b2-8e550823-baea-413a-b507-be77ab4b67f1-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 08937C1D6FA6 for <netmod@ietfa.amsl.com>; Thu, 25 Jul 2024 22:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 mJsGx0Oho0i3 for <netmod@ietfa.amsl.com>; Thu, 25 Jul 2024 22:25:05 -0700 (PDT)
Received: from a48-95.smtp-out.amazonses.com (a48-95.smtp-out.amazonses.com [54.240.48.95]) (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 7F6B0C16942F for <netmod@ietf.org>; Thu, 25 Jul 2024 22:25:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ug7nbtf4gccmlpwj322ax3p6ow6yfsug; d=amazonses.com; t=1721971504; h=Content-Type:Content-Transfer-Encoding:From:Mime-Version:Subject:Message-Id:Date:Cc:To:Feedback-ID; bh=BQmF/v2SXuTCMLIsQkvNwWouR1Z4JAI/zubuk/F1PJU=; b=oYFQeMAANiWlLOPhoDgLMI+UOLyNBcVc5UnJezaufL2tY0moRg7nIpXqXDvR0I24 gLXeE65JhLo8yUXim5k0FrtbP21Q89FlTpGvqcnSEFzjWOwXngpRQz2cK1iL0dbwHKI WIGPUI0JhMb0mw2SOLB33+OmY/RO+0IycZW+C+Nw=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Kent Watsen <kent@watsen.net>
Mime-Version: 1.0 (1.0)
Message-ID: <01000190ed7ff4b2-8e550823-baea-413a-b507-be77ab4b67f1-000000@email.amazonses.com>
Date: Fri, 26 Jul 2024 05:25:04 +0000
To: Italo Busi <Italo.Busi@huawei.com>
X-Mailer: iPhone Mail (21E219)
Feedback-ID: ::1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
X-SES-Outgoing: 2024.07.26-54.240.48.95
Message-ID-Hash: M4W5YFOV776ZPUMDDYD353TDHCU3HRM2
X-Message-ID-Hash: M4W5YFOV776ZPUMDDYD353TDHCU3HRM2
X-MailFrom: 01000190ed7ff4b2-8e550823-baea-413a-b507-be77ab4b67f1-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@nokia.com>, Jürgen Schönwälder <jschoenwaelder@constructor.university>, 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/ZIXb_MrH8xjqGu-9Y8oagb6D4Bo>
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>


> Do you have any reference (URL) to "NIST-like bake off" for people like me who are not aware of it?

I’ll summarize, most likely incorrectly, but it should suffice. 

1) NIST puts out a call for an algorithm

2) NIST evaluates submissions on varying axes: strength, speed, size, implementability, etc.

3) NIST publishes the results of its evaluations and requests updates (this may occur more than once) 

4) NIST selects a winner. 


FWIW, I just did #1 by asking for I-Ds. 


Of course we can do something different, but this approach appeals to me as:
    - several implementations exist. 
    - analyzing them would be insightful.
    - should be faster than starting from scratch. 


Kent