attachment-0001

<!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:st1 = "urn:schemas-microsoft-com:office:smarttags"><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> <META content="MSHTML 6.00.2800.1491" name=GENERATOR><o:SmartTagType name="PostalCode" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType name="State" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType name="City" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType name="Street" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType name="address" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType name="place" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType> <STYLE>  </STYLE> </HEAD> <BODY lang=EN-US vLink=purple link=blue> <DIV>Hi Stuart</DIV> <DIV> </DIV> <DIV>I _don't_ want to leave the hole.  As Mike Fenelon just said, it would be confusing.</DIV> <DIV> </DIV> <DIV>The ppmPortTable you listed indices for below is one table with six entries.</DIV> <DIV> </DIV> <DIV>The need for ppmGeneralNumberOfPorts is to avoid 'walking off the end of the table'</DIV> <DIV>when a client browses the 'ppmPortTable' directly (without previously reading every</DIV> <DIV>entry in 'ppmPrinterTable' which gives the interior bounds).</DIV> <DIV> </DIV> <DIV>It's just best practice to have scalar objects that avoid 'walking off the end' (which</DIV> <DIV>is often incorrectly reported to applications as an SNMP communications error).</DIV> <DIV> </DIV> <DIV>BOTH of these port counters are needed - because it's also important to support</DIV> <DIV>browsing the printer-specific list of ports.</DIV> <DIV> </DIV> <DIV>Cheers,</DIV> <DIV>- Ira</DIV> <DIV> </DIV> Ira McDonald (Musician / Software Architect) Blue Roof Music / High North Inc PO Box 221  Grand Marais, MI  49839 phone: +1-906-494-2434 email: imcdonald@sharplabs.com <BLOCKQUOTE dir=ltr style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Stuart Rowley [mailto:Stuart.Rowley@ktd-kyocera.com] Sent: Thursday, July 28, 2005 11:51 AM To: McDonald, Ira Cc: pmp@pwg.org; thrasher@lexmark.com Subject: RE: PMP> [delete ppmPrinterEnabled] Restructured Port MIB (18 Jul y 2005) </DIV> <DIV class=Section1> Ira,<o:p></o:p> <o:p> </o:p> I am clear on the proposal now and I still don't see the need to maintain the hole at this stage.<o:p></o:p> <o:p> </o:p> Can you clarify this for me...<o:p></o:p> <o:p> </o:p> If I have 2 attached printers each with the same 3 ports, they would be indexed by the Printer and then the Port:<o:p></o:p> .1.1<o:p></o:p> .1.2<o:p></o:p> .1.3<o:p></o:p> .2.1<o:p></o:p> .2.2<o:p></o:p> .2.3<o:p></o:p> <o:p> </o:p> (I don't know if this is considered one table with 6 entries or 2 tables with 3 entries each.)<o:p></o:p> <o:p> </o:p> So I don't understand the need for both<o:p></o:p> ppmGeneralNumberOfPorts<o:p></o:p> ppmPrinterNumberOfPorts<o:p></o:p> <o:p> </o:p> If I know the Printer index and number of printer ports, isn't this enough?<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Stuart<o:p></o:p> <DIV> <DIV class=MsoNormal style="TEXT-ALIGN: center" align=center> <HR tabIndex=-1 align=center width="100%" SIZE=2> </DIV> From: thrasher@lexmark.com [mailto:thrasher@lexmark.com] Sent: Thursday, July 28, 2005 8:24 AM To: Stuart Rowley Cc: pmp@pwg.org Subject: RE: PMP> [delete ppmPrinterEnabled] Restructured Port MIB (18 Jul y 2005)<o:p></o:p></DIV> <o:p> </o:p> Stuart, Sorry about the error in my request.  I was talking about ppmPrinterenabled, not Portenabled. Jerry <o:p></o:p> <TABLE class=MsoNormalTable style="WIDTH: 100%" cellPadding=0 width="100%" border=0> <TBODY> <TR> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top> <o:p> </o:p></TD> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top> Stuart Rowley <Stuart.Rowley@ktd-kyocera.com> Sent by: pmp-owner@pwg.org <o:p></o:p> 07/28/2005 11:19 AM <o:p></o:p></TD> <TD style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt" vAlign=top>                 To:        "'pmp@pwg.org'" <pmp@pwg.org>         cc:        "McDonald, Ira" <imcdonald@sharplabs.com>         Subject:        RE: PMP> [delete ppmPrinterEnabled] Restructured Port MIB (18 Jul         y 2005)<o:p></o:p></TD></TR></TBODY></TABLE> <TT>Hi Ira,</TT> <TT>I'm not clear on the proposal.</TT> <TT>Your email said, "Let's delete ppmPrinterEnabled,..."</TT> <TT>Then Jerry's reply said, "...where ppmPortEnabled "used" to be..."</TT> <TT>So is the proposal to keep ppmPrinterEnabled and remove ppmPortEnabled?</TT> <TT>I don't see the need to leave a hole for the removed object at this stage of</TT> <TT>development.</TT> <TT>Thanks,</TT> <TT>Stuart</TT> <TT>Stuart Rowley, Network Product Mgr.</TT> <TT>stuart.rowley@ktd-kyocera.com      925 849-3306     925 849-3399 (fax)</TT> <TT>Kyocera Technology Development Inc.</TT> <st1:Street w:st="on"><st1:address w:st="on"><TT>1855 Gateway Blvd. Suite 400</TT></st1:address></st1:Street> <st1:place w:st="on"><st1:City w:st="on"><TT>Concord</TT></st1:City><TT>, <st1:State w:st="on">CA</st1:State> <st1:PostalCode w:st="on">94520</st1:PostalCode></TT></st1:place> <TT>_____</TT> <TT>From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org] On Behalf Of McDonald,</TT> <TT>Ira</TT> <TT>Sent: Thursday, July 28, 2005 7:59 AM</TT> <TT>To: 'thrasher@lexmark.com'; McDonald, Ira</TT> <TT>Cc: 'pmp@pwg.org'</TT> <TT>Subject: RE: PMP> [delete ppmPrinterEnabled] Restructured Port MIB (18 Jul y</TT> <TT>2005)</TT> <TT>Hi Jerry,</TT> <TT>There's no such thing as a reserved no-access object, but I'd be happy to</TT> <TT>leave</TT> <TT>the hole (so that the OIDs don't change for any other columnar objects).</TT> <TT>Would</TT> <TT>you prefer that?</TT> <TT>Note that ALL of the columnar objects were cleaned up and reordered (and</TT> <TT>renumbered) in this latest revision, so it would be hard for there to be too</TT> <TT>many</TT> <TT>implementations of the new OIDs already.</TT> <TT>Others - shall I leave the hole and leave the other new OID assignments</TT> <TT>stable?</TT> <TT>Cheers,</TT> <TT>- Ira</TT> <TT>Ira McDonald (Musician / Software Architect)</TT> <TT>Blue Roof Music / High North Inc</TT> <st1:address w:st="on"><st1:Street w:st="on"><TT>PO Box</TT></st1:Street><TT> 221</TT></st1:address><TT>  Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>, <st1:State w:st="on">MI</st1:State>  <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place></TT> <TT>phone: +1-906-494-2434</TT> <TT>email: imcdonald@sharplabs.com</TT> <TT>-----Original Message-----</TT> <TT>From: thrasher@lexmark.com [mailto:thrasher@lexmark.com]</TT> <TT>Sent: Thursday, July 28, 2005 10:33 AM</TT> <TT>To: McDonald, Ira</TT> <TT>Subject: RE: PMP> [delete ppmPrinterEnabled] Restructured Port MIB (18 Jul y</TT> <TT>2005)</TT> <TT>Ira,</TT> <TT>Are you just planning on creating a reserved no-access object where</TT> <TT>ppmPortEnabled "used" to be, or are</TT> <TT>you going to delete the entry and shift everything else in the table up.??</TT> <TT>Jerry</TT> <TT>"McDonald, Ira" <imcdonald@sharplabs.com></TT> <TT>07/23/2005 01:56 PM</TT> <TT>To:        "McDonald, Ira" <imcdonald@sharplabs.com>,</TT> <TT>"'thrasher@lexmark.com'" <thrasher@lexmark.com></TT> <TT>cc:        "'pmp@pwg.org'" <pmp@pwg.org>,</TT> <TT>"'Ron.Bergman@rpsa.ricoh.com'" <Ron.Bergman@rpsa.ricoh.com></TT> <TT>Subject:        RE: PMP> [delete ppmPrinterEnabled] Restructured</TT> <TT>Port MIB (18 Jul        y 2005)</TT> <TT>Hi,</TT> <TT>Let's delete ppmPrinterEnabled, because the 'false' is redundant</TT> <TT>with ppmPortEnabled of 'false' for all supported ports.  And</TT> <TT>because otherwise, we must say "ignore ppmPortEnabled of 'true'</TT> <TT>for installation if ppmPrinterEnabled is 'false'".  Which leads</TT> <TT>me to agree that we should delete ppmPrinterEnabled.</TT> <TT>When a Printer is permanently removed from an ENA interface,</TT> <TT>the whole ppmPrinterTable row and all subordinate rows in</TT> <TT>ppmPortTable can just be deleted.</TT> <TT>For 'ppmPortProtocolType' using 'PrtChannelTypeTC', we're working</TT> <TT>to get 'unknown(2)' registered quickly with IANA, so that we can</TT> <TT>do the 'right thing' that Bert Wijnen pointed out.</TT> <TT>Cheers,</TT> <TT>- Ira</TT> <TT>Ira McDonald (Musician / Software Architect)</TT> <TT>Blue Roof Music / High North Inc</TT> <st1:address w:st="on"><st1:Street w:st="on"><TT>PO Box</TT></st1:Street><TT> 221</TT></st1:address><TT>  Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>, <st1:State w:st="on">MI</st1:State>  <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place></TT> <TT>phone: +1-906-494-2434</TT> <TT>email: imcdonald@sharplabs.com</TT> <TT>-----Original Message-----</TT> <TT>From: McDonald, Ira</TT> <TT>Sent: Friday, July 22, 2005 1:37 PM</TT> <TT>To: 'thrasher@lexmark.com'; McDonald, Ira</TT> <TT>Cc: pmp@pwg.org; Ron.Bergman@rpsa.ricoh.com</TT> <TT>Subject: RE: PMP> Restructured Port MIB (18 July 2005)</TT> <TT>Hi Jerry,</TT> <TT>I agree that feedback from the clients (Microsoft and Apple) on how they'd</TT> <TT>like this to work would be helpful.</TT> <TT>Remember, that a value of 'ppmPrinterIndex' must NEVER be reassigned</TT> <TT>to a different instance of a Printer at a later date.  While the MIB may</TT> <TT>grow and shrink, the base 'ppmPrinterIndex' should be immutably</TT> <TT>associated with exactly one specific instance of a Printer.  This is both</TT> <TT>correct MIB practice and required by the object definition in the current</TT> <TT>MIB draft.</TT> <TT>Cheers,</TT> <TT>- Ira</TT> <TT>Ira McDonald (Musician / Software Architect)</TT> <TT>Blue Roof Music / High North Inc</TT> <st1:address w:st="on"><st1:Street w:st="on"><TT>PO Box</TT></st1:Street><TT> 221</TT></st1:address><TT>  Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>, <st1:State w:st="on">MI</st1:State>  <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place></TT> <TT>phone: +1-906-494-2434</TT> <TT>email: imcdonald@sharplabs.com</TT> <TT>-----Original Message-----</TT> <TT>From: thrasher@lexmark.com [mailto:thrasher@lexmark.com]</TT> <TT>Sent: Friday, July 22, 2005 1:28 PM</TT> <TT>To: McDonald, Ira</TT> <TT>Cc: pmp@pwg.org; Ron.Bergman@rpsa.ricoh.com</TT> <TT>Subject: RE: PMP> Restructured Port MIB (18 July 2005)</TT> <TT>I would think that the usefullness of the ppmPrinterEnabled for an</TT> <TT>ENA would only be for the "transcient" case of the plugging/unplugging</TT> <TT>of the related printer.  However at some point (in the case that the printer</TT> <TT>stays unplugged "permanently") the printer entry and associated protocol</TT> <TT>tables would be removed such that the the MIB could grow and shrink</TT> <TT>over time.....</TT> <TT>For example, an ENA with a USB host interface that supports up to</TT> <TT>128 attached printers, In my opinion, shouldn't need to have 128 printer</TT> <TT>entries</TT> <TT>in the MIB tables from first power on......only the entries that have</TT> <TT>detected (valid 1284ID)</TT> <TT>printers etc. attached.....otherwise you'd end up in most cases with 127</TT> <TT>default printer entries</TT> <TT>with associated port tables that don't actually go anywhere.</TT> <TT>Of course this behaviour is different from the current TCPMON.ini file</TT> <TT>which has static entries.......</TT> <TT>I think maybe the clients should give guidance on how they want it to work.</TT> <TT>Jerry Thrasher</TT> <TT>"McDonald, Ira" <imcdonald@sharplabs.com></TT> <TT>Sent by: pmp-owner@pwg.org</TT> <TT>07/22/2005 12:13 PM</TT> <TT>To:        "'Bergman, Ron'" <Ron.Bergman@rpsa.ricoh.com>, "McDonald,</TT> <TT>Ira" <imcdonald@sharplabs.com>, "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,</TT> <TT>pmp@pwg.org</TT> <TT>cc:</TT> <TT>Subject:        RE: PMP> Restructured Port MIB (18 July 2005)</TT> <TT>Hi Ron,</TT> <TT>If the Printer entry is deleted when an ENA interface</TT> <TT>is disconnected, then all the subordinate Port entries</TT> <TT>MUST be deleted too (because they are indexed by the</TT> <TT>object ppmPrinterIndex).  This is ugly if the local</TT> <TT>printer is promptly plugged _back_ into the interface.</TT> <TT>If the Printer entry is left in place but _not_ clearly</TT> <TT>marked 'disabled', then ppmPrinterIEEE1284DeviceId,</TT> <TT>ppmPrinterHrDeviceIndex and all the other Printer</TT> <TT>columnar objects must be reset (to default values).</TT> <TT>That's why the ppmPrinterEnabled object should be kept.</TT> <TT>The WG concensus was strong that ppmPortEnabled was</TT> <TT>required to keep the port list static (fixed number</TT> <TT>of ports for an interface).  Therefore, I added the</TT> <TT>ppmPrinterEnabled object.</TT> <TT>If others want ppmPrinterEnabled removed, would they</TT> <TT>please speak up soon?</TT> <TT>Cheers,</TT> <TT>- Ira</TT> <TT>PS - Remember that this MIB is supposed to work for</TT> <TT>Network Spoolers too, where the concept of 'the printer</TT> <TT>is removed' is fuzzy.  The 'printer' is just some</TT> <TT>configured downstream network printer that may well</TT> <TT>be administratively disabled _without_ removing the</TT> <TT>configuration at the Network Spooler.</TT> <TT>Ira McDonald (Musician / Software Architect)</TT> <TT>Blue Roof Music / High North Inc</TT> <st1:address w:st="on"><st1:Street w:st="on"><TT>PO Box</TT></st1:Street><TT> 221</TT></st1:address><TT>  Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>, <st1:State w:st="on">MI</st1:State>  <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place></TT> <TT>phone: +1-906-494-2434</TT> <TT>email: imcdonald@sharplabs.com</TT> <TT>> -----Original Message-----</TT> <TT>> From: Bergman, Ron [mailto:Ron.Bergman@rpsa.ricoh.com]</TT> <TT>> Sent: Thursday, July 21, 2005 8:24 PM</TT> <TT>> To: McDonald, Ira; Wijnen, Bert (Bert); pmp@pwg.org</TT> <TT>> Subject: RE: PMP> Restructured Port MIB (18 July 2005)</TT> <TT>></TT> <TT>></TT> <TT>> Ira,</TT> <TT>></TT> <TT>> Base on my experience with ENAs, they do not provide a feature to</TT> <TT>> disable an output port unless the printer is removed.  Normally,</TT> <TT>> this is to replace a worn-out unit or upgrade a printer.</TT> <TT>> In this case the old printer is gone forever.  So how does your</TT> <TT>> "STATIC entries" handle this situation?</TT> <TT>></TT> <TT>>         Ron</TT> <TT>></TT> <TT>> -----Original Message-----</TT> <TT>> From: McDonald, Ira [mailto:imcdonald@sharplabs.com]</TT> <TT>> Sent: Wednesday, July 20, 2005 8:38 AM</TT> <TT>> To: Bergman, Ron; McDonald, Ira; Wijnen, Bert (Bert); pmp@pwg.org</TT> <TT>> Subject: RE: PMP> Restructured Port MIB (18 July 2005)</TT> <TT>></TT> <TT>></TT> <TT>> Hi Ron,</TT> <TT>></TT> <TT>> Based on previous IPP experience, it will take MONTHS to add one</TT> <TT>> new enum to the PrtChannelTypeTC with IANA - that would stop the</TT> <TT>> Port Mon MIB dead in its tracks until it was accepted by IANA.</TT> <TT>></TT> <TT>> About ppmPrinterEnabled - same rationale as ppmPortEnabled - keeps</TT> <TT>> the number of Printer entries STATIC in an implementation - lets</TT> <TT>> the user see that the one Printer (i.e., hardward output interface)</TT> <TT>> on an External Network Adapter should presently be ignored.</TT> <TT>></TT> <TT>> Remember that the Port Mon MIB MUST NOT depend on either Host</TT> <TT>> Resources or Printer MIB, by common concensus - it may only</TT> <TT>> AUGMENT them, if they are present.</TT> <TT>></TT> <TT>> Cheers,</TT> <TT>> - Ira</TT> <TT>></TT> <TT>> Ira McDonald (Musician / Software Architect)</TT> <TT>> Blue Roof Music / High North Inc</TT> <TT>> PO Box 221  Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>, <st1:State w:st="on">MI</st1:State>  <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place></TT> <TT>> phone: +1-906-494-2434</TT> <TT>> email: imcdonald@sharplabs.com</TT> <TT>></TT> <TT>> > -----Original Message-----</TT> <TT>> > From: Bergman, Ron [mailto:Ron.Bergman@rpsa.ricoh.com]</TT> <TT>> > Sent: Tuesday, July 19, 2005 7:40 PM</TT> <TT>> > To: McDonald, Ira; Wijnen, Bert (Bert); pmp@pwg.org</TT> <TT>> > Subject: RE: PMP> Restructured Port MIB (18 July 2005)</TT> <TT>> ></TT> <TT>> ></TT> <TT>> > Ira,</TT> <TT>> ></TT> <TT>> > I am not sure what value ppmPrinterEnabled adds to the MIB.</TT> <TT>> > This appears to be analogous to</TT> <TT>> > On Line/Off Line.  If I want to create a driver for the</TT> <TT>> > printer I don't care what the current</TT> <TT>> > state is.  That information is only necessary when I am ready</TT> <TT>> > to print and then this MIB is</TT> <TT>> > not used.</TT> <TT>> ></TT> <TT>> > I believe that Bert has a valid point in using</TT> <TT>> > ppmPortProtocolType.  It is not a major effort</TT> <TT>> > to add unknown(2) to the IANA registrations.</TT> <TT>> ></TT> <TT>> > Otherwise, the changes are inline with our discussions</TT> <TT>> > following the test.</TT> <TT>> ></TT> <TT>> >         Ron</TT> <TT>> ></TT> <TT>> > -----Original Message-----</TT> <TT>> > From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org]On Behalf</TT> <TT>> > Of McDonald,</TT> <TT>> > Ira</TT> <TT>> > Sent: Tuesday, July 19, 2005 9:46 AM</TT> <TT>> > To: 'Wijnen, Bert (Bert)'; McDonald, Ira; 'pmp@pwg.org'</TT> <TT>> > Subject: RE: PMP> Restructured Port MIB (18 July 2005)</TT> <TT>> ></TT> <TT>> ></TT> <TT>> > Hi Bert,</TT> <TT>> ></TT> <TT>> > Thanks for your quick feedback.  My replies inline below.</TT> <TT>> ></TT> <TT>> > Cheers,</TT> <TT>> > - Ira</TT> <TT>> ></TT> <TT>> ></TT> <TT>> > Ira McDonald (Musician / Software Architect)</TT> <TT>> > Blue Roof Music / High North Inc</TT> <TT>> > <st1:address w:st="on"><st1:Street w:st="on">PO Box</st1:Street> 221</st1:address>  Grand <st1:place w:st="on"><st1:City w:st="on">Marais</st1:City>, <st1:State w:st="on">MI</st1:State>  <st1:PostalCode w:st="on">49839</st1:PostalCode></st1:place></TT> <TT>> > phone: +1-906-494-2434</TT> <TT>> > email: imcdonald@sharplabs.com</TT> <TT>> ></TT> <TT>> > > -----Original Message-----</TT> <TT>> > > From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]</TT> <TT>> > > Sent: Tuesday, July 19, 2005 9:08 AM</TT> <TT>> > > To: McDonald, Ira; 'pmp@pwg.org'</TT> <TT>> > > Subject: RE: PMP> Restructured Port MIB (18 July 2005)</TT> <TT>> > ></TT> <TT>> > ></TT> <TT>> > > Only did a very very quick scan.</TT> <TT>> > ></TT> <TT>> > > Comments.</TT> <TT>> > ></TT> <TT>> > > - ppmPortProtocolTargetPort OBJECT-TYPE</TT> <TT>> > >     SYNTAX      Integer32 (0..65535)</TT> <TT>> > >   I propose that you use InetPortNumber TC from RFC4001</TT> <TT>> > ></TT> <TT>> ></TT> <TT>> > Won't work, because this port is not limited to Internet Suite</TT> <TT>> > protocols.  The 'service:' URI in ppmPortServiceNameOrURI may</TT> <TT>> > also be for non-Internet suites (AppleTalk, NetWare, etc.).</TT> <TT>> ></TT> <TT>> > I'll correct the DESCRIPTION in the MIB and make clear that</TT> <TT>> > (as with the Printer MIB) ports/channels may be from multiple</TT> <TT>> > protocol suites.</TT> <TT>> ></TT> <TT>> ></TT> <TT>> > > - ppmPortProtocolType OBJECT-TYPE</TT> <TT>> > >     SYNTAX      Integer32 (0..2147483647)</TT> <TT>> > ></TT> <TT>> > >   WHy not use TC PrtChannelTypeTC as the SYNTAX?</TT> <TT>> > >   I do see that you want to use zero (meaning not supported).</TT> <TT>> > >   But maybe better is to use none(1) in that case, or maybe</TT> <TT>> > >   adding an enumeration to the TC of notSupported(xx) ??</TT> <TT>> > >   It is now an IANA-maintained TC, so it should not be that</TT> <TT>> > >   difficult to get a label added.</TT> <TT>> > ></TT> <TT>> ></TT> <TT>> > Won't work.  PrtChannelTypeTC currently only defines 'other(1)'</TT> <TT>> > and (foolishly) does NOT define 'unknown(2)' (unlike every other</TT> <TT>> > textual convention in the Printer MIB).  Because the Printer MIB</TT> <TT>> > v2 still doesn't define DEFVAL clauses for most objects, this</TT> <TT>> > oversight has not surfaced before.  We could register 'unknown(2)'</TT> <TT>> > with IANA, but _not_ fast enough (because this MIB's going into OS</TT> <TT>> > and printer vendor products right now).</TT> <TT>> ></TT> <TT>> ></TT> <TT>> > > - ppmPortPrtChannelIndex has a reference to RFC1213, while I</TT> <TT>> > >   think I would reather reference RFC2863 (the current IF-MIB)</TT> <TT>> > ></TT> <TT>> > > Bert</TT> <TT>> > ></TT> <TT>> ></TT> <TT>> > Agreed.  My mistake from the old Printer MIB (RFC 1759).</TT> <TT>> ></TT> <TT>> > I'll correct the references in the MIB.</TT> <TT>> > - Ira</TT> <TT>> ></TT> <TT>></TT> <o:p></o:p></DIV></BLOCKQUOTE></BODY></HTML>