Re: [netmod] Adoption poll for draft-wwx-netmod-event-yang-10

Randy Presuhn <randy_presuhn@alumni.stanford.edu> Tue, 29 December 2020 21:35 UTC

Return-Path: <randy_presuhn@alumni.stanford.edu>
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 B02D13A0AD5 for <netmod@ietfa.amsl.com>; Tue, 29 Dec 2020 13:35:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 Pvbc8THge4nc for <netmod@ietfa.amsl.com>; Tue, 29 Dec 2020 13:35:56 -0800 (PST)
Received: from mail-pl1-f180.google.com (mail-pl1-f180.google.com [209.85.214.180]) (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 7E0CE3A098A for <netmod@ietf.org>; Tue, 29 Dec 2020 13:35:56 -0800 (PST)
Received: by mail-pl1-f180.google.com with SMTP id j1so7725188pld.3 for <netmod@ietf.org>; Tue, 29 Dec 2020 13:35:56 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=yhwf8h8SADcMbjGGM0xVoKnRRIx9D8xil4K0uux2MZs=; b=hTDE/Cb167nlh1dKWfANTb6i3Z7Yz6VVCGN3xl5PFZu3U1FVVJRuhJiHgwkwg53dv5 pDXDq7DNiIuHTW/0tUTFvf2rBSPXgIJyTmCA4r9hP6Yrc1BzoIVnlQb2CI5TMj/uOWzx EuunNki9u7zORqFvqLdXoiOtL60/zB1JIZ/qUmn4ARiCDaiQ5HSCLNffJswl7h7BTKpD TUfwYRwOZM4snKRdU0N6EMNOT9WyZeB5ZsEGrywVw/gr4EtJnIepXHbdmYFDoDJzKiY1 g2+TkYrEAH0dvHMtm4MFeB6uEFAgw+NIJns9ArPPZrEhNSapESAduOOn8iKNZcYluDh2 Zhnw==
X-Gm-Message-State: AOAM530bDtvdzMjiBE5Voo4QMHeEDa2prKpFR1FPMdbcXrro9lIJkUN9 gtbcd3NwuzYT1MoQcagYq+3ffS8P+NCB2A==
X-Google-Smtp-Source: ABdhPJx6To/lGB33RznmS+bLWiKHZKmiqFrO+wNkvY5Y+jfZmW3I2udzkYwhFKXOaG6Nhn5zKM76cA==
X-Received: by 2002:a17:90a:ff03:: with SMTP id ce3mr5646507pjb.44.1609277755654; Tue, 29 Dec 2020 13:35:55 -0800 (PST)
Received: from ?IPv6:2601:646:9300:791:b09b:f35a:c324:405d? ([2601:646:9300:791:b09b:f35a:c324:405d]) by smtp.gmail.com with ESMTPSA id t1sm37846405pfg.212.2020.12.29.13.35.55 for <netmod@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 29 Dec 2020 13:35:55 -0800 (PST)
To: netmod@ietf.org
References: <f836c5b2-ebc5-2775-ca60-3e888f12788c@labn.net> <CAB75xn6OoL63hyOpMJ=BcmVvnTiZHNskMDyQF6H54AafT7Q7Dw@mail.gmail.com> <AM7PR07MB6248FC667BA42C839086153BA0DE0@AM7PR07MB6248.eurprd07.prod.outlook.com> <CABCOCHQRfm0ZnTTeKR43ki0fTGJi037hV83EjDaTO2xO+u64DA@mail.gmail.com> <20201223180852.rnif4ioc3tovvwkv@anna.jacobs.jacobs-university.de> <015a01d6ddff$52cd3ef0$f867bcd0$@olddog.co.uk> <CABCOCHQrZ+tZTXKaJQuMV0uV8FmpO7X-KDyq8rEO_pSiKPbz8Q@mail.gmail.com>
From: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Message-ID: <3db30c46-d95f-8c04-d00f-db29ee44362e@alumni.stanford.edu>
Date: Tue, 29 Dec 2020 13:35:53 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: <CABCOCHQrZ+tZTXKaJQuMV0uV8FmpO7X-KDyq8rEO_pSiKPbz8Q@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/hKUlXYylYUrxtfShOW52Xe5llu0>
Subject: Re: [netmod] Adoption poll for draft-wwx-netmod-event-yang-10
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, 29 Dec 2020 21:35:58 -0000

Hi -

On 2020-12-29 12:31 PM, Andy Bierman wrote:
...
> I am not that interested in lessons from the past because it just sounds
> like an old-timer's negativity.  But I am not interested in boiling the 
> ocean either.
> 
> There is an invalid assumption with ECA that the current client 
> development logic
> (which is completely unbounded in its complexity, purpose, side effects, 
> design,
> or server interaction model) can somehow be replaced with a highly 
> constrained
> YANG model abstraction.
> 
> IMO a script-language-based solution is needed.
> The ECA framework is good progress, but Programming in YANG is not.
> However the IETF is not well-suited for standardizing programming languages
> Open-Source is a much better solution path for this approach.
> 
> The solution also has to do a great job of gluing the model components to
> the ECA logic and actions so there is maximum reusability and scalability.
> 
> Most importantly, it has to be easy for an operator to program and debug 
> ECA.
> There aren't going to be any magic tools to hide the complexity.

There's a tension between the convenience of scripting languages and the
desire to be able to reason about how policies interact, particularly if
one is approaching the problem from a perspective of goal-oriented
management.  To me that suggests that more structured (than mere
scripting) mechanisms are needed to to identify what aspects of what
resources are inputs or outputs in the operation of a given policy.
(That also has the nice side-effect of making policy formulations
vastly more re-usable.)

For the ISO/ITU work, my recollection is that the direction in which
it was headed was to use facilities of the management information
model and protocol (e.g. scoping, filtering, allomorphism, attribute
re-use, etc.) for the parameterization, but to use scripting for the
policy's "body".  I don't know if that's how things ultimately turned
out; I've been away from the work for decades.

If all the semantics, including specification of applicability,
are embodied in the script itself, one ends up with something
like the script MIB.  A potentially useful thing, but not particularly
helpful if one's goal is to be able to reason about policy interaction
or to formulate things in terms of goals.

Randy