attachment-0001
<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On Aug 11, 2011, at 12:11 PM, Ira McDonald wrote:</div><blockquote type="cite">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, <br></blockquote><div><br></div>Here is my proposed text for JPS3 based on the description in MFD Common:</div><div><br></div><div>[operation attributes]</div><div><br></div><div>requesting-user-uri (uri)</div><div><br></div><div>This RECOMMENDED attribute contains the URI of the end user that is submitting the job or subscription creation request.</div><div><br></div><div>[job description attributes]</div><div><br></div><div>job-originating-user-uri (uri)</div><div><br></div><div><div>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).</div><div><br></div><div>[subscription description attributes]</div><div><br></div><div>notify-subscriber-user-uri (uri)</div><div><br></div><div><div>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).</div><div><br></div></div><blockquote type="cite">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?<br></blockquote><div><br></div><div>Where is JobSenderUri defined? I'm not seeing it in the schema or any of the MFD/SM documents?</div><div><br></div></div><div>
<div style="font-family: Helvetica; ">__________________________________________________</div><div style="font-family: Helvetica; ">Michael Sweet, Senior Printing System Engineer, PWG Chair<br></div>
</div>
<br><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>