Network port detail · TCP/UDP/SCTP

3863

Asap-udp
Protocol(s)
TCP/UDP/SCTP
Range
Registered (1024-49151)
Reference
RFC 5352

Summary

// if you see it open
The supplied evidence does not establish UDP deployment or service behavior. RFC 5352 describes ASAP/ENRP server pooling and specifies SCTP for messages between Pool Elements and ENRP servers; that does not establish UDP behavior or safety.
[ 01 ] — Context

About port 3863/udp.

Updated  ·  Confidence: High  ·  2 sources  ·  How this page is checked

IANA registers UDP port 3863 as asap-udp, with RFC 5352 as its reference. That identifies a registry assignment, not a service observed on a host. The available evidence does not establish whether this port should be reachable from the public internet, so its recommended exposure is Unknown.

RFC 5352 describes ASAP as part of a server-pooling protocol suite with ENRP, supporting handle-based addressing, load sharing, and failover. The RFC is Experimental and says the ASAP/ENRP handlespace is not Internet-wide. This gives useful context about the protocol’s intended scope, but does not show that UDP 3863 is deployed for those functions.

There is a transport distinction in the evidence: RFC 5352 says ASAP messages between Pool Elements and ENRP servers must use SCTP, while IANA separately registers the name asap-udp for UDP 3863. The supplied material does not explain that UDP assignment’s role. Do not treat the RFC’s SCTP requirement as proof of UDP behavior, or infer an application, traffic prevalence, or safety from the registration alone.

Exposure
Unknown. The evidence establishes a UDP registry assignment but does not establish the intended audience or whether hosts should accept public connections.
Protocol context
RFC 5352 describes ASAP for server pooling with ENRP, including handle resolution, load sharing, and failover; its handlespace is not Internet-wide.
Transport caveat
RFC 5352 requires SCTP for ASAP messages between Pool Elements and ENRP servers. The available evidence does not explain how that requirement relates to IANA’s UDP registration.
IANA service name
asap-udp [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Protocol context

ASAP is described as part of a high-availability server-pooling suite with ENRP

[Confirmed] — https://www.rfc-editor.org/rfc/rfc5352.txt
Port
3863/udp [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
RFC reference
RFC 5352 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
UDP deployment
Unknown [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Public-internet exposure
Unknown [Unknown] — https://www.rfc-editor.org/rfc/rfc5352.txt
// registry data

Service assignments.

3 entries
// IANA / nmap services registry
NameProtocolDescriptionOpen frequency
asap-tcp TCP RSerPool ASAP (TCP) 0.02%
asap-tcp UDP RSerPool ASAP (UDP) 0.00%
asap-sctp SCTP asap-udp 0.00%
IANA name
asap-udp
Transport
UDP
Range
Registered (1024-49151)
Reference
RFC 5352

Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.