Hi Mike,
JobSenderURI is in your notes from FaxIn review last week. It's needed
for FaxInMetrics to allow selection from AvailableJobTickets based on
the remote phone number (PSTN) or email address (Internet Fax) of the
incoming Fax. This is not the same as RequestingUser, because there's
no in-band RequestingUser.
The lack of JobSenderURI is one of the current list of todo's for the
updated MFD Model (because it will apply to EmailIn as well).
In the near term, it will be defined in my next draft of FaxIn.
For pure IPP Print, it's not necessary. For future IPP FaxIn, it's needed.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Chair - Linux Foundation Open Printing WG
Co-Chair - IEEE-ISTO PWG IPP WG
Chair - TCG Embedded Systems Hardcopy SWG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music/High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto:blueroofmusic at gmail.com
Christmas through April:
579 Park Place Saline, MI 48176
734-944-0094
May to Christmas:
PO Box 221 Grand Marais, MI 49839
906-494-2434
On Thu, Aug 11, 2011 at 12:51 PM, Michael Sweet <msweet at apple.com> wrote:
> On Aug 11, 2011, at 12:11 PM, Ira McDonald wrote:
>> Hi Pete,
>> JobOriginatingUserURI is defined in MFD Model in Table 47 and
> Table 66 - the IETF/PWG reference column is blank.
>> Yes, it should be added to JPS3,
>>> Here is my proposed text for JPS3 based on the description in MFD Common:
>> [operation attributes]
>> requesting-user-uri (uri)
>> This RECOMMENDED attribute contains the URI of the end user that is
> submitting the job or subscription creation request.
>> [job description attributes]
>> job-originating-user-uri (uri)
>> 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).
>> [subscription description attributes]
>> notify-subscriber-user-uri (uri)
>> 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).
>> We also need an IPP definition for JobSenderURI (the remote host's
> URI for Fax, Email, etc.) - this could also be used for the remote dumb
> client's URI (for LPR, Port 9100, etc.) - for IPP, the JobSenderURI
> would be defined to be synonymous with JobOriginatingUserURI
> - right?
>>> Where is JobSenderUri defined? I'm not seeing it in the schema or any of
> the MFD/SM documents?
>> __________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20110811/cc3967f1/attachment-0001.html>