NETCONF Transport Port Numbers

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 2 January 2026.¶

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 (https://trustee.ietf.org/license-info) 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

1. 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, many of these assignments are for a transport protocol (i.e., UDP) for which the requesting application does not apply. Also, many of the assignments are for protocols that are not deployed and were tagged as Historic: [RFC4743] and [RFC4744].¶

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.¶

Releasing back some port numbers softens the exhaustion risk of available port number space (especially the System Ports range (Section 6 of [RFC6335])).¶

2. Operational Considerations

There are no known implementations and deployments of protocols that rely upon the port numbers released back by this document. As such, there are no new operations or manageability requirements introduced by this document.¶

3. Security Considerations

This document does not describe any protocol. As such, this document does not introduce any new security vulnerability.¶

4. IANA Considerations

This document requests IANA to update the "Service Name and Transport Protocol Port Number Registry" registry [IANA-SERVICE] as specified in the following subsections.¶

• Note to the RFC Editor: Please replace "THIS_DOCUMENT" with the RFC number to be assigned to this document.¶

5. References

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 and Mahesh Jethanandani for the AD review.¶

Author's Address