Updates to NETCONF Transport Port Numbers Orange
mohamed.boucadair@orange.com
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.
Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at .
Copyright Notice Copyright (c) 2025 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents () in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.
Table of Contents
  • .  Introduction
  • .  Operational Considerations
  • .  Security Considerations
  • .  IANA Considerations
    • .  NETCONF over BEEP Service
    • .  NETCONF over SOAP Service
  • .  References
    • .  Normative References
    • .  Informative References
  • Acknowledgments
  • Author's Address
Introduction The "Service Name and Transport Protocol Port Number Registry" records several NETCONF-related port and service name assignments such as 830 for NETCONF over Secure Shell (SSH) , 831 for NETCONF over the Blocks Extensible Exchange Protocol (BEEP) , 832 for NETCONF over the Simple Object Access Protocol (SOAP) , 4334 for NETCONF Call Home , and 6513 for NETCONF over Transport Layer Security (TLS) . However, three of these assignments (831, 832, and 833) are for protocols that are not deployed, and the relevant RFCs ( and ) 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 , 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 . 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" as specified in the following subsections. De-assigned allocations are marked per . 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
netconf-beep 831 udp NETCONF over BEEP
NEW:
Service Name Port Number Transport Protocol Description Reference
netconf-beep NETCONF over BEEP 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
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 RFC 9900
netconfsoapbeep NETCONF for SOAP over BEEP 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 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. Informative References Service Name and Transport Protocol Port Number Registry IANA 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. Work in Progress 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] 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 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 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. 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.
Acknowledgments Thanks to and for the guidance. Thanks to for the comments. Thanks to for the Shepherd review, for the AD review, for the INTDIR review, for Gen-ART review, for ARTART review, for the OPSDIR review, for TSVART review, and for the port review. Thanks to for the IESG review.
Author's Address Orange
mohamed.boucadair@orange.com