Here you will find information about OFTP2 communication for EDI.
Volvo IT will discontinue supporting X.25 and ISDN on September 30th, 2011.
Due to the closing of X.25 and ISDN, the Volvo Group has decided to migrate all EDI partners using OFTP over X.25 and ISDN to OFTP2 over TCP/IP. The use of OFTP2 will also reduce costs and increase performance, especially for CAD files.
(read more)
AB Volvo will implement session level encryption by using Transport Layer Security (TLS). The TLS provides data confidentiality by encryption of all protocol commands and data exchanged between Volvo Group and our partners. This will provide enough security, preventing a third party from extracting any useful information from the transmission.
Technical requirements for EDI Partner
The EDI partner needs to take action to secure the fulfilment of the technical requirements:
• Implement OFTP2 support in your EDI system
• Acquire a SSL Certificate issued by a Certificate Authority that has been approved by Volvo, see list below.
• The Common Name (CN) of your server certificate should contain the Fully Qualified Domain Name (FQDN) of your OFTP2 server. Do not use a static IP as host name. Volvo does not support wildcard certificates.
• Volvo uses TLS line security (session encryption only).
• The validation is done against Root CA Certificates. That means that your certificate is NOT stored at Volvo and you should store only the Root CA Certificate of Verisign for verification of Volvo's certificate. (For most of our EDI partners it is enough to verify Volvo's certificate via VeriSign's Root CA but in a few cases the intermediate certificate is also needed.) Import the Root CA Certificate of Verisign (select Select Retail SSL - Secure Site - Enrolled between 5/17/09 to 10/10/10) into your EDI System. For more info see: https://knowledge.verisign.com/support/ssl-certificates-support/index?page=content&id=SO4785&actp=LIST&viewlocale=en_EN
If needed; also import the intermediate certificate found at: http://www.verisign.com/support/verisign-intermediate-ca/secure-site-intermediate/index.html
• Firewall configurations: Incoming and outgoing IP-addresses are different because of HW (cluster) solutions. Identity sending files from Volvo is 192.138.117.2 or 192.138.117.25. If possible configure your firewalls to accept files from 192.138.117*
• Your OFTP2 server address must be resolvable by a Reverse DNS Lookup as well as the ordinary lookup. In more technical terms, your server should have both A- and PTR-records registered in your DNS. Please see http://en.wikipedia.org/wiki/Domain_Name_System#Reverse_lookup for details
OFTP2 Communication Parameters
SSID (ODETTE-Code): O0942000055610326980VOLVO
SFID: O0942000055610326980VOLVO
DNS-Name: oftp2.volvo.com
Port: 6619
Approved Certificate Authorities
Odette International
VeriSign, Inc. (used by Volvo)
America Online Inc.
SECOM Trust Systems CO.,LTD.
SECOM Trust.net
Entrust.net
Thawte Consulting
GlobalSign nv-sa
ValiCert, Inc.
DigiCert Inc
AddTrust AB
TC TrustCenter GmbH
Equifax Secure Inc.
The USERTRUST Network
Starfield Technologies, Inc.
GlobalSign
GeoTrust Inc.
Comodo CA Limited
Baltimore
RSA Data Security, Inc.
Sonera
GTE Corporation
The Go Daddy Group, Inc.
Encode Networks Svenska AB
Mendelson CA
SFID
Files sent to Volvo with other SFID than stated above will not be accepted.
Virtual filename
Volvo does not normally use predefined virtual filenames. If this is requested, please fill out the virtual filename you wish to receive in the EDI Communication Form.
File format
The file format will be Unstructured. Please notify us if you want any other file format.
Code representation
The code representation will be ASCII. Please notify us if you want any other code representation.