LURK Protocol for TLS/DTLS1.2 version 1.0
draft-mglt-lurk-tls-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-03-11
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
LURK WG D. Migault, Ed.
Internet-Draft Ericsson
Intended status: Informational March 11, 2017
Expires: September 12, 2017
LURK Protocol for TLS/DTLS1.2 version 1.0
draft-mglt-lurk-tls-01
Abstract
This document describes the LURK protocol as well as its TLS
extension designated as LURK/TLS.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 12, 2017.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Migault Expires September 12, 2017 [Page 1]
Internet-Draft LURK TLS March 2017
Table of Contents
1. Requirements notation . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology and Acronyms . . . . . . . . . . . . . . . . . . 4
4. LURK . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. LURK Header . . . . . . . . . . . . . . . . . . . . . . . 5
4.1.1. Description . . . . . . . . . . . . . . . . . . . . . 5
4.1.2. LURK Client Behavior . . . . . . . . . . . . . . . . 7
4.1.3. LURK Server Behavior . . . . . . . . . . . . . . . . 7
4.2. capabilities . . . . . . . . . . . . . . . . . . . . . . 8
4.2.1. Request Payload . . . . . . . . . . . . . . . . . . . 8
4.2.2. Response Payload . . . . . . . . . . . . . . . . . . 8
4.2.3. LURK Client Behavior . . . . . . . . . . . . . . . . 8
4.2.4. LURK Server Behavior . . . . . . . . . . . . . . . . 8
4.3. ping . . . . . . . . . . . . . . . . . . . . . . . . . . 8
4.3.1. Request Payload . . . . . . . . . . . . . . . . . . . 8
4.3.2. Response Payload . . . . . . . . . . . . . . . . . . 9
4.3.3. LURK Client Behavior . . . . . . . . . . . . . . . . 9
4.3.4. LURK Server Behavior . . . . . . . . . . . . . . . . 9
4.4. Error Message . . . . . . . . . . . . . . . . . . . . . . 9
5. LURK/TLS . . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.1. LURK/TLS Header Message . . . . . . . . . . . . . . . . . 10
5.1.1. LURK Client Behavior . . . . . . . . . . . . . . . . 10
5.1.2. LURK Server Behavior . . . . . . . . . . . . . . . . 10
5.2. capabilities . . . . . . . . . . . . . . . . . . . . . . 10
5.2.1. Request Payload . . . . . . . . . . . . . . . . . . . 10
5.2.2. Response Payload . . . . . . . . . . . . . . . . . . 10
5.2.3. LURK Client Behavior . . . . . . . . . . . . . . . . 11
5.2.4. LURK Server Behavior . . . . . . . . . . . . . . . . 11
5.3. ping . . . . . . . . . . . . . . . . . . . . . . . . . . 12
5.3.1. Request Payload . . . . . . . . . . . . . . . . . . . 12
5.3.2. Response Payload . . . . . . . . . . . . . . . . . . 12
5.3.3. LURK Client Behavior . . . . . . . . . . . . . . . . 12
5.3.4. LURK Server Behavior . . . . . . . . . . . . . . . . 12
5.4. rsa_master . . . . . . . . . . . . . . . . . . . . . . . 12
5.4.1. Request Payload . . . . . . . . . . . . . . . . . . . 12
5.4.2. Response Payload . . . . . . . . . . . . . . . . . . 13
5.4.3. LURK Client Behavior . . . . . . . . . . . . . . . . 13
5.4.4. LURK Server Behavior . . . . . . . . . . . . . . . . 14
5.5. rsa_extended_master . . . . . . . . . . . . . . . . . . . 14
Show full document text