Skip to main content

LURK TLS/DTLS Use Cases
draft-mglt-lurk-tls-use-cases-02

Document Type Expired Internet-Draft (individual)
Authors Daniel Migault , Kevin J. Ma , Rich Salz , Sanjay Mishra , Oscar Gonzalez de Dios
Last updated 2016-12-30 (Latest revision 2016-06-28)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text xml 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-mglt-lurk-tls-use-cases-02.txt

Abstract

TLS as been designed to setup and authenticate transport layer between a TLS Client and a TLS Server. In most cases, the TLS Server both terminates the TLS Connection and owns the authentication credentials necessary to authenticate the TLS Connection. This document provides use cases where these two functions are split into different entities, i.e. the TLS Connection is terminated on an Edge Server, while authentication credentials are generated by a Key Server, that owns the Private Key.

Authors

Daniel Migault
Kevin J. Ma
Rich Salz
Sanjay Mishra
Oscar Gonzalez de Dios

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