Internet Printing Protocol Working Group                    Tom Hastings
INTERNET DRAFT                                                     Xerox
Expires 19 September 2000 6 January 2001                                      Ira McDonald
                                                              High North
                                                           19 March
                                                             6 July 2000

                   Internet Printing Protocol (IPP):
          Notifications over SNMP via Job Monitoring MIB
                 <draft-ietf-ipp-not-over-snmp-02.txt> Traps
                 <draft-ietf-ipp-not-over-snmp-03.txt>

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

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC2026.  Internet-Drafts are working
   documents of the Internet Engineering Task Force (IETF), its areas,
   and its working groups.  Note that other groups may also distribute
   working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

     The list of current Internet-Drafts can be accessed at
     http://www.ietf.org/ietf/1id-abstracts.txt

     The list of Internet-Draft Shadow Directories can be accessed at
     http://www.ietf.org/shadow.html.

Abstract

   This document is a submission to the Internet Printing Protocol
   Working Group of the Internet Engineering Task Force (IETF).
   Comments should be submitted to the ipp@pwg.org mailing list.

   This document proposes a mapping of IPP notifications over SNMP via
   new device service and job traps trap extensions defined for the Job Monitoring
   MIB [RFC-2707].  This mapping may be used to deliver printer
   notifications for any printer (not just IPP-capable ones) and also
   job notifications for any job (not just ones submitted via IPP).

   This document proposes: proposes (4) SNMP traps; new object groups and (24) (4) new SNMP leaf objects
   (for use in various trap bindings). traps
   for addition to the Job Monitoring MIB [RFC 2707].  A working copy of
   this proposal integrated into the original Job Monitoring MIB ASN.1
   is at:
   ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/jmp-trap-000706.mib
                           Table of Contents

1.  Introduction ...............................................       4       3
  1.1.  Terminology for Conformance ............................       4       3
2.  SNMP Network Management Framework ..........................       4       3
3.  Managed Object Mapping .....................................       5       4
  3.1.  SNMP Mapping for IPP Notifications .....................       4
    3.1.1.  SNMP Mapping for IPP Printer Events ....................       5
  3.2. ................       4
    3.1.2.  SNMP Mapping for IPP Job Events ........................ ....................       5
  3.3.  Rules for Encoding Notifications .......................       6
  3.4.  Registration
  3.2.  Subscription for IPP Notifications .....................       7
    3.4.1.  Registration       6
    3.2.1.  Subscription via IPP ...............................       7
    3.4.2.  Registration       6
    3.2.2.  Subscription via SNMP ..............................       7
  3.5.       6
  3.3.  Relationship to other MIBs .............................       8
    3.5.1.       7
    3.3.1.  MIB-II (RFC 1213) ..................................       8
    3.5.2.       7
    3.3.2.  Host Resources MIB (RFC 1514) 2790) ......................       8
    3.5.3.       7
    3.3.3.  Printer MIB (RFC 1759) .............................       8       7
4.  Managed Object Definitions .................................       9       8
  4.1.  Device  Notification Definitions ...............................       8
    4.1.1.  Service Basic Event - Trap ................................       9
    4.1.1.  jmDeviceBasicV2Event (notification) ................       9
  4.2. .........................       8
    4.1.2.  Job Basic Event - Trap ...................................      10
    4.2.1.  jmJobBasicV2Event (notification) ...................      11
  4.3. .............................       9
    4.1.3.  Job Completed Event - Trap ............................... .........................      11
    4.3.1.  jmJobCompletedV2Event (notification) ...............      12
  4.4.
    4.1.4.  Job Progress Event - Trap ................................ ..........................      12
  4.2.  Object Definitions .....................................      13
    4.4.1.  jmJobProgressV2Event (notification) ................
    4.2.1.  Service Group - Objects ............................      13
  4.5.
    4.2.2.  Service Event Binding Group ....................................      14
    4.5.1.  jmEventTriggerEvent (object) .......................      14
    4.5.2.  jmEventSubscriptionID (object) .....................      15
    4.5.3.  jmEventSubscriberUserName (object) .................      15
    4.5.4.  jmEventSubscriberUserData (object) .................      16
    4.5.5.  jmEventDeviceURI (object) .......................... - Objects ......................      16
    4.5.6.  jmEventDeviceName (object) .........................      17
    4.5.7.  jmEventDeviceState (object) ........................      17
    4.5.8.  jmEventDeviceStateReasons (object) .................      17
    4.5.9.  jmEventDeviceIsAcceptingJobs (object) ..............      18
    4.5.10.  jmEventJobSetIndex (object) .......................      18
    4.5.11.  jmEventJobIndex (object) ..........................      19
    4.5.12.  jmEventJobName (object) ...........................      19
    4.5.13.  jmEventJobState (object)
    4.2.3.  Job Event Group - Objects ..........................      19
    4.5.14.  jmEventJobStateReasons (object) ...................      20
    4.5.15.  jmEventJobKOctets (object) ........................      20
    4.5.16.  jmEventJobKOctetsProcessed (object) ...............      21
    4.5.17.  jmEventJobImpressions (object) ....................      21
    4.5.18.  jmEventJobImpressionsCompleted (object) ...........      21
    4.5.19.  jmEventJobMediaSheets (object) ....................      22
    4.5.20.  jmEventJobMediaSheetsCompleted (object) ...........      22
    4.5.21.  jmEventJobImpressionsCompletedCC (object) .........
    4.2.4.  Job Progress Group - Objects .......................      22
    4.5.22.  jmEventJobCollationType (object) ..................      23
    4.5.23.  jmEventJobSheetCompletedCopyNum (object) ..........      23
    4.5.24.  jmEventJobSheetCompletedDocNum (object) ...........      23
5.  IANA Considerations ........................................      25      24
6.  Internationalization Considerations ........................      25      24
7.  Security Considerations ....................................      25      24
8.  References .................................................      26      25
9.  Change Log .................................................      27      26
10.  Intellectual Property Notice ..............................      29
11.  Authors' Addresses ........................................      29
12.  Full Copyright Statement ..................................      30

1.  Introduction

   The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer
   and Job objects, via client polling

   This document is a submission to the Internet Printing Protocol
   Working Group of IPP object attributes using the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations. Internet Engineering Task Force (IETF).
   Comments should be submitted to the ipp@pwg.org mailing list.

   This IPP Notifications over SNMP document proposes a mapping supports dynamic monitoring of IPP Printer notifications over SNMP via
   new service and job trap extensions defined for the Job objects, via server generation of SNMP traps.

   1.1.  Terminology Monitoring
   MIB [RFC-2707].  This mapping may be used to deliver printer
   notifications for any printer (not just IPP-capable ones) and also
   job notifications for any job (not just ones submitted via IPP).

   This document proposes (4) new object groups and (4) new SNMP traps
   for addition to the Job Monitoring MIB [RFC 2707].  A working copy of
   this proposal integrated into the original Job Monitoring MIB ASN.1
   is at:
   ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/jmp-trap-000706.mib

   The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer
   and Job objects, via client polling of IPP object attributes using
   the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations.

   This document proposes support for dynamic monitoring of IPP Printer
   and Job objects via SNMP traps generated by the service provider
   (server or device).

   1.1.  Terminology for Conformance

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted per [RFC-2119].

2.  SNMP Network Management Framework

   See:  Section 1.1 'SNMPv1', section 1.2 'SNMPv2', and section 1.3
         'SNMPv3' of [RFC-2576].

