Jump to content

OFTP: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
Corrected the creation date of OFTP. It had been stated as 1997 which was the date of the RFC 2204 document. However, OFTP was created in 1986, as is explained within RFC 2204 on the second page.
Tags: Mobile edit Mobile web edit
The Jambo (talk | contribs)
→‎External links: and Advantages updates
Line 3: Line 3:
The ODETTE File Transfer Protocol (ODETTE-FTP) was defined in 1986 by working group four of the Organisation for Data Exchange by Tele-Transmission in Europe (ODETTE) to address the electronic data interchange (EDI) requirements of the European automotive industry. It was designed in the spirit of the Open System Interconnection (OSI) model utilising the Network Service provided by the CCITT X.25 recommendation.
The ODETTE File Transfer Protocol (ODETTE-FTP) was defined in 1986 by working group four of the Organisation for Data Exchange by Tele-Transmission in Europe (ODETTE) to address the electronic data interchange (EDI) requirements of the European automotive industry. It was designed in the spirit of the Open System Interconnection (OSI) model utilising the Network Service provided by the CCITT X.25 recommendation.


OFTP 2 was written in 2007 by Data Interchange, as a specification for the secure transfer of business documents over the [[Internet]], [[ISDN]] and [[X.25]] networks. A description of OFTP 1.3 can be found in RFC 2204, whilst OFTP 2 is defined in RFC 5024.
OFTP 2 was written in 2007 by [http://www.datainterchange.com Data Interchange], as a specification for the secure transfer of business documents over the [[Internet]], [[ISDN]] and [[X.25]] networks. A description of OFTP 1.3 can be found in RFC 2204, whilst OFTP 2 is defined in RFC 5024.


OFTP 2 can work [[Point-to-point tunneling protocol|point-to-point]] or indirectly via a VAN (Value Added Network). A single OFTP 2 entity can make and receive calls, exchanging [[Computer file|files]] in both directions.<ref>[http://www.ietf.org/rfc/rfc5024 OFTP2's RFC Documentation]</ref> This means that OFTP 2 can work in a push or pull mode, as opposed to [[AS2]], which can only work in a push mode.<ref>[http://www.ietf.org/rfc/rfc4130.txt AS2 RFC Documentation]</ref>
OFTP 2 can work [[Point-to-point tunneling protocol|point-to-point]] or indirectly via a VAN (Value Added Network). A single OFTP 2 entity can make and receive calls, exchanging [[Computer file|files]] in both directions.<ref>[http://www.ietf.org/rfc/rfc5024 OFTP2's RFC Documentation]</ref> This means that OFTP 2 can work in a push or pull mode, as opposed to [[AS2]], which can only work in a push mode.<ref>[http://www.ietf.org/rfc/rfc4130.txt AS2 RFC Documentation]</ref>
Line 28: Line 28:
* Operates over TCP/IP, X.25/ISDN, native X.25
* Operates over TCP/IP, X.25/ISDN, native X.25
* Maximum file size of 9PB ([[Petabytes]])
* Maximum file size of 9PB ([[Petabytes]])
* SHA-256 and PFS Security


==References==
==References==
Line 46: Line 47:
* [http://www.rssbus.com/solutions/oftp/ FREE OFTP2 Connector from RSSBus]
* [http://www.rssbus.com/solutions/oftp/ FREE OFTP2 Connector from RSSBus]
* [http://numlog.fr/en/edti-echange-de-donnees-techniques FT-Master from NUMLOG]
* [http://numlog.fr/en/edti-echange-de-donnees-techniques FT-Master from NUMLOG]
* [http://www.datainterchange.com/en/Solutions/Darwin Darwin], [http://www.datainterchange.com/en/Solutions/EPIC Epic] and [http://www.datainterchange.com/en/Solutions/Odex-Enterprise Odex] by [http://www.datainterchange.com/en/Home Data Interchange Plc]
* [http://www.dip.co.uk/Products/ODEX-Enterprise.aspx Data Interchange Plc]
* [http://schaefer-bs.com/index.php?id=167&L=4 ET-Connector EDI Integration suite]
* [http://schaefer-bs.com/index.php?id=167&L=4 ET-Connector EDI Integration suite]
* [http://www.encode.se Encode Networks Svenska AB]
* [http://www.encode.se Encode Networks Svenska AB]

Revision as of 14:04, 1 July 2015

The Odette File Transfer Protocol (OFTP) is a protocol created in 1986, used for EDI (Electronic Data Interchange) between two communications business partners. Its name comes from the Odette Organisation (the Organization for data exchange by teletransmission in Europe).

The ODETTE File Transfer Protocol (ODETTE-FTP) was defined in 1986 by working group four of the Organisation for Data Exchange by Tele-Transmission in Europe (ODETTE) to address the electronic data interchange (EDI) requirements of the European automotive industry. It was designed in the spirit of the Open System Interconnection (OSI) model utilising the Network Service provided by the CCITT X.25 recommendation.

OFTP 2 was written in 2007 by Data Interchange, as a specification for the secure transfer of business documents over the Internet, ISDN and X.25 networks. A description of OFTP 1.3 can be found in RFC 2204, whilst OFTP 2 is defined in RFC 5024.

OFTP 2 can work point-to-point or indirectly via a VAN (Value Added Network). A single OFTP 2 entity can make and receive calls, exchanging files in both directions.[1] This means that OFTP 2 can work in a push or pull mode, as opposed to AS2, which can only work in a push mode.[2]

OFTP 2 can encrypt and digitally sign message data, request signed receipts and also offers high levels of data compression. All of these services are available when using OFTP 2 over TCP/IP, X.25/ISDN or native X.25. When used over a TCP/IP network such as the Internet, additional session level security is available by using OFTP 2 over TLS (Transport Layer Security).

OFTP 2 Feature Summary

  • Message encryption
  • Message signatures
  • Signed receipts
  • Message compression
  • Message integrity
  • Session authentication
  • File & Session level encryption (TLS)
  • CMS envelopes
  • Sub-level addressing

Advantages

  • File restart
  • Push / pull operation
  • Peer-to-peer or indirect communications
  • File compression
  • Operates over TCP/IP, X.25/ISDN, native X.25
  • Maximum file size of 9PB (Petabytes)
  • SHA-256 and PFS Security

References

Open Source software
Commercial software