Re: Last Call: draft-ietf-rserpool-mib (Reliable ServerPooling: Management Information Base using SMIv2) toExperimental RFC)
"Bert Wijnen \(IETF\)" <[email protected]> Thu, 5 Feb 2009 12:41:38 +0100
| Newsgroups | gmane.ietf.rserpool |
|---|---|
| Organization | Consultant |
| Message-ID | <3A47D15143044BF49D3CE910EBFBE0DD@BertLaptop> |
This is a multi-part message in MIME format. --===============0108628080== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0D01_01C9878F.1681D3D0" This is a multi-part message in MIME format. ------=_NextPart_000_0D01_01C9878F.1681D3D0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Thanks Thomas. The new MIB module now compiles clean. I am happy with this version of the MIB module. Bert ----- Original Message -----=20 From: Thomas Dreibholz=20 To: Bert Wijnen (IETF)=20 Cc: [email protected] ; MIB Doctors (E-mail) ; David B Harrington=20 Sent: Thursday, February 05, 2009 12:37 PM Subject: Re: [Rserpool] Last Call: draft-ietf-rserpool-mib (Reliable = ServerPooling: Management Information Base using SMIv2) toExperimental = RFC) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear all, attached to this mail, you find again the latest version of the = RSerPool MIB=20 module. See my comments inline. On Donnerstag 05 Februar 2009, Bert Wijnen (IETF) wrote: > Thanks Thomas for the quick turn-arounds. This helps a lot with > context-switching. In other words, this way I can quickly re-check = (as > opposed to some MIB reviews I have done where it takes montsh for a = new > revision to show up). > > The SMICng check show two naming issues left: > > C:\bw\smicng\work>smicng rserpool.inc > W: f(rserpool.mi2), (761,1) Sequence "RserpoolPoolElementEntry" = and Row > "rserpoolPEEntry" should have related names W: f(rserpool.mi2), = (1074,1) > Sequence "RserpoolPoolUserEntry" and Row "rserpoolPUEntry" should = have > related names > > *** 0 errors and 2 warnings in parsing There warnings should be fixed now. Bert, please could you re-run the = SMICng=20 program? > Further, you claim: > > The normal setup (according to rfc4181) would be something like: > > > > rserpoolMIBObjects OBJECT-IDENTIFIER ::=3D { rserpoolMIB = 1 } > > rserpoolMIBConformance OBJECT IDENTIFIER ::=3D { rserpoolMIB 2 } > > > > rserpoolENRPServers OBJECT IDENTIFIER ::=3D { = rserpoolMIBObjects 1 } > > rserpoolPoolElements OBJECT IDENTIFIER ::=3D { = rserpoolMIBObjects 2 } > > rserpoolPoolUsers OBJECT IDENTIFIER ::=3D { = rserpoolMIBObjects 3 > > } > > > > Your new MIB module has no indertation at all. > > Not a fatal flaw, but does not help in readability. Sorry, I had attached a slightly older version (without this fix) in = my last=20 mail. Now, it should be fixed. Best regards - --=20 = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Dr. Thomas Dreibholz University of Duisburg-Essen, Room ES210 Inst. for Experimental Mathematics Ellernstra=DFe 29 Computer Networking Technology Group D-45326 Essen/Germany - = ----------------------------------------------------------------------- E-Mail: [email protected] Homepage: http://www.iem.uni-due.de/~dreibh = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFJis+T32BbsHYPLWURApfIAKDci0+xEttdSCB9F0AodGzlnDqeDACg006U aFwuKQxu0STd+7t04DdzbbI=3D =3DUeB6 -----END PGP SIGNATURE----- ------=_NextPart_000_0D01_01C9878F.1681D3D0 Content-Type: text/html; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=3DContent-Type content=3D"text/html; = charset=3Diso-8859-15"> <META content=3D"MSHTML 6.00.6001.18183" name=3DGENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=3D#ffffff> <DIV><FONT size=3D2>Thanks Thomas.</FONT></DIV> <DIV><FONT size=3D2>The new MIB module now compiles clean.</FONT></DIV> <DIV><FONT size=3D2>I am happy with this version of the MIB = module.</FONT></DIV> <DIV><FONT size=3D2></FONT> </DIV> <DIV><FONT size=3D2>Bert</FONT></DIV> <BLOCKQUOTE=20 style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"> <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV> <DIV=20 style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: = black"><B>From:</B>=20 <A [email protected] = href=3D"mailto:[email protected]">Thomas=20 Dreibholz</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A = [email protected]=20 href=3D"mailto:[email protected]">Bert Wijnen (IETF)</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>Cc:</B> <A = [email protected]=20 href=3D"mailto:[email protected]">[email protected]</A> ; <A=20 [email protected] href=3D"mailto:[email protected]">MIB = Doctors=20 (E-mail)</A> ; <A [email protected]=20 href=3D"mailto:[email protected]">David B Harrington</A> </DIV> <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, February 05, = 2009 12:37=20 PM</DIV> <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [Rserpool] Last = Call:=20 draft-ietf-rserpool-mib (Reliable ServerPooling: Management = Information Base=20 using SMIv2) toExperimental RFC)</DIV> <DIV><BR></DIV>-----BEGIN PGP SIGNED MESSAGE-----<BR>Hash: = SHA1<BR><BR>Dear=20 all,<BR><BR>attached to this mail, you find again the latest version = of the=20 RSerPool MIB <BR>module.<BR><BR>See my comments inline.<BR><BR><BR>On=20 Donnerstag 05 Februar 2009, Bert Wijnen (IETF) wrote:<BR>> Thanks = Thomas=20 for the quick turn-arounds. This helps a lot with<BR>> = context-switching.=20 In other words, this way I can quickly re-check (as<BR>> opposed to = some=20 MIB reviews I have done where it takes montsh for a new<BR>> = revision to=20 show up).<BR>><BR>> The SMICng check show two naming issues=20 left:<BR>><BR>> C:\bw\smicng\work>smicng=20 rserpool.inc<BR>> W: f(rserpool.mi2), (761,1) Sequence=20 "RserpoolPoolElementEntry" and Row<BR>> "rserpoolPEEntry" should = have=20 related names W: f(rserpool.mi2), (1074,1)<BR>> Sequence=20 "RserpoolPoolUserEntry" and Row "rserpoolPUEntry" should have<BR>> = related=20 names<BR>><BR>> *** 0 errors and 2 warnings in=20 parsing<BR><BR>There warnings should be fixed now. Bert, please could = you=20 re-run the SMICng <BR>program?<BR><BR><BR>> Further, you = claim:<BR>>=20 > The normal setup (according to rfc4181) would be something = like:<BR>>=20 ><BR>> >=20 = rserpoolMIBObjects = OBJECT-IDENTIFIER ::=3D { rserpoolMIB 1 }<BR>> >=20 rserpoolMIBConformance OBJECT IDENTIFIER ::=3D { rserpoolMIB 2 = }<BR>>=20 ><BR>> > = rserpoolENRPServers =20 OBJECT IDENTIFIER ::=3D { rserpoolMIBObjects 1 }<BR>> >=20 rserpoolPoolElements OBJECT IDENTIFIER = ::=3D {=20 rserpoolMIBObjects 2 }<BR>> >=20 = rserpoolPoolUsers &n= bsp;=20 OBJECT IDENTIFIER ::=3D { rserpoolMIBObjects 3<BR>> > }<BR>>=20 ><BR>> > Your new MIB module has no indertation at = all.<BR>> >=20 Not a fatal flaw, but does not help in readability.<BR><BR>Sorry, I = had=20 attached a slightly older version (without this fix) in my last = <BR>mail. Now,=20 it should be fixed.<BR><BR><BR>Best regards<BR>- --=20 = <BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>= Dr.=20 Thomas Dreibholz<BR><BR> University of=20 = Duisburg-Essen, &nbs= p; =20 Room ES210<BR> Inst. for Experimental=20 = Mathematics &n= bsp; =20 Ellernstra=DFe 29<BR> Computer Networking Technology=20 = Group =20 D-45326 Essen/Germany<BR>-=20 = -----------------------------------------------------------------------<B= R> E-Mail: =20 <A=20 = href=3D"mailto:[email protected]">[email protected]</A><BR> = Homepage: =20 <A=20 = href=3D"http://www.iem.uni-due.de/~dreibh">http://www.iem.uni-due.de/~dre= ibh</A><BR>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= <BR>-----BEGIN=20 PGP SIGNATURE-----<BR>Version: GnuPG v1.4.6=20 = (GNU/Linux)<BR><BR>iD8DBQFJis+T32BbsHYPLWURApfIAKDci0+xEttdSCB9F0AodGzlnD= qeDACg006U<BR>aFwuKQxu0STd+7t04DdzbbI=3D<BR>=3DUeB6<BR>-----END=20 PGP SIGNATURE-----<BR></BLOCKQUOTE></BODY></HTML> ------=_NextPart_000_0D01_01C9878F.1681D3D0-- --===============0108628080== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ rserpool mailing list [email protected] https://www.ietf.org/mailman/listinfo/rserpool --===============0108628080==--