OFTP

How it works

OFTP and OFTP2 add compression, encryption, and receipts for trading partners. It is not FTP despite the name. Partners in that industry still require it. A generic SFTP job will be refused.

A parts supplier sends a 20 MB forecast by OFTP2. The receipt comes back. An attempt to 'just SFTP it' is rejected by the partner agreement. They keep the OFTP client for that one partner and SFTP for everyone else.

How it differs

OFTP is not FTP and not AS2, though all three carry EDI.

Certificates expire here too. A failed session on Monday is often an expired cert.

Track the date.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For oftp, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive oftp files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.