3.  Managed Object Mapping

   3.1.  SNMP Mapping for IPP Notifications

   3.1.1.  SNMP Mapping for IPP Printer Events

   IPP Printer event attribute         Job Monitoring MIB object mapping
   ---------------------------         ---------------------------------
   version-number                      [no mapping - not useful]
   status-code                         [implicit in each generated trap]
   request-id
   notify-sequence-number              [request-id in SNMP trap header]
   attributes-charset
   notify-charset                      [no mapping - strings are UTF-8]
   attributes-natural-language
   notify-natural-language             [no mapping - no text bindings]
   printer-uri                         jmEventDeviceURI
   printer-name                        jmEventDeviceName
   job-id                              jmEventJobIndex
                                       [and jmEventJobSetIndex]
   job-name                            jmEventJobName
   trigger-event                       jmEventTriggerEvent
   trigger-time
   subscription-id                     [no mapping]
   notify-subscribed-event             jmServiceEventNotifyEvent
   notify-printer-uri                  jmServiceURI
   printer-up-time                     [sysUpTime in SNMP trap bindings]
   trigger-date-time
   printer-current-time                [hrSystemDate in Host Res MIB]
   subscription-id                     jmEventSubscriptionID
   subscriber-user-name                jmEventSubscriberUserName
   subscriber-user-data                jmEventSubscriberUserData
   notify-user-data                    [no mapping]
   notify-text                         [no mapping]
   printer-state                       jmEventDeviceState                       jmServiceState
   printer-state-reasons               jmEventDeviceStateReasons               jmServiceStateReasons
   printer-is-accepting-jobs           jmEventDeviceIsAcceptingJobs
   3.2.           [jmServiceStateReasons keyword]
   3.1.2.  SNMP Mapping for IPP Job Events

   IPP Job event attribute             Job Monitoring MIB object mapping
   -----------------------             ---------------------------------
   version-number                      [no mapping - not useful]
   status-code                         [implicit in each generated trap]
   request-id
   notify-sequence-number              [request-id in SNMP trap header]
   attributes-charset
   notify-charset                      [no mapping - strings are UTF-8]
   attributes-natural-language
   notify-natural-language             [no mapping - no text bindings]
   printer-uri                         jmEventDeviceURI
   printer-name                        jmEventDeviceName
   subscription-id                     [no mapping]
   notify-subscribed-event             jmJobEventNotifyEvent
   notify-printer-uri                  jmServiceURI
   job-id                              jmEventJobIndex
                                       [and jmEventJobSetIndex]
   job-name                            jmEventJobName
   trigger-event                       jmEventTriggerEvent
   trigger-time                              [via jmJobState OID instance]
   printer-up-time                     [sysUpTime in SNMP trap bindings]
   trigger-date-time
   printer-current-time                [hrSystemDate in Host Res MIB]
   subscription-id                     jmEventSubscriptionID
   subscriber-user-name                jmEventSubscriberUserName
   subscriber-user-data                jmEventSubscriberUserData
   notify-user-data                    [no mapping]
   notify-text                         [no mapping]
   job-state                           jmEventJobState                           jmJobState
   job-state-reasons                   jmEventJobStateReasons                   jmJobEventJobStateReasons
                                       [jmJobStateReasons1 plus zero or]
                                       [more jobStateReasonsN in a strin

   [job-completed and job-purged - extra bindings]
   job-k-octets                        jmEventJobKOctets
   job-k-octets-processed              jmEventJobKOctetsProcessed
   job-impressions                     jmEventJobImpressions              jmJobKOctetsProcessed
   job-impressions-completed           jmEventJobImpressionsCompleted
   job-media-sheets                    jmEventJobMediaSheets
   job-media-sheets-completed          jmEventJobMediaSheetsCompleted           jmJobImpressionsCompleted

   [job-progress - extra bindings]
   impressions-completed-current-copy  jmEventJobImpressionsCompletedCC
   job-k-octets                        jmJobKOctetsPerCopyRequested
   job-impressions                     jmJobImpressionsPerCopyRequested
   job-copies                          jmProgressJobCopiesRequested
   job-collation-type                  jmEventJobCollationType                  jmProgressJobCollationType
   job-media-sheets-completed          jmProgressMediaSheetsCompleted
   sheet-completed-copy-number         jmEventJobSheetCompletedCopyNum         jmProgressSheetCompletedCopyNum
   sheet-completed-document-number     jmEventJobSheetCompletedDocNum
   3.3.  Rules for Encoding Notifications

   Over some transports and/or media, the variable-bindings of these
   SNMP traps MAY not fit the MTU (maximum transmission unit) size.
   Conforming IPP Notification generators SHALL perform this procedure
   to ensure that all variable-bindings of these SNMP traps are always
   included in the generated SNMP trap packet:

   1)  Truncate all strings specified for variable-bindings
       to the reduced maximum sizes that are specified in their
       corresponding OBJECT clauses in their MODULE-COMPLIANCE.
   1a) If all variable-bindings now fit within the MTU,
       then exit this procedure and generate the SNMP trap.
   2)  Truncate the next one of the following string objects to
       the empty string (zero length in the ASN.1 BER encoding),
       in the order listed:
       - 'jmEventSubscriberUserName'
       - 'jmEventSubscriberUserData'
       - 'jmEventDeviceURI'
       - 'jmEventDeviceName'
       - 'jmEventDeviceStateReasons'
       - 'jmEventJobName'
       - 'jmEventJobStateReasons'
   2a) If all variable-bindings now fit within the MTU,
       then exit this procedure and generate the SNMP trap.
   2b) If all variable-bindings do NOT fit within the MTU,
       then repeat step (2) for next string object.
   3)  If all variable-bindings do NOT fit within the MTU,
       then -> logic error (variable-bindings MUST now fit).

   3.4.  Registration     jmProgressSheetCompletedDocNum
   3.2.  Subscription for IPP Notifications

   IPP Clients may register MAY subscribe for IPP Notifications delivered via SNMP by
   either of the following two standard methods:

   3.4.1.  Registration

   3.2.1.  Subscription via IPP

   IPP Create-Subscription and Job creation (Create-Job, Print-Job, Print-URI) and
   Create-Subscription operations MAY be used to create per-Printer or
   per-Job IPP Subscription objects and MAY specify

     'notify-recipient'

     "notify-recipient-uri" = 'snmpnotify://hostname[.port]'
   3.4.2.  Registration

     "notify-events" = <events of interest, e.g., 'job-completed'>

   3.2.2.  Subscription via SNMP

   The SNMP Set-Request operations Notification MIB and SNMP Target MIB (both in [RFC-2573])
   MAY be used to create appropriate rows SNMP subscriptions.

   To create a subscription via SNMP, the IPP Client MAY use an SNMP
   Set-Request operation to create an appropriate row in the SNMP
   Notification MIB defined in [RFC-2573] and MAY specify: with the following variable-bindings:

   1)  'snmpNotifyTag'
       - tag of this notification - see 'snmpTargetAddrTagList' below
       - example "jmDeviceBasicV2Event" or "jmJobBasicV2Event"
   2)  'snmpNotifyType'
       - notification sent using either deliver via SNMP Trap (unacknowledged) or SNMP Inform-Request Inform (acknowledged)
   3)  'snmpNotifyStorageType'
       - row persistence (volatile, nonVolatile, permanent, readOnly)

   Note:  The SNMP Notification MIB uses persistence instead of this registration the
   lease duration supported in IPP Subscription objects.

   To complete a subscription via SNMP, the IPP Client MAY use an SNMP
   Set-Request operations MAY be used operation to create an appropriate rows row in the SNMP Target
   MIB defined in [RFC-2573] and MAY specify: with the following variable-bindings:

   1)  'snmpTargetAddrTDomain' and 'snmpTargetAddrTAddress'
       - notification target (client) transport protocol and address (equivalent
         (corresponds to URI) IPP 'notify-recipient-uri')
   2)  'snmpTargetAddressTimeout' and 'snmpTargetAddrRetryCount'
       - retry timeout and limit (for acknowledged notifications
         delivered using SNMP Inform-Request rather than SNMP Trap) Inform only)
   3)  'snmpTargetAddrTagList'
       - tags of notifications to be sent to this target (client)
       - example "jmDeviceBasicV2Event" or "jmJobBasicV2Event"
   4)  'snmpTargetAddrParamsEntry'
       - notification security and SNMP protocol version
   5)  'snmpTargetAddrStorageType'
       - row persistence (volatile, nonVolatile, permanent, readOnly)

   Note:  The SNMP Target MIB uses persistence instead of this registration

   3.5. the lease
   duration supported in IPP Subscription objects.

   3.3.  Relationship to other MIBs

   3.5.1.

   3.3.1.  MIB-II (RFC 1213)

   All SNMPv1 trap messages include 'time-stamp' which is the value of
   the 'sysUpTime' object from MIB-II [RFC-1213].

   All SNMPv2 trap bindings include the 'sysUpTime' object from MIB-II
   [RFC-1213].

   3.5.2.

   3.3.2.  Host Resources MIB (RFC 1514) 2790)

   The 'jmDeviceBasicV2Event' trap 'jmServiceTable' defined in this document permits
   optional binding of MAY have a sparse
   mapping to the 'hrDeviceStatus', 'hrDevicePrinterStatus',
   and 'hrPrinterDetectedErrorState' objects from 'hrDeviceTable' (same indices) in Host Resources MIB
   [RFC-1514].

   3.5.3.
   [RFC-2790].

   3.3.3.  Printer MIB (RFC 1759)

   The 'jmDeviceBasicV2Event' trap 'jmServiceTable' defined in this document permits
   optional binding of MAY have a sparse
   mapping to the 'hrDeviceStatus', 'hrDevicePrinterStatus',
   and 'hrPrinterDetectedErrorState' objects from 'hrDeviceTable' (same indices) in Host Resources MIB
   [RFC-1514].

   The appropriate value of 'hrDeviceIndex'
   [RFC-2790], thus offering access to use in the Printer MIB
   [RFC-1759] may be indicated by the instance suffix of the
   'hrDeviceStatus' variable's OID. via a
   'hrDeviceIndex' value.

