attachment-0001
<html xmlns:v="urn:schemas-microsoft-com:vml" 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=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@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: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;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.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]--></head><body 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'>I found that “pages-per-subset” which was in PWG5100.4 was not covered in PWG5100.6. It was supposed to be covered in another specification but apparently was dropped. We will need to include it in the IPP model since there are shipping implementations using subset processing. The definition can be lifted directly from “pages-per-subset” in section 5.3 of PWG5100.4 <<a href="ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippoverride10-20010207-5100.4.pdf">ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippoverride10-20010207-5100.4.pdf</a>>.<o:p></o:p></span></p><p class=MsoNormal><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'>Side Note: I made a change to the element “Pages” in “PagesPerSubset” in order to keep a flat namespace. Both “Overrides” and “PagesPerSubset” had a “Pages” element with different syntax and semantics. The new name for “Pages” in “PagesPerSubset” is “NumberOfPagesInSubset”. <o:p></o:p></span></p><p class=MsoNormal><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'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Impact","sans-serif";color:navy'>Peter Zehler</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br><br></span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy'>Xerox Research Center Webster<br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</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'>Voice: (585) 265-8755</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: (585) 265-7441</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'>US Mail: Peter Zehler</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'>Xerox Corp.</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.</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'>M/S 128-25E</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'> </span><span style='color:#1F497D'><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></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"'> Ira McDonald [mailto:blueroofmusic@gmail.com] <br><b>Sent:</b> Thursday, August 11, 2011 4:20 PM<br><b>To:</b> Michael Sweet; Ira McDonald<br><b>Cc:</b> Zehler, Peter; IPP@pwg.org<br><b>Subject:</b> Re: [IPP] job-originating-user-uri Where is it defined?<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi Mike,<br><br>JobSenderURI is in your notes from FaxIn review last week. It's needed<br>for FaxInMetrics to allow selection from AvailableJobTickets based on<br>the remote phone number (PSTN) or email address (Internet Fax) of the<br>incoming Fax. This is not the same as RequestingUser, because there's<br>no in-band RequestingUser.<br><br>The lack of JobSenderURI is one of the current list of todo's for the<br>updated MFD Model (because it will apply to EmailIn as well).<br><br>In the near term, it will be defined in my next draft of FaxIn.<br><br>For pure IPP Print, it's not necessary. For future IPP FaxIn, it's needed.<br><br>Cheers,<br>- Ira<br><br clear=all>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Chair - TCG Embedded Systems Hardcopy SWG<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">http://sites.google.com/site/blueroofmusic</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>Christmas through April:<br> 579 Park Place Saline, MI 48176<br> 734-944-0094<br>May to Christmas:<br> PO Box 221 Grand Marais, MI 49839<br> 906-494-2434<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><br><br><o:p></o:p></p><div><p class=MsoNormal>On Thu, Aug 11, 2011 at 12:51 PM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<o:p></o:p></p><div><div><div><div><p class=MsoNormal>On Aug 11, 2011, at 12:11 PM, Ira McDonald wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>Hi Pete,<br><br>JobOriginatingUserURI is defined in MFD Model in Table 47 and<br>Table 66 - the IETF/PWG reference column is blank.<br><br>Yes, it should be added to JPS3, <o:p></o:p></p></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div></div><p class=MsoNormal>Here is my proposed text for JPS3 based on the description in MFD Common:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>[operation attributes]<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>requesting-user-uri (uri)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>This RECOMMENDED attribute contains the URI of the end user that is submitting the job or subscription creation request.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>[job description attributes]<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>job-originating-user-uri (uri)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>This RECOMMENDED attribute contains the URI of the end user that submitted the job creation request. The Printer object sets this attribute to the most authenticated URI that it can obtain from the authentication service over which the IPP operation was received. Only if such is not available, does the Printer object use the value supplied by the client in the "requesting-user-uri" operation attribute of the create operation (see Sections 4.4.2, 4.4.3, and 8 of RFC 2911).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>[subscription description attributes]<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>notify-subscriber-user-uri (uri)<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>This RECOMMENDED attribute contains the URI of the end user that submitted the subscription creation request. The Printer object sets this attribute to the most authenticated URI that it can obtain from the authentication service over which the IPP operation was received. Only if such is not available, does the Printer object use the value supplied by the client in the "requesting-user-uri" operation attribute of the create operation (see Sections 4.4.2, 4.4.3, and 8 of RFC 2911).<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>We also need an IPP definition for JobSenderURI (the remote host's <br>URI for Fax, Email, etc.) - this could also be used for the remote dumb<br>client's URI (for LPR, Port 9100, etc.) - for IPP, the JobSenderURI <br>would be defined to be synonymous with JobOriginatingUserURI<br>- right?<o:p></o:p></p></blockquote><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><p class=MsoNormal>Where is JobSenderUri defined? I'm not seeing it in the schema or any of the MFD/SM documents?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div></div><div><div><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'>__________________________________________________<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'>Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p></div></div></div><p class=MsoNormal><o:p> </o:p></p></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>