<?xmlversion="1.0" encoding="UTF-8"?>version='1.0' encoding='UTF-8'?> <!DOCTYPErfc> <?rfc toc="yes"?> <?rfc tocompact="yes"?> <?rfc tocdepth="2"?> <?rfc tocindent="yes"?> <?rfc symrefs="yes"?> <?rfc sortrefs="yes"?> <?rfc comments="yes"?> <?rfc inline="yes"?> <?rfc compact="yes"?> <?rfc subcompact="no"?>rfc [ <!ENTITY nbsp " "> <!ENTITY zwsp "​"> <!ENTITY nbhy "‑"> <!ENTITY wj "⁠"> ]> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" category="std" docName="draft-ietf-netconf-udp-client-server-10" number="9984" updates="" obsoletes="" ipr="trust200902" submissionType="IETF" consensus="true"xmlns:xi="http://www.w3.org/2001/XInclude">tocInclude="true" tocDepth="2" symRefs="true" sortRefs="true" version="3" xml:lang="en"> <front> <!--[rfced] We note that most of the recently published RFCs containing YANG modules format their titles as "A YANG Data Model for...", for example: RFC 9094 - A YANG Data Model for Wavelength Switched Optical Networks (WSONs) RFC 9093 - A YANG Data Model for Layer 0 Types RFC 9067 - A YANG Data Model for Routing Policy Please consider whether the title of this document should be updated. Current: YANG Groupings for UDP Clients and UDP Servers Please also consider if the repetition of UDP is necessary: Perhaps: YANG Groupings for UDP Clients and Servers (Note: the title appears in more places throughout the document.) --> <title abbrev="Groupings for UDP Clients and Servers">YANG Groupings for UDP Clients and UDP Servers</title> <seriesInfo name="RFC" value="9984"/> <author fullname="Alex Huang Feng" initials="A." surname="Huang-Feng"> <organization>INSA-Lyon</organization> <address> <postal><street/><city>Lyon</city><region/> <code/><country>France</country> </postal><phone/> <facsimile/><email>alex.huang-feng@insa-lyon.fr</email><uri/></address> </author> <author fullname="Pierre Francois" initials="P." surname="Francois"> <organization>INSA-Lyon</organization> <address> <postal><street/><city>Lyon</city><region/> <code/><country>France</country> </postal><phone/> <facsimile/><email>pierre.francois@insa-lyon.fr</email><uri/></address> </author> <author fullname="Kent Watsen" initials="K." surname="Watsen"> <organization>Watsen Networks</organization> <address> <email>kent+ietf@watsen.net</email> </address> </author> <dateday="16" month="December" year="2025"/> <abstract> <t>Thismonth="May" year="2026"/> <area>OPS</area> <workgroup>netconf</workgroup> <!-- [rfced] Please insert any keywords (beyond those that appear in the title) for use on https://www.rfc-editor.org/search. --> <keyword>example</keyword> <!--[rfced] We note that this document uses "defines" where other documents in cluster C463 use "presents". Please let us know if you'd like to update. Note that similar text appears more than once in the document. Original: This document defines two YANG 1.1 modules with reusable groupings for managing UDP clients and UDPservers.</t> </abstract> <note removeInRFC="true"> <name>Notes to the RFC editor</name> <t>Please replace "RFC XXXX"servers. Perhaps: This document presents two YANG 1.1 modules withthe assigned RFC number prior to publication. Notereusable groupings for managing UDP clients and UDP servers. --> <!--[rfced] We note thatthere are also several occurrences of "RFC XXXX"RFC 9643 (that you mentioned in the document intake form) and the other documents in cluster C463 all have a section titled "Relation to Other RFCs". Please review and let us know if any updates to this document are necessary. --> <abstract> <t>This document defines two YANGmodules. </t> </note>1.1 modules with reusable groupings for managing UDP clients and UDP servers.</t> </abstract> </front> <middle> <sectionanchor="introduction" title="Introduction">anchor="introduction"> <name>Introduction</name> <t>This document defines two YANG 1.1 <xref target="RFC7950"/> modules with reusable groupings for managing UDP clients and UDP servers <xref target="RFC768"/>. These modules may be used directly (e.g., define a specific UDP client or UDP server) or in conjunction with the configuration defined forhigher levelhigher-level protocols that depend on UDP.</t><section title="Requirements Language"> <t>The<section> <name>Requirements Language</name> <t> The key words"MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY","<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>", "<bcp14>MAY</bcp14>", and"OPTIONAL""<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as described inBCP 14BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shownhere.</t>here. </t> </section><section title="Adherence<section> <name>Adherence to theNMDA">NMDA</name> <t>This document is compliant with the Network Management Datastore Architecture (NMDA) <xref target="RFC8342"/>. It does not define anyprotocol accessibleprotocol-accessible nodes that are "config false".</t> </section><section title="Conventions"><section> <name>Conventions</name> <t>Various examples in this document use the XML <xref target="W3C.REC-xml-20081126"/> encoding. Other encodings, such as JSON <xref target="RFC8259"/>, could alternatively be used.</t> </section> </section> <sectionanchor="udp-client" title='Theanchor="udp-client"> <name>The "ietf-udp-client"Module'>Module</name> <t>This section defines a YANG 1.1 module called "ietf-udp-client". This YANG module defines the "udp-client" grouping for providing UDP clients with remote server information.</t> <t><xref target="udp-client-overview"/> provides the overview of the YANG module. An example of usage is illustrated in <xreftarget="example-client"/>, whiletarget="example-client"/>. <xref target="udp-client-ym"/> defines the YANG module itself.</t> <sectionanchor="udp-client-overview" title='Dataanchor="udp-client-overview"> <name>Data ModelOverview'>Overview</name> <t>This section provides an overview of the features and the grouping defined in the "ietf-udp-client" YANG module. </t><section title="Features"><section> <name>Features</name> <!--[rfced] Please review the use of "Features" (plural) in the feature statement in Section 2.1.1. Elsewhere in the document we see Feature (singular). For example, in the module: feature local-binding { --> <t>The "ietf-udp-client" module defines the following "feature" statement:</t> <sourcecode type="yangtree"><![CDATA[ Features: +--local-binding ]]></sourcecode>local-binding]]></sourcecode> <!--[rfced] Please review our update to the following text to ensure we've maintained your intended meaning: Original: The diagram above uses syntax that is similar to but not defined in [RFC8340]. Current: The diagram above uses syntax that is similar to the syntax used in [RFC8340]; but the syntax from the diagram is not defined in [RFC8340]. --> <t>The diagram above uses syntax that is similar to the syntax used in <xref target="RFC8340"/>; but the syntax from the diagram is not defined in <xref target="RFC8340"/>.</t> <t>This feature indicates that the client supports configuring local bindings (i.e., the local address and local port number) for UDP clients.</t> </section> <sectionanchor="udp-client-grouping" title='Theanchor="udp-client-grouping"> <name>The "udp-client"Grouping'>Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the tree structure of the "udp-client" grouping:</t> <sourcecode type="yangtree"><![CDATA[ module: ietf-udp-client grouping udp-client: +-- remote-address inet:host +-- remote-port? inet:port-number +-- local-address? inet:ip-address {local-binding}? +-- local-port? inet:port-number{local-binding}? ]]></sourcecode>{local-binding}?]]></sourcecode> <t>The description of these parameters is provided below:</t> <ul> <li>The "remote-address", which is mandatory, may be configured as an IPv4 address, an IPv6 address, or a hostname. The resolved address should be compatible with the local address family, if also provided.</li> <li>The "remote-port" is defined with neither a "default" nor a "mandatory" statement. YANG modules using this groupingSHOULD<bcp14>SHOULD</bcp14> refine the grouping with a "default"statement,statement when the port number is well-known (e.g., a port number allocated byIANA),IANA) or with a "mandatory"statement,statement if a port number needs to always be configured. ThisMAY<bcp14>MAY</bcp14> be ignored when the port number is neither well-known nor mandatory to configure, such as might be the case when this grouping is used by another grouping.</li> <li>The "local-address", which is enabled by the "local-binding" feature, may be configured as an IPv4 address, an IPv6 address, or a wildcard value. In normal operation, the local and configured remote addressesSHOULD<bcp14>SHOULD</bcp14> be from the same address family. Differences between address families may occur in abnormal or errorconditions andconditions; therefore, they arethereforeallowed to be reported.</li> <li>The "local-port", which depends on the "local-binding" feature, is not mandatory. Its default value is "0", indicating that the operating system can select an arbitrary port number.</li> </ul> </section> </section> <sectionanchor="example-client" title="Example Usage">anchor="example-client"> <name>Example Usage</name> <t>This section presents an example of usage of the "udp-client" grouping.</t> <sourcecode type="xml"><![CDATA[ <!-- The outermost element below doesn't exist in the data model. --> <!-- It simulates if the "grouping" were a "container" instead. --> <udp-client xmlns="urn:ietf:params:xml:ns:yang:ietf-udp-client"> <remote-address>www.example.com</remote-address> <remote-port>10000</remote-port> <local-address>192.0.2.2</local-address> <local-port>12345</local-port></udp-client> ]]></sourcecode></udp-client>]]></sourcecode> </section> <sectionanchor="udp-client-ym" title="YANG Module">anchor="udp-client-ym"> <name>YANG Module</name> <!--[rfced] We had the following questions related to the YANG modules in Sections 2.3 and 3.3: a) FYI - We see that Kent Watson is not listed as an author on the module. We will assume this was intentional unless we hear otherwise. b) We have made slight updates to the format of the modules with pyang (e.g., indentation and whitespace). Please review in the text output and confirm. --> <t>This module imports types defined in <xreftarget="I-D.ietf-netmod-rfc6991-bis"/>.</t>target="RFC9911"/>.</t> <sourcecodename="ietf-udp-client@2025-12-16.yang"name="ietf-udp-client@2026-05-13.yang" type="yang" markers="true"><![CDATA[ module ietf-udp-client { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-udp-client"; prefix udpc; import ietf-inet-types { prefix inet; reference "RFC 9911: Common YANG Data Types"; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: <https://datatracker.ietf.org/group/netconf/> WG List: <mailto:netconf@ietf.org> Authors: Alex Huang Feng <mailto:alex.huang-feng@insa-lyon.fr> Pierre Francois <mailto:pierre.francois@insa-lyon.fr>"; description "Defines a generic grouping for UDP-based client applications. Copyright (c)20252026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). All revisions of IETF and IANA published modules can be found at the YANG Parameters registry group (https://www.iana.org/assignments/yang-parameters). This version of this YANG module is part of RFCXXXX;9984; see the RFC itself for full legal notices. The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document are to be interpreted as described in BCP 14 (RFC 2119) (RFC 8174) when, and only when, they appear in all capitals, as shown here."; revision2025-12-162026-05-13 { description "Initial revision"; reference "RFCXXXX:9984: YANG Groupings for UDP Clients and UDP Servers"; } feature local-binding { description "Indicates that the UDP client supports configuring local bindings (i.e., the local address and local port number) for UDP clients."; } grouping udp-client { description "A reusable grouping for UDP clients. Note that this grouping uses fairly typical descendant node names such that a stack of 'uses' statements will have name conflicts. It is intended that the consuming data model will resolve the issue (e.g., by wrapping the 'uses' statement in a container called 'udp-client-parameters'). Thismodelmodule purposely does not do this itself so as to provide maximum flexibility to consuming models."; leaf remote-address { type inet:host; mandatory true; description "The IP address or hostname of the remote UDP server."; } leaf remote-port { type inet:port-number; description "The port number of the remote UDP server."; } leaf local-address { if-feature "local-binding"; type inet:ip-address; description "The local IP address to bind to when sending UDP datagrams to the remote server. INADDR_ANY ('0.0.0.0') or INADDR6_ANY ('0:0:0:0:0:0:0:0' a.k.a. '::') may be used so that the client can bind to any IPv4 or IPv6 address. In normal operation, the local and configured remote addresses SHOULD be from the same address family. Differences between address families may occur in abnormal or errorconditions andconditions; therefore, they arethereforeallowed to be reported."; } leaf local-port { if-feature "local-binding"; type inet:port-number; default "0"; description "The local port number to bind to when sending UDP datagrams to the remote server. The port number '0', which is the default value, indicates that any available local port number may be used."; } } } ]]></sourcecode> </section> </section> <sectionanchor="udp-server" title='Theanchor="udp-server"> <name>The "ietf-udp-server"Module'>Module</name> <t>This section defines a YANG 1.1 module called "ietf-udp-server". This YANG module defines the "udp-server" grouping for managing UDP servers.</t> <t><xref target="udp-server-overview"/> provides an overview of the "ietf-udp-server" YANG module. An example of usage is illustrated in <xreftarget="example-server"/> whiletarget="example-server"/>. <xref target="udp-server-ym"/> defines the YANG module itself.</t> <sectionanchor="udp-server-overview" title='Dataanchor="udp-server-overview"> <name>Data ModelOverview'>Overview</name> <t>This section provides an overview of the grouping defined in the "ietf-udp-server" module.</t> <sectionanchor="udp-server-grouping" title='Theanchor="udp-server-grouping"> <name>The "udp-server"Grouping'>Grouping</name> <t>The following tree diagram <xref target="RFC8340"/> illustrates the tree structure of "udp-server" grouping:</t> <sourcecode type="yangtree"><![CDATA[ module: ietf-udp-server grouping udp-server: +-- local-bind* [local-address] +-- local-address inet:ip-address +-- local-port?inet:port-number ]]></sourcecode>inet:port-number]]></sourcecode> <t>The description of these parameters is provided below:</t> <ul> <li>The "local-address", which is mandatory, may be configured as an IPv4 address, an IPv6 address, or a wildcard value.</li> <li>The "local-port" is defined with neither a "default" nor a "mandatory" statement. YANG modules using this groupingSHOULD<bcp14>SHOULD</bcp14> refine the grouping with a "default"statement,statement when the port number is well-known (e.g., a port number allocated byIANA),IANA) or with a "mandatory"statement,statement if a port number needs to always be configured. ThisMAY<bcp14>MAY</bcp14> be ignored when the port number is neither well-known nor mandatory to configure, such as might be the case when this grouping is used by another grouping.</li> </ul> </section> </section> <sectionanchor="example-server" title="Example Usage">anchor="example-server"> <name>Example Usage</name> <t>This section presents two examples of usage of the "udp-server" grouping.</t><t>This<t>The following shows an example of a server configured for listening to an IPv4 address:</t> <sourcecode type="xml"><![CDATA[ <!-- The outermost element below doesn't exist in the data model. --> <!-- It simulates if the "grouping" were a "container" instead. --> <udp-server xmlns="urn:ietf:params:xml:ns:yang:ietf-udp-server"> <local-bind> <local-address>192.0.2.2</local-address> <local-port>49152</local-port> </local-bind></udp-server> ]]></sourcecode> <t>This</udp-server>]]></sourcecode> <t>The following shows an example of a server configuredto listenfor listening to an IPv4 and IPv6 together:</t> <sourcecode type="xml"><![CDATA[ <!-- The outermost element below doesn't exist in the data model. --> <!-- It simulates if the "grouping" were a "container" instead. --> <udp-server xmlns="urn:ietf:params:xml:ns:yang:ietf-udp-server"> <local-bind> <local-address>192.0.2.2</local-address> <local-port>49152</local-port> </local-bind> <local-bind> <local-address>2001:db8::0</local-address> <local-port>49153</local-port> </local-bind></udp-server> ]]></sourcecode></udp-server>]]></sourcecode> </section> <sectionanchor="udp-server-ym" title="YANG Module"> <t>The "ietf-udp-server"anchor="udp-server-ym"> <name>YANG Module</name> <t>This module imports types defined in <xreftarget="I-D.ietf-netmod-rfc6991-bis"/>.</t>target="RFC9911"/>.</t> <sourcecodename="ietf-udp-server@2025-12-16.yang"name="ietf-udp-server@2026-05-13.yang" type="yang" markers="true"><![CDATA[ module ietf-udp-server { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-udp-server"; prefix udps; import ietf-inet-types { prefix inet; reference "RFC 9911: Common YANG Data Types"; } organization "IETF NETCONF (Network Configuration) Working Group"; contact "WG Web: <https://datatracker.ietf.org/group/netconf/> WG List: <mailto:netconf@ietf.org> Authors: Alex Huang Feng <mailto:alex.huang-feng@insa-lyon.fr> Pierre Francois <mailto:pierre.francois@insa-lyon.fr>"; description "Defines a generic grouping for UDP-based server applications. Copyright (c)20252026 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Revised BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info). All revisions of IETF and IANA published modules can be found at the YANG Parameters registry group (https://www.iana.org/assignments/yang-parameters). This version of this YANG module is part of RFCXXXX;9984; see the RFC itself for full legal notices."; revision2025-12-162026-05-13 { description "Initial revision"; reference "RFCXXXX:9984: YANG Groupings for UDP Clients and UDP Servers"; } grouping udp-server { description"Provides a"A reusable grouping for managing UDP servers. Note that this grouping uses fairly typical descendant node names such that a stack of 'uses' statements will have name conflicts. It is intended that the consuming data model will resolve the issue (e.g., by wrapping the 'uses' statement in a container called 'udp-server-parameters'). Thismodelmodule purposely does not do this itself so as to provide maximum flexibility to consuming models."; list local-bind { key "local-address"; min-elements 1; description "A list of bind (listen) points for this server instance. A server instance may have multiple bind points to support, e.g., the same port number in different address families or different port numbers in the same address family."; leaf local-address { type inet:ip-address; mandatory true; description "The local IP address to listen on for incoming UDP datagrams. INADDR_ANY ('0.0.0.0') or INADDR6_ANY ('0:0:0:0:0:0:0:0' a.k.a. '::') may be used so that the server can listen to any IPv4 or IPv6 address."; } leaf local-port { type inet:port-number; description "The local port number to listen on for incoming UDP datagrams."; } } } } ]]></sourcecode> </section> </section> <sectionanchor="security" title="Security Considerations">anchor="security"> <name>Security Considerations</name> <!--[rfced] We had the following questions related to the Security Considerations section: a) Please review the following citation mismatch. We have updated to match the security considerations template at https://wiki.ietf.org/group/ops/yang-security-guidelines. Please let us know any objections. Template: ...have to use a secure transport layer (e.g., SSH [RFC4252],... In this document: ...have to use a secure transport layer (e.g., SSH [RFC6242],... b) We have updated the following for consistent pluralization. Please let us know any objections. Original: As such, there are no additional security issues related to the YANG module that need to be considered. Current: As such, there are no additional security issues related to the YANG modules that need to be considered. --> <t>This section uses the template described inSection 3.7 of<xreftarget="I-D.ietf-netmod-rfc8407bis"/>.</t>section="3.7.1" sectionFormat="of" target="RFC9907"/>.</t> <!--DNE begins --> <t>The "ietf-udp-client" and "ietf-udp-server" YANG modulesdefinesdefine a data model that is designed to be accessed via YANG-based management protocols, such asNETCONFNetwork Configuration Protocol (NETCONF) <xref target="RFC6241"/> and RESTCONF <xref target="RFC8040"/>. These YANG-based management protocols (1) have to use a secure transport layer (e.g., SSH <xreftarget="RFC6242"/>,target="RFC4252"/>, TLS <xref target="RFC8446"/>, and QUIC <xref target="RFC9000"/>) and (2) have to use mutual authentication. </t> <t>The Network Configuration Access Control Model (NACM) <xref target="RFC8341"/> provides the means to restrict access for particular NETCONF or RESTCONF users to a preconfigured subset of all available NETCONF or RESTCONF protocol operations and content. </t> <t>These YANG modules define a set of identities, types, and groupings. These nodes are intended to be reused by other YANG modules. The modules by themselves do not expose any data nodes that are writable, data nodes that contain read-only state, or RPCs. As such, there are no additional security issues related to the YANGmodulemodules that need to be considered. </t> <t>Modules that use the groupings that are defined in this document should identify the corresponding security considerations. For example, reusing some of these groupings will expose privacy-related information (e.g., 'remote-address', 'remote-port', 'local-address', or 'local-port'). <!--DNE Ends--> </t> </section> <sectionanchor="IANA_Considerations" title="IANA Considerations">anchor="IANA_Considerations"> <name>IANA Considerations</name> <t>This document describes the URIs fromIETFthe "IETF XMLRegistryRegistry" and the registration ofatwo new YANG modulenames</t> <section title="URI">names.</t> <section> <name>The "IETF XML Registry"</name> <t>IANAis requested to assignhas assigned two new URIs from the <xreftarget="RFC3688">IETFtarget="RFC3688">"IETF XMLRegistry</xref>:</t> <t><figure> <artwork align="left"><![CDATA[ URI: urn:ietf:params:xml:ns:yang:ietf-udp-client Registrant Contact: The IESG. XML: N/A;Registry"</xref>:</t> <dl spacing="compact" newline="false"> <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-udp-client</dd> <dt>Registrant Contact:</dt><dd>The IESG.</dd> <dt>XML:</dt><dd>N/A; the requested URI is an XMLnamespace.]]></artwork> </figure></t> <t><figure> <artwork align="left"><![CDATA[ URI: urn:ietf:params:xml:ns:yang:ietf-udp-server Registrant Contact: The IESG. XML: N/A;namespace.</dd> </dl> <dl spacing="compact" newline="false"> <dt>URI:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-udp-server</dd> <dt>Registrant Contact:</dt><dd>The IESG.</dd> <dt>XML:</dt><dd>N/A; the requested URI is an XMLnamespace.]]></artwork> </figure></t>namespace.</dd> </dl> </section><section title="YANG<section> <name>The "YANG ModuleName"> <t>This document also requests IANA to registerNames" Registry</name> <t>IANA has registered the following YANG modules in the <xreftarget="RFC6020">YANGtarget="RFC6020">"YANG ModuleNamesNames" registry</xref> within the "YANG Parameters" registry group:</t><t><figure> <artwork align="left"><![CDATA[ name: ietf-udp-client namespace: urn:ietf:params:xml:ns:yang:ietf-udp-client prefix: udpc maintained<dl spacing="compact" newline="false"> <dt>Name:</dt><dd>ietf-udp-client</dd> <dt>Maintained byIANA? N reference: RFC XXXX]]></artwork> </figure></t> <t><figure> <artwork align="left"><![CDATA[ name: ietf-udp-server namespace: urn:ietf:params:xml:ns:yang:ietf-udp-server prefix: udps maintainedIANA?</dt><dd>N</dd> <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-udp-client</dd> <dt>Prefix:</dt><dd>udpc</dd> <dt>Reference:</dt><dd>RFC 9984</dd> </dl> <dl spacing="compact" newline="false"> <dt>Name:</dt><dd>ietf-udp-server</dd> <dt>Maintained byIANA? N reference: RFC XXXX]]></artwork> </figure></t>IANA?</dt><dd>N</dd> <dt>Namespace:</dt><dd>urn:ietf:params:xml:ns:yang:ietf-udp-server</dd> <dt>Prefix:</dt><dd>udps</dd> <dt>Reference:</dt><dd>RFC 9984</dd> </dl> </section> </section><section anchor="acknowledgements" title="Acknowledgements"> <t>The authors would like to thank Mohamed Boucadair, Ran Chen, Benoit Claise, Mahesh Jethanandani, Qiufang Ma, Jürgen Schönwälder, Ketan Talaulikar, Eric Vyncke, Paul Wouters and Qin Wu for their review and valuable comments.</t> </section></middle> <back><references title="Normative References"><references> <name>References</name> <references> <name>Normative References</name> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.768.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.768.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.2119.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.3688.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.3688.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.6020.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6020.xml"/> <xi:includehref="https://bib.ietf.org/public/rfc/bibxml-ids/reference.I-D.ietf-netmod-rfc6991-bis.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9911.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.7950.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.7950.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.8341.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8341.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.8174.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8174.xml"/> </references><references title="Informative References"><references> <name>Informative References</name> <!-- [I-D.ietf-netmod-rfc8407bis] now RFC 9907 --> <xi:includehref="https://bib.ietf.org/public/rfc/bibxml-ids/reference.I-D.ietf-netmod-rfc8407bis.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9907.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.6241.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.4252.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.6242.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.6241.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.8040.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8040.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.8259.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8259.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.8340.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8340.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.8342.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8342.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.8446.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.8446.xml"/> <xi:includehref="https://xml.resource.org/public/rfc/bibxml/reference.RFC.9000.xml"/>href="https://bib.ietf.org/public/rfc/bibxml/reference.RFC.9000.xml"/> <reference anchor="W3C.REC-xml-20081126" target="https://www.w3.org/TR/2008/REC-xml-20081126/" quoteTitle="true" derivedAnchor="W3C.REC-xml-20081126"> <front> <title>Extensible Markup Language (XML) 1.0 (Fifth Edition)</title> <author initials="T." surname="Bray" fullname="TimBray"/>Bray" role="editor"/> <author initials="J." surname="Paoli" fullname="JeanPaoli"/>Paoli" role="editor"/> <author initials="C.M." surname="Sperberg-McQueen" fullname="C. M.Sperberg-McQueen"/>Sperberg McQueen" role="editor"/> <author initials="E." surname="Maler" fullname="EveMaler"/>Maler" role="editor"/> <author initials="F." surname="Yergeau"fullname="François Yergeau"/>fullname="Francois Yergeau" role="editor"/> <date day="26" month="November" year="2008"/> </front><seriesInfo name="World Wide Web Consortium Recommendation" value="REC-xml-20081126"/><refcontent>W3C Recommendation</refcontent> <annotation>Latest version available at <eref brackets="angle" target="https://www.w3.org/TR/xml/"/>.</annotation> </reference> </references> </references> <section anchor="acknowledgements" numbered="false"> <name>Acknowledgements</name> <t>The authors would like to thank <contact fullname="Mohamed Boucadair"/>, <contact fullname="Ran Chen"/>, <contact fullname="Benoit Claise"/>, <contact fullname="Mahesh Jethanandani"/>, <contact fullname="Qiufang Ma"/>, <contact fullname="Jürgen Schönwälder"/>, <contact fullname="Ketan Talaulikar"/>, <contact fullname="Éric Vyncke"/>, <contact fullname="Paul Wouters"/>, and <contact fullname="Qin Wu"/> for their reviews and valuable comments.</t> </section> </back> </rfc>