4.  Managed Object Definitions

4.1.  Device  Notification Definitions

4.1.1.  Service Basic Event - Trap

--  Device  Service Basic Event Group (Cond Mandatory) (CONDITIONALLY MANDATORY)
--
--  Implementation of this group is conditionally mandatory;
--  mandatory for systems which send this Device event Service traps via SNMP.

   jmDeviceBasicV1Enterprise

--  The jmServiceBasicEventGroup consists entirely of the
--  jmServiceBasicV2Event notification.

jmServiceBasicV1Enterprise OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The value of the enterprise-specific OID in an SNMPv1 trap
        for a Device Service basic event' event sent by this managed system."
    ::= { jobmonMIBNotifications 1 }

   jmDeviceBasicV2EventPrefix

jmServiceBasicV2EventPrefix
    OBJECT IDENTIFIER ::= { jmDeviceBasicV1Enterprise jmServiceBasicV1Enterprise 0 }

   jmDeviceBasicV2Event

jmServiceBasicV2Event NOTIFICATION-TYPE
    OBJECTS {
           jmEventTriggerEvent,
           jmEventSubscriptionID,
           jmEventSubscriberUserName,
           jmEventSubscriberUserData,
           jmEventDeviceURI,
           jmEventDeviceName,
           jmEventJobSetIndex,
           jmEventJobIndex,
           jmEventJobName,
           jmEventDeviceState,
           jmEventDeviceStateReasons,
           jmEventDeviceIsAcceptingJobs
        jmServiceEventNotifyEvent,
        jmServiceState,
        jmServiceStateReasons
    }
    STATUS      current
    DESCRIPTION
        "This SMIv2 trap corresponds to an IPP Printer basic event.

        The value of 'jmServiceIndex' for
        use with 'jmServiceTable' for this Service is conveyed in the
        instance qualifier (OID suffix) of 'jmServiceState'.

        This trap is sent when requested by a prior subscription.
        The subscribed event type is specified in 'jmEventTriggerEvent'.

           Event 'jmServiceEventNotifyEvent'.

        Standard Printer event types reported via 'jmDeviceBasicV2Event' include: defined in [IPP-NOT] are:
        - 'printer-state-changed'
          - 'printer-restarted'
          - 'printer-shutdown'
        - 'printer-state-changed' 'printer-config-changed'
          - 'printer-media-changed'
          - 'printer-config-changed' 'printer-finishings-changed'
        - 'printer-queue-order-changed'
        - 'printer-queue-changed' 'printer-full'
        - 'printer-no-longer-full'
        - 'printer-almost-idle'
        - 'device-restarted' 'printer-not-almost-idle'

        Standard Service event types generalized from [IPP-NOT] are:
        - 'service-state-changed'
          - 'device-shutdown' 'service-restarted'
          - 'device-state-changed' 'service-shutdown'
        - 'device-media-changed' 'service-config-changed'
          - 'device-config-changed' 'service-media-changed'
          - 'device-queue-changed' 'service-finishings-changed'
        - 'device-no-longer-full' 'service-queue-order-changed'
        - 'device-almost-idle' 'service-full'
        - 'service-no-longer-full'
        - 'service-almost-idle'
        - 'service-not-almost-idle'
        - and (optionally) vendor extension event types

        Additional variable-bindings SHOULD be appended to this trap
           for all device-level events: trap:
        - Systems with the Host Resources MIB [RFC-1514] (RFC 2790) SHOULD add
          'hrSystemDate'
          (compare to IPP 'printer-current-time') and
             'hrDeviceStatus'
             (compare to IPP 'printer-state')

        Additional variable-bindings MAY be appended to this trap
        for all printer-specific events:
        - Systems with the Host Resources MIB [RFC-1514] (RFC 2790) MAY add
          'hrDeviceStatus'
          (compare to IPP 'printer-state')
          'hrPrinterStatus'
          (compare to IPP 'printer-state') and
          'hrPrinterDetectedErrorState'
          (compare to IPP 'printer-state-reasons')

        Systems MAY add other variable-bindings from any MIB.

        See:    Section 5.2 5.3.2 'notify-events' of in [IPP-NOT];
                Section 7 'Notification 8.1 'notify-subscribed-event' in [IPP-NOT];
                Section 9 'Event Notification Content' in [IPP-NOT]."
    ::= { jmDeviceBasicV2EventPrefix jmServiceBasicV2EventPrefix 1 }

   4.2.

4.1.2.  Job Basic Event - Trap

--  Job Basic Event Group (Cond Mandatory) (CONDITIONALLY MANDATORY)
--

--  Implementation of this group is conditionally mandatory;
--  mandatory for systems which send this Job event traps via SNMP.

--  The jmJobBasicEventGroup consists entirely of the
--  jmJobBasicV2Event notification.

jmJobBasicV1Enterprise OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The value of the enterprise-specific OID in an SNMPv1 trap
        for a Job basic event sent by this managed system."
    ::= { jobmonMIBNotifications 2 }

jmJobBasicV2EventPrefix
    OBJECT IDENTIFIER ::= { jmJobBasicV1Enterprise 0 }

jmJobBasicV2Event NOTIFICATION-TYPE
    OBJECTS {
           jmEventTriggerEvent,
           jmEventSubscriptionID,
           jmEventSubscriberUserName,
           jmEventSubscriberUserData,
           jmEventDeviceURI,
           jmEventDeviceName,
           jmEventJobSetIndex,
           jmEventJobIndex,
           jmEventJobName,
           jmEventJobState,
           jmEventJobStateReasons
        jmJobEventNotifyEvent,
        jmJobState,
        jmJobEventJobStateReasons
    }
    STATUS      current
    DESCRIPTION
        "This SMIv2 trap corresponds to an IPP Job basic event.

        The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for
        use with 'jmJobTable' for this Job are conveyed in the
        instance qualifier (OID suffix) of 'jmJobState'.

        This trap is sent when requested by a prior subscription.
        The subscribed event type is specified in 'jmEventTriggerEvent'. 'jmJobEventNotifyEvent'.

        Event types reported via 'jmJobBasicV2Event' include:
        - 'job-created'
           - 'job-state-changed'
          - 'job-config-changed' 'job-created'
          - 'job-completed'
          - 'job-purged'
        - 'job-config-changed'
        - and (optionally) vendor extension event types

        Additional variable-bindings SHOULD be appended to this trap:
        - Systems with the Host Resources MIB (RFC 2790) SHOULD add
          'hrSystemDate'
          (compare to IPP 'printer-current-time')

        Systems MAY add other variable-bindings from any MIB.

        See:    Section 5.2 5.3.2 'notify-events' of in [IPP-NOT];
                Section 7 'Notification 8.1 'notify-subscribed-event' in [IPP-NOT];
                Section 9 'Event Notification Content' in [IPP-NOT]."
    ::= { jmJobBasicV2EventPrefix 1 }

   4.3.

4.1.3.  Job Completed Event - Trap

--  Job Completed Event Group (Cond Mandatory) (CONDITIONALLY MANDATORY)
--
--  Implementation of this group is conditionally mandatory;
--  mandatory for systems which send this Job event traps via SNMP.

jmJobCompletedV1Enterprise OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The value of the enterprise-specific OID in an SNMPv1 trap
        for a Job completed event sent by this managed system."
    ::= { jobmonMIBNotifications 3 }

jmJobCompletedV2EventPrefix
    OBJECT IDENTIFIER ::= { jmJobCompletedV1Enterprise 0 }

jmJobCompletedV2Event NOTIFICATION-TYPE
    OBJECTS {
           jmEventTriggerEvent,
           jmEventSubscriptionID,
           jmEventSubscriberUserName,
           jmEventSubscriberUserData,
           jmEventDeviceURI,
           jmEventDeviceName,
           jmEventJobSetIndex,
           jmEventJobIndex,
           jmEventJobName,
           jmEventJobState,
           jmEventJobStateReasons,
           jmEventJobKOctetsProcessed,
           jmEventJobImpressionsCompleted,
           jmEventJobMediaSheetsCompleted
        jmJobEventNotifyEvent,
        jmJobState,
        jmJobEventJobStateReasons,
        jmJobKOctetsProcessed,
        jmJobImpressionsCompleted
    }
    STATUS      current
    DESCRIPTION
        "This SMIv2 trap corresponds to an IPP 'job-completed' event.

        The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for
        use with 'jmJobTable' for this Job are conveyed in the
        instance qualifier (OID suffix) of 'jmJobState'.

        This trap is sent when requested by a prior subscription.
        The subscribed event type is specified in 'jmEventTriggerEvent'. 'jmJobEventNotifyEvent'.

        Event types reported via 'jmJobCompletedV2Event' include:
        - 'job-completed'
        - 'job-purged'
        - and (optionally) vendor extension event types

        Additional variable-bindings SHOULD be appended to this trap
           for all 'job-completed' events: trap:
        - Systems which support this job information with the Host Resources MIB (RFC 2790) SHOULD add
             'jmEventJobKOctets'
             (compare to IPP 'job-k-octets' job size attribute
             and to Job Mon MIB 'jobKOctetsTransferred' attribute)
             'jmEventJobImpressions'
             (compare to IPP 'job-impressions' job size attribute)
             'jmEventJobMediaSheets'
          'hrSystemDate'
          (compare to IPP 'job-media-sheets' job size attribute
             and to Job Mon MIB 'sheetsRequested' attribute) 'printer-current-time')

        Systems MAY add other variable-bindings from any MIB.

        See:    Section 5.2 5.3.2 'notify-events' of in [IPP-NOT];
                Section 7 'Notification 8.1 'notify-subscribed-event' in [IPP-NOT];
                Section 9 'Event Notification Content' in [IPP-NOT]."
    ::= { jmJobCompletedV2EventPrefix 1 }
   4.4.

