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

Document Type Active Internet-Draft (taps WG)
Last updated 2017-03-25 (latest revision 2016-11-13)
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 Nov 2016
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: May 17, 2017                                  November 13, 2016

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

Abstract

   This document describes how the User Datagram Protocol (UDP) and the
   Lightweight User Datagram Protocol (UDP-Lite) transport protocols
   expose services to applications and how an application can configure
   and use the features offered by the transport service.  The document
   is intended as a contribution to the Transport Services (TAPS)
   working group to assist in analysis of the UDP and UDP-Lite transport
   interface.

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 May 17, 2017.

Copyright Notice

   Copyright (c) 2016 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 and restrictions with respect
   to this document.  Code Components extracted from this document must

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

   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.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  UDP and UDP-Lite Primitives . . . . . . . . . . . . . . . . .   3
     3.1.  Primitives Provided by UDP  . . . . . . . . . . . . . . .   3
       3.1.1.  Excluded Primitives . . . . . . . . . . . . . . . . .   8
     3.2.  Primitives Provided by UDP-Lite . . . . . . . . . . . . .   9
   4.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Revision Notes . . . . . . . . . . . . . . . . . . .  13
   Appendix B.  Notes Based on Typical Usage . . . . . . . . . . . .  14
   Appendix C.  UDP Multicast  . . . . . . . . . . . . . . . . . . .  15
     C.1.  Multicast Primitives  . . . . . . . . . . . . . . . . . .  15
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  18

1.  Terminology

   This document uses common terminology defined in
   [I-D.ietf-taps-transports-usage].  This document also refers to the
   terminology of [RFC2119], but does not itself define new terms using
   this terminology.

2.  Introduction

   This document presents defined interactions between transport
   protocols and applications in the form of 'primitives' (function
   calls).  Primitives can be invoked by an application or a transport
   protocol; the latter type is called an "event".  The list of
   transport service features and primitives in this document is
   strictly based on the parts of protocol specifications that relate to
   what the protocol provides to an application using it and how the
   application interacts with it.  It does not cover parts of a protocol
   that are explicitly stated as optional to implement.

   This follows the methodology defined in
   [I-D.ietf-taps-transports-usage], specifically it provides the first
   pass of this process.  It discusses the relevant RFC text describing
Show full document text