Network Configuration
Internet Engineering Task Force (IETF) M. Boucadair
Internet-Draft
Request for Comments: 9900 Orange
Intended status:
Category: Standards Track 16 September December 2025
Expires: 20 March 2026
ISSN: 2070-1721
Updates to NETCONF Transport Port Numbers
draft-ietf-netconf-port-numbers-07
Abstract
This document releases NETCONF-related port number IANA assignments
for services that have not been in use in production networks.
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 an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list It represents the consensus of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid the IETF community. It has
received public review and has been approved for a maximum publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of six months RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be updated, replaced, or obsoleted by other documents obtained 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 20 March 2026.
https://www.rfc-editor.org/info/rfc9900.
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)
(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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Operational Considerations . . . . . . . . . . . . . . . . . 3
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3
4.1. NETCONF over BEEP Service . . . . . . . . . . . . . . . . 3
4.2. NETCONF over SOAP Service . . . . . . . . . . . . . . . . 4
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.1. Normative References . . . . . . . . . . . . . . . . . . 5
5.2. Informative References . . . . . . . . . . . . . . . . . 5
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction
The "Service Name and Transport Protocol Port Number" registry 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].
[RFC7589][NETCONF-over-TLS].
However, three of these assignments (831, 832, and 833) are for
protocols that are not deployed deployed, and were tagged as Historic the relevant RFCs ([RFC4743] and [RFC4744]).
[RFC4744]) 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 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.
2. 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
Section 4.
Other than that, 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
Per this document, IANA to update has updated the "Service Name and Transport
Protocol Port Number Registry" registry [IANA-SERVICE] as specified in the
following subsections.
De-assigned allocations are marked per Section 8.2 of [RFC6335].
These actions are not repeated here.
Note to the RFC Editor: Please replace "THIS_DOCUMENT" with the
RFC number to be assigned to this document.
4.1. NETCONF over BEEP Service
OLD:
+==============+=============+===========+=============+===========+
| Service Name | Port Number | Transport | Description | Reference |
| | | Protocol | | |
+==============+=============+===========+=============+===========+
| netconf-beep | 831 | tcp | NETCONF | [RFC4744] |
| | | | over BEEP | |
+--------------+-------------+-----------+-------------+-----------+
| netconf-beep | 831 | udp | NETCONF | [RFC4744] |
| | | | over BEEP | |
+--------------+-------------+-----------+-------------+-----------+
Table 1
NEW:
+==============+========+===========+=============+===============+
+==============+=============+===========+=============+===========+
| Service Name | Port Number | Transport | Description | Reference |
| | Number | Protocol | | |
+==============+========+===========+=============+===============+
+==============+=============+===========+=============+===========+
| netconf-beep | | | NETCONF | [RFC4744] |
| | | | over BEEP | THIS_DOCUMENT RFC 9900 |
+--------------+--------+-----------+-------------+---------------+
+--------------+-------------+-----------+-------------+-----------+
Table 2
A note can be has been added to 831 to indicate that the port number used to
be assigned to NETCONF over BEEP but was released by THIS_DOCUMENT. RFC 9900.
4.2. NETCONF over SOAP Service
OLD:
+=================+========+===========+=============+===========+
| Service Name | Port | Transport | Description | Reference |
| | Number | Protocol | | |
+=================+========+===========+=============+===========+
| netconfsoaphttp | 832 | tcp | NETCONF for | [RFC4743] |
| | | | SOAP over | |
| | | | HTTPS | |
+-----------------+--------+-----------+-------------+-----------+
| netconfsoaphttp | 832 | udp | NETCONF for | [RFC4743] |
| | | | SOAP over | |
| | | | HTTPS | |
+-----------------+--------+-----------+-------------+-----------+
| netconfsoapbeep | 833 | tcp | NETCONF for | [RFC4743] |
| | | | SOAP over | |
| | | | BEEP | |
+-----------------+--------+-----------+-------------+-----------+
| netconfsoapbeep | 833 | udp | NETCONF for | [RFC4743] |
| | | | SOAP over | |
| | | | BEEP | |
+-----------------+--------+-----------+-------------+-----------+
Table 3
NEW:
+=================+======+===========+=============+===============+
+=================+========+===========+=============+===========+
| Service Name | Port | Transport | Description | Reference |
| |Number| | Number | Protocol | | |
+=================+======+===========+=============+===============+
+=================+========+===========+=============+===========+
| netconfsoaphttp | | | NETCONF for | [RFC4743] |
| | | | SOAP over | THIS_DOCUMENT RFC 9900 |
| | | | HTTPS | |
+-----------------+------+-----------+-------------+---------------+
+-----------------+--------+-----------+-------------+-----------+
| netconfsoapbeep | | | NETCONF for | [RFC4743] |
| | | | SOAP over | THIS_DOCUMENT RFC 9900 |
| | | | BEEP | |
+-----------------+------+-----------+-------------+---------------+
+-----------------+--------+-----------+-------------+-----------+
Table 4
A note can be has been added to 832/833 832 and 833 to indicate that the port
numbers used to be assigned to NETCONF over SOAP but were released by THIS_DOCUMENT.
RFC 9900.
5. References
5.1. Normative References
[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>.
<https://www.rfc-editor.org/info/rfc6335>.
5.2. Informative References
[I-D.ietf-netconf-over-tls13]
[IANA-SERVICE]
IANA, "Service Name and Transport Protocol Port Number
Registry", <https://www.iana.org/assignments/service-
names-port-numbers>.
[NETCONF-over-TLS]
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>.
[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>. <https://www.rfc-editor.org/info/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>.
<https://www.rfc-editor.org/info/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>.
<https://www.rfc-editor.org/info/rfc6242>.
[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>.
<https://www.rfc-editor.org/info/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>.
<https://www.rfc-editor.org/info/rfc8071>.
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, Mahesh Jethanandani
for the AD review, Bernie Volz for the INTDIR review, Roni Even for
genart
Gen-ART review, Barry Leiba for ARTART review, Dhruv Dhody for the
OPSDIR review, Michael Tüxen for TSVART review, and Joe Touch for the
port review.
Thanks to Gorry Fairhurst for the IESG review.
Author's Address
Mohamed Boucadair
Orange
Email: mohamed.boucadair@orange.com