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 Jun 13, 2014, at 7:50 AM, Zehler, Peter &lt;<a href="mailto:Peter.Zehler@xerox.com">Peter.Zehler@xerox.com</a>&gt; wrote:</div><div><div><br class="Apple-interchange-newline"><blockquote type="cite">

<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@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: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:purple;
        text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
@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">All,<o:p></o:p></p><p class="MsoNormal">I just wanted to check that IPP uses HTTP chunking and that the document data is inline in the request and not in a separate MIME attachment.</p></div></div></blockquote><div><br></div><div>Correct, application/ipp allows for trailing document data, per RFC 2910/2911. &nbsp;This better allows for alternate transports (although the focus is obviously on HTTP).</div><div><br></div><div><div></div></div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal">&nbsp;I was asked and I don’t see anything in the encoding specification that puts the data in a MIME
 attachment.&nbsp; I think WS-Print/scan did it that way.&nbsp; The confusion is over the Get-Next-Document-Images operation that &nbsp;includes<o:p></o:p></p><p class="MsoNormal"><o:p>&nbsp;</o:p></p><p class="MsoNormal">-----------------------------------------------<o:p></o:p></p><p class="MsoNormal"><b><span style="font-size:11.5pt">Group 3: Document content<o:p></o:p></span></b></p><p class="MsoNormal"><b><span style="font-size:11.5pt">&nbsp;</span></b></p><p class="MsoNormal"><span style="font-size:11.5pt">The document content is sent as a MIME attachment. Note that the IPP Scan Client<o:p></o:p></span></p><p class="MsoNormal">MUST be ready to accept a chunked response.<o:p></o:p></p><p class="MsoNormal">-----------------------------------------------<o:p></o:p></p><p class="MsoNormal"><o:p>&nbsp;</o:p></p><p class="MsoNormal"><o:p>&nbsp;</o:p></p><p class="MsoNormal">I think I should strike the clause “<span style="font-size:11.5pt">The document content is sent as a MIME attachment.”</span></p></div></div></blockquote><div><br></div>Right, we should just say that the document content follows the end-of-attributes-tag. &nbsp;You can probably steal the Print-Job example from RFC 2910 (<a href="http://tools.ietf.org/html/rfc2910#page-33">http://tools.ietf.org/html/rfc2910#page-33</a>).</div><div><br></div><div><blockquote type="cite"><div lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal">Pete <o:p></o:p></p><p class="MsoNormal"><o:p>&nbsp;</o:p></p><p class="MsoNormal"><span style="font-family:&quot;Impact&quot;,&quot;sans-serif&quot;;color:navy">Peter Zehler</span><span style="color:#1F497D"><br>
<br>
</span><span style="font-size:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;;color:navy"><span>&lt;image001.png&gt;</span><br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">Email:
</span><a href="mailto:Peter.Zehler@Xerox.com"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:blue">Peter.Zehler@Xerox.com</span></a><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">Office: +1 (585) 265-8755<o:p></o:p></span></p><p class="MsoNormal"><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">Mobile: +1 (585) 329-9508</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">FAX: +1 (585) 265-7441</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">US Mail: Peter Zehler</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">Palo Alto Research Center Incorporated</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">800 Phillips Rd.</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">M/S 128-25E</span><span style="color:#1F497D"><br>
</span><span style="font-size:10.0pt;font-family:&quot;Arial&quot;,&quot;sans-serif&quot;;color:navy">Webster NY, 14580-9701</span><span style="color:#1F497D">
</span><span style="font-size:12.0pt;font-family:&quot;Times New Roman&quot;,&quot;serif&quot;;color:#1F497D"><o:p></o:p></span></p><p class="MsoNormal"><o:p>&nbsp;</o:p></p>
</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&nbsp;Engineer, PWG Chair</div></span></span>
</div>
<br></div></body></html>