3799

IANA registers TCP port 3799 as radius-dynauth for RADIUS Dynamic Authorization. The available protocol document, RFC 3576, describes dynamic session disconnect and authorization-change messages, but specifies UDP port 3799 for those messages. It does not establish that this protocol runs over TCP. Whether a TCP listener belongs on the public internet is therefore Unknown from this evidence.

RFC 3576 describes messages sent by a RADIUS server to a network access server to terminate a user session or change its authorization, such as data filters. These operations can affect active access, so the protocol context is operationally sensitive. The RFC also discusses authorization, impersonation, and replay risks, and recommends protections including IPsec in relevant deployments.

Treat the IANA entry as a service-name assignment, not evidence of a running service, observed exposure, or traffic prevalence. The RFC's UDP details should not be treated as TCP behavior. The supplied sources do not identify TCP implementations, common applications, related ports, or malware associations.

Registration

IANA names TCP port 3799 radius-dynauth for RADIUS Dynamic Authorization.

Protocol evidence

RFC 3576 describes Dynamic Authorization over UDP port 3799; TCP operation is Unknown.

Exposure

Unknown; the evidence does not establish the intended TCP audience or public deployment.

Security

The described UDP operations can disconnect sessions or change authorizations; RFC 3576 discusses authorization, impersonation, and replay risks.

IANA service name

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

TCP protocol behavior

Unknown; RFC 3576's described messages use UDP [Unknown] — https://www.rfc-editor.org/rfc/rfc3576.txt

Dynamic session disconnect and authorization changes

described for RADIUS [Confirmed] — https://www.rfc-editor.org/rfc/rfc3576.txt

Public internet suitability for TCP

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

IANA assigns UDP port 3799 the service name radius-dynauth for RADIUS Dynamic Authorization. RFC 3576 describes Disconnect-Request and Change-of-Authorization (CoA) messages sent by a RADIUS server to a Network Access Server (NAS), using UDP destination port 3799. This identifies the protocol associated with the port; it does not show that a particular host runs it or whether it should be publicly reachable.

The messages can terminate a user session or change its authorizations, such as data filters. That makes the service consequential to network access. RFC 3576 documents security concerns in existing implementations, including missing replay protection and weak per-packet authentication and integrity protections, and recommends IPsec for stronger protection. Restricting access to trusted RADIUS peers is a prudent policy, but the supplied evidence does not establish the intended audience for every deployment, so exposure remains Unknown.

The evidence establishes a registry assignment and protocol behavior, not observed deployment, traffic prevalence, common applications, or malicious use. Treat an observed UDP/3799 endpoint as a lead for protocol validation, not proof of RADIUS service.

Service

IANA registers radius-dynauth for RADIUS Dynamic Authorization over UDP.

Exposure

Unknown; the specification describes server-to-NAS control messages but does not establish the intended public reachability of deployments.

Security

Messages can disconnect sessions or change authorizations; RFC 3576 describes replay and packet-authentication concerns in existing implementations.

IANA service name

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

Protocol and destination port

RADIUS Disconnect-Request and CoA-Request use UDP destination port 3799

Deployment on a particular host

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