No worries! But I'm not sure I get your feedback.
Are you suggesting that it would be better to eliminate the "job-presets-storage-available" and instead have the Printer indicate that it is not capable of accepting an additional Preset via Set-Printer-Attributes by withdrawing "job-presets-supported" from "printer-settable-attributes-supported" attribute? That seems like an "implicit" mechanism, but if we document it properly I guess it would work fine.
Or are you suggesting that a Client should just try it and if the Printer provides the "client-error-request-entity-too-large" status code, then it will know that it was rejected? That doesn't sound optimal. But if you are saying that this is the right status code to use, I'm all for using that.
Smith
> On Oct 9, 2017, at 4:58 PM, Michael Sweet <msweet at apple.com> wrote:
>> Apologies, after re-reading my response this sounds a bit harsh, which was not my intent. My point is just that we don't need to add another attribute - we already have one for this purpose... :)
>>>> On Oct 9, 2017, at 6:52 PM, Michael Sweet <msweet at apple.com> wrote:
>>>> Smith,
>>>>> On Oct 9, 2017, at 5:05 PM, Kennedy, Smith (Wireless Architect) <smith.kennedy at hp.com> wrote:
>>>>>> Greetings,
>>>>>> I posted an updated draft of IPP Presets to the PWG FTP site for review. It is available here:
>>>>>>http://ftp.pwg.org/pub/pwg/ipp/wd/tb-ipp-preset-20171009.pdf>>>http://ftp.pwg.org/pub/pwg/ipp/wd/tb-ipp-preset-20171009.odt>>>http://ftp.pwg.org/pub/pwg/ipp/wd/tb-ipp-preset-20171009-rev.pdf>>>http://ftp.pwg.org/pub/pwg/ipp/wd/tb-ipp-preset-20171009-rev.odt>>>>>> Changes include:
>>>>>> • Added the “job-presets-storage-available” attribute definition and semantics
>>>> That is not the way to advertise making these attributes settable.
>>>> RFC 3380 defines the Set-Printer-Attributes operation, its semantics, and the one attribute you use to determine which Printer attributes can be written - namely "printer-settable-attributes-supported".
>>>> If the "job-presets-supported" and/or "job-triggers-supported" attributes are settable using Set-Printer-Attributes, they must be listed in the "printer-settable-attributes-supported" attribute. Any limits to the sizes of the attributes are handled at request time through the "client-error-request-entity-too-large" status code - see section 4.1.3 of RFC 3380.
>>>>> • Added additional Client considerations and Printer behavior for error conditions when the submitted Preset contains unsupported values or lacks resources to store the Preset it received
>>>>>> Cheers,
>>> Smith
>>>>>> /**
>>> Smith Kennedy
>>> Wireless Architect - Client Software - IPG-PPS
>>> Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB IF
>>> Chair, IEEE ISTO Printer Working Group
>>> HP Inc.
>>> */
>>>>>>>>>>>> _______________________________________________
>>> ipp mailing list
>>>ipp at pwg.org>>>https://www.pwg.org/mailman/listinfo/ipp>>>> _________________________________________________________
>> Michael Sweet, Senior Printing System Engineer
>>>> _______________________________________________
>> ipp mailing list
>>ipp at pwg.org>>https://www.pwg.org/mailman/listinfo/ipp>> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4241 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20171010/a322fc72/attachment.p7s>