Ideas for a Next Generation of the Stream Control Transmission Protocol (SCTP)
draft-dreibholz-tsvwg-sctp-nextgen-ideas-05
The information below is for an old version of the document.
Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
---|---|---|---|
Author | Thomas Dreibholz | ||
Last updated | 2017-07-26 (Latest revision 2017-01-22) | ||
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 collects some ideas for a next generation of the Stream Control Transmission Protocol (SCTP) for further discussion. It is a result of lessons learned from more than one decade of SCTP deployment.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)