[Hubmib] RE: [IANA #33594] draft-ietf-hubmib-rfc3636bis
"Wijnen, Bert \(Bert\)" <bwijnen@alcatel-lucent.com> Tue, 16 January 2007 09:08 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6kIj-0004W4-7h; Tue, 16 Jan 2007 04:08:17 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1H6kIh-0004Vi-Ae; Tue, 16 Jan 2007 04:08:15 -0500
Received: from ihemail2.lucent.com ([135.245.0.35]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H6kIg-0004pR-1D; Tue, 16 Jan 2007 04:08:15 -0500
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id l0G974WK018780; Tue, 16 Jan 2007 03:07:04 -0600 (CST)
Received: from DEEXP02.DE.lucent.com ([135.248.187.66]) by ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 Jan 2007 03:07:03 -0600
Received: from DEEXC1U02.de.lucent.com ([135.248.187.30]) by DEEXP02.DE.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 16 Jan 2007 10:07:01 +0100
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Date: Tue, 16 Jan 2007 10:06:55 +0100
Message-ID: <D4D321F6118846429CD792F0B5AF471F08C679@DEEXC1U02.de.lucent.com>
In-Reply-To: <rt-3.5.HEAD-841-1168927353-1474.33594-7-0@icann.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [IANA #33594] draft-ietf-hubmib-rfc3636bis
Thread-index: Acc5M+HykAal8ZF/RLiHI/DhRQbKxAAGVcxg
From: "Wijnen, Bert (Bert)" <bwijnen@alcatel-lucent.com>
To: drafts-approval@icann.org
X-OriginalArrivalTime: 16 Jan 2007 09:07:01.0642 (UTC) FILETIME=[AF1B5EA0:01C7394D]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: edward.beili@actelis.com, Hub Mib <hubmib@ietf.org>, dromasca@avaya.com, iesg@ietf.org, hubmib-ads@tools.ietf.org, rfc-editor@rfc-editor.org
Subject: [Hubmib] RE: [IANA #33594] draft-ietf-hubmib-rfc3636bis
X-BeenThere: hubmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Ethernet Interfaces an Hub MIB WG <hubmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:hubmib@ietf.org>
List-Help: <mailto:hubmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hubmib>, <mailto:hubmib-request@ietf.org?subject=subscribe>
Errors-To: hubmib-bounces@ietf.org
Michelle (IANA),
Document draft-ietf-hubmib-rfc3636bis-05.txt suggests to put
the new IANA-maintained IANA-MAU-MIB module under
::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1
It is not a (fatal) technical flaw, but... sofar,
ALL IANA maintained MIB modules are located directly under
mib-2. I missed this during my reviews (as HUBMIB WG chair).
I have checked with the WG, and the WG has consensus to
make this MIB module location inline with all other
IANA maintained MIB modules and so we ask for
assignment as follows:
IANA-MAU-MIB
.. snip ..
ianaMauMIB MODULE-IDENTITY
.. snip ..
::= { mib-2 nnn } -- to be assigned by IANA
Pls note that this also means that the following comments
need to be changed (bottom of page 12, top of page 13) by
the RFC-Editor:
OLD:
-- the following OID is the MODULE-IDENTITY value
-- for this MIB module: { snmpDot3MauMgt 6 }
-- the following OID is the MODULE-IDENTITY value
-- for the IANA-MAU-MIB: { snmpDot3MauMgt 7 }
NEW:
-- the following OID is the MODULE-IDENTITY value
-- for this MIB module: { snmpDot3MauMgt 6 }
Bert Wijnen
HUBMIB WG chair
_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib
- [Hubmib] RE: [IANA #33594] draft-ietf-hubmib-rfc3… Wijnen, Bert (Bert)