Software Guidelines for Protocol Evolution
draft-pauly-taps-guidelines-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Author | Tommy Pauly | ||
| Last updated | 2017-08-11 (Latest revision 2017-02-07) | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)