Port 3305: OFTP — The Automotive Internet Nobody Talks About

Port 3305 carries OFTP — the Odette File Transfer Protocol. You have probably never heard of it. But if you drive a European car, parts of it were assembled because of this port.

What Runs on Port 3305

OFTP is a peer-to-peer file transfer protocol built specifically for Electronic Data Interchange (EDI) between trading partners. Not file-sharing between employees. Not FTP between servers. Business-to-business document exchange between organizations: purchase orders, shipping notices, invoices, CAD drawings, engineering specifications.

It was created in 1986 by ODETTE — the Organisation for Data Exchange by Tele Transmission in Europe — a working group formed by the European automotive industry to solve a very specific problem.¹

The secure variant, OFTP over TLS, runs on port 6619.²

The Problem It Was Built to Solve

In the mid-1980s, European automakers were adopting just-in-time manufacturing. JIT meant suppliers had to deliver parts to the factory floor precisely when needed — not days early (too much inventory), not hours late (line stops). The margin for error collapsed.

This required fast, reliable, automated data exchange. An order for 10,000 brake calipers had to move from the automaker's system to the supplier's system without human hands touching it. Standard FTP didn't have acknowledgment mechanisms — you could send a file, but you had no guaranteed confirmation it arrived correctly and completely. In a JIT supply chain, that uncertainty was unacceptable.

OFTP was designed with a defined acknowledgment process: a signed receipt confirming successful receipt of every file. Your order didn't just go into the void. It came back with proof.³

How It Works

OFTP runs a single session for both control and data. Partners exchange identity credentials (called "SSID" — Session Start Identification) at connection time, negotiate transfer parameters, and then exchange files with start/end file markers and acknowledgments.

The original 1986 design ran on X.25 — dedicated leased-line networks that predated the consumer Internet. When TCP/IP took over, OFTP adapted. When the Internet needed encryption, OFTP2 (2007) added TLS and certificate-based authentication on a single TCP port.⁴

OFTP2, formalized in RFC 5024, added:

• TLS encryption for data in transit
• File encryption and digital signing using CMS (Cryptographic Message Syntax)
• Compression
• Signed receipts for non-repudiation — legally provable confirmation that a file was received

Non-repudiation matters when a supplier needs to prove they sent an order and an automaker needs to prove they received it. In a dispute over a missed delivery, "we sent the file" isn't enough. OFTP2 gives you a signed receipt that holds up.

Who Uses It

OFTP is still the dominant EDI standard in the European automotive supply chain. Volkswagen, BMW, Renault, PSA, and their thousands of tier-1 and tier-2 suppliers exchange files on port 3305 every day. The Odette organization continues to maintain the standard and certify compliant software.

It's essentially invisible to everyone outside the industry — and deliberately so. It runs in the background, machine to machine, no human involvement. When it works, nobody notices. When it doesn't, a factory stops.

Security Considerations

Older OFTP implementations (OFTP version 1) send data without encryption. If you see traffic on port 3305 on a network that shouldn't be communicating with automotive supply chain systems, investigate.

OFTP2 on port 6619 uses TLS, which addresses the plaintext problem. Implementations should enforce certificate validation and not accept self-signed certificates from unknown partners.⁵

Because OFTP is a niche protocol, it tends to get less security scrutiny than common protocols. Vulnerabilities in OFTP implementations have been found and patched over the years — keep implementations updated.

Checking What's Listening on This Port

To see if anything is listening on port 3305 on your system:

# Linux/macOS
ss -tlnp | grep 3305
lsof -i :3305

# Windows
netstat -ano | findstr :3305

Unless you're running automotive EDI software or a Value Added Network (VAN) service, nothing should be listening here.

Why This Port Exists

Port 3305 is a reminder that the Internet is not one thing. Alongside the public web, there are dozens of specialized networks running specialized protocols for industries with specialized requirements. The automotive supply chain, healthcare (HL7), financial messaging (FIX), aviation (ACARS) — each has its own protocol designed before the modern Internet existed, adapted to survive it, and still running.

Standard protocols exist because general problems need general solutions. OFTP exists because the European automotive industry had a problem so specific — guaranteed, acknowledged, non-repudiable file exchange between regulated trading partners — that it needed its own answer.

Forty years later, it's still the answer.

Related Ports