Re: RFC8011 is ambiguous for 'compression' attribute
Michael Sweet via ipp <[email protected]> Thu, 5 Feb 2026 18:54:22 -0500
| Newsgroups | gmane.ietf.ipp |
|---|---|
| Message-ID | <[email protected]> |
--===============2854805615883319575== Content-Type: multipart/alternative; boundary="Apple-Mail=_A7420A54-8F64-4A71-820D-1A94F1FD3A91" --Apple-Mail=_A7420A54-8F64-4A71-820D-1A94F1FD3A91 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Michael, > On Feb 5, 2026, at 4:37=E2=80=AFPM, Michael Ziller via ipp = <[email protected]> wrote: >=20 > create-job simply defers to print-job as far as attributes supplied: = https://datatracker.ietf.org/doc/html/rfc8011#section-4.2.4 The first paragraph of section 4.2.4 (Create-Job) says (highlighting is = mine): This RECOMMENDED operation is similar to the Print-Job operation (Section 4.2.1), except that in the Create-Job request, a Client does not supply Document data or any reference to Document data. Also, the Client does not supply any of the "document-name", "document-format", "compression", or "document-natural-language" operation attributes. This operation is followed by one or more Send-Document or Send-URI operations. In each of those operation requests, the Client MAY supply the "document-name", "document-format", and "document-natural-language" attributes for each Document in the Job. ________________________ Michael Sweet --Apple-Mail=_A7420A54-8F64-4A71-820D-1A94F1FD3A91 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" = content=3D"text/html; charset=3Dutf-8"></head><body = style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; = line-break: after-white-space;">Michael,<br = id=3D"lineBreakAtBeginningOfMessage"><br><blockquote type=3D"cite">On = Feb 5, 2026, at 4:37=E2=80=AFPM, Michael Ziller via ipp = <[email protected]> wrote:<br><br = class=3D"Apple-interchange-newline">create-job simply defers to = print-job as far as attributes = supplied: https://datatracker.ietf.org/doc/html/rfc8011#section-4.2.4= <br></blockquote><div><br></div>The first paragraph of section 4.2.4 = (Create-Job) says (highlighting is mine):<div><br></div><div><div> = This RECOMMENDED operation is similar to the Print-Job = operation</div><div> (Section 4.2.1), except that in the = Create-Job request, a Client does</div><div> not supply = Document data or any reference to Document data. <span = style=3D"background-color: rgb(255, 251, = 0);">Also,</span></div><div><span style=3D"background-color: rgb(255, = 251, 0);"> the Client does not supply any of the = "document-name",</span></div><div><span style=3D"background-color: = rgb(255, 251, 0);"> "document-format", "compression", or = "document-natural-language"</span></div><div><span = style=3D"background-color: rgb(255, 251, 0);"> operation = attributes.</span> This operation is followed by one or = more</div><div> Send-Document or Send-URI operations. = In each of those operation</div><div> requests, the = Client MAY supply the "document-name",</div><div> = "document-format", and "document-natural-language" attributes = for</div><div> each Document in the = Job.</div><div><br></div><div> ________________________<br>Michael Sweet<br> </div> <br></div></body></html>= --Apple-Mail=_A7420A54-8F64-4A71-820D-1A94F1FD3A91-- --===============2854805615883319575== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ ipp mailing list [email protected] https://www.pwg.org/mailman/listinfo/ipp --===============2854805615883319575==--