Secure SCTP
draft-hohendorf-secure-sctp-20
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (individual) | |
| Last updated | 2016-01-06 (latest revision 2015-07-05) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-hohendorf-secure-sctp-20.txt
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
(hohend@iem.uni-due.de)
Esbold Unurkhaan
(esbold@csms.edu.mn)
Thomas Dreibholz
(dreibh@simula.no)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)