Pete,
I thought we were requiring pull scan and recommending push scan because low-end devices couldn't retry a push automatically. Any push-related attributes would be conditionally required if the service supports push. And any retry-related attributes would be conditionally required for services that do output spooling.
On Feb 10, 2014, at 2:59 PM, Zehler, Peter <Peter.Zehler at xerox.com> wrote:
> All,
>> I have conflicting notes. I have some Push scan related attributes marked as conditionally mandatory while Pull and Push scan are listed as required.
>> My opinion is that Push and Pull scanning are mandated and therefore the Push related attributes are also mandatory. For Push scanning the “http”, “https”, “ftp” and “ftps URI schemes MUST be supported.
>> Any objections?
>> 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
>> _______________________________________________
> ipp mailing list
>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/20140210/72ff2d15/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/20140210/72ff2d15/attachment.p7s>