Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP- Lite) Transport Protocols
draft-ietf-taps-transports-usage-udp-03

Document Type Active Internet-Draft (taps WG)
Last updated 2017-05-24
Replaces draft-fairhurst-taps-transports-usage-udp
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream WG state WG Document (wg milestone: Nov 2016 - Submit an Informatio... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                             G. Fairhurst
Internet-Draft                                                  T. Jones
Intended status: Informational                    University of Aberdeen
Expires: November 23, 2017                                  May 24, 2017

 Features of the User Datagram Protocol (UDP) and Lightweight UDP (UDP-
                       Lite) Transport Protocols
                draft-ietf-taps-transports-usage-udp-03

Abstract

   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.  The
   resulting road map to documentation may be of help to users of the
   UDP and UDP-Lite protocols.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 23, 2017.

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents (http://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights

Fairhurst & Jones      Expires November 23, 2017                [Page 1]
Internet-Draft           UDP Transport Features                 May 2017

   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  UDP and UDP-Lite Primitives  . . . . . . . . . . . . . . . . .  3
     3.1.  Primitives Provided by UDP . . . . . . . . . . . . . . . .  3
       3.1.1.  Excluded Primitives  . . . . . . . . . . . . . . . . . 10
     3.2.  Primitives Provided by UDP-Lite  . . . . . . . . . . . . . 10
   4.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 11
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
     7.2.  Informative References . . . . . . . . . . . . . . . . . . 13
   Appendix A. Multicast Primitives . . . . . . . . . . . . . . . . . 14
   Appendix B. Revision Notes . . . . . . . . . . . . . . . . . . . . 17
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19

1.  Introduction

   This document presents defined interactions between transport
   protocols and applications in the form of 'primitives' (function
   calls) for the User Datagram Protocol (UDP) [RFC0768] and the
   Lightweight User Datagram Protocol (UDP-Lite) [RFC3828].  In this
   usage, the word application refers to any program built on the
   datagram interface, and including tunnels and other upper layer
   protocols that use UDP and UDP-LIte.

   The de facto standard application programming interface (API) for TCP
   /IP applications is the "socket" interface [POSIX].  An application
   can use the recv() and send() POSIX functions as well as the
   recvfrom() and sendto() and recvmsg() and sendmsg() functions.  The
   UDP and UDP-Lite sockets API differs from that for TCP in several key
   ways.  (Examples of usage of this API are provided in [STEVENS].)

   Additional functions in the sockets API are provided by socket
   options, examples include:

   o  SO_REUSEADDR specifies the rules for validating addresses supplied
      to bind() should allow reuse of local addresses

   o  SO_REUSEPORT specifies that the rules for validating ports
Show full document text