IETF Logo Mail Archive

Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on draft-asai-vmm-mib-04)

"Randy Presuhn" <randy_presuhn@mindspring.com> Thu, 29 August 2013 23:59 UTC

Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A038311E8110 for <opsawg@ietfa.amsl.com>; Thu, 29 Aug 2013 16:59:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mzwaPnCnbgHu for <opsawg@ietfa.amsl.com>; Thu, 29 Aug 2013 16:59:21 -0700 (PDT)
Received: from elasmtp-curtail.atl.sa.earthlink.net (elasmtp-curtail.atl.sa.earthlink.net [209.86.89.64]) by ietfa.amsl.com (Postfix) with ESMTP id A8B7511E80D2 for <opsawg@ietf.org>; Thu, 29 Aug 2013 16:59:21 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=e83Rnwj119o6B8oKPdIJ3uquz2VaY+EmjLrg+pCShdhYATyXvFshJZ4g2iapWuER; h=Received:Message-ID:From:To:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.23.161.81] (helo=oemcomputer) by elasmtp-curtail.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1VFC7S-0006ds-IB for opsawg@ietf.org; Thu, 29 Aug 2013 19:59:18 -0400
Message-ID: <001b01cea513$e15181e0$6b01a8c0@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: opsawg@ietf.org
References: <26070259.1377798792684.JavaMail.root@mswamui-billy.atl.sa.earthlink.net> <521FA120.7090401@cisco.com> <001201cea4f0$56576f00$6b01a8c0@oemcomputer> <521FD51A.9050500@cisco.com>
Date: Thu, 29 Aug 2013 17:00:02 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d888ba196d48fc2e3f08ea1d675a706d19a9fde4c063deff0504350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.161.81
Subject: Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on draft-asai-vmm-mib-04)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsawg>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Aug 2013 23:59:27 -0000

Hi -

> From: "Joe Marcus Clarke" <jclarke@cisco.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: <opsawg@ietf.org>
> Sent: Thursday, August 29, 2013 4:11 PM
> Subject: Re: [OPSAWG] VMM-MIB: Proposal: Joe -3 (Was Re: Comments on draft-asai-vmm-mib-04)
...
> I would be happy with read-only objects that showed the operational
> values.  But there was a use case for changing the operational
> parameters via SNMP SET.

In my book, that's a configuration change.  It might be made with the
intention of reverting to some previous configuration at some time in
the future, but a configuration change nonetheless.

It sounds like the claim here is that there are knobs whose initial 
settings are presumed to persist as part of system configuration,
but for which any "tweaks" are forgotten.  Those are two different
knobs, should be clearly identified as such, and their relationship
formally spelled out.  Depending on the complexity of their relationship,
it sounds like you may be asking for THREE objects (not all in MIB
modules, of course):
   - the persistent configuration parameter, Netconf or whatever
   - the writable "tweak" knob, whose values might potentially
     be constrained by persistent configuration
   - the read-only operational value, which would be some
     function of the configuration, the tweak knob, and heaven-knows-what
     else.

Randy

v2.23.0 | Report a Bug | By Email