attachment
<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Andale Mono";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:123811852;
mso-list-type:hybrid;
mso-list-template-ids:-805530462 -1 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:20.25pt;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:56.25pt;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:92.25pt;
text-indent:-9.0pt;}
@list l0:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:128.25pt;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:164.25pt;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:200.25pt;
text-indent:-9.0pt;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:236.25pt;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:272.25pt;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
margin-left:308.25pt;
text-indent:-9.0pt;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Kaneda-san,</p><p class=MsoNormal>I would add the following to Michael’s comments, based on the IPP workgroup discussion:</p><ol style='margin-top:0in' start=1 type=1><li class=MsoNormal style='margin-left:-15.75pt;mso-list:l0 level1 lfo1'>We agree with your observation that the document is not clear with respect to “the client is responsible for copying the Job Template attributes from the job-presets-supported collection value to the job creation request” and that these preset-specified Job Template attribute values in the Job Creation request may be overwritten by the Client upon input from the User. The document will be updated so that this is clearly stated.</li><li class=MsoNormal style='margin-left:-15.75pt;mso-list:l0 level1 lfo1'>Because the client is to return the contents of the selected preset in the job creation request (except for values changed by the User or Client), regardless of whether or not the client displays the Preset collection to the user, the contents of the selected preset is returned to the printer (except for any attribute values changed). </li><li class=MsoNormal style='margin-left:-15.75pt;mso-list:l0 level1 lfo1'>If the printer needs to the know the preset selected, possibly for handling of non-standard IPP attributes that may be unknown to the Client, </li></ol><p class=MsoNormal>perhaps the best approach would be to include in the Preset a vendor extension attribute that would also be returned with the Job Template attributes.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thank you for your contribution to defining this proposed IPP capability.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Bill Wagner</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:msweet@apple.com">Michael Sweet</a><br><b>Sent: </b>Thursday, October 26, 2017 3:33 PM<br><b>To: </b><a href="mailto:kaneda.takeshi@canon.co.jp">Takeshi KANEDA</a><br><b>Cc: </b><a href="mailto:ipp@pwg.org">ipp@pwg.org</a>; <a href="mailto:hosoda.osamu@canon.co.jp">HOSODA Osamu</a><br><b>Subject: </b>Re: [IPP] [!!]Re: PWG: Canon proposal to extend the IPP Presetdraftspecification</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>WRT slide 5, during the IPP WG concall today the following question came up:<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>- What is meant by "non-IPP attributes"? Is it a vendor-specific attribute ("canon-foo", etc.), or is it out-of-band data associated with the named preset, or ???<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><p class=MsoNormal>On Oct 26, 2017, at 3:00 PM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<o:p></o:p></p></div><p class=MsoNormal><o:p> </o:p></p><div><div><p class=MsoNormal>OK, I've reviewed your PDF. Some feedback:<br><br>- 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.<br><br>- 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.<br><br>- 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.<br><br><br><br><o:p></o:p></p><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>On Oct 26, 2017, at 6:14 AM, Takeshi KANEDA <<a href="mailto:kaneda.takeshi@canon.co.jp">kaneda.takeshi@canon.co.jp</a>> wrote:<br><br><br>Hello, Mr. Smith Kennedy. <br>Hello, Mr. Michael Sweet.<br><br>This is Takeshi Kaneda at Canon Inc. Thank you for your opinions. <br><br>we would like to express our opinion on Canon as to the feedback we received. <br>Please refer to attached file. The password is "ipp-preset".<br><br>If you have any questions, please reply this mail. (Even if you contact Rick, it is OK.)<br><br>Thank you.<br>-- <br>Takeshi KANEDA <<a href="mailto:kaneda.takeshi@canon.co.jp">kaneda.takeshi@canon.co.jp</a>><br><IPP_Preset_improvement_proposal_20171025.pdf><o:p></o:p></p></blockquote><p class=MsoNormal><br>_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer<br><br>_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/ipp<o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal><span style='font-family:"Andale Mono",serif;color:black'>_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer<o:p></o:p></span></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>