Authors,
While reviewing this document during AUTH48, please resolve (as necessary) the
following questions, which are also in the source file.
1) <!--[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.)
-->
2) <!-- [rfced] Please insert any keywords (beyond those that appear in
the title) for use on https://www.rfc-editor.org/search. -->
3) <!--[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 UDP servers.
Perhaps:
This document presents two YANG 1.1 modules with reusable
groupings for managing UDP clients and UDP servers.
-->
4) <!--[rfced] We note that 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. -->
5) <!--[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 {
-->
6) <!--[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].
-->
7) <!--[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.
-->
8) <!--[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.
-->
Thank you.
Megan Ferguson
RFC Production Center
*****IMPORTANT*****
Updated 2026/05/13
RFC Author(s):
--------------
Instructions for Completing AUTH48
Your document has now entered AUTH48. Once it has been reviewed and
approved by you and all coauthors, it will be published as an RFC.
If an author is no longer available, there are several remedies
available as listed in the FAQ (https://www.rfc-editor.org/faq/).
You and you coauthors are responsible for engaging other parties
(e.g., Contributors or Working Group) as necessary before providing
your approval.
Planning your review
---------------------
Please review the following aspects of your document:
* RFC Editor questions
Please review and resolve any questions raised by the RFC Editor
that have been included in the XML file as comments marked as
follows:
<!-- [rfced] ... -->
These questions will also be sent in a subsequent email.
* Changes submitted by coauthors
Please ensure that you review any changes submitted by your
coauthors. We assume that if you do not speak up that you
agree to changes submitted by your coauthors.
* Content
Please review the full content of the document, as this cannot
change once the RFC is published. Please pay particular attention to:
- IANA considerations updates (if applicable)
- contact information
- references
* Copyright notices and legends
Please review the copyright notice and legends as defined in
RFC 5378 and the Trust Legal Provisions
(TLP – https://trustee.ietf.org/license-info).
* Semantic markup
Please review the markup in the XML file to ensure that elements of
content are correctly tagged. For example, ensure that <sourcecode>
and <artwork> are set correctly. See details at
<https://authors.ietf.org/rfcxml-vocabulary>.
* Formatted output
Please review the PDF, HTML, and TXT files to ensure that the
formatted output, as generated from the markup in the XML file, is
reasonable. Please note that the TXT will have formatting
limitations compared to the PDF and HTML.
Submitting changes
------------------
To submit changes, please reply to this email using ‘REPLY ALL’ as all
the parties CCed on this message need to see your changes. The parties
include:
* your coauthors
* [email protected] (the RPC team)
* other document participants, depending on the stream (e.g.,
IETF Stream participants are your working group chairs, the
responsible ADs, and the document shepherd).
* [email protected], which is a new archival mailing list
to preserve AUTH48 conversations; it is not an active discussion
list:
* More info:
https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc
* The archive itself:
https://mailarchive.ietf.org/arch/browse/auth48archive/
* Note: If only absolutely necessary, you may temporarily opt out
of the archiving of messages (e.g., to discuss a sensitive matter).
If needed, please add a note at the top of the message that you
have dropped the address. When the discussion is concluded,
[email protected] will be re-added to the CC list and
its addition will be noted at the top of the message.
You may submit your changes in one of two ways:
An update to the provided XML file
— OR —
An explicit list of changes in this format
Section # (or indicate Global)
OLD:
old text
NEW:
new text
You do not need to reply with both an updated XML file and an explicit
list of changes, as either form is sufficient.
We will ask a stream manager to review and approve any changes that seem
beyond editorial in nature, e.g., addition of new text, deletion of text,
and technical changes. Information about stream managers can be found in
the FAQ. Editorial changes do not require approval from a stream manager.
Approving for publication
--------------------------
To approve your RFC for publication, please reply to this email stating
that you approve this RFC for publication. Please use ‘REPLY ALL’,
as all the parties CCed on this message need to see your approval.
Files
-----
The files are available here:
https://www.rfc-editor.org/authors/rfc9984.xml
https://www.rfc-editor.org/authors/rfc9984.html
https://www.rfc-editor.org/authors/rfc9984.pdf
https://www.rfc-editor.org/authors/rfc9984.txt
Diff file of the text:
https://www.rfc-editor.org/authors/rfc9984-diff.html
https://www.rfc-editor.org/authors/rfc9984-rfcdiff.html (side by side)
Diff of the XML:
https://www.rfc-editor.org/authors/rfc9984-xmldiff1.html
Tracking progress
-----------------
The details of the AUTH48 status of your document are here:
https://www.rfc-editor.org/auth48/rfc9984
Please let us know if you have any questions.
Thank you for your cooperation,
RFC Editor
--------------------------------------
RFC9984 (draft-ietf-netconf-udp-client-server-10)
Title : YANG Groupings for UDP Clients and UDP Servers
Author(s) : A. Huang-Feng, P. Francois, K. Watsen
WG Chair(s) : Kent Watsen, Per Andersson
Area Director(s) : Mohamed Boucadair, Mahesh Jethanandani
--
auth48archive mailing list -- [email protected]
To unsubscribe send an email to [email protected]
