6619
Summary
- // if you see it open
- TLS session encryption and authentication are specified; restrict access to intended trading partners where feasible and use appropriate authentication. RFC 5024 is informational and cautions that it is not an Internet Standard.
- // common applications
- Automated business-to-business file tran RFC 5024 specifies that responding ODETTE-FTP systems listen for secure TLS connections on registered port 6619; an observed listener is not thereby confirmed as ODETTE-FTP.
About port 6619.
TCP port 6619 is registered for odette-ftps, the secure ODETTE-FTP service. RFC 5024 specifies that responding ODETTE-FTP systems listen there for TLS connections. The assignment identifies the intended protocol, but does not show whether a particular host runs it. Its expected audience is ODETTE-FTP trading partners, not arbitrary Internet clients.
ODETTE-FTP supports automated business file exchange, including file acknowledgements. RFC 5024 describes TLS session encryption and authentication, alongside optional file-level protections. It distinguishes the secure service on 6619 from unencrypted ODETTE-FTP on TCP 3305. The RFC is informational and cautions that it is not an Internet Standard.
Because this service is designed for partner connections over the Internet, an authorized ODETTE-FTP endpoint may need Internet reachability. Limit access to known trading partners where feasible and require TLS and appropriate authentication. The supplied evidence does not establish deployment prevalence, observed exposure, or malware associations.
- Intended service
- IANA registers
odette-ftpson TCP 6619 for ODETTE-FTP over TLS/SSL. [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv - Protocol behavior
- RFC 5024 specifies secure TLS connections to registered port 6619 for ODETTE-FTP. [Confirmed] — https://www.rfc-editor.org/rfc/rfc5024.txt
- Exposure
- Partner-facing Internet access may be appropriate for an authorized endpoint; restrict connections to intended trading partners where feasible. [Likely] — https://www.rfc-editor.org/rfc/rfc5024.txt
- Deployment and prevalence
- No host-specific deployment or scoped prevalence measurement is supplied. [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
- IANA service name
odette-ftps[Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
- Registered use
- ODETTE-FTP over TLS/SSL [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
- RFC reference
- RFC 5024, informational [Confirmed] — https://www.rfc-editor.org/rfc/rfc5024.txt
- Deployment on any particular host
- Unknown [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| odette-ftps | TCP | ODETTE-FTP over TLS/SSL | 0.01% |
| odette-ftps | UDP | ODETTE-FTP over TLS/SSL | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.