Dear Mike, Thank you for pointing that out. I'll remove RFC4188 and RFC4363 from normative references and add them to informative references in order to make sure these are informative.
Thank you. Hirochika On Oct 14, 2013, at 10:47 PM, Michael MacFaden <[email protected]> wrote: > > Asai-san writes: > >> 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. > > Just checking, you meant for this to be an informative reference right? > I'd prefer if we change the example mib module to the IEEE mib module. > RFC 4188 is the last of its kind. IETF gave this mib module and most layer 2 > related mibs > over to IEEE. ESXi for example implements IEEE8021-Q-BRIDGE-MIB, REVISION > 200810150000Z. > > Thanks, > Mike MacFaden > -- Hirochika Asai <[email protected]>, The University of Tokyo _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
