IETF Logo Mail Archive

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

Hirochika Asai <panda@hongo.wide.ad.jp> Tue, 15 October 2013 07:29 UTC

Return-Path: <panda@hongo.wide.ad.jp>
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 8013C21E81B3 for <opsawg@ietfa.amsl.com>; Tue, 15 Oct 2013 00:29:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.004
X-Spam-Level: *
X-Spam-Status: No, score=1.004 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994]
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 lOX5zDbRzIxe for <opsawg@ietfa.amsl.com>; Tue, 15 Oct 2013 00:28:56 -0700 (PDT)
Received: from mail.hongo.wide.ad.jp (mail.hongo.wide.ad.jp [203.178.135.13]) by ietfa.amsl.com (Postfix) with ESMTP id B35E411E810A for <opsawg@ietf.org>; Tue, 15 Oct 2013 00:28:56 -0700 (PDT)
Received: from [157.82.7.5] (unknown [157.82.7.5]) by mail.hongo.wide.ad.jp (Postfix) with ESMTPSA id 68EE6108E8B7; Tue, 15 Oct 2013 16:28:55 +0900 (JST)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset="iso-2022-jp"
From: Hirochika Asai <panda@hongo.wide.ad.jp>
In-Reply-To: <1193937661.420734.1381758464561.JavaMail.root@vmware.com>
Date: Tue, 15 Oct 2013 16:28:57 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <3456AAED-1E67-4AB5-ABA3-686E1CFAD13E@hongo.wide.ad.jp>
References: <20131013061914.31896.77972.idtracker@ietfa.amsl.com> <126539BC-2994-4DF6-9A5C-E66ED691B24D@hongo.wide.ad.jp> <1193937661.420734.1381758464561.JavaMail.root@vmware.com>
To: Michael MacFaden <mrm@vmware.com>
X-Mailer: Apple Mail (2.1510)
Cc: opsawg@ietf.org
Subject: Re: [OPSAWG] Fwd: New Version Notification for draft-asai-vmm-mib-05.txt
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: Tue, 15 Oct 2013 07:29:02 -0000

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 <mrm@vmware.com> 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 <panda@hongo.wide.ad.jp>, The University of Tokyo

v2.23.0 | Report a Bug | By Email