RE: [Hubmib] draft-ietf-hubmib-efm-epon-mib-03.txt almost ready to go

"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Mon, 27 June 2005 06:28 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmn6a-0007zM-Oc; Mon, 27 Jun 2005 02:28:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dmn6Y-0007zH-C3 for hubmib@megatron.ietf.org; Mon, 27 Jun 2005 02:28:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA14247 for <hubmib@ietf.org>; Mon, 27 Jun 2005 02:28:24 -0400 (EDT)
Received: from tierw.net.avaya.com ([198.152.13.100]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DmnVe-00052A-9G for hubmib@ietf.org; Mon, 27 Jun 2005 02:54:22 -0400
Received: from tierw.net.avaya.com (localhost [127.0.0.1]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j5R6GJAK022468 for <hubmib@ietf.org>; Mon, 27 Jun 2005 02:16:19 -0400 (EDT)
Received: from IS0004AVEXU1.global.avaya.com (h135-64-105-51.avaya.com [135.64.105.51]) by tierw.net.avaya.com (Switch-3.1.2/Switch-3.1.0) with ESMTP id j5R6GHAK022445 for <hubmib@ietf.org>; Mon, 27 Jun 2005 02:16:17 -0400 (EDT)
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.0.6603.0
Subject: RE: [Hubmib] draft-ietf-hubmib-efm-epon-mib-03.txt almost ready to go
Date: Mon, 27 Jun 2005 09:28:17 +0300
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F08BF9AFE@is0004avexu1.global.avaya.com>
Thread-Topic: [Hubmib] draft-ietf-hubmib-efm-epon-mib-03.txt almost ready to go
Thread-Index: AcV4Nk3tfoATl2K0QuOJQreW7OdBcwCqcImw
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: "C. M. Heard" <heard@pobox.com>, Hub MIB <hubmib@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5
Content-Transfer-Encoding: quoted-printable
Cc:
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>
Sender: hubmib-bounces@ietf.org
Errors-To: hubmib-bounces@ietf.org

Thanks for the advice, Mike. 

Taking this into account, I believe that the EFM MIB and the EPON MIB
are OK to be shipped to the IESG, and I will fill in the necessary
recommendations. The boilerplate and formatting problems are tolerable
in my opinion, taking into account that the documents were issued before
May 2005 when the latest IPR RFCs were issued. 

The EFM Cu and new MAU MIB are still in works and will need another
round of editing and WGLC.

Dan



> -----Original Message-----
> From: hubmib-bounces@ietf.org 
> [mailto:hubmib-bounces@ietf.org] On Behalf Of C. M. Heard
> Sent: Thursday, June 23, 2005 11:56 PM
> To: Hub MIB
> Subject: Re: [Hubmib] draft-ietf-hubmib-efm-epon-mib-03.txt 
> almost ready to go
> 
> On Thu, 23 Jun 2005, Dan Romascanu wrote:
> >    draft-ietf-hubmib-efm-epon-mib-03.txt is almost ready to 
> go. There are
> >    several objects with a length exceeding 32 characters 
> that lead to
> >    smilit complaining:
> 
> According to section 4.2 of the MIB review guidelines (see
> http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-
> guidelines-04.txt)
> this is not something that needs to be corrected.
> 
> >    smilint -m -s -e -m -s -l 6 -I namelength-32 epon-mib-03.txt
> __________________________________^
> 
> That should be a lower-case 'i' (in which case the directive 
> will mean "ignore names over 32 characters").  When I do that 
> (and put in fake mib-2 numbers in place of XXX) I get this 
> from the smilint e-mail robot:
> 
> smilint -m -s -e -l 6 -i namelength-32 EPON-DEVICE-MIB
> 
> no errors found.
> 
> smilint -m -s -e -l 6 -i namelength-32 DOT3-EFM-EPON-MIB
> 
> no errors found.
> 
> So, I don't think there are any purely SMI issues to worry about.
> For sure it's not necessary to shorten the names. 
> 
> >    Also, idnits complains about the boilerplate not being 
> update - no
> >    wonder taking into account that RFC 3978 and 3979 started to be
> >    applied after the Internet-Draft was published:
> >    
> ... details snipped ...
> > 
> > I would kindly request the document editor to publish an 
> updated draft 
> > to fix t hese editorial issues before I submit the I-D to 
> the IESG. I 
> > do not believe tha t these changes would require a new WGLC, unless 
> > somebody feels strongly otherwise.
> 
> I agree with the above.
> 
> Mike Heard
> 
> 
> _______________________________________________
> Hubmib mailing list
> Hubmib@ietf.org
> https://www1.ietf.org/mailman/listinfo/hubmib
> 

_______________________________________________
Hubmib mailing list
Hubmib@ietf.org
https://www1.ietf.org/mailman/listinfo/hubmib