4555
Summary
- // if you see it open
- RSIP allows a host to lease gateway addressing parameters and establish a global network presence. The supplied evidence does not establish specific vulnerabilities or malware use.
- // common applications
- Realm Specific IP (RSIP) A registry assignment and protocol specification are available; no deployment or traffic observations were supplied.
About port 4555/tcp.
IANA assigns TCP port 4555 to rsip (the “RSIP Port”) and cites RFC 3103. The registry identifies a service assignment; it does not show that any host currently runs RSIP on this port or establish whether it belongs on the public internet.
RFC 3103 describes Realm Specific IP (RSIP), an application-layer protocol for negotiating resources between an RSIP host and gateway. The host can lease gateway addressing parameters to establish a global network presence. The specification describes RSIP as Experimental and says it is not an Internet standard.
The RFC says RSIP gateways must support TCP and should support UDP, but it does not establish that every implementation uses port 4555. The supplied evidence provides no deployment, traffic prevalence, or malware observations. Identify RSIP through protocol evidence before attributing this port to it on a particular host.
- Service
- IANA assigns
rsipto TCP port4555and describes it as the “RSIP Port.” - Exposure
- Unknown — RFC 3103 describes RSIP resource negotiation between a private-realm host and a boundary gateway. The protocol carries control messages; data packets use a separate tunnel, and gateway flow policy can restrict communications by remote address and, at finer granularity, remote port. This design does not determine whether the service should be publicly accessible.
- Security
- RSIP enables hosts to lease gateway addressing parameters. The supplied sources do not establish specific vulnerabilities or malware associations.
- Service
- IANA assigns
rsipto 4555/tcp [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv - Status
- RFC 3103 defines an Experimental Protocol and says it does not specify an Internet standard [Confirmed] — https://www.rfc-editor.org/rfc/rfc3103.txt
Protocol purpose
RSIP negotiates resources between an RSIP host and gateway, including leased gateway addressing parameters
- Deployment, prevalence, and malware use
- Not established by supplied evidence [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
About port 4555/udp.
IANA assigns UDP port 4555 to rsip (RSIP Port) and cites RFC 3103. That identifies the registered service, not whether any particular host runs it or whether it belongs on the public internet; the intended exposure policy is therefore Unknown.
RFC 3103 describes Realm Specific IP (RSIP), an experimental application-layer protocol for negotiating address and related resources between a host and gateway. The RFC says the protocol can use TCP or UDP. It specifies that gateways must support TCP and should support UDP, while hosts may support UDP instead of TCP or alongside TCP. These general protocol requirements do not establish deployment on UDP 4555.
RSIP exchanges can affect gateway address assignments and traffic-flow policy. If UDP 4555 is observed, identify the endpoint and validate the service and its access controls before drawing conclusions from the port number alone. The supplied evidence gives no measured prevalence, current implementation status, or malware association.
- Service
- IANA assigns
rsipto UDP 4555 and cites RFC 3103. [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv - Protocol
- RFC 3103 describes RSIP resource negotiation between a host and gateway; UDP is supported by the protocol specification. [Confirmed] — https://www.rfc-editor.org/rfc/rfc3103.txt
- Exposure
- Unknown; RFC 3103 describes RSIP hosts in a private realm acquiring address and routing parameters from a gateway between private and public realms to establish global network presence, but the evidence does not show whether UDP 4555 is deployed or publicly exposed.[Unknown] — https://www.rfc-editor.org/rfc/rfc3103.txt
- Security
- RSIP involves gateway resource assignments and flow policy; confirm service identity and access controls when investigating an observed endpoint. [Likely] — https://www.rfc-editor.org/rfc/rfc3103.txt
- IANA service name
rsip[Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv- IANA description
RSIP Port[Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Protocol status
Experimental
Malware association
Unknown
- Reference
- RFC 3103 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
- Deployment on UDP 4555
- Unknown [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
- Traffic prevalence
- Unknown [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| rsip | TCP | RSIP Port | 0.02% |
| rsip | UDP | RSIP Port | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.