4.1.4.  Job Progress Event - Trap

--  Job Progress Event Group (Cond Mandatory) (CONDITIONALLY MANDATORY)
--
--  Implementation of this group is conditionally mandatory;
--  mandatory for systems which send this Job event traps via SNMP.

jmJobProgressV1Enterprise OBJECT-IDENTITY
    STATUS      current
    DESCRIPTION
        "The value of the enterprise-specific OID in an SNMPv1 trap
        for a Job progress event sent by this managed system."
    ::= { jobmonMIBNotifications 4 }

jmJobProgressV2EventPrefix
    OBJECT IDENTIFIER ::= { jmJobProgressV1Enterprise 0 }

jmJobProgressV2Event NOTIFICATION-TYPE
    OBJECTS {
           jmEventTriggerEvent,
           jmEventSubscriptionID,
           jmEventSubscriberUserName,
           jmEventSubscriberUserData,
           jmEventDeviceURI,
           jmEventDeviceName,
           jmEventJobSetIndex,
           jmEventJobIndex,
           jmEventJobName,
           jmEventJobState,
           jmEventJobStateReasons,
           jmEventJobKOctetsProcessed,
           jmEventJobImpressionsCompleted,
           jmEventJobMediaSheetsCompleted,
           jmEventJobImpressionsCompletedCC,
           jmEventJobCollationType,
           jmEventJobSheetCompletedCopyNum,
           jmEventJobSheetCompletedDocNum
        jmJobKOctetsPerCopyRequested,
        jmJobKOctetsProcessed,
        jmJobImpressionsPerCopyRequested,
        jmJobImpressionsCompleted,
        jmProgressJobCopiesRequested,
        jmProgressJobCollationType,
        jmProgressMediaSheetsCompleted,
        jmProgressSheetCompletedCopyNum,
        jmProgressSheetCompletedDocNum
    }
    STATUS      current
    DESCRIPTION
        "This SMIv2 trap corresponds to an IPP 'job-progress' event.

        The values of 'jmGeneralJobSetIndex' and 'jmJobIndex' for
        use with 'jmJobTable' for this Job are conveyed in the
        instance qualifier (OID suffix) of 'jmJobKOctetsProcessed'.

        This trap is sent when requested by a prior subscription.
        The event type is specified in 'jmEventTriggerEvent'.

           Event types reported via 'jmJobProgressV2Event' include:
           - 'job-progress'
           - and (optionally) vendor extension event types 'job-progress'.

        Additional variable-bindings SHOULD be appended to this trap
           for all 'job-progress' events: trap:
        - Systems which support this job information with the Host Resources MIB (RFC 2790) SHOULD add
             'jmEventJobKOctets'
             (compare to IPP 'job-k-octets' job size attribute
             and to Job Mon MIB 'jobKOctetsTransferred' attribute)
             'jmEventJobImpressions'
             (compare to IPP 'job-impressions' job size attribute)
             'jmEventJobMediaSheets'
          'hrSystemDate'
          (compare to IPP 'job-media-sheets' job size attribute
             and to Job Mon MIB 'sheetsRequested' attribute) 'printer-current-time')

        Systems MAY add other variable-bindings from any MIB.

        See:    Section 5.2 5.3.2 'notify-events' of in [IPP-NOT];
                Section 7 'Notification 8.1 'notify-subscribed-event' in [IPP-NOT];
                Section 9 'Event Notification Content' in [IPP-NOT]."
    ::= { jmJobProgressV2EventPrefix 1 }

   4.5.  Event Binding

4.2.  Object Definitions

4.2.1.  Service Group - Objects

--  Event Binding  The Service Group (Cond Mandatory) (CONDITIONALLY MANDATORY)
--
--  Implementation of this group is conditionally mandatory;
--  mandatory for systems which send Device or Job events show Service state via SNMP.

--
   --  Note:  All  The jmServiceGroup consists entirely of the objects in this group are defined ONLY for the
   --  purpose of providing instantaneous bindings for SNMP traps - it's
   --  NEVER suitable for an SNMP Manager to Get these objects directly.

   jmEventBinding jmServiceTable

jmService  OBJECT IDENTIFIER ::= { jobmonMIBObjects 5 7 }

   jmEventTriggerEvent

jmServiceTable  OBJECT-TYPE
    SYNTAX      JmUTF8StringTC (SIZE (0..63))   -- 255 in [IPP-MOD]      SEQUENCE OF JmServiceEntry
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "The trigger event type associated with jmServiceTable consists of basic service state and status
        information for each service which offers one or more job
        services on this event.

           Standard Printer event types defined in [IPP-NOT] are:
           - 'printer-restarted'
           - 'printer-shutdown'
           - 'printer-state-changed'
           - 'printer-media-changed'
           - 'printer-config-changed'
           - 'printer-queue-changed'
           - 'printer-no-longer-full'
           - 'printer-almost-idle'

           Standard Device event types generalized from [IPP-NOT] are:

           - 'device-restarted'
           - 'device-shutdown'
           - 'device-state-changed'
           - 'device-media-changed'
           - 'device-config-changed'
           - 'device-queue-changed'
           - 'device-no-longer-full'
           - 'device-almost-idle'

           Standard Job event types defined managed system.

        An entry SHALL exist in [IPP-NOT] are:
           - 'job-created'
           - 'job-completed'
           - 'job-state-changed'
           - 'job-config-changed'
           - 'job-purged'
           - 'job-progress'

           Conformance:    The natural language this table for keywords
           in trigger event type SHALL always be US English.

           Conformance:    This trigger event type SHALL be valid each service, no matter
        what the state of that service.  A service MAY support multiple
        configured job sets and reported in ALL Job Monitoring MIB notifications. configured devices.

        See:    Section 5.2 'notify-events'    'jmServiceJobSetsConfigured' and
                   Section 7 'Notification Content'
                'jmServiceDevicesConfigured' bit-arrays in [IPP-NOT]."
   --  DEFVAL intentionally omitted - reported value SHALL be valid this MIB."
    ::= { jmEventBinding jmService 1 }

   jmEventSubscriptionID

jmServiceEntry  OBJECT-TYPE
    SYNTAX      JmServiceEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Basic service state and status information."
    INDEX  { jmServiceIndex }
    ::= { jmServiceTable 1 }

JmServiceEntry ::= SEQUENCE {
    jmServiceIndex                      Integer32 (0..2147483647) (1..2147483647),
    jmServiceName                       JmUTF8StringTC (SIZE (0..63)),
    jmServiceURI                        JmUTF8StringTC (SIZE (0..63)),
    jmServiceJobServiceTypes            JmJobServiceTypesTC,
    jmServiceJobSetsConfigured          OCTET STRING (SIZE (0..255)),
    jmServiceDevicesConfigured          OCTET STRING (SIZE (0..255)),
    jmServiceState                      JmServiceStateTC,
    jmServiceStateReasons               SnmpAdminString (SIZE (0..255))
}

jmServiceIndex OBJECT-TYPE
    SYNTAX      Integer32 (1..2147483647)
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "The subscription unique identifier associated with for this event
           or zero (if none).

           Conformance:    This subscription identifier SHALL be valid
           and reported, if available service on this managed system.

        See:    'jmServiceEventServiceIndex' object in this MIB."
    ::= { jmServiceEntry 1 }

jmServiceName OBJECT-TYPE
    SYNTAX      JmUTF8StringTC (SIZE(0..63))    -- 127 in IPP
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The human readable name of this managed service.

        See:    'deviceNameRequested' job attribute in this MIB;
                'physicalDevice' job attribute in this MIB;
                Section 5.8 'subscription-id' and
                   Section 7 'Notification Content' 4.4.4 'printer-name' in [IPP-NOT]." [IPP-MOD]."
    DEFVAL      { 0 ''H }                 -- no subscription ID service name
    ::= { jmEventBinding jmServiceEntry 2 }

   jmEventSubscriberUserName

