rfc2708.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

   1. The job priority is determined by the priority assigned to the
      queue that contains the job.  Each queue can be assigned a unique
      priority and the priority of the job is inherited from the queue.

11.0  NETWARE NPRINTER or RPRINTER

   The NetWare NPrinter/RPrinter protocol was designed to transfer print
   data from a Novell File Server to a printer attached directly to a
   local port (e.g. parallel or serial) on a PC.  NPrinter/RPrinter is
   an extremely lightweight printing protocol.  Consequently, no
   information required by the Job Monitoring MIB is provided and a
   meaningful jmJobSubmissionID cannot be generated.

   It is recommended that an additional job submission layer, such as
   PJL or another vendor private protocol,  be included on top of
   NPrinter/RPrinter to provide the required information.  The mapping
   should then be performed according to the recommendations of the
   higher layer submission protocol.








Bergman                      Informational                     [Page 20]

RFC 2708            Job Submission Protocol Mapping        November 1999


12.0  SERVER MESSAGE BLOCK (SMB) PROTOCOL

   The Server Message Block protocol is used with several PC Network
   operating systems, such as Microsoft Windows for Workgroups, IBM LAN
   Server, and Artisoft Lantastic.  SMB systems supporting the Job
   Monitoring MIB will conform to either configuration 1 or 3.

12.1  jmJobSubmissionID Mapped to SMB

   octet 1:   'C'

   octets 2-40:  Contains a decimal (ASCII coded) representation of the
                 16 bit SMB Tree Id field, which uniquely identifies the
                 connection that submitted the job to the printer.  The
                 most significant digit of the numeric string shall be
                 placed in octet position 2.  All unused portions of
                 this field shall be filled with spaces.  The SMB Tree
                 Id has a maximum value of 65,535.

   octets 41-48:  Contains a decimal (ASCII coded) representation of the
                  File Handle returned from the printer agent to the
                  client in response to a Create Print File command.
                  Leading zeros shall be inserted to fill the entire 8
                  octet field.

12.2  jmJobIndex Mapped to SMB

   It is strongly recommended that the File Handle returned from the
   printer agent be identical to jmJobIndex.  If these items are
   identical, there is no need for the client application to perform a
   search on jmJobSubmissionID.  To be compatible with the 16 bit field
   allocated to this value by SMB, the maximum jmJobIndex is 65,535.

12.3  Other MIB objects Mapped to SMB

   MIB Object      | SMB Parameter
   ----------------+------------------------------------------------
   jmJobOwner      | SMB User Id field (note 1)

   Notes:
   ------
   1. A decimal (ASCII coded) representation of the SMB User Id numeric
      shall be presented as jmJobOwner.








Bergman                      Informational                     [Page 21]

RFC 2708            Job Submission Protocol Mapping        November 1999


13.0  TRANSPORT INDEPENDENT PRINTER/SYSTEM INTERFACE (TIP/SI)

   The TIP/SI protocol, although currently specified as a part of the
   IEEE 1284 parallel port standards [TIP/SI], was originally developed
   as a network protocol.  TIP/SI thus has the potential of being
   integrated into any network or non-network configuration.

13.1  jmJobSubmissionID Mapped to TIP/SI

   octet 1:   'D'

   octets 2-40:  Contains the Job Name from the Job Control-Start Job
                 (JC-SJ) command.  If the Job Name portion is less than
                 40 octets, the left-most character in the string shall
                 appear in octet position 2.  Any unused portion of this
                 field shall be filled with spaces.  Otherwise, only the
                 last 39 bytes shall be included.

   octets 41-48:  Contains a decimal (ASCII coded) representation of the
                  jmJobIndex assigned by the agent.  Leading zeros shall
                  be inserted to fill the entire 8 octet field.

13.2  jmJobIndex Mapped to TIP/SI

   jmJobIndex is returned to the client as the Printer Assigned Job Id
   in a Job Control-Start Job (JC-SJ) response packet.  To be compatible
   with the 16 bit field allocated to this value by TIP/SI, the maximum
   jmJobIndex is 65,535.

13.3  Other MIB Objects Mapped to TIP/SI

   MIB Object             | TIP/SI Parameter
   -----------------------+---------------------------------------------
   jmJobOwner             | User string

13.4  The Attribute Group Mapped to TIP/SI

  MIB attribute         | TIP/SI information              | Data type
  ----------------------+---------------------------------+-------------
  jobName               | Job Name string                 | Octet String
  jobComment            | Additional Information string   | Octet String










Bergman                      Informational                     [Page 22]

RFC 2708            Job Submission Protocol Mapping        November 1999


