5004

IANA registers TCP port 5004 as avt-profile-1, described as “RTP media data.” That assignment identifies a service name, but does not show that a host is listening on the port or determine whether it should be reachable from the public internet. Based on the supplied evidence, exposure policy is Unknown.

RFC 3551 defines RTP/AVP for audio and video conferences and specifies that the profile can use TCP as well as UDP. It also says use of the profile may be implicit, without an explicit port indication. The registration therefore does not prove that traffic on 5004 is RTP/AVP.

RFC 4571 describes framing RTP and RTCP packets over connection-oriented transports such as TCP. It prefixes each packet with a 16-bit length. The RFCs explain relevant protocol behavior, but the supplied material does not establish that a particular application uses this framing on port 5004.

Protocol context

RTP/AVP supports TCP, and RFC 4571 specifies framing RTP/RTCP over connection-oriented transports. [Confirmed]

Public exposure

Unknown; the assignment does not establish intended audience or actual deployment. [Unknown]

Security note

RFC 4571 warns that untrusted length fields require safe handling. [Confirmed]

IANA service name

avt-profile-1 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

IANA description

RTP media data [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

RTP/AVP supports TCP

[Confirmed] — https://www.rfc-editor.org/rfc/rfc3551.txt

RTP/RTCP framing over connection-oriented transport uses a 16-bit length field

[Confirmed] — https://www.rfc-editor.org/rfc/rfc4571.txt

Intended exposure policy

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

IANA assigns UDP port 5004 the service name avt-profile-1 and describes it as RTP media data. RFC 3551 defines the RTP/AVP profile for audio and video conferences with minimal control. The supplied evidence does not establish whether a particular host uses this port or whether it should be reachable from the public internet, so exposure is Unknown.

RFC 3551 says the profile supports RTP over unicast and multicast UDP, as well as TCP. This describes profile transport support; it does not establish that TCP uses port 5004. The RFC also says profile use may be implicit, without an explicit port number or protocol identifier, so a port number alone cannot confirm RTP/AVP traffic.

Treat the registry entry as a service reference, not evidence of deployment or observed traffic. The sources provide no scoped prevalence measurement or information about malware associations.

Exposure

Unknown; the supplied protocol evidence does not establish the intended public reachability of this service.

Protocol

IANA assigns 5004/UDP to avt-profile-1, described as RTP media data.

Identification

A port match alone does not confirm RTP/AVP, whose use may be implicit under RFC 3551.

IANA service

avt-profile-1, described as RTP media data [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Protocol profile

RFC 3551 specifies RTP/AVP for RTP version 2 and RTCP in audio and video multiparticipant conferences with minimal control

UDP and TCP support

RFC 3551 specifies RTP over unicast and multicast UDP as well as TCP; this does not establish TCP on port 5004 [Confirmed] — https://www.rfc-editor.org/rfc/rfc3551.txt

Deployment on a particular host

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