Subject: Re: [Lurk] New Version Notification for draft-mglt-lurk-tls-use-cases-02.txt

From: Daniel Migault <[email-masked]>
Date: Tue, 28 Jun 2016 14:31:04 +0000

Hi, 

Please find an update of the use case document. We mostly address the comments received during the virtual meeting, that is: 
    - 1) Clarifying the expectation from LURK with the for each use case a "Description" and a "LURK Expectation" subsections 
    - 2) Clarifying the impact of the Edge Server leaking authentication credentials to the Key Server vs leaking the Private Key 

Comments are welcome!

BR, 
Daniel

-----Original Message-----
From: [email-masked] [mailto:[email-masked]] 
Sent: Tuesday, June 28, 2016 5:20 PM
To: Kevin Ma J; Oscar Gonzales de Dios; Oscar Gonzalez de Dios; Kevin Ma J; Rich Salz; Sanjay Mishra; Daniel Migault
Subject: New Version Notification for draft-mglt-lurk-tls-use-cases-02.txt

A new version of I-D, draft-mglt-lurk-tls-use-cases-02.txt
has been successfully submitted by Daniel Migault and posted to the IETF repository.

Name:		draft-mglt-lurk-tls-use-cases
Revision:	02
Title:		LURK TLS/DTLS Use Cases
Document date:	2016-06-28
Group:		Individual Submission
Pages:		13
URL:            https://www.ietf.org/internet-drafts/draft-mglt-lurk-tls-use-cases-02.txt
Status:         https://datatracker.ietf.org/doc/draft-mglt-lurk-tls-use-cases/
Htmlized:       https://tools.ietf.org/html/draft-mglt-lurk-tls-use-cases-02
Diff:           https://www.ietf.org/rfcdiff?url2=draft-mglt-lurk-tls-use-cases-02

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.

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat