rfc9900.original   rfc9900.txt 
Network Configuration M. Boucadair Internet Engineering Task Force (IETF) M. Boucadair
Internet-Draft Orange Request for Comments: 9900 Orange
Intended status: Standards Track 16 September 2025 Category: Standards Track December 2025
Expires: 20 March 2026 ISSN: 2070-1721
Updates to NETCONF Transport Port Numbers Updates to NETCONF Transport Port Numbers
draft-ietf-netconf-port-numbers-07
Abstract Abstract
This document releases NETCONF-related port number IANA assignments This document releases NETCONF-related port number IANA assignments
for services that have not been in use in production networks. 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 Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
This Internet-Draft will expire on 20 March 2026. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc9900.
Copyright Notice Copyright Notice
Copyright (c) 2025 IETF Trust and the persons identified as the Copyright (c) 2025 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents (https://trustee.ietf.org/ Provisions Relating to IETF Documents
license-info) in effect on the date of publication of this document. (https://trustee.ietf.org/license-info) in effect on the date of
Please review these documents carefully, as they describe your rights publication of this document. Please review these documents
and restrictions with respect to this document. Code Components carefully, as they describe your rights and restrictions with respect
extracted from this document must include Revised BSD License text as to this document. Code Components extracted from this document must
described in Section 4.e of the Trust Legal Provisions and are include Revised BSD License text as described in Section 4.e of the
provided without warranty as described in the Revised BSD License. Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction
2. Operational Considerations . . . . . . . . . . . . . . . . . 3 2. Operational Considerations
3. Security Considerations . . . . . . . . . . . . . . . . . . . 3 3. Security Considerations
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 3 4. IANA Considerations
4.1. NETCONF over BEEP Service . . . . . . . . . . . . . . . . 3 4.1. NETCONF over BEEP Service
4.2. NETCONF over SOAP Service . . . . . . . . . . . . . . . . 4 4.2. NETCONF over SOAP Service
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 5. References
5.1. Normative References . . . . . . . . . . . . . . . . . . 5 5.1. Normative References
5.2. Informative References . . . . . . . . . . . . . . . . . 5 5.2. Informative References
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 6 Acknowledgments
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address
1. Introduction 1. Introduction
The "Service Name and Transport Protocol Port Number" registry The "Service Name and Transport Protocol Port Number Registry"
[IANA-SERVICE] records several NETCONF-related port and service name [IANA-SERVICE] records several NETCONF-related port and service name
assignments such as 830 for NETCONF over Secure Shell (SSH) assignments such as 830 for NETCONF over Secure Shell (SSH)
[RFC6242], 831 for NETCONF over the Blocks Extensible Exchange [RFC6242], 831 for NETCONF over the Blocks Extensible Exchange
Protocol (BEEP) [RFC4744], 832 for NETCONF over the Simple Object Protocol (BEEP) [RFC4744], 832 for NETCONF over the Simple Object
Access Protocol (SOAP) [RFC4743], 4334 for NETCONF Call Home Access Protocol (SOAP) [RFC4743], 4334 for NETCONF Call Home
[RFC8071], and 6513 for NETCONF over Transport Layer Security (TLS) [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 However, three of these assignments (831, 832, and 833) are for
protocols that are not deployed and were tagged as Historic protocols that are not deployed, and the relevant RFCs ([RFC4743] and
([RFC4743] and [RFC4744]). All these assignments are thus no longer [RFC4744]) have been marked Historic. All these assignments are thus
required to support these services. no longer required to support these services.
This document de-assigns these unused port numbers. This document de-assigns these unused port numbers.
Consistent with Section 8.2 of [RFC6335], this document does not de- Consistent with Section 8.2 of [RFC6335], this document does not de-
assign service names; only port numbers are de-assigned for better assign service names; only port numbers are de-assigned for better
usage of available scarce resources. usage of available scarce resources.
2. Operational Considerations 2. Operational Considerations
There are no known implementations and deployments of protocols that There are no known implementations and deployments of protocols that
skipping to change at page 3, line 25 skipping to change at line 99
Other than that, there are no new operations or manageability Other than that, there are no new operations or manageability
requirements introduced by this document. requirements introduced by this document.
3. Security Considerations 3. Security Considerations
This document does not describe any protocol. As such, this document This document does not describe any protocol. As such, this document
does not introduce any new security vulnerability. does not introduce any new security vulnerability.
4. IANA Considerations 4. IANA Considerations
This document requests IANA to update the "Service Name and Transport Per this document, IANA has updated the "Service Name and Transport
Protocol Port Number Registry" registry [IANA-SERVICE] as specified Protocol Port Number Registry" [IANA-SERVICE] as specified in the
in the following subsections. following subsections.
De-assigned allocations are marked per Section 8.2 of [RFC6335]. De-assigned allocations are marked per Section 8.2 of [RFC6335].
These actions are not repeated here. 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 4.1. NETCONF over BEEP Service
OLD: OLD:
+==============+=============+===========+=============+===========+ +==============+=============+===========+=============+===========+
| Service Name | Port Number | Transport | Description | Reference | | Service Name | Port Number | Transport | Description | Reference |
| | | Protocol | | | | | | Protocol | | |
+==============+=============+===========+=============+===========+ +==============+=============+===========+=============+===========+
| netconf-beep | 831 | tcp | NETCONF | [RFC4744] | | netconf-beep | 831 | tcp | NETCONF | [RFC4744] |
| | | | over BEEP | | | | | | over BEEP | |
+--------------+-------------+-----------+-------------+-----------+ +--------------+-------------+-----------+-------------+-----------+
| netconf-beep | 831 | udp | NETCONF | [RFC4744] | | netconf-beep | 831 | udp | NETCONF | [RFC4744] |
| | | | over BEEP | | | | | | over BEEP | |
+--------------+-------------+-----------+-------------+-----------+ +--------------+-------------+-----------+-------------+-----------+
Table 1 Table 1
NEW: NEW:
+==============+========+===========+=============+===============+ +==============+=============+===========+=============+===========+
| Service Name | Port | Transport | Description | Reference | | Service Name | Port Number | Transport | Description | Reference |
| | Number | Protocol | | | | | | Protocol | | |
+==============+========+===========+=============+===============+ +==============+=============+===========+=============+===========+
| netconf-beep | | | NETCONF | [RFC4744] | | netconf-beep | | | NETCONF | [RFC4744] |
| | | | over BEEP | THIS_DOCUMENT | | | | | over BEEP | RFC 9900 |
+--------------+--------+-----------+-------------+---------------+ +--------------+-------------+-----------+-------------+-----------+
Table 2 Table 2
A note can be added to 831 to indicate that the port number used to A note has been added to 831 to indicate that the port number used to
be assigned to NETCONF over BEEP but released by THIS_DOCUMENT. be assigned to NETCONF over BEEP but was released by RFC 9900.
4.2. NETCONF over SOAP Service 4.2. NETCONF over SOAP Service
OLD: OLD:
+=================+========+===========+=============+===========+ +=================+========+===========+=============+===========+
| Service Name | Port | Transport | Description | Reference | | Service Name | Port | Transport | Description | Reference |
| | Number | Protocol | | | | | Number | Protocol | | |
+=================+========+===========+=============+===========+ +=================+========+===========+=============+===========+
| netconfsoaphttp | 832 | tcp | NETCONF for | [RFC4743] | | netconfsoaphttp | 832 | tcp | NETCONF for | [RFC4743] |
skipping to change at page 5, line 5 skipping to change at line 167
+-----------------+--------+-----------+-------------+-----------+ +-----------------+--------+-----------+-------------+-----------+
| netconfsoapbeep | 833 | udp | NETCONF for | [RFC4743] | | netconfsoapbeep | 833 | udp | NETCONF for | [RFC4743] |
| | | | SOAP over | | | | | | SOAP over | |
| | | | BEEP | | | | | | BEEP | |
+-----------------+--------+-----------+-------------+-----------+ +-----------------+--------+-----------+-------------+-----------+
Table 3 Table 3
NEW: NEW:
+=================+======+===========+=============+===============+ +=================+========+===========+=============+===========+
| Service Name | Port | Transport | Description | Reference | | Service Name | Port | Transport | Description | Reference |
| |Number| Protocol | | | | | Number | Protocol | | |
+=================+======+===========+=============+===============+ +=================+========+===========+=============+===========+
| netconfsoaphttp | | | NETCONF for | [RFC4743] | | netconfsoaphttp | | | NETCONF for | [RFC4743] |
| | | | SOAP over | THIS_DOCUMENT | | | | | SOAP over | RFC 9900 |
| | | | HTTPS | | | | | | HTTPS | |
+-----------------+------+-----------+-------------+---------------+ +-----------------+--------+-----------+-------------+-----------+
| netconfsoapbeep | | | NETCONF for | [RFC4743] | | netconfsoapbeep | | | NETCONF for | [RFC4743] |
| | | | SOAP over | THIS_DOCUMENT | | | | | SOAP over | RFC 9900 |
| | | | BEEP | | | | | | BEEP | |
+-----------------+------+-----------+-------------+---------------+ +-----------------+--------+-----------+-------------+-----------+
Table 4 Table 4
A note can be added to 832/833 to indicate that the port numbers used A note has been added to 832 and 833 to indicate that the port
to be assigned to NETCONF over SOAP but released by THIS_DOCUMENT. numbers used to be assigned to NETCONF over SOAP but were released by
RFC 9900.
5. References 5. References
5.1. Normative References 5.1. Normative References
[RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S. [RFC6335] Cotton, M., Eggert, L., Touch, J., Westerlund, M., and S.
Cheshire, "Internet Assigned Numbers Authority (IANA) Cheshire, "Internet Assigned Numbers Authority (IANA)
Procedures for the Management of the Service Name and Procedures for the Management of the Service Name and
Transport Protocol Port Number Registry", BCP 165, Transport Protocol Port Number Registry", BCP 165,
RFC 6335, DOI 10.17487/RFC6335, August 2011, 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 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 Turner, S. and R. Housley, "Updates to Using the NETCONF
Protocol over Transport Layer Security (TLS) with Mutual Protocol over Transport Layer Security (TLS) with Mutual
X.509 Authentication", Work in Progress, Internet-Draft, X.509 Authentication", Work in Progress, Internet-Draft,
draft-ietf-netconf-over-tls13-04, 18 January 2024, draft-ietf-netconf-over-tls13-04, 18 January 2024,
<https://datatracker.ietf.org/doc/html/draft-ietf-netconf- <https://datatracker.ietf.org/doc/html/draft-ietf-netconf-
over-tls13-04>. 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 [RFC4743] Goddard, T., "Using NETCONF over the Simple Object Access
Protocol (SOAP)", RFC 4743, DOI 10.17487/RFC4743, December Protocol (SOAP)", RFC 4743, DOI 10.17487/RFC4743, December
2006, <https://www.rfc-editor.org/rfc/rfc4743>. 2006, <https://www.rfc-editor.org/info/rfc4743>.
[RFC4744] Lear, E. and K. Crozier, "Using the NETCONF Protocol over [RFC4744] Lear, E. and K. Crozier, "Using the NETCONF Protocol over
the Blocks Extensible Exchange Protocol (BEEP)", RFC 4744, the Blocks Extensible Exchange Protocol (BEEP)", RFC 4744,
DOI 10.17487/RFC4744, December 2006, 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 [RFC6242] Wasserman, M., "Using the NETCONF Protocol over Secure
Shell (SSH)", RFC 6242, DOI 10.17487/RFC6242, June 2011, 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 [RFC7589] Badra, M., Luchuk, A., and J. Schoenwaelder, "Using the
NETCONF Protocol over Transport Layer Security (TLS) with NETCONF Protocol over Transport Layer Security (TLS) with
Mutual X.509 Authentication", RFC 7589, Mutual X.509 Authentication", RFC 7589,
DOI 10.17487/RFC7589, June 2015, 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", [RFC8071] Watsen, K., "NETCONF Call Home and RESTCONF Call Home",
RFC 8071, DOI 10.17487/RFC8071, February 2017, RFC 8071, DOI 10.17487/RFC8071, February 2017,
<https://www.rfc-editor.org/rfc/rfc8071>. <https://www.rfc-editor.org/info/rfc8071>.
Acknowledgments Acknowledgments
Thanks to Amanda Baber and Zahed Sarker for the guidance. Thanks to Thanks to Amanda Baber and Zahed Sarker for the guidance. Thanks to
Tom Petch for the comments. Tom Petch for the comments.
Thanks to Kent Watsen for the Shepherd review, Mahesh Jethanandani Thanks to Kent Watsen for the Shepherd review, Mahesh Jethanandani
for the AD review, Bernie Volz for the INTDIR review, Roni Even for for the AD review, Bernie Volz for the INTDIR review, Roni Even for
genart review, Barry Leiba for ARTART review, Dhruv Dhody for the 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 OPSDIR review, Michael Tüxen for TSVART review, and Joe Touch for the
port review. port review.
Thanks to Gorry Fairhurst for the IESG review. Thanks to Gorry Fairhurst for the IESG review.
Author's Address Author's Address
Mohamed Boucadair Mohamed Boucadair
Orange Orange
Email: mohamed.boucadair@orange.com Email: mohamed.boucadair@orange.com
 End of changes. 27 change blocks. 
95 lines changed or deleted 78 lines changed or added

This html diff was produced by rfcdiff 1.48.