Multipath DTLS Session Layer
draft-hardie-mdtls-session-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Ted Hardie , Jake Khuon | ||
| Last updated | 2010-10-18 | ||
| 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
The Internet model has traditionally avoided the complication of an explicit session layer, in favor of having applications and transports divide the relevant work between them. While this has been a successful strategy when the packet flows from two hosts all take the same path, there may be advantages in using a session-layer strategy when a host initiates related flows from multiple interfaces in independent routing domains (e.g. a 3G or 4G interface and a WiFi interface). This draft discusses an approach re-using the security association mechanisms present in DTLS [RFC4347] to create a simple session layer.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)