Skip to main content

4. IANA Considerations

Per this document, IANA has updated the "Service Name and Transport Protocol Port Number 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.

4.1 NETCONF over BEEP Service

OLD:

Service NamePort NumberTransport ProtocolDescriptionReference
netconf-beep831tcpNETCONF over BEEP[RFC4744]
netconf-beep831udpNETCONF over BEEP[RFC4744]

NEW:

Service NamePort NumberTransport ProtocolDescriptionReference
netconf-beepNETCONF over BEEP[RFC4744] RFC 9900

A note has been added to 831 to indicate that the port number used to be assigned to NETCONF over BEEP but was released by RFC 9900.

4.2 NETCONF over SOAP Service

OLD:

Service NamePort NumberTransport ProtocolDescriptionReference
netconfsoaphttp832tcpNETCONF for SOAP over HTTPS[RFC4743]
netconfsoaphttp832udpNETCONF for SOAP over HTTPS[RFC4743]
netconfsoapbeep833tcpNETCONF for SOAP over BEEP[RFC4743]
netconfsoapbeep833udpNETCONF for SOAP over BEEP[RFC4743]

NEW:

Service NamePort NumberTransport ProtocolDescriptionReference
netconfsoaphttpNETCONF for SOAP over HTTPS[RFC4743] RFC 9900
netconfsoapbeepNETCONF for SOAP over BEEP[RFC4743] RFC 9900

A note has been added to 832 and 833 to indicate that the port numbers used to be assigned to NETCONF over SOAP but were released by RFC 9900.