IPP> NOT - Updated Job Submission Notification spec posted

IPP> NOT - Updated Job Submission Notification spec posted

IPP> NOT - Updated Job Submission Notification spec posted

Hastings, Tom N hastings at cp10.es.xerox.com
Mon Dec 14 01:25:37 EST 1998


I sent this message out Friday and again on Saturday, but did not see it
arrive, so I'm sending it again tonight (Sunday).

Tom

>-----Original Message-----
>From:	Hastings, Tom N 
>Sent:	Saturday, December 12, 1998 04:41
>To:	'ipp'
>Subject:	NOT - Updated Job Submission Notification spec posted
>
>I've updated the notification specification.  I've removed a 
>lot in order to get agreement.
>Also to make it easier to agree on notification for use with 
>IFAX.  The files are at: 
>
>ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notifications-very-short-981210.p
df
>ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notifications-very-short-981210-r
ev.pdf
>ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notifications-very-short-981210.d
oc
>ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notifications-very-short-981210-r
ev.pdf
>ftp://ftp.pwg.org/pub/pwg/ipp/new_NOT/ipp-notifications-very-short-981210.t
xt
>
>There are a few issues highlighted throughout the document.
>
>I'll bring copies to the meeting.  Its only 13 pages.  I hope 
>we can spend some serious time with it and progress it.  It 
>would be nice if we could try some interoperability testing of 
>it in March.  A job submission protocol without notification is ...
>
>
>1.1	Changes made from the July 1, 1998 to the December 10, 
>1998 version
>The following changes made from the July 1, 1998 to make the 
>December 10, 1998 version:
>1.	Clarified the terminology so that an "event" doesn't 
>necessarily mean that a notification report is delivered.
>2.	Removed many of the job and printer attributes for 
>being sent in a notification event report, so that we can get 
>agreement on a basic set of notification content.  Only 
>attributes really needs are included, including what may be 
>needed for FAX.  Changed the names of the event groups by 
>adding the suffix '-basic' to indicate that these event groups 
>return only basic information.  Additional event groups can be 
>registered in order to get more attributes as needed for 
>accounting and more detailed job monitoring purposes.
>3.	Deleted the "job-progress" event group.  We can bring 
>it back when we agree to all of the extra attributes.  Its not 
>very useful with only the basic attributes.
>4.	The printer events are indicted using the 
>"printer-state-reasons" values, instead of the Printer MIB 
>alert codes.  Since most of the Printer MIB alert codes, 
>except for the generic ones, have equivalent IPP keyword 
>reason values, this should be a problem and makes IPP more 
>readably implemented in a server that doesn't have the Printer MIB.
>5.	Added the "job-last-event" job description attribute to 
>give the job event some persistence.
>6.	Changed the job's "time-at-event (integer)" to 
>"job-last-date-time-of-event (dateTime)" to give an absolute 
>date and time, in case events are being relayed back through 
>multiple servers, such as in FAX.  Also made it a Job 
>Description attribute to give it persistence.
>7.	Changed the printer's "time-at-event(integer)" to 
>"printer-last-date-time-of-event(dateTime)" to give an 
>absolute date and time, in case events are being relayed back 
>through multiple servers, such as in FAX.  Also made it a 
>Printer Description attribute to give it persistence.
>8.	Added the IPP/1.0 "printer-is-accepting-jobs" to the 
>event report, since changes in its value are really device 
>state changes.
>9.  Added the complete semantics for each job event under the 
>"last-job-event" Job Description attribute.
>Tom Hastings
>(310) 333-6413
>
>



More information about the Ipp mailing list