rfc9984v1.txt   rfc9984.txt 
skipping to change at line 13 skipping to change at line 13
Request for Comments: 9984 P. Francois Request for Comments: 9984 P. Francois
Category: Standards Track INSA-Lyon Category: Standards Track INSA-Lyon
ISSN: 2070-1721 K. Watsen ISSN: 2070-1721 K. Watsen
Watsen Networks Watsen Networks
May 2026 May 2026
YANG Groupings for UDP Clients and UDP Servers YANG Groupings for UDP Clients and UDP Servers
Abstract Abstract
This document defines two YANG 1.1 modules with reusable groupings This document presents two YANG 1.1 modules with reusable groupings
for managing UDP clients and UDP servers. for managing UDP clients and UDP servers.
Status of This Memo Status of This Memo
This is an Internet Standards Track document. This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has (IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on Internet Engineering Steering Group (IESG). Further information on
skipping to change at line 71 skipping to change at line 71
5.1. The "IETF XML Registry" 5.1. The "IETF XML Registry"
5.2. The "YANG Module Names" Registry 5.2. The "YANG Module Names" Registry
6. References 6. References
6.1. Normative References 6.1. Normative References
6.2. Informative References 6.2. Informative References
Acknowledgements Acknowledgements
Authors' Addresses Authors' Addresses
1. Introduction 1. Introduction
This document defines two YANG 1.1 [RFC7950] modules with reusable This document presents two YANG 1.1 [RFC7950] modules with reusable
groupings for managing UDP clients and UDP servers [RFC768]. These groupings for managing UDP clients and UDP servers [RFC768]. These
modules may be used directly (e.g., define a specific UDP client or modules may be used directly (e.g., define a specific UDP client or
UDP server) or in conjunction with the configuration defined for UDP server) or in conjunction with the configuration defined for
higher-level protocols that depend on UDP. higher-level protocols that depend on UDP.
1.1. Requirements Language 1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
 End of changes. 2 change blocks. 
2 lines changed or deleted 2 lines changed or added

This html diff was produced by rfcdiff 1.48.