Stream Control Transmission Protocol (SCTP) CRYPTO Chunk
draft-westerlund-tsvwg-sctp-crypto-chunk-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Magnus Westerlund , John Preuß Mattsson , Claudio Porfiri | ||
| Last updated | 2024-03-18 (Latest revision 2023-09-08) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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 describes a method for adding cryptographic protection to the Stream Control Transmission Protocol (SCTP). The SCTP CRYPTO chunk defined in this document is intended to enable communications privacy for applications that use SCTP as their transport protocol and allows applications to communicate in a way that is designed to prevent eavesdropping and detect tampering or message forgery. The CRYPTO chunk defined here in is one half of a complete solution. Where a companion specification is required to define how the content of the CRYPTO chunk is protected, authenticated, and protected against replay, as well as how key management is accomplished. Applications using SCTP CRYPTO chunk can use all transport features provided by SCTP and its extensions but with some limitations.
Authors
Magnus Westerlund
John Preuß Mattsson
Claudio Porfiri
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)