DNS Push Notifications
draft-ietf-dnssd-push-01

The information below is for an old version of the document
Document Type Active Internet-Draft (dnssd WG)
Last updated 2015-10-19
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestones: Aug 2015 - Confirm long-lived q..., May 2017 - Submit DNS Push draf... )
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                              T. Pusateri
Internet-Draft                                       Seeking affiliation
Intended status: Standards Track                             S. Cheshire
Expires: April 21, 2016                                       Apple Inc.
                                                        October 19, 2015

                         DNS Push Notifications
                        draft-ietf-dnssd-push-01

Abstract

   The Domain Name System (DNS) was designed to efficiently return
   matching records for queries for data that is relatively static.
   When those records change frequently, DNS is still efficient at
   returning the updated results when polled.  But there exists no
   mechanism for a client to be asynchronously notified when these
   changes occur.  This document defines a mechanism for a client to be
   notified of such changes to DNS records, called DNS Push
   Notifications.

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 April 21, 2016.

Copyright Notice

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

Pusateri & Cheshire      Expires April 21, 2016                 [Page 1]
Internet-Draft           DNS Push Notifications             October 2015

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Transport . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  State Considerations  . . . . . . . . . . . . . . . . . . . .   5
   6.  Protocol Operation  . . . . . . . . . . . . . . . . . . . . .   6
     6.1.  Discovery . . . . . . . . . . . . . . . . . . . . . . . .   6
     6.2.  DNS Push Notification SUBSCRIBE . . . . . . . . . . . . .   8
     6.3.  DNS Push Notification UNSUBSCRIBE . . . . . . . . . . . .  10
     6.4.  DNS Push Notification Update Messages . . . . . . . . . .  11
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     9.1.  Security Services . . . . . . . . . . . . . . . . . . . .  14
     9.2.  TLS Name Authentication . . . . . . . . . . . . . . . . .  14
     9.3.  TLS Compression . . . . . . . . . . . . . . . . . . . . .  15
     9.4.  TLS Session Resumption  . . . . . . . . . . . . . . . . .  15
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   DNS records may be updated using DNS Update [RFC2136].  Other
   mechanisms such as a Hybrid Proxy [I-D.ietf-dnssd-hybrid] can also
   generate changes to a DNS zone.  This document specifies a protocol
   for Unicast DNS clients to subscribe to receive asynchronous
   notifications of changes to RRSets of interest.  It is immediately
   relevant in the case of DNS Service Discovery [RFC6763] but is not
   limited to that use case and provides a general DNS mechanism for DNS
   record change notifications.  Familiarity with the DNS protocol and
   DNS packet formats is assumed [RFC1034] [RFC1035] [RFC6195].

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in "Key words for use in
Show full document text