Hi Mike,
Bottom line - does that mean it's OK and appropriate to have the System
attributes
group (for System status changes from Printer operations) at the *end*
(last) of the
response attribute groups?
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto: blueroofmusic at gmail.com
Jan-April: 579 Park Place Saline, MI 48176 734-944-0094
May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434
On Mon, May 15, 2017 at 6:13 PM, Michael Sweet <msweet at apple.com> wrote:
> All,
>> Re: my pending action item:
>> Action: Mike to check on group ordering restrictions in CUPS
> (PENDING)
>> I have the following information to provide:
>> 1. The CUPS scheduler (cupsd) enforces the RFC 8011 group ordering in IPP
> requests.
>> 2. The ipptool utility enforces the RFC 8011 group ordering in IPP
> responses.
>> 3. The CUPS library (libcups) does not enforce the RFC 8011 group ordering
> for requests or responses.
>>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer
>> _______________________________________________
> ipp mailing list
>ipp at pwg.org>https://www.pwg.org/mailman/listinfo/ipp>-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20170515/f6ff9326/attachment.html>