jmServiceURI OBJECT-TYPE
    SYNTAX      JmUTF8StringTC (SIZE (0..63)) (SIZE(0..63))    -- 1023 in [IPP-MOD] IPP
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
           "The subscriber user name associated with this event
           or the empty string (if none).

           Note:   The natural language appropriate for text-to-speech
           of subscriber user name is orthogonal to the localized text
           context in IPP 'attributes-natural-language'.  The subscriber
           user name MAY include an in-line 'language tag' using Plane
           14 'language tag' characters approved
        "A URI for ISO 10646/Unicode.

           Conformance:    This subscriber user name SHALL be valid
           and reported, if available on this managed system. service (valid for job services).

        See:    'Language Tagging in Unicode Plain Text', RFC 2482
                   (January 1999);
                   'Plane 14 Characters for Language Tags', Unicode
                   Technical Report #7 (January 1999);
                   Section 4.3.6 'job-originating-user-name' and    Section 4.4.2 'uri-authentication-supported'
                   (usage of 'requesting-user-name') 4.3.3 'job-printer-uri' in [IPP-MOD];
                Section 5.11 'subscriber-user-name' and
                   Section 7 'Notification Content' 4.4.1 'printer-uri-supported' in [IPP-NOT]." [IPP-MOD]."
    DEFVAL      { ''H }                 -- no subscriber user name service URI
    ::= { jmEventBinding jmServiceEntry 3 }

   jmEventSubscriberUserData

jmServiceJobServiceTypes OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..63))     -- 63 in [IPP-NOT]      JmJobServiceTypesTC
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The subscriber user data associated with this event
           or the empty string (if none).

           Conformance:    This subscriber user data SHALL be valid
           and reported, if available on types of job services supported by this managed system. service.

        See:    Section 5.4 'subscriber-user-data' and
                   Section 7 'Notification Content'    'JmJobServiceTypesTC' textual convention in [IPP-NOT]." this MIB;
                'jobServiceTypes' job attribute in this MIB."
    DEFVAL      { ''H 0 }                   -- no subscriber user data job services
    ::= { jmEventBinding jmServiceEntry 4 }

   jmEventDeviceURI

jmServiceJobSetsConfigured OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..255))    -- 1023 in [IPP-MOD] (SIZE(0..255))
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
           "The device URI associated with this event
           or
        "A bit-array that specifies the empty string (if none).

           Conformance:    This device URI SHALL be valid
           and reported, if available on job sets configured for this managed system.

           See:    Section 4.3.3 'job-printer-uri'
        service, where each bit '2**n' is set if 'jmGeneralJobSetIndex'
        is a configured job set.   Uses network byte order (big-endian)
        rules - the high-order bit of the first octet corresponds to
        'jmGeneralJobSetIndex' of '0' (reserved) - the low-order bit of
        the first octet corresponds to 'jmGeneralJobSetIndex' of '7'.
        Supports values of 'jmGeneralJobSetIndex' from '1' to '2039'.

        Compare to the BITS pseudotype defined in [IPP-MOD];
                   Section 4.4.1 'printer-uri-supported' IETF SMIv2 (RFC 2578)
        which has the same bit ordering rules (big-endian).

        See:    'queueNameRequested' job attribute in [IPP-MOD];
                   Section 7 'Notification Content' this MIB;
                'jmGeneralJobSetIndex' table index in [IPP-NOT]." this MIB."
    DEFVAL      { ''H }                 -- no device URI job sets configured
    ::= { jmEventBinding jmServiceEntry 5 }

   jmEventDeviceName

jmServiceDevicesConfigured OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..127))    -- 127 in [IPP-MOD] (SIZE(0..255))
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
           "The device name associated with this event
           or
        "A bit-array that specifies the empty string (if none).

           Conformance:    This device name SHALL be valid
           and reported, if available on devices configured for this managed system.
        service, where each bit '2**n' is set if 'hrDeviceIndex'
        is a configured device.   Uses network byte order (big-endian)
        rules - the high-order bit of the first octet corresponds to
        'hrDeviceIndex' of '0' (reserved) - the low-order bit of
        the first octet corresponds to 'hrDeviceIndex' of '7'.
        Supports values of 'hrDeviceIndex' from '1' to '2039'.

        Compare to the BITS pseudotype defined in IETF SMIv2 (RFC 2578)
        which has the same bit ordering rules (big-endian).

        See:    Section 4.4.4 'printer-name'    'physicalDevice' job attribute in [IPP-MOD];
                   Section 7 'Notification Content' this MIB;
                'hrDeviceIndex' in [IPP-NOT]." IETF Host MIB (RFC 2790)."
    DEFVAL      { ''H }                 -- no device name devices configured
    ::= { jmEventBinding jmServiceEntry 6 }

   jmEventDeviceState

jmServiceState OBJECT-TYPE
    SYNTAX      INTEGER {                       -- enum in [IPP-MOD]
           unknown(2),                     -- unknown device state
           idle(3),
           processing(4),
           stopped(5)
       }      JmServiceStateTC
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The device state associated with this event
           or 'unknown'.

           Note:   This object uses the keywords from the [IPP-MOD]
           enumerated type 'printer-state' for coherence.

           Conformance:    This device current state SHALL be valid
           and reported, if available on of this managed system. service.

        See:    'jmServiceEventServiceState' object in this MIB;
                'jmJobState' object in this MIB;
                Section 4.4.11 'printer-state' in [IPP-MOD];
                   Section 7 'Notification Content' in [IPP-NOT]." [IPP-MOD]."
    DEFVAL      { unknown }             -- unknown device service state
    ::= { jmEventBinding jmServiceEntry 7 }

   jmEventDeviceStateReasons

jmServiceStateReasons OBJECT-TYPE
    SYNTAX      OCTET STRING      SnmpAdminString (SIZE (0..255)) -- 255*n multi-valued in [IPP-MOD] IPP
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The device service state reasons associated with this event service state
        (as a comma-separated list) or the empty string (if none).

           Conformance:    The natural language for keywords

        See:    'jmServiceEventServiceStateReasons' object in device state reasons SHALL always be US English.

           Conformance:    These device state reasons SHALL be valid
           and reported, if available on this managed system.

           See: MIB;
                'jmJobStateReasons1' object in this MIB;
                Section 4.4.12 'printer-state-reasons' in [IPP-MOD];
                   Section 7 'Notification Content' in [IPP-NOT]." [IPP-MOD]."
    DEFVAL      { ''H }                 -- no device service state reasons
    ::= { jmEventBinding 8 jmServiceEntry 8 }

4.2.2.  Service Event Group - Objects

--  The Service Event Group (CONDITIONALLY MANDATORY)
--
--  Implementation of this group is conditionally mandatory;
--  mandatory for systems which show Service events via SNMP.

--  The jmServiceEventGroup consists entirely of the jmServiceEventTable

jmServiceEvent  OBJECT IDENTIFIER ::= { jobmonMIBObjects 8 }

jmServiceEventTable  OBJECT-TYPE
    SYNTAX      SEQUENCE OF JmServiceEventEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The jmServiceEventTable contains service event entries for the
        services which offer job services on this managed system."
    ::= { jmServiceEvent 1 }

jmServiceEventEntry  OBJECT-TYPE
    SYNTAX      JmServiceEventEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Basic service event information."
    INDEX  { jmServiceEventIndex }
    ::= { jmServiceEventTable 1 }

JmServiceEventEntry ::= SEQUENCE {
    jmServiceEventIndex                 Integer32 (1..2147483647),
    jmServiceEventNotifyEvent           SnmpAdminString (SIZE (0..63)),
    jmServiceEventNotifyTime            TimeTicks,
    jmServiceEventServiceIndex          Integer32 (1..2147483647),
    jmServiceEventServiceState          JmServiceStateTC,
    jmServiceEventServiceStateReasons   SnmpAdminString (SIZE (0..255))
}

   jmEventDeviceIsAcceptingJobs

jmServiceEventIndex OBJECT-TYPE
    SYNTAX      TruthValue      Integer32 (1..2147483647)
    MAX-ACCESS  read-only  not-accessible
    STATUS      current
    DESCRIPTION
        "The device substate associated with unique identifier for this event
           or 'true' (if unknown).

           Conformance:    This device substate SHALL be valid
           and reported, if available on this managed system.

           See:    Section 4.4.23 'printer-is-accepting-jobs'
                   in [IPP-MOD];
                   Section 7 'Notification Content' in [IPP-NOT]."
       DEFVAL      { true }                -- device is accepting jobs system."
    ::= { jmEventBinding 9 jmServiceEventEntry 1 }

   jmEventJobSetIndex

