]> NETCONF Transport Port Numbers Orange
mohamed.boucadair@orange.com
Operations and Management Network Configuration de-assign This document releases NETCONF-related port number IANA assignments that were made for inappropriate transport protocols or for an Historic NETCONF-related protocol. Discussion Venues Discussion of this document takes place on the Network Configuration Working Group mailing list (netconf@ietf.org), which is archived at . Source for this draft and an issue tracker can be found at .
Introduction The following table lists currently (per 2024) assigned port numbers for various NETCONF transports.
Service Name Port Number Transport Protocol Description Reference
netconf-ssh 830 tcp NETCONF over SSH
netconf-ssh 830 udp NETCONF over SSH
netconf-beep 831 tcp NETCONF over BEEP
netconf-beep 831 udp NETCONF over BEEP
netconfsoaphttp 832 tcp NETCONF for SOAP over HTTPS
netconfsoaphttp 832 udp NETCONF for SOAP over HTTPS
netconfsoapbeep 833 tcp NETCONF for SOAP over BEEP
netconfsoapbeep 833 udp NETCONF for SOAP over BEEP
netconf-ch-ssh 4334 tcp NETCONF Call Home (SSH)
netconf-ch-tls 4335 tcp NETCONF Call Home (TLS)
netconf-tls 6513 tcp NETCONF over TLS
Many of these assignments are for a transport protocol (UDP) for which the requesting application does not apply. For example:
  • "Using the NETCONF Protocol over "the Blocks Extensible Exchange Protocol (BEEP)" specification () states the following:
IANA assigned TCP port (831) for NETCONF over BEEP.
  • "Using the NETCONF Protocol over Secure Shell (SSH)" specification () states the following:
Based on the previous version of this document, RFC 4742, IANA assigned the TCP port 830 as the default port for NETCONF over SSH sessions.
  • "Using NETCONF over the Simple Object Access Protocol (SOAP)" specification () states the following:
IANA assigned TCP port (833) for NETCONF over SOAP over BEEP, and TCP port (832) for NETCONF over SOAP over HTTPS.
It is understood that these assignments were made when the practice at that time (prior to 2011) was to automatically assign a port number for both TCP and UDP, even if a request was for only one of these transport protocols. Also, many of these assignments are for protocols that are not deployed and which were tagged as Historic: and . reported in 2012 that these two protocols:
"have shown very little (if any) implementations and deployment"
This document de-assigns these port numbers, that fall in the System Ports range. Consistent with , this document does not request to de-assign service names; only port numbers (for specific transport protocols) are de-assigned for better usage of available scarce resources.
Security Considerations Releasing back some port number softens the exhaustion risk of available port number space (especially the System Ports range). This document does not describe any protocol.
IANA Considerations This document requests IANA to update the "Service Name and Transport Protocol Port Number Registry" registry as specified in the following subsections.
NETCONF over SSH Service OLD:
Service Name Port Number Transport Protocol Description Reference
netconf-ssh 830 tcp NETCONF over SSH
netconf-ssh 830 udp NETCONF over SSH
NEW:
Service Name Port Number Transport Protocol Description Reference
netconf-ssh 830 tcp NETCONF over SSH
A note can be added to 830/udp to indicate that the port number used to be assigned to NETCONF over SSH but released by THIS_DOCUMENT.
NETCONF over BEEP Service OLD:
Service Name Port Number Transport Protocol Description Reference
netconf-beep 831 tcp NETCONF over BEEP
netconf-beep 831 udp NETCONF over BEEP
NEW:
Service Name Port Number Transport Protocol Description Reference
netconf-beep     NETCONF over BEEP THIS_DOCUMENT
A note can be added to 831 to indicate that the port number used to be assigned to NETCONF over BEEP but released by THIS_DOCUMENT.
NETCONF over SOAP Service OLD:
Service Name Port Number Transport Protocol Description Reference
netconfsoaphttp 832 tcp NETCONF for SOAP over HTTPS
netconfsoaphttp 832 udp NETCONF for SOAP over HTTPS
netconfsoapbeep 833 tcp NETCONF for SOAP over BEEP
netconfsoapbeep 833 udp NETCONF for SOAP over BEEP
NEW:
Service Name Port Number Transport Protocol Description Reference
netconfsoaphttp     NETCONF for SOAP over HTTPS THIS_DOCUMENT
netconfsoapbeep     NETCONF for SOAP over BEEP THIS_DOCUMENT
A note can be added to 832/833 to indicate that the port numbers used to be assigned to NETCONF over SOAP but released by THIS_DOCUMENT.
Informative References Service Name and Transport Protocol Port Number Registry n.d. Using the NETCONF Protocol over Secure Shell (SSH) This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP) This document specifies an application protocol mapping for the Network Configuration Protocol (NETCONF) over the Blocks Extensible Exchange Protocol (BEEP). [STANDARDS-TRACK] Using NETCONF over the Simple Object Access Protocol (SOAP) The Network Configuration Protocol (NETCONF) is applicable to a wide range of devices in a variety of environments. Web Services is one such environment and is presently characterized by the use of the Simple Object Access Protocol (SOAP). NETCONF finds many benefits in this environment: from the reuse of existing standards, to ease of software development, to integration with deployed systems. Herein, we describe SOAP over HTTP and SOAP over Blocks Exchange Extensible Protocol (BEEP) bindings for NETCONF. [STANDARDS-TRACK] NETCONF Call Home and RESTCONF Call Home This RFC presents NETCONF Call Home and RESTCONF Call Home, which enable a NETCONF or RESTCONF server to initiate a secure connection to a NETCONF or RESTCONF client, respectively. Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication The Network Configuration Protocol (NETCONF) provides mechanisms to install, manipulate, and delete the configuration of network devices. This document describes how to use the Transport Layer Security (TLS) protocol with mutual X.509 authentication to secure the exchange of NETCONF messages. This revision of RFC 5539 documents the new message framing used by NETCONF 1.1 and it obsoletes RFC 5539. Updates to Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication sn3rd Vigil Security, LLC RFC 7589 defines how to protect NETCONF messages with TLS 1.2. This document updates RFC 7589 to update support requirements for TLS 1.2 and add TLS 1.3 support requirements, including restrictions on the use of TLS 1.3's early data. RFC4743 and RFC4744 to Historic status This document moves RFC4743 (Using NETCONF over the Simple Object Access Protocol (SOAP)) and RFC4744 (Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)) to HISTORIC status to reflect the fact that those two documents have shown very little (if any) implementations and deployment. Furthermore, no-one in the NETCONF WG is interested or volunteering to work on them anymore. Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the Service Name and Transport Protocol Port Number registry. It also discusses the rationale and principles behind these procedures and how they facilitate the long-term sustainability of the registry. This document updates IANA's procedures by obsoleting the previous UDP and TCP port assignment procedures defined in Sections 8 and 9.1 of the IANA Allocation Guidelines, and it updates the IANA service name and port assignment procedures for UDP-Lite, the Datagram Congestion Control Protocol (DCCP), and the Stream Control Transmission Protocol (SCTP). It also updates the DNS SRV specification to clarify what a service name is and how it is registered. This memo documents an Internet Best Current Practice.
Acknowledgments TBC.