OK, I've reviewed your PDF. Some feedback:
- Slide 3: Aside from some server implementations, Clients pretty much universally have greater resources than Printers. And RFC 8011 places specific requirements on Client implementations WRT supporting all defined attribute syntaxes, including the collection attribute syntax used for job-presets-supported. So IMHO Client limitations are not a realistic concern for this attribute.
- Slide 5: There is no such thing as non-IPP attributes in a preset. They are all IPP attributes, and by definition the only member attribute in the collection that is not used by the Client as a Job Template attribute is the "preset-name" member attribute.
- Slide 6: Conforming client implementations MUST support all of the attribute syntaxes defined in RFC 8011, so this is not a realistic concern IMHO. We can make this explicit in the definition of job-presets-supported if you like, but it isn't explicitly necessary since the definition of the attribute says that the collection contains Job Template attributes to be copied to the job creation request.
> On Oct 26, 2017, at 6:14 AM, Takeshi KANEDA <kaneda.takeshi at canon.co.jp> wrote:
>>> Hello, Mr. Smith Kennedy.
> Hello, Mr. Michael Sweet.
>> This is Takeshi Kaneda at Canon Inc. Thank you for your opinions.
>> we would like to express our opinion on Canon as to the feedback we received.
> Please refer to attached file. The password is "ipp-preset".
>> If you have any questions, please reply this mail. (Even if you contact Rick, it is OK.)
>> Thank you.
> Takeshi KANEDA <kaneda.takeshi at canon.co.jp>
Michael Sweet, Senior Printing System Engineer