data transport standard (dts) executive overview
TRANSCRIPT
Data Transport Standard (DTS)
Executive Overview
7/1/2005
Executive Summary
• DTS uses Internet technologies to facilitate real time data exchange and transaction processing
• DTS builds on stable technologies, not specific products
• DTS, once implemented, reduces programming and per-transaction costs through standardization
7/1/2005
DTS Defined• Data Transport Standard• Established by PESC for exchanging data:
– Inquiry– Reports– Transactions
• An adjunct to or replacement for existing data transport mechanisms (PGP, Secret Agent, e-mail and FTP)
7/1/2005
Specification for DTS
• Specification Covers– Technical interchange rules and processes– Recommended best practices
• Specification Does Not Cover– Business rules for transaction processing– Operational oversight, monitoring or escalation
• Implementation Examples– Code samples are available
7/1/2005
DTS Benefits
• A Web Services implementation – Delivery confirmation included - no guessing– All requests get a response– All submissions get an answer of some kind
• Facilitates real time data exchange• Includes automatic data encryption• Uses digital signature standards• Platform independent• Strong authentication with non-repudiation
7/1/2005
Next Steps
• Identify business partners or internal applications seeking real time data exchange
• Support the standard by funding and scheduling implementation of DTS
• Implement DTS
• Monitor improvements in throughput and reductions in transaction cost
7/1/2005
Share Information
• Notify the PESC DTS Workgroup with– Implementation and testing schedules– Trading partners– Issues with the defined standard
• Share Implementation Experiences with Community– Successes– Difficulties
7/1/2005
Additional DTS Information
• Visit PESC at www.pesc.org– Letter of Intent (including Business Case)
• Historical Overview• Justification and Description• Community Collaboration
– Executive Summaries– Specification– Reference Implementations
7/1/2005
PESC Workgroup Contacts
Workgroup Chair:
Workgroup co-Chair:
Workgroup co-Chair:
Kim Shiflette, USA Funds(317) [email protected]
Gary Allen, Oracle(925) [email protected]
Gary Sandler, ELM Resources(510) [email protected]
7/1/2005
More Technical Slides Follow
• The remaining slides can be material for a more technical presentation
7/1/2005
Data Transport – Issues• E-mail data exchange is not reliable or flexible enough
– No guarantee of delivery– No guarantee of order of delivery for sequence dependent data– No automatic confirmation of receipt or facility for retransmit– No synchronous response available– Email size limitations
• FTP data exchange has own challenges– Possible to overwrite earlier files– No confirmation of receipt– No synchronous response
• Encryption is always separate and subject to its own issues, maintenance and failures
7/1/2005
DTS Addresses Transport Issues
• DTS addresses – the confirmation issue with a send-receive protocol –
confirmation is built in– the order of delivery problem by actively delivering and
receiving the data – no unconfirmed hand-offs– the size problem through data compression– the FTP overwrite problem by not using filenames– the lack of a synchronous response by building in a
required synchronous response, even if only for handling status
– the encryption issue by using standard HTTPS for encryption – the same technology as for online banking
7/1/2005
DTS Technologies
• Standards– HTTP1.1, SSL2.0, SOAP1.1, XML, WSDL2.0, zLib (RFC
1950), Base64 (RFC 3548), UUID, X.509– This suite is generally accepted as the base set of
standards for building a Web Services solution
• SSL encryption of HTTP Streams• WS-Security / XML-DSIG – digital signature
standards– Strong authentication with non-repudiation– X.509 encryption keys and certificate authorities