Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)
RFC 8304

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Cc: The IESG <iesg@ietf.org>, Zaheduzzaman.Sarker@ericsson.com, taps-chairs@ietf.org, spencerdawkins.ietf@gmail.com, Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>, rfc-editor@rfc-editor.org, draft-ietf-taps-transports-usage-udp@ietf.org, taps@ietf.org
Subject: Document Action: 'Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP- Lite) Transport Protocols' to Informational RFC (draft-ietf-taps-transports-usage-udp-07.txt)

The IESG has approved the following document:
- 'Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-
   Lite) Transport Protocols'
  (draft-ietf-taps-transports-usage-udp-07.txt) as Informational RFC

This document is the product of the Transport Services Working Group.

The IESG contact persons are Mirja K├╝hlewind and Spencer Dawkins.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-taps-transports-usage-udp/


Technical Summary

This document describes well established function calls as "primitives" 
that any program can use to get automated transport services from the 
UDP and UDP-lite transport protocols. These primitives are services 
provided by the standards-track versions of the corresponding protocols. 
The working group believes the primitives will be useful for users of a 
transport service implementation.

Working Group Summary

The primitives for UDP and UDP-lite were initially intended to be 
part of draft-ietf-transport-usage, however working group agreed to 
have a smaller document for these protocols, because the authors
providing descriptions for these protocols had little overlap with 
the authors of draft-ietf-transport-usage, and the split allowed 
for better review by readers with expertise in these protocols.
 
As this document describes primitives based on what already 
available in standards-track RFCs for those protocol it was 
straightforward to get consensus on the primitives. 

Document Quality

All versions of this document got a fair amount of discussion on
the working group mailing list, were well reviewed and got 
positive feedback during working group last call.

Personnel

The document shepherd is Zaheduzzaman Sarker. 
The responsible Area Director is Spencer Dawkins.