RE: Re: PLS review BEFORE 10 Jan 2007 - IANA-MAU-MIB under mib-2 (rfc3636bis)

The only comment I have seen is that Mike feels a bit
uneasy about the change, because of a risk of messing up.
(not that I had stated that silence would be interpreted
as no objection).=20

The good news is that Mike also included additional instructions
to make sure we do not mess up. Thanks Mike.

SO I interpret this as consensus to request IANA for the change.
So I will tell IANA that we want the change as follows:

Document draft-ietf-hubmib-rfc3636bis-05.txt suggests to put=20
the new IANA-maintained IANA-MAU-MIB module under

    ::=3D { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1
=20
It is not a (fatal) technical flaw, but...
sofar, ALL IANA maintained MIB modules are located directly under=20
mib-2. I missed this during my reviews (as HUBMIB WG chair).
=20
The WG has consensus to make this MIB module location inline=20
with all other IANA maintained MIB modules and so we ask for=20
assignment as  follows:

   IANA-MAU-MIB
   .. snip ..
   ianaMauMIB MODULE-IDENTITY
   .. snip ..
   ::=3D { mib-2 nnn } -- to be assigned by IANA

Pls note that this also means that these 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 }
=20
    -- the following OID is the MODULE-IDENTITY value
    -- for the IANA-MAU-MIB:  { snmpDot3MauMgt 7 }
=20
NEW:
    -- the following OID is the MODULE-IDENTITY value
    -- for this MIB module:   { snmpDot3MauMgt 6 }
=20

Bert Wijnen
HUBMIB WG chair


> -----Original Message-----
> From: C. M. Heard [mailto:[email protected]]=20
> Sent: woensdag 3 januari 2007 16:18
> To: Hub Mib
> Subject: [Hubmib] Re: PLS review BEFORE 10 Jan 2007 -=20
> IANA-MAU-MIB under mib-2 (rfc3636bis)
>=20
> On Wed, 3 Jan 2007 12:23:15 +0100 Bert Wijnen wrote:
> > draft-ietf-hubmib-rfc3636bis-05.txt is in the RFC-editor=20
> Queue and is=20
> > in a stage where IANA wants to make the final registration for the=20
> > IANA-MAU-MIB.
> > During that step, we found that the document
> >    draft-ietf-hubmib-rfc3636bis-05.txt
> > suggest to put this new IANA-maintained MIB module under
> >    ::=3D { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1
> >=20
> > It is not a (fatal) technical flaw, but...
> > sofar, ALL IANA maintained MIB modules are located directly under=20
> > mib-2. I missed this during my reviews.
> >=20
> > The proposal now is to make this MIB module location inline=20
> with all=20
> > other IANA maintained MIB modules and so to ask for assignment as=20
> > follows:
> >
> >   IANA-MAU-MIB
> >   .. snip ..
> >   ianaMauMIB MODULE-IDENTITY
> >    .. snip ..
> >    ::=3D { mib-2 nnn } -- to be assigned by IANA
> >=20
> > Pls speak up BEFORE 10 Jan 2007 if you see an issue with this
> > (late) change.
> > Silence will (this time) be interpreted as no-objection.
>=20
> Here is some perspective from the MIB Doctor reviewer.
>=20
> Although I recommended during my early reviews to put the=20
> MODULE-IDENTITY value for the IANA-MAU-MIB under mib-2, I=20
> also noted that it is not a technical flaw to have it set to=20
> { mib-2 snmpDot3MauMgt(26) 7 }.  So I let it pass as long as=20
> the assignment was noted with the appropriate
> ASN.1 comments in the MAU-MIB, which "owns" the { mib-2=20
> snmpDot3MauMgt(26) } OID branch, which was done.
>=20
> I am frankly uneasy about making such last-minute changes if=20
> they are not necessary to correct technical flaws, as they=20
> tend to introduce errors or inconsistencies elsewhere.
> If the WG does agree to make the change to the IANA-MAU-MIB=20
> MODULE-IDENTITY assignment, then the following change also=20
> needs to be made to the ASN.1 comments in the MAU-MIB:
>=20
> OLD:
>     -- the following OID is the MODULE-IDENTITY value
>     -- for this MIB module:   { snmpDot3MauMgt 6 }
>=20
>     -- the following OID is the MODULE-IDENTITY value
>     -- for the IANA-MAU-MIB:  { snmpDot3MauMgt 7 }
>=20
> NEW:
>     -- the following OID is the MODULE-IDENTITY value
>     -- for this MIB module:   { snmpDot3MauMgt 6 }
>=20
> The text to be removed is at the bottom of p. 12 and the top=20
> of p. 13 of draft-ietf-hubmib-rfc3636bis-05.txt.
>=20
> Mike
>=20
> _______________________________________________
> Hubmib mailing list
> [email protected]
> https://www1.ietf.org/mailman/listinfo/hubmib
>=20