Application Layer Authentication for MPTCP
draft-paasch-mptcp-application-authentication-00

Document Type Expired Internet-Draft (individual)
Authors Christoph Paasch  , Alan Ford 
Last updated 2016-11-28 (latest revision 2016-05-27)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text xml pdf ps 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)

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-paasch-mptcp-application-authentication-00.txt

Abstract

Multipath TCP (MPTCP), described in [3], is an extension to TCP to provide the ability to simultaneously use multiple paths between hosts. MPTCP currently specifies a single authentication mechanism, using keys that are initially exchanged in the clear. There are application-layer protocols that may have better information as to the identity of the parties and so is able to better provide keying material that could be used for the authentication of future subflows. This document specifies "application layer authentication" for Multipath TCP, an alternatively negotiated keying mechanism for MPTCP.

Authors

Christoph Paasch (cpaasch@apple.com)
Alan Ford (alan.ford@gmail.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)