jmServiceEventNotifyEvent OBJECT-TYPE
    SYNTAX      Integer32 (0..32767)      SnmpAdminString (SIZE (0..63))   -- 255 in [IPP-NOT]
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job set index associated with event type that created this row in 'jmServiceEventTable'.

        Standard Printer event
           or zero (if none). types defined in [IPP-NOT] are:
        - 'printer-state-changed'
          - 'printer-restarted'
          - 'printer-shutdown'
        - 'printer-config-changed'
          - 'printer-media-changed'
          - 'printer-finishings-changed'
        - 'printer-queue-order-changed'
        - 'printer-full'
        - 'printer-no-longer-full'
        - 'printer-almost-idle'
        - 'printer-not-almost-idle'

        Standard Service event types generalized from [IPP-NOT] are:
        - 'service-state-changed'
          - 'service-restarted'
          - 'service-shutdown'
        - 'service-config-changed'
          - 'service-media-changed'
          - 'service-finishings-changed'
        - 'service-queue-order-changed'
        - 'service-full'
        - 'service-no-longer-full'
        - 'service-almost-idle'
        - 'service-not-almost-idle'

        Conformance:    The natural language for keywords
        in subscribed event type SHALL always be US English.

        Conformance:    This job set index subscribed event type SHALL be valid
        and reported, if available on this managed system.

           See:    'jmGeneralJobSetIndex' object in [RFC-2707];
                   Section 4.3.2 'job-id' reported in [IPP-MOD]; ALL Job Monitoring MIB notifications.

        See:    Section 7 'Notification Content' 8.1 'notify-subscribed-event' in [IPP-NOT]."
    DEFVAL      { 0 ''H }                 -- no job set index notify subscribed event
    ::= { jmEventBinding 10 jmServiceEventEntry 2 }
   jmEventJobIndex

jmServiceEventNotifyTime OBJECT-TYPE
    SYNTAX      Integer32 (0..2147483647)      TimeTicks
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job index associated with time of this event
           or zero (if none).

           Conformance:    This job index service event.

        Usage:  Conforming management agents, which MUST implement the
        IETF MIB-II (RFC 1213), SHALL be valid
           and reported, if available on this managed system. set 'jmServiceEventNotifyTime' to
        'sysUpTime' when a service event row is created.

        See:    'jmJobIndex' object    'sysUpTime' in [RFC-2707]; IETF MIB-II (RFC 1213);
                Section 4.3.2 'job-id' 5.4.4 'notify-printer-up-time' in [IPP-MOD]; [IPP-NOT];
                Section 7 'Notification Content' 4.4.29 'printer-up-time' in [IPP-NOT]."
       DEFVAL      { 0 }                   -- no job index [IPP-MOD]."
    ::= { jmEventBinding 11 jmServiceEventEntry 3 }

   jmEventJobName

jmServiceEventServiceIndex OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..255))    -- 255 in [IPP-MOD]      Integer32 (1..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job name associated with unique identifier for this event
           or the empty string (if none).

           Conformance:    This job name SHALL be valid
           and reported, if available service on this managed system.

        See:    'jobName' attribute in [RFC-2707];
                   Section 4.3.5 'job-name' in [IPP-MOD];
                   Section 7 'Notification Content'    'jmServiceIndex' object in [IPP-NOT]."
       DEFVAL      { ''H }                 -- no job name this MIB."
    ::= { jmEventBinding 12 jmServiceEventEntry 4 }

   jmEventJobState

jmServiceEventServiceState OBJECT-TYPE
    SYNTAX      INTEGER {                       -- enum in [IPP-MOD]
           unknown(2),                     -- unknown job state
           pending(3),
           pendingHeld(4),
           processing(5),
           processingStopped(6),
           canceled(7),
           aborted(8),
           completed(9)
       }      JmServiceStateTC
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job state associated with of this event
           or 'unknown'.

           Note:   This object uses the keywords from managed service at the [IPP-MOD]
           enumerated type 'job-state' for coherence.

           Conformance:    This job state SHALL be valid
           and reported, if available on time of this managed system. event.

        See:    'jmJobState'    'jmServiceState' object in [RFC-2707];
                   Section 4.3.7 'job-state' this MIB;
                'jmJobState' object in [IPP-MOD]; this MIB;
                Section 7 'Notification Content' 4.4.11 'printer-state' in [IPP-NOT]." [IPP-MOD]."
    DEFVAL      { unknown }             -- unknown job service state
    ::= { jmEventBinding 13 jmServiceEventEntry 5 }

   jmEventJobStateReasons

jmServiceEventServiceStateReasons OBJECT-TYPE
    SYNTAX      OCTET STRING      SnmpAdminString (SIZE (0..255)) -- 255*n multi-valued in [IPP-MOD] IPP
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job service state reasons associated with this event service state
        (as a comma-separated list) or the empty string (if none).

           Conformance:    The natural language for keywords

        See:    'jmServiceStateReasons' object in job state reasons SHALL always be US English.

           Conformance:    These job state reasons SHALL be valid
           and reported, if available on this managed system.

           See: MIB;
                'jmJobStateReasons1' object in [RFC-2707];
                   'jobStateReasons2', 'jobStateReasons3', and
                   'jobStateReasons4' attributes in [RFC-2707];
                   Section 4.3.8 'job-state-reasons' in [IPP-MOD]; this MIB;
                Section 7 'Notification Content' 4.4.12 'printer-state-reasons' in [IPP-NOT]." [IPP-MOD]."
    DEFVAL      { ''H }                 -- no job service state reasons
    ::= { jmEventBinding 14 jmServiceEventEntry 6 }

4.2.3.  Job Event Group - Objects

--  The Job Event Group (CONDITIONALLY MANDATORY)
--
--  Implementation of this group is conditionally mandatory;
--  mandatory for systems which show Job events via SNMP.

--  The jmJobEventGroup consists entirely of the jmJobEventTable

jmJobEvent  OBJECT IDENTIFIER ::= { jobmonMIBObjects 9 }

jmJobEventTable  OBJECT-TYPE
    SYNTAX      SEQUENCE OF JmJobEventEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The jmJobEventTable contains job event entries for the
        jobs present on this managed system."
    ::= { jmJobEvent 1 }

jmJobEventEntry  OBJECT-TYPE
    SYNTAX      JmJobEventEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Basic job event information."
    INDEX  { jmJobEventIndex }
    ::= { jmJobEventTable 1 }

JmJobEventEntry ::= SEQUENCE {
    jmJobEventIndex                     Integer32 (1..2147483647),
    jmJobEventNotifyEvent               SnmpAdminString (SIZE (0..63)),
    jmJobEventNotifyTime                TimeTicks,
    jmJobEventJobSetIndex               Integer32 (1..32767),
    jmJobEventJobIndex                  Integer32 (1..2147483647),
    jmJobEventJobState                  JmJobStateTC,
    jmJobEventJobStateReasons           OCTET STRING (SIZE (4..16))
}

   jmEventJobKOctets

jmJobEventIndex OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647) (1..2147483647)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The unique identifier for this event on this managed system."
    ::= { jmJobEventEntry 1 }

jmJobEventNotifyEvent OBJECT-TYPE
    SYNTAX      SnmpAdminString (SIZE (0..63))   -- 255 in [IPP-NOT]
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job size event type that created this row in 'jmJobEventTable'.

        Standard Job event types defined in [IPP-NOT] are:
        - 'job-state-changed'
          - 'job-created'
          - 'job-completed'
          - 'job-purged'
        - 'job-config-changed'
        - 'job-progress'

        Conformance:    The natural language for keywords
        in K octets associated with this subscribed event
           or zero (if none) or '-2' (if unknown). type SHALL always be US English.

        Conformance:    This job size subscribed event type SHALL be valid
        and reported, if available on this managed system.

           See:    'jobKOctetsTransferred' attribute in [RFC-2707];
                   Section 4.3.17.1 'job-k-octets' reported in [IPP-MOD]; ALL Job Monitoring MIB notifications.

        See:    Section 7 'Notification Content' 8.1 'notify-subscribed-event' in [IPP-NOT]."
    DEFVAL      { -2 ''H }                 -- unknown job size no notify subscribed event
    ::= { jmEventBinding 15 jmJobEventEntry 2 }
   jmEventJobKOctetsProcessed

jmJobEventNotifyTime OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647)      TimeTicks
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job progress in K octets associated with time of this event
           or zero (if none) or '-2' (if unknown).

           Conformance:    This job progress event.

        Usage:  Conforming management agents, which MUST implement the
        IETF MIB-II (RFC 1213), SHALL be valid
           and reported, if available on this managed system. set 'jmJobEventNotifyTime' to
        'sysUpTime' when a job event row is created.

        See:    'jmJobKOctetsProcessed' object    'sysUpTime' in [RFC-2707]; IETF MIB-II (RFC 1213);
                Section 4.3.18.1 'job-k-octets-processed' 5.4.4 'notify-printer-up-time' in [IPP-MOD]; [IPP-NOT];
                Section 7 'Notification Content' 4.4.29 'printer-up-time' in [IPP-NOT]."
       DEFVAL      { -2 }                  -- unknown job progress [IPP-MOD]."
    ::= { jmEventBinding 16 jmJobEventEntry 3 }

   jmEventJobImpressions

