There was a formatting problem with the page headers in the .pdf file. Also
revision marks on section headers. So I've reposted the documents. If
you've already printed the original version there is no need to re-print the
new one, since no real content is changed.
Sorry,
Tom
> -----Original Message-----
> From: Hastings, Tom N
> Sent: Tuesday, April 06, 1999 11:34
> To: 'ipp'
> Subject: MOD - Updated IPP/1.1 Model with AGREED Issue resolutions
> from BakeOff2 for Wed telecon
>> For discussion on the DL and tomorrow's telecon, Wed, 4/7, 10-12 PDT (1-3
> EDT):
>> The updated IPP/1.1 Model and Semantics document is available with
> revision marks at:
>>ftp://ftp.pwg.org/pub/pwg/ipp/new_MOD/ipp-model-v11-990406-rev.doc>ftp://ftp.pwg.org/pub/pwg/ipp/new_MOD/ipp-model-v11-990406-rev.pdf>> with the proposed resolutions to the issues from the Bake Off 2.
>> This is an intermediate draft. We will be reviewing it on the
> distribution list and at the New Orleans meeting next week. The next
> Internet-Draft will be sent after the Last Call period ends at the end of
> April.
>> The change history and Differences from IPP/1.0 has not yet been updated.
>> Also we have not attempted to include the IPP/1.0 text, so that the
> IPP/1.1 document defined both IPP/1.0 and IPP/1.1 as agreed at the IETF
> meeting in March.
>> All issues 1-31 have proposed text except the following still OPEN issues:
>> 2) ISSUE: How can client force identified (authenticated) mode?
> 17) ISSUE: Client display of absolute time for job attributes?
> 30) ISSUE: Should "job-state-reasons" and "printer-state-reasons" be
> MUST in IPP/1.1?
> 31) ISSUE: How indicate a ripped job that is waiting for the marker?
>>> The following proposed issue resolutions only affect the Implementer's
> Guide; they do not affect the Model and Semantics document:
>> 7) ISSUE: Please implement Manufacturer make and model printer attribute
> and send the .INF file model name of the printer.
> 10) ISSUE: How distinguish between submit vs processing auto-sense?
> 16) ISSUE: Get-Printer-Attributes Polling
> 22) ISSUE: Status code on variable-length attributes that are 'too
> short'
>>