



Network Configuration                                       M. Boucadair
Internet-Draft                                                    Orange
Intended status: Standards Track                        8 September 2025
Expires: 12 March 2026


               Updates to NETCONF Transport Port Numbers
                   draft-ietf-netconf-port-numbers-06

Abstract

   This document releases NETCONF-related port number IANA assignments
   that have not stood the test of time.

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 12 March 2026.

Copyright Notice

   Copyright (c) 2025 IETF Trust and the persons identified as the
   document authors.  All rights reserved.





Boucadair                 Expires 12 March 2026                 [Page 1]

Internet-Draft       NETCONF Transport Port Numbers       September 2025


   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  . . . . . . . . . . . . . . . . . . . . . . . .   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
   [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, three of these assignments are for protocols that are not
   deployed and were tagged as Historic ([RFC4743] and [RFC4744]).  All
   these assignments are undesirable.

   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.








Boucadair                 Expires 12 March 2026                 [Page 2]

Internet-Draft       NETCONF Transport Port Numbers       September 2025


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.

   Unassigned 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:









Boucadair                 Expires 12 March 2026                 [Page 3]

Internet-Draft       NETCONF Transport Port Numbers       September 2025


    +==============+========+===========+=============+===============+
    | Service Name |  Port  | Transport | Description |   Reference   |
    |              | Number |  Protocol |             |               |
    +==============+========+===========+=============+===============+
    | netconf-beep |        |           | NETCONF     |   [RFC4744]   |
    |              |        |           | over BEEP   | THIS_DOCUMENT |
    +--------------+--------+-----------+-------------+---------------+

                                  Table 2

   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.

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:










Boucadair                 Expires 12 March 2026                 [Page 4]

Internet-Draft       NETCONF Transport Port Numbers       September 2025


   +=================+======+===========+=============+===============+
   | Service Name    | Port | Transport | Description |   Reference   |
   |                 |Number|  Protocol |             |               |
   +=================+======+===========+=============+===============+
   | netconfsoaphttp |      |           | NETCONF for |   [RFC4743]   |
   |                 |      |           | SOAP over   | THIS_DOCUMENT |
   |                 |      |           | HTTPS       |               |
   +-----------------+------+-----------+-------------+---------------+
   | netconfsoapbeep |      |           | NETCONF for |   [RFC4743]   |
   |                 |      |           | SOAP over   | THIS_DOCUMENT |
   |                 |      |           | BEEP        |               |
   +-----------------+------+-----------+-------------+---------------+

                                 Table 4

   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.

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

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

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



Boucadair                 Expires 12 March 2026                 [Page 5]

Internet-Draft       NETCONF Transport Port Numbers       September 2025


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

   [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

   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 review, Barry Leiba for ARTART review, Dhruv Dhody for the
   OPSDIR review, and Michael Tüxen for TSVART review.

Author's Address

   Mohamed Boucadair
   Orange
   Email: mohamed.boucadair@orange.com

















Boucadair                 Expires 12 March 2026                 [Page 6]
