Bill,
What I meant by my terse response is that the FaxIn job can be used to
store the incoming document to the appropriate "Hot" folder pointed to
by DestinationUri based on JobMetrics (e.g., T33SubAddress). The magic
comes via a Print Service configured, by means outside the scope of the
MFD model, to processes documents in the "Hot" folders into Print Jobs.
Each "Hot" folder would be associated with a virtual printer (i.e.,
Printer) with its default values set to include a JobPassword. The end
user can then use implementation specific means to list his jobs and
enter the password to get the faxed document printed.
I do not believe "secure retrieval of printed FaxIn document via PIN"
is a requirement of FaxIn.
Pete
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
From: William Wagner [mailto:wamwagner at comcast.net]
Sent: Wednesday, August 10, 2011 2:44 PM
To: Zehler, Peter; Nancy.Chen at okidata.com; 'Ira McDonald'
Cc: mfd at pwg.org; mfd-bounces at pwg.org
Subject: RE: [MFD] Why FaxIn should NOT add the PrintService attributes
I thought that the available job ticket just related to FaxIn processing
(including the destination). The default job ticket for the destination
printer would define print processing. I don't recall that we had
available job ticket capability for printers (do we?). At any rate, the
path for communication the PIN code to the printer (and the intended
recipient) is not clear.
Thanks.
Bill Wagner
From: mfd-bounces at pwg.org [mailto:mfd-bounces at pwg.org] On Behalf Of
Zehler, Peter
Sent: Wednesday, August 10, 2011 2:06 PM
To: Nancy.Chen at okidata.com; Ira McDonald
Cc: mfd at pwg.org; mfd-bounces at pwg.org
Subject: RE: [MFD] Why FaxIn should NOT add the PrintService attributes
This can be accomplished via the AvailableJobTicket, its FaxInMetrics
and FaxInJobTicket, and a properly configured Printer pointed to by
DestinationUri.
Peter Zehler
Xerox Research Center Webster
Email: Peter.Zehler at Xerox.com
Voice: (585) 265-8755
FAX: (585) 265-7441
US Mail: Peter Zehler
Xerox Corp.
800 Phillips Rd.
M/S 128-25E
Webster NY, 14580-9701
From: Nancy.Chen at okidata.com [mailto:Nancy.Chen at okidata.com]
Sent: Wednesday, August 10, 2011 1:33 PM
To: Ira McDonald
Cc: Ira McDonald; mfd at pwg.org; mfd-bounces at pwg.org; Zehler, Peter
Subject: Re: [MFD] Why FaxIn should NOT add the PrintService attributes
How can secure retrieval of printed FaxIn document via PIN be supported
this way? I remember somebody mentioned before in one of our meetings
that this feature is desired. Just won't be supported?
-Nancy
Ira McDonald <blueroofmusic at gmail.com>
Sent by: mfd-bounces at pwg.org
08/10/2011 11:57 AM
To
"Zehler, Peter" <Peter.Zehler at xerox.com>, Ira McDonald
<blueroofmusic at gmail.com>, mfd at pwg.org
cc
Subject
[MFD] Why FaxIn should NOT add the PrintService attributes
Hi Pete,
Originally, we had some boolean to say "and by the way print"
for FaxIn (and EmailIn, presumably) - no longer in the schema.
Then we decided instead to tread print as just another destination.
And treating it that way let's the hardcopy for the FaxIn document
happen easily off-box (e.g., on a printer nearer the user).
I strongly favor no extra privilege/details for the print destination of
FaxIn - just a URI that points to some PrintService that prints with
the configured defaults.
Otherwise FaxIn-to-Print becomes more of a true compound
service - very undesirable.
WDYT?
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
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
_______________________________________________
mfd mailing list
mfd at pwg.orghttps://www.pwg.org/mailman/listinfo/mfd
--
This message has been scanned for viruses and
dangerous content by MailScanner <http://www.mailscanner.info/> , and is
believed to be clean.
--
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/mfd/attachments/20110811/618c4d9c/attachment-0001.html>