DNS Session Signaling
draft-bellis-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-07-11 (latest revision 2016-07-06)
Replaced by draft-ietf-dnsop-session-signal, rfc8490
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DNSOP Working Group                                            R. Bellis
Internet-Draft                                                       ISC
Intended status: Standards Track                             S. Cheshire
Expires: January 7, 2017                                      Apple Inc.
                                                            J. Dickinson
                                                                 Sinodun
                                                               A. Mankin
                                                             T. Pusateri
                                                            Unaffiliated
                                                            July 6, 2016

                         DNS Session Signaling
                  draft-bellis-dnsop-session-signal-00

Abstract

   The Extension Mechanisms for DNS (EDNS(0)) [RFC6891] 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
   handle feature negotiation and 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 January 7, 2017.

Copyright Notice

   Copyright (c) 2016 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

Bellis, et al.           Expires January 7, 2017                [Page 1]
Internet-Draft            DNS Session Signaling                July 2016

   (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  . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Message Format  . . . . . . . . . . . . . . . . . . . . .   3
     3.2.  Message Handling  . . . . . . . . . . . . . . . . . . . .   4
     3.3.  TLV Format  . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Mandatory TLVs  . . . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Feature Negotiation . . . . . . . . . . . . . . . . . . .   5
       4.1.1.  TypeCode Support  . . . . . . . . . . . . . . . . . .   5
     4.2.  Layer 4 Connection Management TLVs  . . . . . . . . . . .   6
       4.2.1.  Terminate . . . . . . . . . . . . . . . . . . . . . .   6
       4.2.2.  Idle Timeout  . . . . . . . . . . . . . . . . . . . .   6
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
     5.1.  DNS Session Signaling OpCode Registration . . . . . . . .   7
     5.2.  DNS Session Signaling Status Codes Registry . . . . . . .   7
     5.3.  DNS Session Signaling Type Codes Registry . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The Extension Mechanisms for DNS (EDNS(0)) [RFC6891] 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
   handle feature negotiation and to manage session timeouts and
   termination.

   A further issue with EDNS(0) is that there is no standard mechanism
   for a client to be able to tell whether a server has processed or
   otherwise acted upon the individual options contained with an OPT RR.
   The Session Signaling Opcode therefore requires an explicit response
   to each TLV within a request.

   The message format (see Section 3.1) does not completely conform to
Show full document text