605

IANA assigns TCP port 605 to soap-beep, described as SOAP over BEEP; the available evidence does not establish whether a particular host runs it or whether it belongs on the public internet.

RFC 4227 specifies a SOAP binding to BEEP, a messaging protocol over TCP/IP. It describes SOAP envelopes carried in BEEP messages, with one-way, request-response, and request/multiple-response patterns. The RFC also describes soap.beep address resolution using the soap-beep service name and TCP when a URL omits its port.

This assignment identifies a standardized protocol, not observed traffic or deployment. No supplied evidence measures prevalence, identifies common applications in current use, or establishes malware associations. RFC 4227 discusses authentication and confidentiality options, but that specification alone does not show how any deployment is configured.

Exposure

Unknown; the supplied protocol specification and registry entry do not establish the intended audience or justify a public access policy.

Protocol

soap-beep is the IANA-assigned service name for SOAP over BEEP on TCP port 605.

Security

RFC 4227 describes authentication and confidentiality tuning options; the evidence does not establish deployment configuration or safety.

IANA service name

soap-beep [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Protocol

SOAP over BEEP

Port

605/tcp [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

RFC reference

RFC 4227 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Deployment and intended public exposure

Unknown [Unknown] — https://www.rfc-editor.org/rfc/rfc4227.txt

IANA assigns UDP port 605 the service name soap-beep, described as “SOAP over BEEP,” and cites RFC 4227. That assignment does not establish that a UDP service runs there. The supplied evidence does not identify a confirmed UDP application or establish whether this port belongs on the public internet, so its recommended exposure is Unknown.

RFC 4227 describes SOAP messaging over BEEP using TCP/IP. For its soap.beep URL scheme, clients can look up _soap-beep._tcp SRV records to find TCP addressing information. The RFC also defines soap.beeps, which requires privacy tuning of the BEEP session. These are TCP protocol details and do not establish behavior on UDP port 605.

The RFC specifies SOAP 1.2 support for its BEEP profile, with other versions optional. This helps explain the registered service label, but does not establish that SOAP-over-BEEP traffic is observed on UDP. The supplied evidence gives no scoped traffic measurement or malware association.

Service

IANA registers UDP 605 as soap-beep (“SOAP over BEEP”) [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Protocol evidence

RFC 4227 describes SOAP over BEEP over TCP; it does not establish UDP operation on port 605 [Confirmed] — https://www.rfc-editor.org/rfc/rfc4227.txt

Recommended exposure

Unknown because the evidence does not establish the intended audience of a UDP service on this port [Unknown] — https://www.rfc-editor.org/rfc/rfc4227.txt

IANA service name

soap-beep [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

IANA description

SOAP over BEEP [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

IANA reference

RFC 4227 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

UDP application behavior

Unknown; RFC 4227 specifies TCP protocol details [Unknown] — https://www.rfc-editor.org/rfc/rfc4227.txt

Traffic prevalence

Unknown; no scoped measurement supplied [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv