Secure MPTCP
draft-bagnulo-mptcp-secure-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Marcelo Bagnulo | ||
| Last updated | 2014-08-17 (Latest revision 2014-02-13) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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 can be found at:
https://www.ietf.org/archive/id/draft-bagnulo-mptcp-secure-00.txt
https://www.ietf.org/archive/id/draft-bagnulo-mptcp-secure-00.txt
Abstract
This memo contains some initial thoughts about how to secure MPTCP. As currently defined, MPTCP provides basic security features to protect the MPTCP signaling and the data flows unprotected. In this note, we explore the possible use to tcpcrypt to provide enhanced security to MPTCP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)