Secure SCTP
draft-hohendorf-secure-sctp-22
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Carsten Hohendorf , Esbold Unurkhaan , Thomas Dreibholz | ||
| Last updated | 2017-01-19 (Latest revision 2016-07-18) | ||
| 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 explains the reason for the integration of security functionality into SCTP, and gives a short description of S-SCTP and its services. S-SCTP is fully compatible with SCTP defined in RFC4960, it is designed to integrate cryptographic functions into SCTP.
Authors
Carsten Hohendorf
Esbold Unurkhaan
Thomas Dreibholz
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)