[IPP] Are these attributes what were agreed to for IPP Scan?

[IPP] Are these attributes what were agreed to for IPP Scan?

[IPP] Are these attributes what were agreed to for IPP Scan?

Michael Sweet msweet at apple.com
Wed Apr 9 13:26:01 UTC 2014


Pete,

Which operation attributes do you want to include?

attributes-charset
attributes-natural-language

These can be taken from the Job already.

compression or compression-accepted

Certainly a possibility, although the Client probably doesn't know the destination's capabilities so we might want to use "compression-accepted" attribute to list what is acceptable to the Client.  Using "compression-accepted" would also address security considerations for compression (BEAST and other attacks) that we've never talked about in the PWG - the Client is the only entity with the context to know whether it is safe to compress the output from a security perspective...

document-charset
document-metadata
document-name
document-natural-language

These can be taken from the Job or generated by the Scan service.

document-digital-signature
document-format
document-format-details
job-impressions
job-impressions-estimated

These are generated/set by the Scan service.

document-password
job-password
job-password-encryption

These are explicitly *not* part of the Job Ticket for security reasons, and thus we cannot include them in the "destination-attributes" collection.  And while it is possible we could introduce a parallel operation attribute ("destination-operation-attributes (1setOf collection)"?) that seems a bit too hackish.

ipp-attribute-fidelity
job-mandatory-attributes

These could be take from the Job, but I can see how you might want to apply fidelity to a specific destination.

job-authorization-uri

Implementation-defined behavior until we have a standard for passing credentials through (to be used with Validate-Job to get the job-authorization-uri value...)

original-requesting-user-name
requesting-user-name
requesting-user-uri

These can be taken from the Job; supporting it per-destination seems like we are trying to address identity-passing without authentication...

....

Also, if we do a "destination-attributes (collection)" Job Template and member attribute then we'll need a "destination-attributes-supported" Printer Description attribute.  I don't see a need for a -default version, as there is no -default for the destination, but we'll need to make it clear whether any "destination-attributes" attribute in the "destination-uri-ready" value is used as the default for that destination URI.


On Apr 9, 2014, at 6:49 AM, Zehler, Peter <Peter.Zehler at xerox.com> wrote:

> Mike,
> I really want to put the Job Template Attributes in a collection.  I will change the name and drop “-collection”.  The contents of the collection is not strictly limited to IPP Job Template Attributes.
> Pete
>  
> Peter Zehler
> 
> Xerox Research Center Webster
> Email: 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: Michael Sweet [mailto:msweet at apple.com] 
> Sent: Tuesday, April 08, 2014 3:28 PM
> To: Zehler, Peter
> Cc: 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> 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
> 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
> https://www.pwg.org/mailman/listinfo/ipp
>  
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>  

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140409/70a5b2e2/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4881 bytes
Desc: not available
URL: <http://www.pwg.org/pipermail/ipp/attachments/20140409/70a5b2e2/attachment.p7s>


More information about the ipp mailing list