]> Orange

mohamed.boucadair@orange.com

Operations and Management Network Configuration de-assign deallocate release This document releases NETCONF-related port number IANA assignments that were made for inappropriate transport protocols or for Historic NETCONF-related protocols. Discussion Venues Discussion of this document takes place on the Network Configuration Working Group mailing list (netconf@ietf.org), which is archived at . Source for this draft and an issue tracker can be found at .

Introduction The "Service Name and Transport Protocol Port Number" registry records several NETCONF-related port and service name assignments such as 830 for NETCONF over Secure Shell (SSH) , 831 for NETCONF over the Blocks Extensible Exchange Protocol (BEEP) , 832 for NETCONF over the Simple Object Access Protocol (SOAP) , 4334 for NETCONF Call Home , and 6513 for NETCONF over Transport Layer Security (TLS) . However, many of these assignments are for a transport protocol (i.e., UDP) for which the requesting application does not apply. Also, many of the assignments are for protocols that are not deployed and were tagged as Historic: and . This document de-assigns these unused port numbers. Consistent with , this document does not de-assign service names; only port numbers are de-assigned for better usage of available scarce resources.

Security Considerations Releasing back some port numbers softens the exhaustion risk of available port number space (especially the System Ports range ()). This document does not describe any protocol.

IANA Considerations This document requests IANA to update the "Service Name and Transport Protocol Port Number Registry" registry as specified in the following subsections.

• Note to the RFC Editor: Please replace "THIS_DOCUMENT" with the RFC number to be assigned to this document.

NETCONF over SSH Service OLD:

Service Name	Port Number	Transport Protocol	Description	Reference
netconf-ssh	830	tcp	NETCONF over SSH
netconf-ssh	830	udp	NETCONF over SSH

NEW:

Service Name	Port Number	Transport Protocol	Description	Reference
netconf-ssh	830	tcp	NETCONF over SSH

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.

NETCONF over BEEP Service OLD:

Service Name	Port Number	Transport Protocol	Description	Reference
netconf-beep	831	tcp	NETCONF over BEEP
netconf-beep	831	udp	NETCONF over BEEP

NEW:

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

NETCONF over SOAP Service OLD:

Service Name	Port Number	Transport Protocol	Description	Reference
netconfsoaphttp	832	tcp	NETCONF for SOAP over HTTPS
netconfsoaphttp	832	udp	NETCONF for SOAP over HTTPS
netconfsoapbeep	833	tcp	NETCONF for SOAP over BEEP
netconfsoapbeep	833	udp	NETCONF for SOAP over BEEP

NEW:

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

References Normative References This document defines the procedures that the Internet Assigned Numbers Authority (IANA) uses when handling assignment and other requests related to the Service Name and Transport Protocol Port Number registry. It also discusses the rationale and principles behind these procedures and how they facilitate the long-term sustainability of the registry. This document updates IANA's procedures by obsoleting the previous UDP and TCP port assignment procedures defined in Sections 8 and 9.1 of the IANA Allocation Guidelines, and it updates the IANA service name and port assignment procedures for UDP-Lite, the Datagram Congestion Control Protocol (DCCP), and the Stream Control Transmission Protocol (SCTP). It also updates the DNS SRV specification to clarify what a service name is and how it is registered. This memo documents an Internet Best Current Practice. Informative References n.d. This document describes a method for invoking and running the Network Configuration Protocol (NETCONF) within a Secure Shell (SSH) session as an SSH subsystem. This document obsoletes RFC 4742. [STANDARDS-TRACK] This document specifies an application protocol mapping for the Network Configuration Protocol (NETCONF) over the Blocks Extensible Exchange Protocol (BEEP). [STANDARDS-TRACK] The Network Configuration Protocol (NETCONF) is applicable to a wide range of devices in a variety of environments. Web Services is one such environment and is presently characterized by the use of the Simple Object Access Protocol (SOAP). NETCONF finds many benefits in this environment: from the reuse of existing standards, to ease of software development, to integration with deployed systems. Herein, we describe SOAP over HTTP and SOAP over Blocks Exchange Extensible Protocol (BEEP) bindings for NETCONF. [STANDARDS-TRACK] This RFC presents NETCONF Call Home and RESTCONF Call Home, which enable a NETCONF or RESTCONF server to initiate a secure connection to a NETCONF or RESTCONF client, respectively. The Network Configuration Protocol (NETCONF) provides mechanisms to install, manipulate, and delete the configuration of network devices. This document describes how to use the Transport Layer Security (TLS) protocol with mutual X.509 authentication to secure the exchange of NETCONF messages. This revision of RFC 5539 documents the new message framing used by NETCONF 1.1 and it obsoletes RFC 5539. sn3rd Vigil Security, LLC RFC 7589 defines how to protect NETCONF messages with TLS 1.2. This document updates RFC 7589 to update support requirements for TLS 1.2 and add TLS 1.3 support requirements, including restrictions on the use of TLS 1.3's early data.

Acknowledgments Thanks to Amanda Baber and Zahed Sarker for the guidance. Thanks to Kent Watsen for the Shepherd review.