70 likes | 203 Vues
Browsefax Integration. 15 May 2002, San Diego D. Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker@brandenburg.com. Function Document Distribution Authentication Printing End-user service Easy to use Delivery confirmation Accounting Integration Workflow
E N D
Browsefax Integration 15 May 2002, San Diego D. Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker@brandenburg.com
Function Document Distribution Authentication Printing End-user service Easy to use Delivery confirmation Accounting Integration Workflow Directory, database Web Operation Revenue Transaction fees Adoption, Interworking No Critical Mass Barrier Standards Transmission Firewall friendly Internet friendly VPN friendly Performance Hi speed Large files Browsefax goals* *www.browsefax.com/docdist.htm Browsefax Integration
Browsefax document scenarios* • Secure Color • To Individual • To BrowseFax Machine • Gateway • TO Legacy Fax Machine • FROM Legacy Fax Machine • Hardcopy Posting • To Individual • To Virtual Filing Cabinet • Workflow *www.mfpa.org/pub/browsefax_wp.htm Browsefax Integration
Specifics Secure Color Web storage with email notice – reads on Tumbleweed patent Gateway Same as T.37 Fax Gateway? Scan input to doc xfer Failed FedEx experiment Existing Kinkos service Underlying factors Reliance on providers (proxies) Contrary to existing T.30 and Internet P2P trend How to choose proxy? Barrier to entry – why cost more than email? Lack of Interoperability with existing Internet services Capabilities negotiation Issues Browsefax Integration
Document End-user service Core format(s) Extensibility Separate “control” vs. exchange mechanisms Adoption, interworking No Critical Mass Barrier Existing, deployed standards, services Re-use code, when good Distribution Transmission Firewall friendly Fax peer to peer, permitting proxies Operations Internet speeds Large files Delivery confirmation Modified Goals (proposed) Goal: Re-use specs and code, where appropriate Browsefax Integration
Document Content MIME [and S/MIME-PGP] XML/RFC822, w/accounting Base of TIFF-FX, GIF, JPEG, HTML, Unicode, …?? Negotiated enhancements Control HTTP/SOAP HTTP/Form-URL Content negotiation Addressing T.37, enhanced for proxy specification Distribution Transmission BEEP/XML session layer Fax-level p2p, permitting proxies, via DNS SRV “Timely” delivery SMTP or HTTP/SOAP/… Operations Hi speed (?) Large files Delivery confirmation Modified Details Browsefax Integration
Control DNS Directory Service Provider Content Web Server Content Mgmt SMTP Server SMTP Server Gateway FTP Client FTP Server Modular Scenarios MFP MFP Content Mgmt Gateway Browsefax Integration