attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:x = "urn:schemas-microsoft-com:office:excel" xmlns:p = "urn:schemas-microsoft-com:office:powerpoint" xmlns:a = "urn:schemas-microsoft-com:office:access" xmlns:dt = "uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s = "uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs = "urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b = "urn:schemas-microsoft-com:office:publisher" xmlns:ss = "urn:schemas-microsoft-com:office:spreadsheet" xmlns:c = "urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:oa = "urn:schemas-microsoft-com:office:activation" xmlns:html = "http://www.w3.org/TR/REC-html40" xmlns:q = "http://schemas.xmlsoap.org/soap/envelope/" XMLNS:D = "DAV:" xmlns:x2 = "http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois = "http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir = "http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds = "http://www.w3.org/2000/09/xmldsig#" xmlns:dsp = "http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc = "http://schemas.microsoft.com/data/udc" xmlns:xsd = "http://www.w3.org/2001/XMLSchema" xmlns:sps = "http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf = "http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf = "http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver = "http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels = "http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t = "http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m = "http://schemas.microsoft.com/exchange/services/2006/messages"><HEAD><TITLE>New draft MIB files on FTP.</TITLE> <META http-equiv=Content-Type content="text/html; charset=us-ascii"> <META content="MSHTML 6.00.2900.3199" name=GENERATOR> <STYLE>@font-face { font-family: Cambria Math; } @font-face { font-family: Calibri; } @font-face { font-family: MS Sans Serif; } @font-face { font-family: Tahoma; } @font-face { font-family: Verdana; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif" } A:link { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99 } A:visited { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } SPAN.MsoHyperlinkFollowed { COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99 } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman","serif"; mso-style-priority: 99; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto } SPAN.EmailStyle18 { COLOR: #1f497d; mso-style-type: personal-reply } .MsoChpDefault { FONT-SIZE: 10pt; mso-style-type: export-only } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US vLink=purple link=blue> <DIV dir=ltr align=left>Yes, we will fix the max-is-less-than-min warnings.  And the other two are surprising, because I think that's the standard idiom for such definitions.  To avoid the warnings, I may break it into separate declarations.  But, hey, who's complaining.  </DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>COMPILES WITHOUT ERROR!  Mark the day.  Break out the cheap champagne.  Sincere thanks to all.  We're not done yet, but we are getting closer to something we can ask the public to review.  </DIV> <DIV dir=ltr align=left> </DIV> <DIV dir=ltr align=left>rick</DIV> <DIV> </DIV> <DIV>  </DIV> <DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left> <HR tabIndex=-1> From: Raymond Rogers [mailto:ReRogers@SYMON.com] Sent: Monday, November 26, 2007 17:28 To: Landau, Richard; pdm@pwg.org Subject: RE: PDM> New draft MIB files on FTP. </DIV> <DIV></DIV> <DIV class=Section1> 0 Errors<o:p></o:p> 6 Warnings<o:p></o:p> <o:p> </o:p> The warnings we care about are at lines 1651 and 1627 of skeleton-final-mib.mib,  the max value of the range is missing.<o:p></o:p> <o:p> </o:p> The other 4 warnings are because I don’t have the pwg MIBs in my database and I get warnings like “Node "pwg" with OID "1.3.6.1.4.1.2699" created“.<o:p></o:p> <o:p> </o:p> <DIV> Regards, Raymond Rogers<o:p></o:p> Symon Communications, Inc.<o:p></o:p> (972)543-9586<o:p></o:p></DIV> <o:p> </o:p> <DIV> <DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0in; PADDING-BOTTOM: 0in; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none"> From: owner-pdm@pwg.org [mailto:owner-pdm@pwg.org] On Behalf Of Richard_Landau@Dell.com Sent: Monday, November 26, 2007 4:24 PM To: pdm@pwg.org Subject: PDM> New draft MIB files on FTP.<o:p></o:p></DIV></DIV> <o:p> </o:p> I updated, on  <A href="ftp://ftp.pwg.org/pub/pwg/pdm/objects/">ftp://ftp.pwg.org/pub/pwg/pdm/objects/</A> <o:p></o:p> skeleton-final.mib skeleton-final-mib.mib skeleton-final-tc.mib skeleton-final-names-too-long.txt <o:p></o:p> Please try again to compile the beast and let me know the results.  <o:p></o:p> rick ---------------------- Richard_Landau(at)dell(dot)com, Stds & System Mgt Architecture, CTO Office +1-512-728-9023, One Dell Way, RR5-3, MS RR5-09, Round Rock, TX 78682 <o:p></o:p></DIV> Notice of Confidentiality: This transmission contains information that may be confidential and that may also be privileged. Unless you are the intended recipient of the message (or authorized to receive it for the intended recipient) you may not copy, forward, or otherwise use it, or disclose its contents to anyone else. If you have received this transmission in error, please notify us immediately and delete it from your system. </BODY></HTML>