Internet-Draft NETCONF Transport Port Numbers September 2024
Boucadair Expires 30 March 2025 [Page]
Workgroup:
Network Configuration
Internet-Draft:
draft-boucadair-netconf-port-numbers-00
Published:
Intended Status:
Standards Track
Expires:
Author:
M. Boucadair
Orange

NETCONF Transport Port Numbers

Abstract

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

This note is to be removed before publishing as an RFC.

Discussion of this document takes place on the Network Configuration Working Group mailing list (netconf@ietf.org), which is archived at https://mailarchive.ietf.org/arch/browse/netconf/.

Source for this draft and an issue tracker can be found at https://github.com/boucadair/netconf-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 30 March 2025.

Table of Contents

1. Introduction

The following table lists currently (per 2024) assigned port numbers [IANA-SERVICE] for various NETCONF transports.

Table 1
Service Name Port Number Transport Protocol Description Reference
netconf-ssh 830 tcp NETCONF over SSH [RFC6242]
netconf-ssh 830 udp NETCONF over SSH [RFC6242]
netconf-beep 831 tcp NETCONF over BEEP [RFC4744]
netconf-beep 831 udp NETCONF over BEEP [RFC4744]
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]
netconf-ch-ssh 4334 tcp NETCONF Call Home (SSH) [RFC8071]
netconf-ch-tls 4335 tcp NETCONF Call Home (TLS) [RFC8071]
netconf-tls 6513 tcp NETCONF over TLS [RFC7589][RFC-ietf-netconf-over-tls13-04]

Many of these assignments are for a transport protocol (UDP) for which the requesting application does not apply. For example:

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

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.

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.

3.1. NETCONF over SSH Service

OLD:

Table 2
Service Name Port Number Transport Protocol Description Reference
netconf-ssh 830 tcp NETCONF over SSH [RFC6242]
netconf-ssh 830 udp NETCONF over SSH [RFC6242]

NEW:

Table 3
Service Name Port Number Transport Protocol Description Reference
netconf-ssh 830 tcp NETCONF over SSH [RFC6242]

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.

3.2. NETCONF over BEEP Service

OLD:

Table 4
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:

Table 5
Service Name Port Number Transport Protocol Description Reference
netconf-beep     NETCONF over BEEP [RFC4744] 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.

3.3. NETCONF over SOAP Service

OLD:

Table 6
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:

Table 7
Service Name Port Number Transport Protocol Description Reference
netconfsoaphttp     NETCONF for SOAP over HTTPS [RFC4743] THIS_DOCUMENT
netconfsoapbeep     NETCONF for SOAP over BEEP [RFC4743] 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.

3.4. NETCONF over TLS Service

OLD:

Table 8
Service Name Port Number Transport Protocol Description Reference
netconf-tls 6513 tcp NETCONF over TLS [RFC7589][RFC-ietf-netconf-over-tls13-04]

NEW:

Table 9
Service Name Port Number Transport Protocol Description Reference
netconf-tls 6513 tcp NETCONF over TLS [RFC7589][RFC8446]THIS_DOCUMENT

4. Informative References

[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, , <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, , <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, , <https://www.rfc-editor.org/rfc/rfc4744>.
[RFC6242]
Wasserman, M., "Using the NETCONF Protocol over Secure Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, , <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, , <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, , <https://www.rfc-editor.org/rfc/rfc7589>.
[RFC8071]
Watsen, K., "NETCONF Call Home and RESTCONF Call Home", RFC 8071, DOI 10.17487/RFC8071, , <https://www.rfc-editor.org/rfc/rfc8071>.
[RFC8446]
Rescorla, E., "The Transport Layer Security (TLS) Protocol Version 1.3", RFC 8446, DOI 10.17487/RFC8446, , <https://www.rfc-editor.org/rfc/rfc8446>.

Acknowledgments

TBC.

Author's Address

Mohamed Boucadair
Orange