Re: [IETFMIBS] [EXT] Re: Issues with master/slave terminology in SNMP and FDDI MIBs

Mark Ellison <ellison@ieee.org> Tue, 30 November 2021 23:15 UTC

Return-Path: <mark@ellisonsoftware.com>
X-Original-To: ietfmibs@ietfa.amsl.com
Delivered-To: ietfmibs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 086BA3A0474 for <ietfmibs@ietfa.amsl.com>; Tue, 30 Nov 2021 15:15:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.701, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
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 M-UOlmiTQHHT for <ietfmibs@ietfa.amsl.com>; Tue, 30 Nov 2021 15:15:09 -0800 (PST)
Received: from mail-yb1-xb32.google.com (mail-yb1-xb32.google.com [IPv6:2607:f8b0:4864:20::b32]) (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 D51363A044F for <ietfmibs@ietf.org>; Tue, 30 Nov 2021 15:15:08 -0800 (PST)
Received: by mail-yb1-xb32.google.com with SMTP id v138so57529581ybb.8 for <ietfmibs@ietf.org>; Tue, 30 Nov 2021 15:15:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=MG5zCS8rLOh2nTWqlHc3f2mOv1bETsNeBoEiY4WAtEA=; b=NxMpkcIO5Vxj+zJHRYs/krnqbqGHDtlW3r9lX+80Kl4e1G31NX2A2QQ9rmgs+6Qy11 9f2OF8ya1+wSzLpV7LI0rBkJfGO0uJY23/li2R33Vi1+4E/z3qzC4QrBBJTzzkso2yM/ V+5/3Tlpe+s2lRGSMJZUoM3d/o1gDs9NDXLDs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MG5zCS8rLOh2nTWqlHc3f2mOv1bETsNeBoEiY4WAtEA=; b=ZU+TPRHuGHNJ+HfNa+S0CrRF3mliVstMg6zrDCVMtMuqo/Di6kPwAGwt+rhWOku+l7 co2A3ThH4n7/9fvFVdt+WSHBmaKIfUGxEUAnkisq166ShTx5QCwwA34e1D/lRPpGmkSy Ce2bemZai+upzlges4tcAB8789lluNBUwC0fTFs/P4n3ZceMwEgdfOChn3uVt5YLevdb +VKBg3EYUYmnwVx/Cwwyfwk3UKYD6dy9D/VAlBn/UTXykQaHU464QpBCgupv70n7PH2q MpXta/LjCZWkEs/4dHebAnf7wU4BNd29rIS0h8ZWTjXTl/494UO4Ctey48+k+z/kS37z 4qoQ==
X-Gm-Message-State: AOAM532x+HAUMFDJL2+xjofUYxT9unbIiUl3zJlyeA3QOSwtLTTEcSX8 L+DmrWlnOINPH/bWi9nGfuq3Sj9gJLp6vNpHPFiv
X-Google-Smtp-Source: ABdhPJxtvp7J0QOdSlbYH3LRCFkXHF4JjAxbz739oDzYMLBKDNhBEbEwdjyscje8YS4Ot3Oyo3/0op1PPmJ4MXVl9Yo=
X-Received: by 2002:a25:ce93:: with SMTP id x141mr2688268ybe.109.1638314106482; Tue, 30 Nov 2021 15:15:06 -0800 (PST)
MIME-Version: 1.0
References: <OF9F597A9A.90F9B174-ON8525879D.0066FDB2-8525879D.0068A4A9@ibm.com> <31840_1638302237_61A6821B_31840_442_1_3c6281a7-69f1-2b08-0189-b023ae7c85ee@alumni.stanford.edu> <MN2PR09MB471664A0568446DA77AE0CCFA8679@MN2PR09MB4716.namprd09.prod.outlook.com> <cdb2366e-577d-9cbd-d6ed-cfa32662c038@alumni.stanford.edu> <CABfCB8qvYv3kUOU+_qPLKFn_GN5rpKEJnc1Nm5ci0g4NExBq+g@mail.gmail.com> <7f6217d3-48fe-d37c-50af-a7214b064ee7@alumni.stanford.edu>
In-Reply-To: <7f6217d3-48fe-d37c-50af-a7214b064ee7@alumni.stanford.edu>
From: Mark Ellison <ellison@ieee.org>
Date: Tue, 30 Nov 2021 18:14:55 -0500
Message-ID: <CABfCB8rGkwx1iHSyufHgbJHczCjRObURNoBp2rL-MqbndDEYnA@mail.gmail.com>
To: Randy Presuhn <randy_presuhn@alumni.stanford.edu>
Cc: ietfmibs@ietf.org
Content-Type: multipart/alternative; boundary="000000000000590c5f05d209baef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietfmibs/a3yXQC8_K4fIQqCTmswaZMTLi24>
Subject: Re: [IETFMIBS] [EXT] Re: Issues with master/slave terminology in SNMP and FDDI MIBs
X-BeenThere: ietfmibs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF MIB Discussion list <ietfmibs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietfmibs/>
List-Post: <mailto:ietfmibs@ietf.org>
List-Help: <mailto:ietfmibs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietfmibs>, <mailto:ietfmibs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Nov 2021 23:15:14 -0000

Hello,

On Tue, Nov 30, 2021 at 5:27 PM Randy Presuhn <
randy_presuhn@alumni.stanford.edu> wrote:

> Hi -
>
> On 2021-11-30 2:03 PM, Mark Ellison wrote:
> ...
> >  From my perspective, there is no benefit in changing RFC text for the
> > AgentX protocol.  Organizations reacting to the presence of 'offensive
> > terminology' in AgentX now have another reason to adopt the NetConf
> > protocol, designed as the replacement for SNMP.
>
> A minor problem being that the NetConf work does not address the
> issues that motivated the development of subagent technology,
> and defines no interfaces between the NetConf Server and whatever
> processes implement the instrumentation.
>

Yes, a valid point.  There are extensibility features in some of the
NetConf server development kits.  However, master- and sub-agent
terminology is used.  Since the NetConf WG has a clean slate wrt
extensibility and related terms, were it to take up extensibility as a
standard, less triggering terms would be in scope.

Mark Ellison


> > Of course, an
> > organization is free to decide which terms are used in its
> > documentation- perhaps, Executive Agent?  (note:  no Chief here ;-)
> >
> > And, if the terminology in the RFC *were changed*, you'd be facing a
> > term mismatch between re-written RFCs and existing, running code.
>
> Yup.  I'd be willing to wager that the priority for updating that
> code is *really* low on the priority list of whoever is taking
> care of it these days.
>
> Randy
>
> _______________________________________________
> IETFMIBS mailing list
> IETFMIBS@ietf.org
> https://www.ietf.org/mailman/listinfo/ietfmibs
>