Updates to NETCONF Transport Port Numbers
RFC 9900
Mohamed Boucadair
Orange
mohamed.boucadair@orange.com
December 2025
OPS
netconf
de-assign
deallocate
release
This document releases IANA-assigned port numbers for services related to the Network Configuration Protocol (NETCONF) that have not been in use in production networks.
Introduction
The "Service Name and Transport Protocol Port Number Registry" [IANA-SERVICE] records several NETCONF-related port and service name assignments such as 830 for NETCONF over Secure Shell (SSH) [RFC6242], 831 for NETCONF over the Blocks Extensible Exchange Protocol (BEEP) [RFC4744], 832 for NETCONF over the Simple Object Access Protocol (SOAP) [RFC4743], 4334 for NETCONF Call Home [RFC8071], and 6513 for NETCONF over Transport Layer Security (TLS) [RFC7589][I-D.ietf-netconf-over-tls13].
However, three of these assignments (831, 832, and 833) are for protocols that are not deployed, and the relevant RFCs ([RFC4743] and [RFC4744]) have been marked Historic. All these assignments are thus no longer required to support these services.
This document de-assigns these unused port numbers.
Consistent with Section 8.2 of [RFC6335], this document does not de-assign service names; only port numbers are de-assigned for better usage of available scarce resources.
Operational Considerations
There are no known implementations and deployments of protocols that rely upon the port numbers released back by this document.
Existing configurations (if any) that associate the released port numbers with the service names "netconf-beep" and "netconfsoaphttp" need to be reassessed and updated according to the actions in Section 4.
Other than that, there are no new operations or manageability requirements introduced by this document.
Security Considerations
This document does not describe any protocol. As such, this document does not introduce any new security vulnerability.
IANA Considerations
Per this document, IANA has updated the "Service Name and Transport Protocol Port Number Registry" [IANA-SERVICE] as specified in the following subsections.
De-assigned allocations are marked per Section 8.2 of [RFC6335]. These actions are not repeated here.
NETCONF over BEEP Service
OLD:
Service Name | Port Number | Transport Protocol | Description | Reference
netconf-beep | 831 | tcp | NETCONF over BEEP | [RFC4744]
netconf-beep | 831 | udp | NETCONF over BEEP | [RFC4744]
NEW:
Service Name | Port Number | Transport Protocol | Description | Reference
netconf-beep | | | NETCONF over BEEP | [RFC4744] RFC 9900
A note has been added to 831 to indicate that the port number used to be assigned to NETCONF over BEEP but was released by RFC 9900.
NETCONF over SOAP Service
OLD:
Service Name | Port Number | Transport Protocol | Description | Reference
netconfsoaphttp | 832 | tcp | NETCONF for SOAP over HTTPS | [RFC4743]
netconfsoaphttp | 832 | udp | NETCONF for SOAP over HTTPS | [RFC4743]
netconfsoapbeep | 833 | tcp | NETCONF for SOAP over BEEP | [RFC4743]
netconfsoapbeep | 833 | udp | NETCONF for SOAP over BEEP | [RFC4743]
NEW:
Service Name | Port Number | Transport Protocol | Description | Reference
netconfsoaphttp | | | NETCONF for SOAP over HTTPS | [RFC4743] RFC 9900
netconfsoapbeep | | | NETCONF for SOAP over BEEP | [RFC4743] RFC 9900
A note has been added to 832 and 833 to indicate that the port numbers used to be assigned to NETCONF over SOAP but were released by RFC 9900.
References
Normative References
Informative References
[IANA-SERVICE]

Service Name and Transport Protocol Port Number Registry
IANA
[RFC6242]
[RFC4744]
[RFC4743]
[RFC8071]
[RFC7589]
[I-D.ietf-netconf-over-tls13]
[RFC6335]
Acknowledgments
Thanks to Amanda Baber and Zahed Sarker for the guidance. Thanks to Tom Petch for the comments.
Thanks to Kent Watsen for the Shepherd review, Mahesh Jethanandani for the AD review, Bernie Volz for the INTDIR review, Roni Even for Gen-ART review, Barry Leiba for ARTART review, Dhruv Dhody for the OPSDIR review, Michael Tüxen for TSVART review, and Joe Touch for the port review.
Thanks to Gorry Fairhurst for the IESG review.