Software Guidelines for Protocol Evolution
draft-pauly-taps-guidelines-00

Document Type Active Internet-Draft (individual)
Last updated 2017-02-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
Network                                                         T. Pauly
Internet-Draft                                                Apple Inc.
Intended status: Informational                          February 7, 2017
Expires: August 11, 2017

               Software Guidelines for Protocol Evolution
                     draft-pauly-taps-guidelines-00

Abstract

   This document outlines a set of recommendations and guidelines for
   how networking software should be designed to enable the development,
   testing, and deployment of new protocols and protocol features.  The
   focus is primarily on the API contract that a client-side networking
   library should present to applications using networking features, and
   how that library can be architected to maximize flexibility and
   longevity.

   Specific areas of protocol development that should be enabled
   include:

   o  Making security and privacy easy to use

   o  Reducing latency with 0-RTT protocols

   o  Allowing wider use of multi-stream protocols

   o  Providing a simple interface for multi-path 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 August 11, 2017.

Pauly                    Expires August 11, 2017                [Page 1]
Internet-Draft Software Guidelines for Protocol Evolution  February 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 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Problem Statement . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   2.  Guideline Summary . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.1.  Endpoint  . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.2.  Derived Endpoint  . . . . . . . . . . . . . . . . . . . .   5
     3.3.  Path  . . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.4.  Connection  . . . . . . . . . . . . . . . . . . . . . . .   5
     3.5.  Multi-stream  . . . . . . . . . . . . . . . . . . . . . .   6
     3.6.  Multi-path  . . . . . . . . . . . . . . . . . . . . . . .   6
     3.7.  0-RTT Protocol  . . . . . . . . . . . . . . . . . . . . .   6
   4.  Guidelines  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Application interfaces should be derived from usage
           patterns  . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  Connection establishment should attempt a tree of options   7
       4.2.1.  Derived Endpoint Racing . . . . . . . . . . . . . . .   8
       4.2.2.  Path Racing . . . . . . . . . . . . . . . . . . . . .   9
       4.2.3.  Protocol Stack Racing . . . . . . . . . . . . . . . .   9
       4.2.4.  Impacts of Racing on APIs . . . . . . . . . . . . . .   9
     4.3.  Parameters should not be protocol-specific  . . . . . . .  10
     4.4.  Dynamically evaluate network state and operating system
           policy  . . . . . . . . . . . . . . . . . . . . . . . . .  11
   5.  Guideline Adoption  . . . . . . . . . . . . . . . . . . . . .  12
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  12
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  12
   8.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  12
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  13
Show full document text