PMP Mail Archive: PMP> Restructured Port MIB (18 July 2005)

PMP Mail Archive: PMP> Restructured Port MIB (18 July 2005)

PMP> Restructured Port MIB (18 July 2005)

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Mon Jul 18 2005 - 23:23:38 EDT

  • Next message: Wijnen, Bert (Bert): "RE: PMP> Restructured Port MIB (18 July 2005)"

    Hi folks, Monday (18 July 2005)

    I've just posted an ASN.1-only release of a revised Printer Port Monitor
    MIB on the PWG FTP server at:

        ftp://ftp.pwg.org/pub/pwg/pmp/wd/lcrc-pmpportmib10-20050718.mib

    Quick agreement on the new MIB structure is needed for the Microsoft and
    Apple teams to proceed with their development!

    Please see the discussion below on the use of the terms 'input port'
    and 'output port' in the PPM MIB context. Also see change log.

    Cheers,
    - Ira

    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
    ------------------------------------------------------------------------

    Input Ports versus Output Ports
    -------------------------------

    [Refer to the section 'Use Models of PPM MIB' in the current spec]

    In all three use models, each ppmPrinterTable entry represents a Print
    Service offered _by_ the given network system, and each subordinate
    ppmPortTable entry advertises an _input_ path to this Print Service
    (for pass-through or local processing).

    In both the Network Spooler and External Network Adapter use models,
    each ppmPortTable entry advertises an _input_ path to a Print Service
    (for pass-through to a downstream Print Device - see the Job attribute
    'output-device-assigned' in IPP/1.1, RFC 2911).

    In the Network Printer use model, exactly one ppmPrinterTable entry
    advertises a Print Service offered _by_ the Network Printer and each
    subordinate ppmPortTable entry advertises an _input_ path to that Print
    Service (for local processing).

    An External Network Adapter does NOT advertise the _output_ paths to its
    locally attached printers (serial, USB, etc.) as they are of no interest
    to the Client application.

    ------------------------------------------------------------------------

    [Change Log]

    18 July 2005 - Prototype Interoperability Test comments

    * added 'ppmGeneralNumberOfPrinters' (for 'ppmPrinterTable' below);

    * moved 'ppmGeneralPreferredPortIndex' to 'ppmPrinterTable';

    * added 'ppmPrinterTable' (to disambiguate the use models for Network
      Spoolers and External Network Adapters) with selected objects moved
      from the former 'ppmPortTable':
      
      ppmPrinterIndex - new
      ppmPrinterEnabled - new (but like ppmPortEnabled)
      ppmPrinterName - new (but like ppmPortName)
      ppmPrinterIEEE1284DeviceId <-- ppmPortIEEE1284DeviceId
      ppmPrinterNumberOfPorts - new (port count on THIS printer)
      ppmPrinterPreferredPortIndex <-- ppmGeneralPreferredPortIndex
      ppmPrinterHrDeviceIndex <-- ppmPortHrDeviceIndex
      ppmPrinterSnmpCommunityName <-- ppmPortSnmpCommunityName
      ppmPrinterSnmpQueryEnabled <-- ppmPortSnmpStatusQueryEnabled

    * changed SYNTAX of 'ppmPrinterIEEE1284DeviceID' to 'OCTET STRING',
      increased max length to 1023 octets, and required MANUFACTURER and
      MODEL in first 255 octets, per recent discussion on mailing list;

    * revised 'ppmPortTable' and 'ppmPortEntry' to clarify that they model
      only _input_ printer ports (and NOT the outgoing paths to downstream
      print devices).

    * revised description of 'ppmPortProtocolTargetPort' to state that it
      SHOULD NOT conflict with the value of 'ppmPortProtocolType', per
      discussion during Prototype Interoperability Test;

    * deleted 'ppmPortDescription', because it's redundant with the contents
      of the objects 'ppmPrinterIEEE1284DeviceId', 'ppmPortProtocolType',
      'ppmPortProtocolTargetPort', 'ppmPortServiceNameOrURI' (queue), and
      'ppmPortChannelIndex' (which leads via 'prtChannelIfIndex' in IETF
      Printer MIB to the hardware interface in 'ifTable' in IETF MIB-II).

    ------------------------------------------------------------------------



    This archive was generated by hypermail 2b29 : Mon Jul 18 2005 - 23:22:29 EDT