DNS Session Signaling
draft-ietf-dnsop-session-signal-00
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (dnsop WG)
|
|
Last updated |
|
2016-08-15
|
|
Replaces |
|
draft-bellis-dnsop-session-signal
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
Tim Wicinski
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
"Tim Wicinski" <tjw.ietf@gmail.com>
|
DNSOP Working Group R. Bellis
Internet-Draft ISC
Intended status: Standards Track S. Cheshire
Expires: February 15, 2017 Apple Inc.
J. Dickinson
S. Dickinson
Sinodun
A. Mankin
Salesforce
T. Pusateri
Unaffiliated
August 14, 2016
DNS Session Signaling
draft-ietf-dnsop-session-signal-00
Abstract
The EDNS(0) Extension Mechanism for DNS is explicitly defined to only
have "per-message" semantics. This document defines a new Session
Signaling Opcode used to carry persistent "per-session" type-length-
values (TLVs), and defines an initial set of TLVs used to manage
session timeouts and termination.
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 February 15, 2017.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved.
Bellis, et al. Expires February 15, 2017 [Page 1]
Internet-Draft DNS Session Signaling August 2016
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Protocol Details . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Session Lifecycle . . . . . . . . . . . . . . . . . . . . 4
3.2. Message Format . . . . . . . . . . . . . . . . . . . . . 5
3.3. Message Handling . . . . . . . . . . . . . . . . . . . . 6
3.4. TLV Format . . . . . . . . . . . . . . . . . . . . . . . 7
4. Mandatory TLVs . . . . . . . . . . . . . . . . . . . . . . . 7
4.1. Session Management Support TLVs . . . . . . . . . . . . . 7
4.1.1. "Not Implemented" . . . . . . . . . . . . . . . . . . 8
4.2. Session Management TLVs . . . . . . . . . . . . . . . . . 8
4.2.1. Idle Timeout . . . . . . . . . . . . . . . . . . . . 8
4.2.2. Terminate Session . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
5.1. DNS Session Signaling Opcode Registration . . . . . . . . 10
5.2. DNS Session Signaling Type Codes Registry . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . . . 11
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
8.1. Normative References . . . . . . . . . . . . . . . . . . 11
8.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
The use of transports other than UDP for DNS is being increasingly
specified, for example, DNS-over-TCP [RFC7766], DNS-over-TLS
[RFC7858] and recent work on DNS Push Notifications
[I-D.ietf-dnssd-push]. Such transports frequently use persistent,
long-lived sessions and therefore when using them for transporting
DNS messages it is of benefit to have a mechanism that can establish
parameters associated with those sessions, such as timeouts. In such
Show full document text