Simple Datagram Usability and Connectivity Kata
draft-pardue-quic-siduck-00

Document Type Active Internet-Draft (individual)
Last updated 2019-11-17
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
QUIC                                                           L. Pardue
Internet-Draft                                         November 18, 2019
Intended status: Experimental
Expires: May 21, 2020

            Simple Datagram Usability and Connectivity Kata
                      draft-pardue-quic-siduck-00

Abstract

   This document describes a simple application protocol for testing
   implementations of the QUIC DATAGRAM frame.  SiDUCK (Simple Datagram
   Usability and Connectivity Kata) defines a new ALPN ID, "siduck-00",
   along with a basic offer and acknowledgement interaction using
   datagram payload data.

Note to Readers

   Discussion of this document takes place on the QUIC Working Group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/browse/quic/ [1].

   Source for this draft and an issue tracker can be found at
   https://github.com/lpardue/draft-pardue-quic-siduck [2].

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 https://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 21, 2020.

Copyright Notice

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

Pardue                    Expires May 21, 2020                  [Page 1]
Internet-Draft                   SiDUCK                    November 2019

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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
   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
     1.1.  Notational Conventions  . . . . . . . . . . . . . . . . .   3
   2.  Negotiating SiDUCK  . . . . . . . . . . . . . . . . . . . . .   3
   3.  Protocol Behaviour  . . . . . . . . . . . . . . . . . . . . .   4
   4.  The SIDUCK_ONLY_QUACKS_ECHO error code  . . . . . . . . . . .   4
   5.  Known Issues / Problems . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
     8.3.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   The DATAGRAM frame [I-D.pauly-quic-datagram] for QUIC
   [I-D.ietf-quic-transport] is an extension for the unreliable delivery
   of datagrams.  Applications using DATAGRAM negotiate it using
   Transport Parameters but the application-specific contents are left
   for a higher-level mechanism.

   HTTP/3 DATAGRAM [I-D.schinazi-quic-h3-datagram] defines the usage of
   QUIC DATAGRAM frames when the application protocol running over QUIC
   is HTTP/3 [I-D.ietf-quic-http], which is negotiated using ALPN
   [RFC7301] with an identifier such as "h3-24".  The HTTP/3 DATAGRAM
   frame is transmitted as the QUIC DATAGRAM frame Datagram Data field.
   It contains a flow identifier field that can be used for
   demultiplexing applications, and an HTTP/3 Datagram Payload field
   whose semantics are defined by individual applications.

   Since the QUIC DATAGRAM and HTTP/3 DATAGRAM specifications leave the
   semantic higher-order behaviour undefined, it is difficult to prove
   the interoperability of implementations.  This document defines
   SiDUCK (Simple Datagram Usability and Connectivity Kata), a new

Pardue                    Expires May 21, 2020                  [Page 2]
Internet-Draft                   SiDUCK                    November 2019

   application that maps directly to QUIC DATAGRAM and uses the Datagram
   Data field directly to support a simple client-server echo service.

   Using QUIC DATAGRAM directly provides the benefit of avoiding
Show full document text