A TLS application-specific identifier
draft-mavrogiannopoulos-app-id-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nikos Mavrogiannopoulos , David Woodhouse | ||
| Last updated | 2017-03-27 (Latest revision 2016-09-21) | ||
| 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 memo proposes an application-specific identifier for use with the TLS and DTLS protocols. It defines a TLS extension to allow an arbitrary identifier to be specified in the Client Hello, which can be used for application-specific routing purposes.
Authors
Nikos Mavrogiannopoulos
David Woodhouse
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)