draft-ietf-ipp-not-over-snmp-00.txt   draft-ietf-ipp-not-over-snmp-01.txt 
Internet Printing Protocol Working Group Tom Hastings Internet Printing Protocol Working Group Tom Hastings
INTERNET DRAFT Xerox INTERNET DRAFT Xerox
Expires 10 April 2000 Ira McDonald Expires 1 June 2000 Ira McDonald
High North High North
10 October 1999 1 December 1999
Internet Printing Protocol/1.1: Notifications over SNMP Internet Printing Protocol/1.1: Notifications over SNMP
<draft-ietf-ipp-not-over-snmp-00.txt> <draft-ietf-ipp-not-over-snmp-01.txt>
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
To view the list of Internet-Draft Shadow Directories, see 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. http://www.ietf.org/shadow.html.
Abstract Abstract
This document is a submission to the Internet Printing Protocol This document is a submission to the Internet Printing Protocol
Working Group of the Internet Engineering Task Force (IETF). Working Group of the Internet Engineering Task Force (IETF).
Comments should be submitted to the ipp@pwg.org mailing list. Comments should be submitted to the ipp@pwg.org mailing list.
This document proposes a mapping of IPP notifications over SNMP, This document proposes a mapping of IPP notifications over SNMP,
using new Printer Event and Job Event traps (to be added to the PWG using new Printer Event and Job Event traps (to be added to the PWG
Job Monitoring MIB [PWG-JOB]). This mapping may be used to deliver Job Monitoring MIB [PWG-JOB]). This mapping may be used to deliver
printer notifications for any printer (not just IPP-capable ones) and printer notifications for any printer (not just IPP-capable ones) and
also job notifications for any job (not just ones submitted via IPP). also job notifications for any job (not just ones submitted via IPP).
This document proposes: (2) SNMP traps; (1) SNMP textual convention; This document proposes: (2) SNMP traps; and (7) SNMP leaf objects
and (4) SNMP leaf objects (for use in trap bindings). (for use in trap bindings).
Table of Contents Table of Contents
1. Introduction ............................................... 3 1. Introduction ............................................... 3
1.1. Terminology for Conformance ............................ 3 1.1. Terminology for Conformance ............................ 3
2. SNMP Network Management Framework .......................... 3 2. SNMP Network Management Framework .......................... 3
3. Managed Object Mapping ..................................... 3 3. Managed Object Mapping ..................................... 3
3.1. SNMP Mapping for IPP Printer Events .................... 3 3.1. SNMP Mapping for IPP Printer Events .................... 3
3.2. SNMP Mapping for IPP Job Events ........................ 4 3.2. SNMP Mapping for IPP Job Events ........................ 4
3.3. Rules for Encoding Notifications ....................... 4 3.3. Rules for Encoding Notifications ....................... 4
3.4. Registration for IPP Notifications ..................... 5 3.4. Registration for IPP Notifications ..................... 5
3.4.1. Registration via IPP ............................... 5 3.4.1. Registration via IPP ............................... 5
3.4.2. Registration via SNMP .............................. 5 3.4.2. Registration via SNMP .............................. 5
3.5. Relationship to other MIBs ............................. 6 3.5. Relationship to other MIBs ............................. 6
3.5.1. IETF Host Resources MIB (RFC 1514) ................. 6 3.5.1. IETF Host Resources MIB (RFC 1514) ................. 6
3.5.2. IETF Printer MIB (RFC 1759) ........................ 6 3.5.2. IETF Printer MIB (RFC 1759) ........................ 6
3.5.3. Printer MIB v2 (work-in-progress) .................. 6 3.5.3. Printer MIB v2 (work-in-progress) .................. 7
4. Managed Object Definitions ................................. 8 4. Managed Object Definitions ................................. 8
4.1. Printer Event Trap ..................................... 8 4.1. Printer Event Trap ..................................... 8
4.1.1. jmPrinterEventV2Event (notification) ............... 8 4.1.1. jmPrinterEventV2Event (notification) ............... 8
4.2. Job Event Trap ......................................... 9 4.2. Job Event Trap ......................................... 9
4.2.1. jmJobEventV2Event (notification) ................... 9 4.2.1. jmJobEventV2Event (notification) ................... 9
4.3. Trigger Events ......................................... 10 4.3. Event Objects .......................................... 10
4.3.1. JmTriggerEventTC (textual convention) .............. 10 4.3.1. jmEventTriggerEvent (object) ....................... 11
4.4. Event Objects .......................................... 11 4.3.2. jmEventSubscriptionID (object) ..................... 11
4.4.1. jmEventTriggerEvent (object) ....................... 11 4.3.3. jmEventSubscriberUserName (object) ................. 11
4.4.2. jmEventSubscriptionID (object) ..................... 11 4.3.4. jmEventSubscriberUserData (object) ................. 12
4.4.3. jmEventSubscriberUserName (object) ................. 12 4.3.5. jmEventPrinterState (object) ....................... 12
4.4.4. jmEventSubscriberUserData (object) ................. 12 4.3.6. jmEventPrinterStateReasons (object) ................ 13
5. IANA Considerations ........................................ 13 4.3.7. jmEventPrinterIsAcceptingJobs (object) ............. 13
6. Internationalization Considerations ........................ 13 5. IANA Considerations ........................................ 14
7. Security Considerations .................................... 13 6. Internationalization Considerations ........................ 14
8. References ................................................. 14 7. Security Considerations .................................... 14
9. Intellectual Property Notice ............................... 14 8. References ................................................. 15
10. Authors' Addresses ........................................ 14 9. Change Log ................................................. 15
11. Full Copyright Statement .................................. 15 10. Intellectual Property Notice .............................. 16
11. Authors' Addresses ........................................ 16
12. Full Copyright Statement .................................. 17
1. Introduction 1. Introduction
The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer The IPP protocol [IPP-PRO] supports passive monitoring of IPP Printer
and Job objects, via client polling of IPP object attributes using and Job objects, via client polling of IPP object attributes using
the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations. the 'Get-Printer-Attributes' and 'Get-Job-Attributes' operations.
This IPP Notifications over SNMP mapping supports dynamic monitoring This IPP Notifications over SNMP mapping supports dynamic monitoring
of IPP Printer and Job objects, via server generation of SNMP traps. of IPP Printer and Job objects, via server generation of SNMP traps.
skipping to change at page 4, line 4 skipping to change at page 4, line 4
printer-uri [prtChannelInformation in PMv2] printer-uri [prtChannelInformation in PMv2]
printer-name [prtGeneralPrinterName in PMv2] printer-name [prtGeneralPrinterName in PMv2]
job-id jmJobIndex in OID instance suffix job-id jmJobIndex in OID instance suffix
job-name jobName job-name jobName
trigger-event jmEventTriggerEvent trigger-event jmEventTriggerEvent
trigger-time [time-stamp in SNMP trap header] trigger-time [time-stamp in SNMP trap header]
trigger-date-time hrSystemDate in Host Res MIB trigger-date-time hrSystemDate in Host Res MIB
subscription-id jmEventSubscriptionID subscription-id jmEventSubscriptionID
subscriber-user-name jmEventSubscriberUserName subscriber-user-name jmEventSubscriberUserName
subscriber-user-data jmEventSubscriberUserData subscriber-user-data jmEventSubscriberUserData
printer-state hrDeviceStatus in Host Res MIB printer-state jmEventEventPrinterState
hrDeviceStatus in Host Res MIB
hrPrinterStatus in Host Res MIB hrPrinterStatus in Host Res MIB
printer-state-reasons hrPrinterDetectedErrorState printer-state-reasons jmEventPrinterStateReasons
hrPrinterDetectedErrorState
in Host Res MIB in Host Res MIB
printer-is-accepting-jobs [no mapping] printer-is-accepting-jobs jmEventPrinterIsAcceptingJobs
3.2. SNMP Mapping for IPP Job Events 3.2. SNMP Mapping for IPP Job Events
IPP Job event attribute Printer/Job MIB object mapping IPP Job event attribute Printer/Job MIB object mapping
----------------------- ------------------------------ ----------------------- ------------------------------
version-number [no mapping - not useful] version-number [no mapping - not useful]
status-code [implicit in generated trap] status-code [implicit in generated trap]
request-id [request-id in SNMP trap header] request-id [request-id in SNMP trap header]
attributes-charset [no mapping - strings are UTF-8] attributes-charset [no mapping - strings are UTF-8]
attributes-natural-language [no mapping - no text bindings] attributes-natural-language [no mapping - no text bindings]
skipping to change at page 5, line 19 skipping to change at page 5, line 22
1a) If all variable-bindings now fit within the MTU, 1a) If all variable-bindings now fit within the MTU,
then exit this procedure and generate the SNMP trap. then exit this procedure and generate the SNMP trap.
2) Truncate the next one of the following string objects to 2) Truncate the next one of the following string objects to
the empty string (zero length in the ASN.1 BER encoding), the empty string (zero length in the ASN.1 BER encoding),
in the order listed: in the order listed:
- 'prtChannelInformation' (from Printer MIB v2 [PRT-MIB2]) - 'prtChannelInformation' (from Printer MIB v2 [PRT-MIB2])
- 'prtGeneralPrinterName' (from Printer MIB v2 [PRT-MIB2]) - 'prtGeneralPrinterName' (from Printer MIB v2 [PRT-MIB2])
- 'jmEventSubscriberUserName' - 'jmEventSubscriberUserName'
- 'jmEventSubscriberUserData' - 'jmEventSubscriberUserData'
- 'jmAttributeValue...jobName.1' - 'jmAttributeValue...jobName.1'
- 'jmEventPrinterStateReasons'
- 'jmEventPrinterState'
2a) If all variable-bindings now fit within the MTU, 2a) If all variable-bindings now fit within the MTU,
then exit this procedure and generate the SNMP trap. then exit this procedure and generate the SNMP trap.
2b) If all variable-bindings do NOT fit within the MTU, 2b) If all variable-bindings do NOT fit within the MTU,
then repeat step (2) for next string object. then repeat step (2) for next string object.
3) If all variable-bindings do NOT fit within the MTU, 3) If all variable-bindings do NOT fit within the MTU,
then -> logic error (variable-bindings MUST now fit). then -> logic error (variable-bindings MUST now fit).
3.4. Registration for IPP Notifications 3.4. Registration for IPP Notifications
IPP Clients may register for IPP Notifications delivered via SNMP by IPP Clients may register for IPP Notifications delivered via SNMP by
skipping to change at page 8, line 51 skipping to change at page 8, line 51
Additional variable-bindings SHALL be appended to this trap Additional variable-bindings SHALL be appended to this trap
for all printer-level events: for all printer-level events:
- Systems that support 'jobName' SHALL add - Systems that support 'jobName' SHALL add
'jmAttributeValue...jobName.1' (if job-level subscription) 'jmAttributeValue...jobName.1' (if job-level subscription)
- Systems that support 'hrSystemDate' defined in - Systems that support 'hrSystemDate' defined in
the IETF Host Resources MIB (RFC 1514) SHALL add the IETF Host Resources MIB (RFC 1514) SHALL add
'hrSystemDate' (corresponds to IPP 'printer-current-time') 'hrSystemDate' (corresponds to IPP 'printer-current-time')
Additional variable-bindings SHOULD be appended to this trap Additional variable-bindings SHOULD be appended to this trap
for all printer-level events: for all printer-level events:
- Systems that support the model of printer states defined
in the (work-in-progress) IPP Model and Semantics [IPP-MOD]
SHOULD add
'jmEventPrinterState' (corresponds to IPP 'printer-state'),
'jmEventPrinterStateReasons' (corresponds to IPP
'printer-state-reasons'), and
'jmEventPrinterIsAcceptingJobs' (corresponds to IPP
'printer-is-accepting-jobs')
- Systems that support 'prtChannelInformation' defined in - Systems that support 'prtChannelInformation' defined in
the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add
'prtChannelInformation' (corresponds to IPP 'printer-uri') 'prtChannelInformation' (corresponds to IPP 'printer-uri')
- Systems that support 'prtGeneralPrinterName' defined in - Systems that support 'prtGeneralPrinterName' defined in
the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add the (work-in-progress) Printer MIB v2 [PRT-MIB2] SHOULD add
'prtGeneralPrinterName' (corresponds to IPP 'printer-name') 'prtGeneralPrinterName' (compare to IPP 'printer-name')
Systems MAY add other variable-bindings from any MIB." Systems MAY add other variable-bindings from any MIB."
::= { jmPrinterEventV2EventPrefix 1 } ::= { jmPrinterEventV2EventPrefix 1 }
4.2. Job Event Trap 4.2. Job Event Trap
-- Job Event Group (Cond Mandatory) -- Job Event Group (Cond Mandatory)
-- --
-- Implementation of this group is conditionally mandatory; -- Implementation of this group is conditionally mandatory;
-- mandatory for systems which send this Job event via SNMP. -- mandatory for systems which send this Job event via SNMP.
skipping to change at page 10, line 35 skipping to change at page 10, line 44
- Systems that support the respective attributes SHALL add - Systems that support the respective attributes SHALL add
'jmAttributeValue...jobCollationType.1' 'jmAttributeValue...jobCollationType.1'
'jmAttributeValue...sheetCompletedCopyNumber.1' 'jmAttributeValue...sheetCompletedCopyNumber.1'
'jmAttributeValue...sheetCompletedDocumentNumber.1' 'jmAttributeValue...sheetCompletedDocumentNumber.1'
'jmAttributeValue...impressionsInterpreted.1' 'jmAttributeValue...impressionsInterpreted.1'
'jmAttributeValue...impressionsCompletedCurrentCopy.1' 'jmAttributeValue...impressionsCompletedCurrentCopy.1'
Systems MAY add other variable-bindings from any MIB." Systems MAY add other variable-bindings from any MIB."
::= { jmJobEventV2EventPrefix 1 } ::= { jmJobEventV2EventPrefix 1 }
4.3. Trigger Events 4.3. Event Objects
JmTriggerEventTC ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The trigger event type associated with this event.
See: Section 5.2 'notify-events' and
Section 7 'Notification Content' in [IPP-NOT]."
SYNTAX INTEGER {
other(1),
unknown(2),
none(3), -- SHOULD not be used
printerRestarted(11), -- 'printer-restarted'
printerShutdown(12), -- 'printer-shutdown'
printerStateChanged(13), -- 'printer-state-changed'
printerMediaChanged(14), -- 'printer-media-changed'
printerConfigChanged(15), -- 'printer-config-changed'
printerQueueChanged(16), -- 'printer-queue-changed'
printerNoLongerFull(17), -- 'printer-no-longer-full'
printerAlmostIdle(18), -- 'printer-almost-idle'
jobCreated(21), -- 'job-created'
jobCompleted(22), -- 'job-completed'
jobStateChanged(23), -- 'job-state-changed'
jobConfigChanged(24), -- 'job-config-changed'
jobPurged(25), -- 'job-purged'
jobProgress(26) -- 'job-progress'
}
4.4. Event Objects
-- Event Group (Cond Mandatory) -- Event Group (Cond Mandatory)
-- --
-- Implementation of this group is conditionally mandatory; -- Implementation of this group is conditionally mandatory;
-- mandatory for systems which support Job events via SNMP. -- mandatory for systems which send Printer or Job events via SNMP.
jmEvent OBJECT IDENTIFIER ::= { jobmonMIBObjects 5 } jmEvent OBJECT IDENTIFIER ::= { jobmonMIBObjects 5 }
jmEventTriggerEvent OBJECT-TYPE jmEventTriggerEvent OBJECT-TYPE
SYNTAX JmTriggerEventTC SYNTAX JmUTF8StringTC (SIZE (0..63)) -- 255 in [IPP-MOD]
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The trigger event type associated with this event. "The trigger event type associated with this event.
Conformance: This trigger event type SHALL be valid and Conformance: The natural language for keywords
consistent with [IPP-NOT]. in trigger event type SHALL always be US English.
Conformance: This trigger event type SHALL be valid.
See: Section 5.2 'notify-events' and See: Section 5.2 'notify-events' and
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
-- DEFVAL intentionally omitted - trigger event SHALL be valid -- DEFVAL intentionally omitted - reported value SHALL be valid
::= { jmEvent 1 } ::= { jmEvent 1 }
jmEventSubscriptionID OBJECT-TYPE jmEventSubscriptionID OBJECT-TYPE
SYNTAX Integer32 (0..2147483647) SYNTAX Integer32 (0..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subscription identifier associated with this event "The subscription identifier associated with this event
or zero (if none). or zero (if none).
skipping to change at page 12, line 16 skipping to change at page 11, line 49
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The subscriber user name associated with this event "The subscriber user name associated with this event
or the empty string (if none). or the empty string (if none).
Note: The natural language appropriate for text-to-speech Note: The natural language appropriate for text-to-speech
of subscriber user name is orthogonal to the localized text of subscriber user name is orthogonal to the localized text
context in IPP 'attributes-natural-language'. The subscriber context in IPP 'attributes-natural-language'. The subscriber
user name MAY include an in-line 'language tag' using Plane user name MAY include an in-line 'language tag' using Plane
14 'language tag' characters proposed for ISO 10646/Unicode. 14 'language tag' characters approved for ISO 10646/Unicode.
Conformance: This subscriber user name SHALL be valid Conformance: This subscriber user name SHALL be valid
and non-empty, if available on this managed system. and conserved, if available on this managed system.
See: Section 4.3.6 'job-originating-user-name' and 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' Section 4.4.2 'uri-authentication-supported'
(usage of 'requesting-user-name') in [IPP-MOD]; (usage of 'requesting-user-name') in [IPP-MOD];
Section 5.11 'subscriber-user-name' and Section 5.11 'subscriber-user-name' and
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no subscriber user name DEFVAL { ''H } -- no subscriber user name
::= { jmEvent 3 } ::= { jmEvent 3 }
jmEventSubscriberUserData OBJECT-TYPE jmEventSubscriberUserData OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..63)) -- 63 in [IPP-NOT] SYNTAX OCTET STRING (SIZE (0..63)) -- 63 in [IPP-NOT]
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 13, line 5 skipping to change at page 12, line 31
or the empty string (if none). or the empty string (if none).
Conformance: This subscriber user data SHALL be valid Conformance: This subscriber user data SHALL be valid
and conserved, if available on this managed system. and conserved, if available on this managed system.
See: Section 5.4 'subscriber-user-data' and See: Section 5.4 'subscriber-user-data' and
Section 7 'Notification Content' in [IPP-NOT]." Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no subscriber user data DEFVAL { ''H } -- no subscriber user data
::= { jmEvent 4 } ::= { jmEvent 4 }
jmEventPrinterState OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..31)) -- 255 in [IPP-MOD]
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The printer state associated with this event
or the empty string (if none).
Note: This object uses the keywords from the [IPP-MOD]
enumerated type 'printer-state', to avoid adding a new
textual convention to the PWG Job Monitoring MIB [PWG-JOB].
Conformance: The natural language for keywords
in printer state SHALL always be US English.
Conformance: This printer state SHALL be valid
and non-empty, if available on this managed system.
See: Section 4.4.11 'printer-state' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no printer state
::= { jmEvent 5 }
jmEventPrinterStateReasons OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..255)) -- 255*n in [IPP-MOD]
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The printer state reasons associated with this event
(as a comma-separated list) or the empty string (if none).
Conformance: The natural language for keywords
in printer state reasons SHALL always be US English.
Conformance: These printer state reasons SHALL be valid
and conserved, if available on this managed system.
See: Section 4.4.12 'printer-state-reasons' in [IPP-MOD];
Section 7 'Notification Content' in [IPP-NOT]."
DEFVAL { ''H } -- no printer state reasons
::= { jmEvent 6 }
jmEventPrinterIsAcceptingJobs OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The printer substate associated with this event
or 'true' (if unknown).
Conformance: This printer substate SHALL be valid
and conserved, 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 } -- printer is accepting jobs
::= { jmEvent 7 }
5. IANA Considerations 5. IANA Considerations
None - the only enumerated textual convention defined in this documen None - no enumerated textual conventions are defined in this
is proposed for addition to the PWG Job Monitoring MIB which is not a document.
IETF standards track document. The PWG does maintain a registration
process for updates to the PWG Job Monitoring MIB.
6. Internationalization Considerations 6. Internationalization Considerations
The 'jmEventSubscriberUserName' text string defined in this document The 'jmEventTriggerEvent', 'jmEventPrinterState', and
of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode text 'jmEventPrinterStateReasons' text objects defined in this document
defined in the PWG Job Monitoring MIB [PWG-JOB]. The natural languag are of type 'JmUTF8StringTC' (UTF-8 stream-encoded ISO 10646/Unicode
of this object is inherently ambiguous (as it usually contains some text) defined in the PWG Job Monitoring MIB [PWG-JOB]. The natural
transform of a personal name). 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 PWG Job Monitoring MIB [PWG-JOB]. The natural
language of this object is inherently ambiguous (as it usually
contains some transform of a personal name).
7. Security Considerations 7. Security Considerations
This IPP Notifications over SNMP mapping defines only 'read-only' This IPP Notifications over SNMP mapping defines only 'read-only'
objects. It is suitable for use with any version of SNMP, as no upda objects. It is suitable for use with any version of SNMP, as no
security is required (because no configuration updates are supported) update security is required (because no configuration updates are
supported).
No sensitive information is available via IPP Notifications over SNMP No sensitive information is available via IPP Notifications over
SNMP.
8. References 8. References
To be supplied. To be supplied.
9. Intellectual Property Notice 9. Change Log
Changes in reverse chronological order (most recent first).
<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 The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
skipping to change at page 14, line 31 skipping to change at page 16, line 27
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementers or users of this specification can proprietary rights by implementers or users of this specification can
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
10. Authors' Addresses 11. Authors' Addresses
Tom Hastings Tom Hastings
Xerox Corporation Xerox Corporation
701 S Aviation Blvd, MS 834-03E 701 S Aviation Blvd, MS 834-03E
El Segundo, CA 90245 El Segundo, CA 90245
Phone: +1 310-333-6413 Phone: +1 310-333-6413
Email: hastings@cp10.es.xerox.com Email: hastings@cp10.es.xerox.com
Ira McDonald Ira McDonald
High North Inc High North Inc
221 Ridge Ave 221 Ridge Ave
Grand Marais, MI 49839 Grand Marais, MI 49839
Phone: +1 906-494-2434 or +1 906-494-2697 Phone: +1 906-494-2434 or +1 906-494-2697
Email: imcdonal@sdsp.mc.xerox.com Email: imcdonald@sharplabs.com
11. Full Copyright Statement 12. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/