Dear Benoit,
Thank you for your clarification. I understand that the IESG statement does
not forbid all the use of objects with read-write access, and our
vmPerVMNotificationsEnabled and vmBulkNotificationsEnabled can be
read-write.
Hirochika
On Jul 16, 2014, at 12:43 PM, Benoit Claise
Dear Hirochika,
Very sorry for the delay in getting back to you.
Dear Joel and Benoit,
Thank you.
Since Joel has invited Benoit, another AD of OPS AREA, to this discussion,
I summarize my question for clarity as follows:
The IESG statement (*1) encourages to remove read-write access to
On Wed, 28 May 2014, t.petch wrote:
SNMP has never said much about persistence (table row status [with
StorageType] being the exception).
This omission was recognized when the MIB review guidelines
(http://tools.ietf.org/html/rfc4181) were developed, and as a result
the following text was
Subject: Re: [OPSAWG] Read-write access in VMM-MIB
...
SNMP has never
said much about persistence (table row status being the exception).
You seem to have overlooked the StorageType textual convention
from RFC 2579. It's fairly widely used.
Randy,
No, not overlooked, just referred
And yes that model, per row, was alot of state to maintain, RFC 3514.
Correction, d/RFC 3514/cut past error. Sorry for the confusion.
Mike
___
OPSAWG mailing list
OPSAWG@ietf.org
https://www.ietf.org/mailman/listinfo/opsawg
- Original Message -
From: Hirochika Asai pa...@hongo.wide.ad.jp
To: joel jaeggli joe...@bogus.com
Cc: opsawg@ietf.org
Sent: Wednesday, May 28, 2014 12:57 AM
Dear Joel and Benoit,
Since Joel has invited Benoit, another AD of OPS AREA, to this
discussion,
I summarize my question for
Hi -
From: t.petch ie...@btconnect.com
Sent: May 28, 2014 2:30 AM
To: Hirochika Asai pa...@hongo.wide.ad.jp, joel jaeggli joe...@bogus.com
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Read-write access in VMM-MIB
...
SNMP has never
said much about persistence (table row status being the exception
...@emc.com Mobile: +1 (978) 394-7754
-Original Message-
From: OPSAWG [mailto:opsawg-boun...@ietf.org] On Behalf Of Hirochika Asai
Sent: Monday, May 26, 2014 3:25 AM
To: opsawg@ietf.org
Subject: [OPSAWG] Read-write access in VMM
Dear all,
We'd like to discuss the read-write access in the proposed MIB about virtual
machine monitoring: http://tools.ietf.org/html/draft-ietf-opsawg-vmm-mib .
It has 10 read-write objects. All of them do not affect persistent configuration
of hypervisor or virtual machines. However, according
Asai,
the IESG statement is here:
http://www.ietf.org/iesg/statement/writable-mib-module.html
My reading is that it specifically talks about configuration. While
the discussion started with lets ban all write access, it may be
important to note that the final statement does not say this.
Hi -
From: Hirochika Asai pa...@hongo.wide.ad.jp
Sent: May 26, 2014 10:48 AM
To: joel jaeggli joe...@bogus.com
Cc: opsawg@ietf.org opsawg@ietf.org
Subject: Re: [OPSAWG] Read-write access in VMM-MIB
...
I think it would be better to move this issue to the IESG, but I don't keep
up the procedure
11 matches
Mail list logo