jmJobEventJobSetIndex OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647) (1..32767)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job size in impressions associated with unique identifier for this event
           or zero (if none) or '-2' (if unknown).

           Conformance:    This job size SHALL be valid
           and reported, if available set on this managed system.

        See:    Section 4.3.17.2 'job-impressions' in [IPP-MOD];
                   Section 7 'Notification Content'    'jmGeneralJobSetIndex' object in [IPP-NOT]."
       DEFVAL      { -2 }                  -- unknown job size this MIB."
    ::= { jmEventBinding 17 jmJobEventEntry 4 }

   jmEventJobImpressionsCompleted

jmJobEventJobIndex OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647) (1..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job progress in impressions associated with unique identifier for this event
           or zero (if none) or '-2' (if unknown).

           Conformance:    This job progress SHALL be valid
           and reported, if available on this managed system. system,
        when prefixed with 'jmJobEventJobSetIndex'.

        See:    'jmJobImpressionsCompleted'    'jmJobIndex' object in [RFC-2707];
                   Section 4.3.18.2 'job-impressions-completed'
                   in [IPP-MOD];
                   Section 7 'Notification Content' in [IPP-NOT]."
       DEFVAL      { -2 }                  -- unknown job progress this MIB."
    ::= { jmEventBinding 18 jmJobEventEntry 5 }

   jmEventJobMediaSheets

jmJobEventJobState OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647)      JmJobStateTC
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job size in media sheets associated with state of this event
           or zero (if none) or '-2' (if unknown).

           Conformance:    This managed job size SHALL be valid
           and reported, if available on at the time of this managed system. event.

        See:    'sheetsRequested' attribute in [RFC-2707];
                   Section 4.3.17.3 'job-media-sheets'    'jmJobState' in [IPP-MOD]; this MIB;
                Section 7 'Notification Content' 4.3.7 'job-state' in [IPP-NOT]." [IPP-MOD]."
    DEFVAL      { -2 unknown }             -- unknown job size state
    ::= { jmEventBinding 19 jmJobEventEntry 6 }

   jmEventJobMediaSheetsCompleted

jmJobEventJobStateReasons OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647)      OCTET STRING (SIZE (4..16)) -- multi-valued in IPP
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job progress in media sheets state reasons associated with this event
           or zero (if none) or '-2' (if unknown).

           Conformance:    This job progress state
        represented as one to four concatenated 32-bit integers
        in network byte order (big-endian).

        Usage:  Conforming management stations SHALL be valid always report the
        value of the object 'jmJobStateReasons1' in the first four
        octets of 'jmJobEventJobStateReasons' and reported, if available on this managed system.

           See:    'sheetsCompleted' attribute SHOULD report values
        of the attributes 'jobStateReasons2', 'jobStateReasons3', and
        'jobStateReasons4' in [RFC-2707];
                   Section 4.3.18.3 'job-media-sheets-completed' subsequent octets.

        See:    'jmJobStateReasons1' in [IPP-MOD]; this MIB;
                Section 7 'Notification Content' 4.3.8 'job-state-reasons' in [IPP-NOT]." [IPP-MOD]."
    DEFVAL      { -2 '00000000'H }         -- unknown no job state reasons
    ::= { jmJobEventEntry 7 }

4.2.4.  Job Progress Group - Objects

--  The Job Progress Group (CONDITIONALLY MANDATORY)
--
--  Implementation of this group is conditionally mandatory;
--  mandatory for systems which send Job progress traps via SNMP.

--  The jmProgressGroup consists entirely of leaf objects for traps

jmProgress  OBJECT IDENTIFIER ::= { jmEventBinding 20 jobmonMIBObjects 10 }

   jmEventJobImpressionsCompletedCC

jmProgressJobCopiesRequested OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of copies of this job progress in impressions completed
           on requested by the current copy associated with client.

        See:    'jobCopiesRequested' attribute in this event
           or zero (if none) or '-2' (if unknown).

           Conformance:    This MIB."
    DEFVAL      { -2 }                  -- unknown job progress SHALL be valid
           and reported, if available on copies
    ::= { jmProgress 1 }

jmProgressJobCollationType OBJECT-TYPE
    SYNTAX      JmJobCollationTypeTC
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The number of copies of this managed system. job requested by the client.

        See:    'jmJobImpressionsCompleted' object    'jobCollationType' attribute in [RFC-2707];
                   'impressions-completed-current-copy' this MIB;
                'job-collation-type' in [IPP-PROG];
                Section 7 'Notification 9 'Event Notification Content' in [IPP-NOT]."
    DEFVAL      { unknown }             -- unknown job progress collation type
    ::= { jmEventBinding 21 jmProgress 2 }

   jmEventJobCollationType

jmProgressMediaSheetsCompleted OBJECT-TYPE
    SYNTAX      JmJobCollationTypeTC      Integer32 (-2..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job collation type associated with this event
           or 'unknown' (if unknown).

           Conformance:    This job collation type be valid
           and reported, if available on number of media sheets completed for this managed system. job.

        See:    'jobCollationType'    'sheetsCompleted' attribute in [RFC-2707];
                   'job-collation-type' this MIB;
                Section 4.3.18.3 'job-media-sheets-completed'
                in [IPP-PROG]; [IPP-MOD];
                Section 7 'Notification 9 'Event Notification Content' in [IPP-NOT]."
    DEFVAL      { unknown -2 }                  -- unknown job collation type progress
    ::= { jmEventBinding 22 jmProgress 3 }

   jmEventJobSheetCompletedCopyNum

jmProgressSheetCompletedCopyNum OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job progress number of the job copy currently being stacked for the
        current document associated with this event or zero (if none) or '-2' (if unknown).

           Conformance:    This job progress SHALL be valid
           and reported, if available on this managed system. (unknown).

        See:    'sheetCompletedCopyNumber' attribute in [RFC-2707]; this MIB;
                'sheet-completed-copy-number' in [IPP-PROG];
                Section 7 'Notification 9 'Event Notification Content' in [IPP-NOT]."
    DEFVAL      { -2 }                  -- unknown sheet complete copy number
    ::= { jmEventBinding 23 jmProgress 4 }

   jmEventJobSheetCompletedDocNum

jmProgressSheetCompletedDocNum OBJECT-TYPE
    SYNTAX      Integer32 (-2..2147483647)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The job progress number of the job document currently being stacked associated with this event for the
        current job or zero (if none) or '-2' (if unknown).

           Conformance:    This job progress SHALL be valid
           and reported, if available on this managed system. (unknown).

        See:    'sheetCompletedDocumentNumber' attribute in [RFC-2707]; this MIB;
                'sheet-completed-document-number' in [IPP-PROG];
                Section 7 'Notification 9 'Event Notification Content' in [IPP-NOT]."
    DEFVAL      { -2 }                  -- unknown document number sheet complete doc
    ::= { jmEventBinding 24 jmProgress 5 }

5.  IANA Considerations

   None.

6.  Internationalization Considerations

   The 'jmEventTriggerEvent', 'jmEventDeviceState', 'jmServiceStateReasons', 'jmServiceEventServiceStateReasons',
   'jmServiceEventNotifyEvent', and
   'jmEventDeviceStateReasons' 'jmJobEventNotifyEvent', text string
   objects defined in this document are of type 'JmUTF8StringTC' 'SnmpAdminString' (UTF-8
   stream-encoded ISO 10646/Unicode text) defined in the Job Monitoring SNMPv3
   Framework MIB [RFC-2707]. [RFC-2571].  The natural language of these objects is
   US English.

   The 'jmEventSubscriberUserName' text object defined in this document
   is of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode
   text) defined in the Job Monitoring MIB [RFC-2707].  The natural
   language of this object is inherently ambiguous (as it usually
   contains some transform of a personal name). English (they contain keywords).

7.  Security Considerations

   This IPP Notifications over SNMP mapping defines only 'read-only'
   objects.  It is suitable for use with any version of SNMP, as no
   update security is required (because no configuration updates are
   supported).

   No sensitive information is available via IPP Notifications over
   SNMP.

