attachment
<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Pete,<div><br><div><div>On Sep 17, 2014, at 7:25 AM, Zehler, Peter <<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</a>> wrote:</div><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Cambria;
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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Impact;
panose-1:2 11 8 6 3 9 2 5 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Daniel,<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I agree with Ira. Section 3.5 are design requirements. Also note that no conformance terminology is used in the design requirements. My preference would
be to leave the specification as currently written. <o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If it must be changed, perhaps the “Push Scan and Pull Scan are required” could be changed to “Push Scan and Pull Scan must be included in the definition”.</span></p></div></div></blockquote><div><br></div><div>I think some editorial changes to remove conformance-like words would be appropriate and useful. In the process we can normalize the text so that is reads consistently, e.g.:</div><div><br></div><div> The design requirements for this specification are:</div><div><br></div><div> 1. Follow the PWG Semantic Model for the Network Scan Service.</div> 2. Follow the naming conventions defined in IPP/1.1: Model and Semantics [RFC2911], including keyword value case (lower) and hyphenation requirements<br><div> 3. Re-use existing IPP operations, attributes, and values when possible.</div><div><div> 4. Define IPP attributes, values, and operations necessary for Push Scan.</div><div><div> 5. Define IPP attributes, values, and operations necessary for Pull Scan.</div></div><div> 6. Define a minimum set of required document formats for interoperability.</div></div><div> 7. Define security requirements necessary to support privacy, integrity, and auditing policies</div><div> 8. Define sections to register all attributes, values, and operations with IANA<div><br></div><div> (not sure if these are "design requirements" or just "functional requirements driven by use cases")</div><div><br></div><div> 9. Support one or more destinations for Push Scan.</div></div><div> 10. Support monitoring of the status of transmission to each destination.</div><div> 11. Support streaming of basic page-based raster data.</div><div> 12. Support identification of the Imaging Device.</div><br><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Pete<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Impact","sans-serif";color:navy">Peter Zehler<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">PARC, A Xerox Company</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">800 Phillips Rd, 128-27E</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Webster NY, 14580-9701</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Email:
</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><a href="mailto:Peter.Zehler@Xerox.com"><span style="font-size:10.0pt;font-family:"Arial","sans-serif"">Peter.Zehler@Xerox.com</span></a></span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Office: +1 (585) 265-8755<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">Mobile: +1 (585) 329-9508</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:navy">FAX: +1 (585) 265-7441</span><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"> </span></p><p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:ipp-bounces@pwg.org">ipp-bounces@pwg.org</a> [<a href="mailto:ipp-bounces@pwg.org">mailto:ipp-bounces@pwg.org</a>]
<b>On Behalf Of </b>Ira McDonald<br>
<b>Sent:</b> Tuesday, September 16, 2014 9:16 PM<br>
<b>To:</b> Manchala, Daniel; Ira McDonald<br>
<b>Cc:</b> <a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<b>Subject:</b> Re: [IPP] IPP Scan question.<o:p></o:p></span></p><p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<div>
<div>
<div>
<div>
<div><p class="MsoNormal" style="margin-bottom:12.0pt">Hi Daniel,<o:p></o:p></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt">I'll try to answer this one. Mike and Pete can chime in of course.<o:p></o:p></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt">Section 3.5 Design Requirements simply requires that the *spec*<br>
defines methods and attributes for both Push and Pull scan - NOT<br>
that any Printer or Client has to implement them.<o:p></o:p></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt">Sections 8.x are correct that Push Scan is OPTIONAL - this was<br>
always intended.<o:p></o:p></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt">The old section 11.1 requirement (SHOULD) was redundant and<br>
removed in the clarification of sections 11.x in general.<o:p></o:p></p>
</div><p class="MsoNormal" style="margin-bottom:12.0pt">Does that help?<o:p></o:p></p>
</div><p class="MsoNormal">Cheers,<o:p></o:p></p>
</div><p class="MsoNormal">- Ira<o:p></o:p></p>
<div>
<div>
<div>
<div>
<div><p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
<div><p class="MsoNormal"><br clear="all">
<o:p></o:p></p>
<div>
<div><p class="MsoNormal" style="margin-bottom:12.0pt">Ira McDonald (Musician / Software Architect)<br>
Co-Chair - TCG Trusted Mobility Solutions WG<br>
Chair - Linux Foundation Open Printing WG<br>
Secretary - IEEE-ISTO Printer Working Group<br>
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>
IETF Designated Expert - IPP & Printer MIB<br>
Blue Roof Music / High North Inc<br>
<a href="http://sites.google.com/site/blueroofmusic" target="_blank"><span style="color:#3333FF">http://sites.google.com/site/blueroofmusic</span></a><br>
<a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style="color:#6600CC">http://sites.google.com/site/highnorthinc</span></a><br>
mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>
Winter 579 Park Place Saline, MI 48176 734-944-0094<br>
Summer PO Box 221 Grand Marais, MI 49839 906-494-2434<o:p></o:p></p>
</div>
</div><p class="MsoNormal"><o:p> </o:p></p>
<div><p class="MsoNormal">On Tue, Sep 16, 2014 at 8:41 PM, Manchala, Daniel <<a href="mailto:Daniel.Manchala@xerox.com" target="_blank">Daniel.Manchala@xerox.com</a>> wrote:<o:p></o:p></p>
<div>
<div><p class="MsoNormal" style="margin-bottom:12.0pt"><span style="font-family: Cambria, serif;">Section 3.5 (Design Requirements) Item 3. says:</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-family: Cambria, serif;">* Push Scan and Pull Scan are required.</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-family: Cambria, serif;">This statement (...are required...) states that the Push Scan is required.</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-family: Cambria, serif;">However, Section 8.2 Job Template attributes: destination-uris says:</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-size: 11pt; font-family: Cambria, serif;">* Scan Services that support Push Scanning MUST support this attribute.</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-size: 11pt; font-family: Cambria, serif;">This statement (...that support ...) states that the Push Scan is optional.</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-family: Cambria, serif;">Again</span><span style="font-size: 10pt; font-family: Cambria, serif;">,
</span><span style="font-family: Cambria, serif;">Section 8.3.2 destination-uri-schemes-supported says:</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-size: 11pt; font-family: Cambria, serif;">* Scan Services that support Push Scan MUST support this attribute.</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-size: 11pt; font-family: Cambria, serif;">This statement (...that support ...) states that the Push Scan is optional.</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-size: 11pt; font-family: Cambria, serif;">Section 11.1 mentioned "Scan Services MUST support Pull Scan and SHOULD support Push Scan" in an older version of the document (20140725), but the current
version does not mention that.</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-size: 11pt; font-family: Cambria, serif;">Can you clarify this?</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p><p style="margin-left:.25in"><span style="font-size: 11pt; font-family: Cambria, serif;">Thanks,</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p style="margin-left:.25in"><span style="font-size: 11pt; font-family: Cambria, serif;">Daniel.</span><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"><o:p></o:p></span></p><p class="MsoNormal"><span style="font-size: 10pt; font-family: Tahoma, sans-serif;"> </span></p>
</div>
</div><p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
<a href="https://www.pwg.org/mailman/listinfo/ipp" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><o:p></o:p></p>
</div><p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
_______________________________________________<br>ipp mailing list<br><a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>https://www.pwg.org/mailman/listinfo/ipp<br></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; font-family: 'Andale Mono'; border-spacing: 0px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">_________________________________________________________<br>Michael Sweet, Senior Printing System Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>