attachment
<html>
<head>
<meta name="generator" content="Windows Mail 17.5.9600.20689">
<style><!--
.EmailQuote {
margin-left:1pt;
padding-left:4pt;
border-left:#800000 2px solid;
}
--></style><style data-externalstyle="true"><!--
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
}
p.MsoNormal, li.MsoNormal, div.MsoNormal {
margin:0in;
margin-bottom:.0001pt;
}
p.MsoListParagraphCxSpFirst, li.MsoListParagraphCxSpFirst, div.MsoListParagraphCxSpFirst,
p.MsoListParagraphCxSpMiddle, li.MsoListParagraphCxSpMiddle, div.MsoListParagraphCxSpMiddle,
p.MsoListParagraphCxSpLast, li.MsoListParagraphCxSpLast, div.MsoListParagraphCxSpLast {
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
line-height:115%;
}
--></style></head>
<body dir="ltr">
<div data-externalstyle="false" dir="ltr" style="font-family: 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif';font-size:12pt;"><div>Sorry I am late, but I suspect that the review period will need to be extended.</div><div><br></div><div>Comments below are primarily areas that I think may be confusing to new readers, based upon my re-reading the spec after some time. Thanks,</div><div>Bill Wagner</div><div>----------------</div><div><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><span style="line-height: 115%; font-size: 10pt;"><font face="Arial">Footer:<span style="mso-spacerun: yes;"> </span>Copyright date range will need to be changed
to 2013-2015</font></span></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial"><span style="line-height: 115%; font-size: 10pt;">Section 3.2,
line 401: Introduction of Jane at end of paragraph is confusing (what is Jane?)
Suggest "Each of the use cases in this section involve Jane (the User)
initiating a print action</span><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'> and selecting
a Printer, with her Client querying the Printer status and capabilities and
displaying any important status information:"</span><span style="line-height: 115%; font-size: 10pt;"> Alternatively, just refer to the
User rather than "Jane".</span></font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><span style="line-height: 115%; font-size: 10pt;"><font face="Arial">Section 3.2,
General Comment. I appreciate that we have spent much time on Use Cases to the
extent that we just want to ignore them now. <span style="mso-spacerun: yes;"> </span>But I suggest that use cases may be important
to the new reader to understand the circumstances<span style="mso-spacerun: yes;"> </span>to be addressed<span style="mso-spacerun: yes;"> by </span>the newly specified capabilities.<span style="mso-spacerun: yes;"> </span>Why the specified capabilities are needed is perhaps
more significant than how the capabilities work. <span style="mso-spacerun: yes;"> </span>Perhaps the second paragraphs<span style="mso-spacerun: yes;"> </span>could be dropped in each of the use cases ?<span style="mso-spacerun: yes;"> </span>But if the ‘how’ descriptions are kept, I suggest that the reader may
consider the Output Device to be a Printer. Therefore it would be better to use
"Infrastructure Printer" rather than just "Printer" when it
is intended. <span style="mso-spacerun: yes;"> </span>Following suggestions to
the first use case apply to all of the use cases. </font></span></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><span style="line-height: 115%; font-size: 10pt;"><font face="Arial">Section
3.2.1, line 410:<span style="mso-spacerun: yes;"> </span>Suggest "...has a
document, stored on her phone, that she is to print prior to a meeting. The
Wi-Fi network does not provide access to the Print Output Device she wishes to
use." That is, identify why traditional IPP would not work.</font></span></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial"><span style="line-height: 115%; font-size: 10pt;">Section 3.2.1,
Line 414: Suggest " ...</span><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'>request to
the Infrastructure Printer with the Job Ticket and attached document data. The
Proxy for the desired Output Device pulls this information from the
Infrastructure Printer, validates ...</span><span style="line-height: 115%; font-size: 10pt;"> </span><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'>from the Infrastructure
Printer and causes the document to be printed, providing status updates to the
Infrastructure Printer."</span></font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'><font face="Arial">Section 4.1.1, line 570: "... MUST
NOT perform any pre-processing for things that can be done by the Proxy in
order to follow established Late Binding principles."<span style="mso-spacerun: yes;"> </span>I suggest that MUST NOT is too strong.<span style="mso-spacerun: yes;"> </span>There may be reasons (speed, for example)
where it is desirable for the Infrastructure Printer to act even though the
Proxy may report the capability. Also, I assume that generally you attribute
all capabilities downstream of the Proxy to be Proxy capabilities. Perhaps this
might be made more clear in the discussion of Figure 3. Certainly, a viable
configuration is to have the Proxy a simple translating application on a general
purpose computer, or a minimal stand-alone device, in any case with no imaging
preprocessing capabilities. However, for the discussion, the Proxy acquires the
capabilities of all downstream devices it represents, to the extent that the
owner(s) of those devices has made the capabilities accessible.</font></span></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'><font face="Arial">Section 4.1.8: Do we have some
convention when citing specification titles (e.g., Quote marks, Underline. It
is not clear what the title is vs the surrounding words. </font></span></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'><font face="Arial">Section 4.2, line 870: semicolon before
"however".</font></span></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial"><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'>Section 5, General:<span style="mso-spacerun: yes;"> </span>The paragraph for each operation clearly
indicates that the </span><span style="line-height: 115%; font-size: 10pt;">Proxy
is the only possible authenticated user for these operations. But each
operation also identifies Requesting User attribute in a more general way as
supplied by the Proxy, but not as being the Proxy. <span style="mso-spacerun: yes;"> </span>Section 8.3. of RFC2911 refers to "job-originating-user-name"
and the "job owner", which would suggest the original job originator rather
than the Proxy. It is unclear who or what this attribute should refer to. This situation
also appears in Section 6, although since these are less Job related
operations, there is less potential for confusion.</span></font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><font face="Arial"><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'>Section 5.4, line 1190: ”</span><span style="line-height: 115%; font-size: 10pt;"> If the Output Device has previously
sent..." This is confusing, since the Proxy sends the messages, not the
Output Device.</span></font></p><font face="Times New Roman">
</font><p style="margin: 0in 0in 10pt;"><span style='line-height: 115%; font-size: 10pt; mso-fareast-font-family: "Times New Roman"; mso-font-kerning: 0pt;'><font face="Arial">Section 7.4.5: I am less certain about
making the path a MUST.</font></span></p><font face="Times New Roman">
</font><br></div>
</div>
</body>
</html>