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 8 April 2025.¶

Copyright Notice

Copyright (c) 2024 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 following table lists currently (per 2024) assigned port numbers [IANA-SERVICE] for various NETCONF transports.¶

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 (Section 7 of [RFC4744]) states the following:¶

IANA assigned TCP port (831) for NETCONF over BEEP.¶

• "Using the NETCONF Protocol over Secure Shell (SSH)" specification (Section 7 of [RFC6242]) 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 (Section 5 of [RFC4743]) 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: [RFC4743] and [RFC4744]. [I-D.ietf-netconf-rfc4743-rfc4744-to-historic] 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 Section 8.2 of [RFC6335], 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.¶

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

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

4. Informative References

[I-D.ietf-netconf-over-tls13]

Turner, S. and R. Housley, "Updates to Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication", Work in Progress, Internet-Draft, draft-ietf-netconf-over-tls13-04, 18 January 2024, <https://datatracker.ietf.org/doc/html/draft-ietf-netconf-over-tls13-04>.

[I-D.ietf-netconf-rfc4743-rfc4744-to-historic]

Wijnen, B., "RFC4743 and RFC4744 to Historic status", Work in Progress, Internet-Draft, draft-ietf-netconf-rfc4743-rfc4744-to-historic-00, 7 September 2012, <https://datatracker.ietf.org/doc/html/draft-ietf-netconf-rfc4743-rfc4744-to-historic-00>.

[IANA-SERVICE]

"Service Name and Transport Protocol Port Number Registry", n.d., <https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml>.

[RFC4743]

Goddard, T., "Using NETCONF over the Simple Object Access Protocol (SOAP)", RFC 4743, DOI 10.17487/RFC4743, December 2006, <https://www.rfc-editor.org/rfc/rfc4743>.

[RFC4744]

Lear, E. and K. Crozier, "Using the NETCONF Protocol over the Blocks Extensible Exchange Protocol (BEEP)", RFC 4744, DOI 10.17487/RFC4744, December 2006, <https://www.rfc-editor.org/rfc/rfc4744>.

[RFC6242]

Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, <https://www.rfc-editor.org/rfc/rfc6242>.

[RFC6335]

Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. Cheshire, "Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry", BCP 165, RFC 6335, DOI 10.17487/RFC6335, August 2011, <https://www.rfc-editor.org/rfc/rfc6335>.

[RFC7589]

Badra, M., Luchuk, A., and J. Schoenwaelder, "Using the NETCONF Protocol over Transport Layer Security (TLS) with Mutual X.509 Authentication", RFC 7589, DOI 10.17487/RFC7589, June 2015, <https://www.rfc-editor.org/rfc/rfc7589>.

[RFC8071]

Watsen, K., "NETCONF Call Home and RESTCONF Call Home", RFC 8071, DOI 10.17487/RFC8071, February 2017, <https://www.rfc-editor.org/rfc/rfc8071>.

Acknowledgments

TBC.¶

Author's Address