Somasundaram,
In IPP the destinations for fax/scan are handled the same way sources are handled for print by reference. Authentication credentials of the user are not given to the IPP Printer/FaxOut/Scanner to gain access. AAA of the referenced document/destination is not incorporated into the protocol or model. Based on market and customer requirements the appropriate security scheme is used in the implementation. The IPP specification does not dictate the required security model. For example the destination could be public or restricted to only allowing write access by the scan service. Other alternatives include the inclusion of access tokens in the URL as is used with OAUTH's Resource Owner Credentials Grant. One of the reasons for the "destination-uri-ready" was to assist the user in a secure environment determine the destinations available for the deployment. As with any IPP attributes the values returned by the Server can be filtered based on the Client's current role.
Pete
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com<mailto:Peter.Zehler at Xerox.com>
Office: +1 (585) 265-8755
Mobile: +1 (585) 329-9508
FAX: +1 (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
From: Soma Meiyappan [mailto:Soma.Meiyappan at conexant.com]
Sent: Wednesday, April 09, 2014 12:13 AM
To: Michael Sweet; Zehler, Peter
Cc: IPP at pwg.org
Subject: RE: [IPP] Are these attributes what were agreed to for IPP Scan?
Mike/Pete,
May I know how PWG solves supporting IPP destinations (and other HTTP destinations) that need authentication when used as a destination in FaxOut/Scan2 defined workflows?
Are authentication information for URIs under destination-uri-ready (implicitly) managed by the MFD as it appears that the specification does not provide any destination specific attributes in the destination-uri collection to provide authentication credentials? Or should authentication information be provided in the URI as it is done for some http URI allows like http://user:passwd@mystoragedrive.com/folder? If so, I would wonder about IPP destinations and ipp/ipps URIs.
Please see the attached email that I had sent earlier on the topic.
Thanks and Regards,
Somasundaram.
From: ipp-bounces at pwg.org<mailto:ipp-bounces at pwg.org> [mailto:ipp-bounces at pwg.org] On Behalf Of Michael Sweet
Sent: Wednesday, April 09, 2014 3:28 AM
To: Peter Zehler
Cc: IPP at pwg.org<mailto:IPP at pwg.org>
Subject: Re: [IPP] Are these attributes what were agreed to for IPP Scan?
Pete,
My only beef with the proposed additions are the "destination-attribute-collection" attributes.
We should just include Job Template attributes directly in the destination-uris and destination-uri-ready collections. Thus, it would just be:
destination-uris
destination-uri
[number-or-retries]
[retry-interval]
[retry-time-out]
[any Job Template attribute]
destination-uri-ready
destination-uri
[destination-info]
[destination-is-directory]
[destination-name]
[any Job Template attribute]
This would be consistent with how other attributes (job-sheets-col, covers, etc.) deal with embedding Job Template attributes in collection attributes.
If you really want to put the Job Template attributes in their own collection, call it "destination-attributes"; we never use "collection" spelled out in the name, and generally only add -col if there is already a non-collection form of the attribute (e.g. media and media-col, finishings and finishings-col, etc.)
On Apr 8, 2014, at 3:07 PM, Zehler, Peter <Peter.Zehler at xerox.com<mailto:Peter.Zehler at xerox.com>> wrote:
All,
Before I put out the Stable version of the IPP Scan specification I wanted to check with you regarding the addition of the attributes below. Let me know if it does not capture what we agreed to at the IPP teleconference. I plan to publish it on Thursday.
Pete
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com<mailto:Peter.Zehler at Xerox.com>
Office: +1 (585) 265-8755
Mobile: +1 (585) 329-9508
FAX: +1 (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
Added the following new member element to the Job Template Attribute "destination-uris"
8.2.1.1 destination-attribute-collection (1setOf collection)
This OPTIONAL attribute allows the client to specify attributes to be applied to the method implied by the "destination". For example if the destination uri scheme is "ipp://" this attribute would contain Operation and Job Template Attributes to be used in the creation of the IPP Print Job.
Added the following new IPP Scan Service Description Attribute
8.4.2 destination-uri-ready (1setOf collection)
The OPTIONAL "destination-uri-ready" IPP Scan Service attribute lists the configured destinations. This does not limit the destinations that a user may specify. It is a list of administratively set destinations to assist the user in selecting an appropriate destination. IPP Scan Services that support Push Scan MAY support this attribute.
8.4.2.1 destination-info (text(MAX))
The OPTIONAL "destination-info" member attribute provides a human readable description of the destination.
8.4.2.2 destination-is-directory (boolean)
The OPTIONAL "destination-is-directory" member attribute indicates if the destination is a folder that can contain multiple files. The default value if this attribute is not included is 'false'.
8.4.2.3 destination-name (name(MAX))
The OPTIONAL "destination-name" member attribute provides a human readable user friendly name for the destination.
8.4.2.4 destination-uri (uri)
The REQUIRED "destination-uri" member attribute specifies the destination.
8.4.2.5 destination-attribute-collection (1setOf collection)
This OPTIONAL "destination-attribute-collection" member attribute allows the administrator to specify attributes to be applied to the "destination-attribute-collection" Job Template Attribute (See section 8.2.1.1).
_______________________________________________
ipp mailing list
ipp at pwg.org<mailto:ipp at pwg.org>
https://www.pwg.org/mailman/listinfo/ipp
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140409/3097402e/attachment.html>