702

Port 702/tcp is registered for IRIS over BEEP, but the supplied evidence does not establish whether this service belongs on the public internet. Treat the port number as a protocol clue, not proof that a host runs IRIS or is reachable from the internet.

RFC 3983 specifies the binding of the Internet Registry Information Service (IRIS) to BEEP over TCP. In its default exchange, a client sends an IRIS XML request in a BEEP MSG, and the server returns an IRIS XML response in RPY; ERR carries fault codes. Registry types may define different message patterns.

The RFC describes TLS-based server authentication and BEEP tuning profiles for authentication or encryption. Those are protocol provisions, not evidence that a particular deployment enables them. The sources contain no deployment, traffic measurement, malware association, or exposure observations, so those details remain unknown.

Exposure

Unknown. The protocol specification alone does not establish the intended network audience or an access policy.

Security

RFC 3983 describes TLS options for server authentication and session protection; a port assignment does not show whether a deployment uses them.

Interpretation

A listener on 702/tcp may warrant protocol identification, but the port number alone cannot confirm IRIS over BEEP.

Port assignment

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

Transport mapping

RFC 3983 specifies that the IRIS-over-BEEP mapping uses TCP [Confirmed] — https://www.rfc-editor.org/rfc/rfc3983.txt

Default exchange

IRIS XML request in BEEP MSG, response in RPY; ERR is used for fault codes [Confirmed] — https://www.rfc-editor.org/rfc/rfc3983.txt

Current deployment or public reachability

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

IANA assigns UDP port 702 the service name iris-beep and describes it as “IRIS over BEEP.” RFC 3983 specifies carrying the Internet Registry Information Service (IRIS) over BEEP, but its defined BEEP mapping explicitly uses TCP. The supplied evidence does not explain how that TCP mapping relates to the UDP assignment, so the protocol intended to run on 702/udp is Unknown.

RFC 3983 describes IRIS request and response messages, XML payloads, and authentication options. Those details apply to the RFC’s TCP mapping; they do not establish that the same exchange occurs over UDP. A registry entry alone also does not show that any host deploys the service, how often it is encountered, or whether observed traffic is benign or malicious.

Because the evidence does not establish the intended audience or UDP protocol behavior, a recommended exposure policy cannot be determined. Treat the service label as a registry identifier, not as evidence that opening UDP 702 to the public internet is appropriate.

Service

IANA registers iris-beep for UDP port 702, described as IRIS over BEEP. [Confirmed]

UDP protocol behavior

Unknown; RFC 3983 defines its BEEP mapping over TCP. [Confirmed]

Recommended exposure

Unknown; supplied evidence does not establish the intended audience for UDP 702. [Unknown]

Prevalence and deployment

Unknown; assignment does not demonstrate observed use. [Unknown]

IANA service name

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

IANA description

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

RFC reference

RFC 3983; the specified BEEP mapping uses TCP [Confirmed] — https://www.rfc-editor.org/rfc/rfc3983.txt

Intended UDP protocol behavior

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

Deployment and prevalence

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