3232

IANA registers TCP port 3232 as mdtp, described as “MDT port,” and associates it with RFC 6513, *Multicast in MPLS/BGP IP VPNs*. That identifies the registry entry, but it does not establish what software listens on 3232/tcp or whether a particular host uses it. The appropriate public-internet access policy is therefore unknown from the available protocol evidence.

RFC 6513 describes multicast VPN procedures for provider networks. In that context, provider edge routers exchange multicast routing information using PIM or BGP. The RFC also describes ingress replication: an ingress router sends a unicast copy toward each egress router, reducing the need for multicast distribution state in the provider backbone while increasing replication work at the ingress.

These are RFC 6513 network-design mechanisms, not verified behavior of TCP port 3232. The available record does not specify a TCP/3232 message format, endpoint role, deployment pattern, prevalence, or security properties. Identify traffic by its actual protocol behavior and host configuration rather than by the port number alone.

Assessment

RFC 6513 provides multicast VPN context, but does not establish that its PIM, BGP, or ingress-replication procedures use this TCP port.

IANA service

mdtp, described as “MDT port” [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Protocol behavior on TCP/3232

Unknown

RFC association

RFC 6513, *Multicast in MPLS/BGP IP VPNs* [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv

Public access policy

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