[OPSAWG] Fwd: New Version Notification for draft-asai-vmm-mib-05.txt

[Hirochika Asai <[e-mail]>]

Hi folks,

Thanks to comments from the mailing list, we've uploaded new version
of our I-D: http://tools.ietf.org/html/draft-asai-vmm-mib-05

We would like to submit our I-D as a working group draft soon and
have a discussion in the next IETF as a working group draft.
Chairs, could you please poll for adoption as a working group item
on the mailing list?

I've already noticed an error: RFC4133 must be RFC6933.  Please let
us know if you find any other errors.  These errors will be
corrected in the next version (the first version for working group
draft if adopted).


Here, I summarize the updates from the previous version.

* According to the thread Joe-1
Modified a paragraph as follows:

The design of this MIB module has been derived from enterprise
specific MIB modules, namely a MIB module for managing guests of the
Xen hypervisor, a MIB module for managing virtual machines controlled
by the VMware hypervisor, and a MIB module using the libvirt
programming interface to access different hypervisors.
+ However, this MIB module attempts to generalize
+ the managed objects to support other hypervisors.

* According to the thread Joe-2
Added description of an example of hypervisor-specific case
using ENTITY-MIB, but not modified the MIB definition.

* According to the thread Joe-3
 vmAutoStart --> read-only
 vmCur* --> read-write
 vm*Mem vm*Cpu --> description w/ MUST NOT: "Changes to these objects MUST NOT persist"

* According to the thread Joe-5
For the network portion of the hypervisor, added a note on a case
equipping virtual switches on the hypervisor as follows:
   The objects related to virtual switches
   are not also included in this MIB module
   though virtual switches shall be placed on a hypervisor.
   This is because the virtual network interfaces are
   the lowest abstraction of network resources allocated
   to a virtual machine.
   Instead of including the objects related to virtual switches,
   for example, <xref target="RFC4188">BRIDGE-MIB</xref>
   and <xref target="RFC4363">Q-BRIDGE-MIB</xref> could be used.

* According to the thread Joe-7
Added Notifications for shuttingDown, resuming suspending, migrating, and blocked
# I think we still need discussion at this point.

* Others
Modified VirtualMachineOperState to be more clear.
Revised the description of VirtualMachine*Index.
Fixed some typos.


Best regards,
Hirochika


Begin forwarded message:

> From: [e-mail]
> Subject: New Version Notification for draft-asai-vmm-mib-05.txt
> Date: October 13, 2013 3:19:14 PM GMT+09:00
> To: Yuji Sekiya <[e-mail]>, Cathy Zhou <[e-mail]>, Tina Tsou <[e-mail]>, Keiichi Shima <[e-mail]>, Juergen Schoenwaelder <[e-mail]>, Michael MacFaden <[e-mail]>, Hirochika Asai <[e-mail]>, Hiroshi Esaki <[e-mail]>
> 
> 
> A new version of I-D, draft-asai-vmm-mib-05.txt
> has been successfully submitted by Hirochika Asai and posted to the
> IETF repository.
> 
> Filename:	 draft-asai-vmm-mib
> Revision:	 05
> Title:		 Management Information Base for Virtual Machines Controlled by a Hypervisor
> Creation date:	 2013-10-13
> Group:		 Individual Submission
> Number of pages: 56
> URL:             http://www.ietf.org/internet-drafts/draft-asai-vmm-mib-05.txt
> Status:          http://datatracker.ietf.org/doc/draft-asai-vmm-mib
> Htmlized:        http://tools.ietf.org/html/draft-asai-vmm-mib-05
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-asai-vmm-mib-05
> 
> Abstract:
>   This document defines a portion of the Management Information Base
>   (MIB) for use with network management protocols in the Internet
>   community.  In particular, this specifies objects for managing
>   virtual machines controlled by a hypervisor (a.k.a. virtual machine
>   monitor).
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
> 
> 

-- 
Hirochika Asai <[e-mail]>, The University of Tokyo