14.0  Security Considerations

   This document provides mapping recommendations of job submission
   protocols for use with the Job Monitoring MIB. The mapping procedures
   defined do not enhance or compromise any security provisions
   available within the job submission protocols contained within this
   document.

   The security considerations specified for the Job Monitoring MIB
   [JobMIB] are also unaffected by any of the recommendations in this
   document.

   The security provisions available in the job submission protocols are
   documented in the appropriate specifications that define the
   protocols.  The degree of security available varies from very good,
   for protocols such as the Internet Printing Protocol [IPP], to non-
   existent, for example the Line Printer Daemon Protocol [LPD].

   Since the defined mapping operation occurs as a secondary operation
   after the user has been authenticated and there is no storage of any
   authorization credentials other than the user name, no security
   breaches are anticipated.  Also, the Job MIB does not provide any
   back-door mechanism for access to any other security parameters.
   However, implementers must always consider the impact of the defined
   mapping procedures upon the security model desired from the protocol.

15.0  REFERENCES

   [DPA]        ISO/IEC 10175-1:1996(E), "Information technology - Text
                and office systems - Document Printing Application (DPA)
                - Part 1: Abstract service definition and procedures",
                JTC1/SC18.

   [IPP]        deBry, R., Hastings, T., Herriot, R., Issaacson, S. and
                P. Powell, "The Internet Printing Protocol/1.0: Model
                and Semantics", RFC 2566, April 1999.

   [ISO-8824]   ISO/IEC 8824:1990, "Information technology - Open
                Systems Interconnection - Specification of Abstract
                Syntax Notation (ASN.1)".

   [JobMIB]     Bergman, R., Hastings, T., Isaacson, S. and H. Lewis,
                "The Job Monitoring MIB - V1.0", RFC 2707, November
                1999.

   [LPD]        McLaughlin, L., "Line Printer Daemon Protocol", RFC
                1179, August 1990.




Bergman                      Informational                     [Page 23]

RFC 2708            Job Submission Protocol Mapping        November 1999


   [PJL]        Printer Job Language Technical Reference Manual,
                Hewlett-Packard part number 5021-0328.

   [PrtMIB]     Smith, R., Wright, F., Hastings, T., Zilles, S. and J.
                Gyllenskog, "Printer MIB", RFC 1759, March 1995.

   [SNMPv2-TC]  McCloghrie, K., Perkins, D. and J. Schoenwaelder,
                "Textual Conventions for SMIv2", STD 58, RFC 2579, April
                1999.

   [TIP/SI]     IEEE Standard 1284.1, Transport Independent
                Printer/System Interface.

16.0  Authors' Addresses

   This document was created with significant contributions from the
   following individuals.

   Ron Bergman (Editor)
   Dataproducts Corp.
   1757 Tapo Canyon Road
   Simi Valley, CA 93063-3394

   Phone: [phone]
   Fax:  [phone]
   EMail: [e-mail]


   Tom Hastings
   Xerox Corporation, ESAE-231
   701 S. Aviation Blvd.
   El Segundo, CA   90245

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Scott A. Isaacson
   Novell, Inc.
   122 E 1700 S
   Provo, UT   84606

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]





Bergman                      Informational                     [Page 24]

RFC 2708            Job Submission Protocol Mapping        November 1999


   Harry Lewis
   IBM Corporation
   6300 Diagonal Hwy
   Boulder, CO 80301

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Bob Pentecost
   Hewlett-Packard Corporation
   11311 Chinden Boulevard
   Boise, ID 83714

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]

   Send comments to the printmib WG using the Job Monitoring Project
   (JMP) Mailing List: [e-mail]

   For further information, access the PWG web page under "JMP":
   http://www.pwg.org/

   Other Participants:

      Chuck Adams - Tektronix
      Keith Carter - IBM Corporation
      Angelo Caruso - Xerox
      Jeff Copeland - QMS
      Andy Davidson - Tektronix
      Mabry Dozier - QMS
      Lee Farrell - Canon
      David Kellerman - Northlake Software
      Rick Landau - Digital
      Jay Martin - Underscore
      Ira McDonald - Xerox
      Stuart Rowley - Kyocera
      Bob Setterbo - Adobe
      Gail Songer - EFI
      Mike Timperman - Lexmark
      William Wagner - DPI/Osicom
      Chris Wellens - Interworking Labs
      Rob Whittle - Novell
      Don Wright - Lexmark
      Lloyd Young - Lexmark




Bergman                      Informational                     [Page 25]

RFC 2708            Job Submission Protocol Mapping        November 1999


17.  Full Copyright Statement

   Copyright (C) The Internet Society (1999).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Bergman                      Informational                     [Page 26]