8.  References

   [IPP-MOD] R. deBry, T. Hastings, R. Herriot, S. Isaacson, P. Powell.
   IPP/1.1 Model and Semantics, <draft-ietf-ipp-model-v11-06.txt> <draft-ietf-ipp-model-v11-07.txt>
   (work-in-progress), March May 2000.

   [IPP-NOT] S. Isaacson, J. Martin, R. deBry, T. Hastings, M. Shepherd,
   R. Bergman.  IPP Event Notification Specification,
   <draft-ietf-ipp-not-spec-02.txt> (work-in-progress), March 2000.

   [IPP-PROG] T. Hastings, R. Bergman, H. Lewis.  Proposed Job Progress
   Attributes for IPP, <draft-ietf-ipp-job-prog.txt> <draft-ietf-ipp-job-prog-00.txt>
   (work-in-progress), February 2000.

   [RFC-1213] K. McCloghrie, M. Rose.  MIB-II, RFC 1213, March 1991.

   [RFC-1514] P. Grillo, S. Waldbusser.  Host Resources MIB, RFC 1514,
   September 1993.

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

   [RFC-2571] D. Harrington, R. Presuhn, B. Wijnen.  Architecture for
   SNMP Management Frameworks, RFC 2571, April 1999.

   [RFC-2573] D. Levi, P. Meyer, B. Stewart.  SNMP Applications, RFC
   2573, April 1999.

   [RFC-2576] R. Frye, D. Levi, S. Routhier, B. Wijnen.  Coexistence
   between Version 1, Version 2, and Version 3 of the Internet-standard
   Network Management Framework, RFC 2576, March 2000.

   [RFC-2707] R. Bergman, T. Hastings, S. Isaacson, H. Lewis.  Job
   Monitoring MIB v1.0, RFC 2707, November 1999

   [RFC-2790] P. Grillo, S. Waldbusser.  Host Resources MIB, RFC 2790,
   March 2000.

9.  Change Log

   Changes in reverse chronological order (most recent first).

   <draft-ietf-ipp-not-over-snmp-03.txt> - 6 July 2000
   1)  Added 'SnmpAdminString' to IMPORTS clause for new objects.
   2)  Corrected OID in MODULE-IDENTITY to use forward reference to
       definition of 'pwg' from 'enterprises' and 'mibs' from 'pwg'.
   3)  Added 'JmServiceStateTC' textual convention.
   4)  Added 'jmMirrorAttr' and 'jmSystem' object identifiers reserved
       for future extensions.
   5)  Major rewrite, per email discussion on IETF IPP WG list, to
       specify four new small (traditional) SNMP traps for:
       'jmServiceBasicV2Event' (generalized from IPP Printer event),
       'jmJobBasicV2Event' (corresponds IPP Job event),
       'jmJobCompletedV2Event' (corresponds IPP Job completed event),
       'jmJobProgressV2Event' (corresponds IPP Job progress event).
   6)  Major rewrite, per email discussion on IETF IPP WG list, to
       specify four new SNMP object groups:  'jmServiceTable' (name,
       URI, state, etc.  - from IPP Printer), 'jmServiceEventTable'
       (records IPP Printer events for polling), 'jmJobEventTable'
       (records IPP Job events for polling), 'jmJobProgressGroup' (leaf
       objects for IPP Job progress event).
   7)  Revised section 3.1 'SNMP Mapping for IPP Printer Events' and
       section 3.2 'SNMP Mapping for IPP Job Events', to agree with
       above.
   8)  Deleted obsolete section 3.3 'Rules for Encoding Notifications',
       as event bindings now always fit over all SNMP transport
       protocols.

   <draft-ietf-ipp-not-over-snmp-02.txt> - 19 March 2000
   1)  Renamed Printer Event notification group to Device Basic Event
       and 'jmPrinterEventV2Event' notification to
       'jmDeviceBasicV2Event', to better align with IPP and to support
       non-printing jobs.
   2)  Revised 'jmDeviceBasicV2Event' notification to remove
       'hrDeviceStatus', 'hrPrinterStatus',
       'hrPrinterDetectedErrorState' from mandatory trap bindings
       because they were redundant, per request of Ron Bergman.
   3)  Renamed Job Event notification group to Job Basic Event and
       'jmJobEventV2Event' notification to 'jmJobBasicV2Event', to
       better align with IPP and to support variant job events.
   4)  Defined new Job Completed Event notification group and defined
       new Job Progress Event notification group, to better align with
       IPP and to support variant job events.
   5)  Renamed Event object group to Event Binding,
       'jmEventPrinterState' to 'jmEventDeviceState',
       'jmEventPrinterStateReasons' to 'jmEventDeviceStateReasons',
       'jmEventPrinterIsAcceptingJobs' to
       'jmEventDeviceIsAcceptingJobs', to support non-printing jobs.
   6)  Revised Event Binding object group, adding explicit objects
       'jmEventDeviceURI', 'jmEventDeviceName', 'jmEventJobSetIndex',
       'jmEventJobIndex', 'jmEventJobName', 'jmEventJobState',
       'jmEventJobStateReasons', 'jmEventJobKOctets',
       'jmEventJobKOctetsProcessed', 'jmEventJobImpressions',
       'jmEventJobImpressionsCompleted', 'jmEventJobMediaSheets',
       'jmEventJobMediaSheetsCompleted',
       'jmEventJobImpressionsCompletedCC', 'jmEventJobCollationType',
       'jmEventJobSheetCompletedCopyNum',
       'jmEventJobSheetCompletedDocNum', per request of Ron Bergman.
   7)  Revised SYNTAX of 'jmEventTriggerEvent' object from from
       'JmUTF8StringTC' (string) to IPP-aligned enumeration, per request
       of Ron Bergman.
   8)  Removed all references to Printer MIB v2, as they were of limited
       value, per request of Ron Bergman.
   9)  Revised 'SNMP Mapping for IPP Printer Events' section for renamed
       event binding objects, per request of Ron Bergman.
   10) Revised 'Rules for Encoding Notifications' section to truncate
       additional string bindings, per request of Ron Bergman.
   11) Revised 'Registration via IPP' section, to change scheme name
       from 'ipp-snmp:' to 'snmpnotify:', per request of Ron Bergman.

   <draft-ietf-ipp-not-over-snmp-01.txt> - 1 December 1999
   1)  Deleted 'JmTriggerEventTC' textual convention (see below).
   2)  Revised SYNTAX of 'jmEventTriggerEvent' object from
       'JmTriggerEventTC' (enumeration) to 'JmUTF8StringTC' (string), to
       support use of IPP standard keywords.
   3)  Added 'jmEventPrinterState', 'jmEventPrinterStateReasons', and
       'jmEventPrinterIsAcceptingJobs' objects for consistency w/
       [IPP-NOT] and to reduce ambiguity about printer states inherent
       in RFC 1759.
   4)  Revised DESCRIPTION of 'jmPrinterEventV2Event' notification to
       add SHOULD (recommendation) for 'jmEventPrinterState',
       'jmEventPrinterStateReasons', and 'jmEventPrinterIsAcceptingJobs'
       objects.
   5)  Revised 'SNMP Mapping for IPP Printer Events' section to add
       direct mapping of IPP notification attributes to
       'jmEventPrinterState', 'jmEventPrinterStateReasons', and
       'jmEventPrinterIsAcceptingJobs' objects.
   6)  Revised 'Rules for Encoding Notifications' section to add
       'jmEventPrinterState' and 'jmEventPrinterStateReasons'.
   7)  Revised 'IANA Considerations' section to specify there are none -
       no enumerated or keyword textual conventions are now defined in
       this document.
   8)  Revised 'Internationalization Considerations' section to specify
       that US English keywords are used in 'jmEventTriggerEvent',
       'jmEventPrinterState', and 'jmEventPrinterStateReasons' objects
       and thus no explicit natural language tagging is required.

   <draft-ietf-ipp-not-over-snmp-00.txt> - 10 October 1999
   1)  Initial version.

10.  Intellectual Property Notice

   The IETF takes no position regarding the validity or scope of any
   intellectual property or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; neither does it represent that it
   has made any effort to identify any such rights.  Information on the
   IETF's procedures with respect to rights in standards-track and
   standards-related documentation can be found in BCP-11.  Copies of
   claims of rights made available for publication and any assurances of
   licenses to be made available, or the result of an attempt made to
   obtain a general license or permission for the use of such
   proprietary rights by implementers or users of this specification can
   be obtained from the IETF Secretariat.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights which may cover technology that may be required to practice
   this standard.  Please address the information to the IETF Executive
   Director.

11.  Authors' Addresses

   Tom Hastings
   Xerox Corporation
   701 S Aviation Blvd, MS 834-03E
   El Segundo, CA  90245

   Phone: +1 310-333-6413
   Email: hastings@cp10.es.xerox.com

   Ira McDonald
   High North Inc
   221 Ridge Ave
   Grand Marais, MI  49839

   Phone: +1 906-494-2434 or +1 906-494-2697
   Email: imcdonald@sharplabs.com
   Email: imcdonal@sdsp.mc.xerox.com

12.  Full Copyright Statement

   Copyright (C) The Internet Society (2000).  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.