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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
h1
{mso-style-priority:9;
mso-style-link:"Heading 1 Char";
margin-top:12.0pt;
margin-right:0in;
margin-bottom:0in;
margin-left:0in;
margin-bottom:.0001pt;
page-break-after:avoid;
font-size:16.0pt;
font-family:"Calibri Light",sans-serif;
color:#2F5496;
font-weight:normal;}
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;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
mso-add-space:auto;
line-height:115%;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast
{mso-style-priority:34;
mso-style-type:export-only;
margin-top:0in;
margin-right:0in;
margin-bottom:10.0pt;
margin-left:.5in;
mso-add-space:auto;
line-height:115%;
font-size:12.0pt;
font-family:"Arial",sans-serif;}
span.Heading1Char
{mso-style-name:"Heading 1 Char";
mso-style-priority:9;
mso-style-link:"Heading 1";
font-family:"Calibri Light",sans-serif;
color:#2F5496;}
.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:343212275;
mso-list-template-ids:67698717;}
@list l0:level1
{mso-level-text:"%1\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.25in;
text-indent:-.25in;}
@list l0:level2
{mso-level-number-format:alpha-lower;
mso-level-text:"%2\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.5in;
text-indent:-.25in;}
@list l0:level3
{mso-level-number-format:roman-lower;
mso-level-text:"%3\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:.75in;
text-indent:-.25in;}
@list l0:level4
{mso-level-text:"\(%4\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.0in;
text-indent:-.25in;}
@list l0:level5
{mso-level-number-format:alpha-lower;
mso-level-text:"\(%5\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.25in;
text-indent:-.25in;}
@list l0:level6
{mso-level-number-format:roman-lower;
mso-level-text:"\(%6\)";
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.5in;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:1.75in;
text-indent:-.25in;}
@list l0:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.0in;
text-indent:-.25in;}
@list l0:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
margin-left:2.25in;
text-indent:-.25in;}
@list l1
{mso-list-id:723914768;
mso-list-type:hybrid;
mso-list-template-ids:-1155502562 -1 209855960 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level2
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level3
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level4
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level5
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level6
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
text-indent:-9.0pt;}
@list l1:level7
{mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level8
{mso-level-number-format:alpha-lower;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;}
@list l1:level9
{mso-level-number-format:roman-lower;
mso-level-tab-stop:none;
mso-level-number-position:right;
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><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Greetings,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Some comments on this draft, largely prompted by observations during the last IPP conference. Sorry about the wordiness.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Comments made based on my understanding (or misunderstanding) of this proposed element, as it has evolved. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><ol style='margin-top:0in' start=1 type=1><li class=MsoListParagraphCxSpFirst style='margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo2'>The function of this password is to control access to a retained job. As evolved, it has been maintained that access is only for printing the job and access (as far as IPP is concerned) is only from a console on which the retained job is stored. [There might, one would assume, be non-IPP mechanisms, such as a remote console, or out-of-band communications whereby a user could request access to a job stored elsewhere, but once a job is tagged with a Job Reprint Password, access to the stored by someone not normally having access should require submission of the Job Reprint Password defined when the job was created.]</li><li class=MsoListParagraphCxSpMiddle style='margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo2'>I would argue that this should be a Job Description attribute rather than an Operation attribute, because it stays with the Job and is really an attribute of the job rather than any IPP operation. I also suggest that this attribute should not in itself cause Job Save, since IPP already has the “job-save-disposition” (collection) Job Template attribute and there are other implementation dependent job retention factors. This would also preclude the automatic saving of copied jobs.<o:p></o:p></li><li class=MsoListParagraphCxSpMiddle style='margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo2'>It may be desirable to make clear the distinction between Job Password, Document Password and Job Reprint Password in this specification. I would suggest a simple statement of the purpose of these three passwords.</li></ol><ol style='margin-top:0in' start=3 type=1><ol style='margin-top:0in' start=1 type=a><li class=MsoListParagraphCxSpMiddle style='margin-left:0in;mso-add-space:auto;mso-list:l1 level2 lfo2'>document-password [<a href="http://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext3v10-20120727-5100.13.pdf"><span style='color:windowtext;text-decoration:none'>PWG5100.13</span></a>] is an operation attribute provided with a Print-Job, Print-URI, Send-Document, or Send-URI operation to allow access to the document content, typically to "unlock" a previously password-protected PDF or OpenXPS document. The value supplied is retained by the Printer as long as the corresponding Document is retained.</li><li class=MsoListParagraphCxSpMiddle style='margin-left:0in;mso-add-space:auto;mso-list:l1 level2 lfo2'>job-password [<a href="http://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext10-20101030-5100.11.pdf"><span style='color:windowtext;text-decoration:none'>PWG5100.11</span></a>] is an operation attribute optionally provided with a Print-Job, Print-URI, or Create-Job operation to cause a submitted job to be held in a 'pending-held' state until the password value is submitted to the printing device. The method in which the password is entered and validated at the Printer is implementation dependent. The job-password value is not saved with the Job.</li><li class=MsoListParagraphCxSpMiddle style='margin-left:0in;mso-add-space:auto;mso-list:l1 level2 lfo2'>job-reprint-password is [<i>a Job Description or an operation attribute</i>] optionally provided with a Print-Job, Print-URI, or Create-Job operation that (if accepted by the Printer), causes the submitted job-reprint-password to be saved with the retained Job. It does not affect the processing of the job in any other way. Although IPP does allow a retained job to be reprinted via Resubmit-Job, this capability is only available if the user performing this operation is the job owner or an operator or administrator of the Printer object. However, if outside of IPP, the Printer provides a user with the ability to reprint retained jobs, and the desired Job has been tagged with a job-reprint-password, the user must supply that password to get access to the job for reprint (<i>or any other purpose?)</i></li></ol></ol><ol style='margin-top:0in' start=4 type=1><li class=MsoListParagraphCxSpMiddle style='margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo2'>As far as I can tell, reprinting a job is not a defined IPP operation nor is it clear to me why giving access to an IPP retained Job by some means other than IPP can restrict how that job is used. At any rate, from the discussion, the identified job (which is somehow selected by the user) is not itself affected in any way other than by being copied and, since "most operation attributes do not persist beyond the life of the operation" that new job is printed (whatever than might involve) following operation attributes defined by the user when he has, by whatever means outside of IPP, initiated "reprint" of a selected IPP job. </li><li class=MsoListParagraphCxSpLast style='margin-left:0in;mso-add-space:auto;mso-list:l1 level1 lfo2'>The original use case of allowing remote reprint was eliminated, although if the purpose of Job Reprint Password is solely to allow access to a retained IPP Job, (rather than to act as a Job Password for a reprinted Job), it would seem that remote reprint is a useful feature. Would it be that cumbersome to change an operation such as ResubmitJob to bestow job ownership (of the copied Job) to a user having the password? </li></ol><p class=MsoNormal style='margin-left:.25in'><span style='font-size:12.0pt;font-family:"Arial",sans-serif'>Thanks, Bill Wagner<o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt;font-family:"Arial",sans-serif'><o:p> </o:p></span></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:smith.kennedy@hp.com">Kennedy, Smith (Wireless & Standards Architec)</a><br><b>Sent: </b>Wednesday, June 20, 2018 2:06 PM<br><b>To: </b><a href="mailto:ipp@pwg.org">PWG IPP WG Reflector</a><br><b>Subject: </b>[IPP] Another updated stable draft of IPP Reprint Password postedfor review</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Greetings,</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I have posted another update to IPP Reprint Password. It is available here:</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippreprintpwd-20180620.pdf</p><p class=MsoNormal> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippreprintpwd-20180620.odt</p><p class=MsoNormal> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippreprintpwd-20180620-rev.pdf</p><p class=MsoNormal> https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippreprintpwd-20180620-rev.odt</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Changes in this revision include:</p><p class=MsoNormal>• Added a figure to section 3, and moved the section 4 preamble text added in the 2018-06-19 revision to be in section 3</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Cheers!</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Smith</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>/**</p><p class=MsoNormal> Smith Kennedy</p><p class=MsoNormal> Wireless & Standards Architect - IPG-PPS</p><p class=MsoNormal> Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF</p><p class=MsoNormal> Chair, IEEE ISTO Printer Working Group</p><p class=MsoNormal> HP Inc.</p><p class=MsoNormal>*/</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>