Re: Volunteers needed for IPCDN wg: prioritized list of IDs for MIBdoctor review

["C. M. Heard" <heard@pobox.com>]

Howdy,

I volunteered for

ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-01.txt

but I think Bert still needs help for the other one.

Mike

On Tue, 22 Jul 2003, Wijnen, Bert (Bert) wrote:
> I need help. I have two of these that I have done
> detailed review in the past (marked [bw] below).
> For the others (i.e. the first 2) I would appreciate volunteers.
> 
> Thanks,
> Bert 
> 
> -----Original Message-----
> From: Wijnen, Bert (Bert) 
> Sent: dinsdag 22 juli 2003 0:56
> To: Jean-Francois Mule; Bert Wijnen
> Cc: Richard Woundy; Margaret Wasserman; Thomas Narten
> Subject: RE: IPCDN wg: prioritized list of IDs for MIB doctor review
> 
> > 1. PacketCable/IPCablecom MTA MIB 
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-mtamib-01.txt
> > 
> Bad chars at 2053
> Bad chars at 2056
> -: 2 lines containing non-US-ASCII characters
> 
>   W: f(ipcdnPktcMta.mi2), (1347,4) NOTIFICATION-GROUP 
>      "pktcMtaNotificationGroup" is not used in a
>      MODULE-COMPLIANCE in current module
> 
> You IMPORT from IF-MIB (RFC2863) and SNMP-FRAMEWORK-MIB (RFC3411)
> and SNMPv2-MIB (RFC3418). So those must be listed as normative
> references
> 
> But more review needed
> 
> > 2. PacketCable/IPCablecom NCS Signaling MIB
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-pktc-signaling-01.txt
> > 
> Bad chars at 1947
> Bad chars at 2927
> Bad chars at 2930
> -: 3 lines containing non-US-ASCII characters
> 
> Still to do even basic checking
> 
> More review needed
> 
> > 3. Subscriber Mgmt MIB
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-subscriber-mib-11.txt
> [Bert has this one under review]
> >    addresses comments received during your review. 
> >    I sent 1 minor comment was sent yesterday on the ipcdn list.
> > 
> need to re-check
> 
> > 4. BPI+ MIB
> > ftp://ftp.ietf.org/internet-drafts/draft-ietf-ipcdn-bpiplus-mib-10.txt
> 
> [Bert Has this one under review]
> 
> >    addresses comments from your review. I attach the detailed 
> > responses to your comments.
> >    2 open issues that do not prevent the request for additional mib
> > doctor review imo:
> >           a) Explain why for some objects enum values start with 0
> >              (docsBpi2CmtsAuthCmBpiVersion, docsBpi2CmtsTEKSAType)
> >           b) Split compliance statement into 2, 1 for CM, 1 for CMTS
> >    => co-authors expect to release an updated draft by the 
> > end of August so you may want to hold on to this one until then
> > depending on your timeline.
> > 
> Gave you detailed answers on your response to my comments.
> I see that more of the above have (minor) issues... like InetAddres
> DESCRIPTION clause, normative references for all IMPORTed materials
> More tomorrow
> Bert
> > Thank you,
> > Jean-Francois.
> > Ps: there are 4 other IDs we hope to ask mib doctor review for in the
> > early September timeframe.
> > 
>