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

rfc-editor@rfc-editor.org Thu, 08 February 2018 07:06 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: taps@ietfa.amsl.com
Delivered-To: taps@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9057712D86F; Wed, 7 Feb 2018 23:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tpDJZw0CY5oQ; Wed, 7 Feb 2018 23:06:04 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B24E912D85E; Wed, 7 Feb 2018 23:06:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B4C94B80DA1; Wed, 7 Feb 2018 23:05:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, taps@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180208070555.B4C94B80DA1@rfc-editor.org>
Date: Wed, 07 Feb 2018 23:05:55 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/taps/amm0HBVv-bOjvW1cDrRxWi5bxEQ>
Subject: [Taps] RFC 8304 on Transport Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-Lite)
X-BeenThere: taps@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF Transport Services \(TAPS\) Working Group" <taps.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/taps>, <mailto:taps-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/taps/>
List-Post: <mailto:taps@ietf.org>
List-Help: <mailto:taps-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/taps>, <mailto:taps-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Feb 2018 07:06:06 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8304

        Title:      Transport Features of the User Datagram
                    Protocol (UDP) and Lightweight UDP (UDP-Lite)
        Author:     G. Fairhurst, 
                    T. Jones
        Status:     Informational
        Stream:     IETF
        Date:       February 2018
        Mailbox:    gorry@erg.abdn.ac.uk, 
                    tom@erg.abdn.ac.uk
        Pages:      20
        Characters: 49343
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-taps-transports-usage-udp-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8304

        DOI:        10.17487/RFC8304

This is an informational document that describes the transport
protocol interface primitives provided by the User Datagram Protocol
(UDP) and the Lightweight User Datagram Protocol (UDP-Lite) transport
protocols.  It identifies the datagram services exposed to
applications and how an application can configure and use the
features offered by the Internet datagram transport service.  RFC
8303 documents the usage of transport features provided by IETF
transport protocols, describing the way UDP, UDP-Lite, and other
transport protocols expose their services to applications and how an
application can configure and use the features that make up these
services.  This document provides input to and context for that
document, as well as offers a road map to documentation that may help
users of the UDP and UDP-Lite protocols.

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


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC