Unicast Service Discovery Autoconfiguration

Document Type Active Internet-Draft (individual)
Last updated 2018-11-07
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Internet Engineering Task Force                              S. Cheshire
Internet-Draft                                                Apple Inc.
Intended status: Informational                                  T. Lemon
Expires: May 12, 2019                                Nibbhaya Consulting
                                                        November 8, 2018

              Unicast Service Discovery Autoconfiguration


   This document considers the requirements for adding a Thread mesh to
   an existing home network, where the infrastructure of that existing
   home network was designed with no prior knowledge of Thread, and
   provides no special or unusual facilities designed to support this.

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 https://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 May 12, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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.

Cheshire & Lemon          Expires May 12, 2019                  [Page 1]
Internet-Draft    Unicast Service Discovery Autoconfig     November 2018

1.  Introduction

   [Authors' note: As an initial draft, in places this document presents
   several alternatives that are being considered.  We invite feedback
   and comments to help evolve this document.]

   Because multicast can be inefficient and unreliable [Mcast], work is
   taking place to enable DNS-Based Service Discovery [RFC6763] to
   operate with less reliance on multicast [Roadmap].  One current
   target use case for this work is Thread [Thread] wireless mesh

   Thread wireless mesh networking uses IEEE 802.15.4 radios, which use
   little power, and are suitable for battery-powered devices.  The
   Thread protocol organizes the network nodes into a mesh, typically
   with a Thread border router that connects the mesh to the home
   network.  For the purposes of this document we will refer to the home
   network, be it Ethernet, or Wi-Fi, or both, or other similar
   technologies, simply as the home network.  The home network forms a
   backbone to which one or more Thread mesh networks connect via Thread
   border routers.

   Existing work describes how DNS-Based Service Discovery can be
   performed using unicast on such a network.  Devices on the Thread
   mesh offering services use Service Registration Protocol [RegProt] to
   register their services at a Service Registration Server.  Devices
   seeking to discover these services send unicast queries to the
   Service Registration Server using unicast DNS [RFC1034] [RFC1035] for
   single individual queries, and using DNS Push Notifications [Push]
   where ongoing change notification is required.

   Certain configuration information is required for this to work.
   Devices on the Thread mesh offering services need to know what names
   to use when registering those services, and to what address they
   should send their service registrations.  Devices seeking to discover
   these services need to know what names to use when constructing their
   queries, and to what address they should send those queries.  In
   addition, IPv6 address prefixes need to be chosen and configured for
   both the home network and the Thread mesh network(s), and
   communicated, in order to facilitate unicast communication between
   clients and the services they have discovered.

   For proof-of-concept experiments, the necessary information can be
   configured manually, and this has been done successfully.  For
   deployment, we need to determine how the necessary information will
   be learned and configured automatically in real-world scenarios.

Cheshire & Lemon          Expires May 12, 2019                  [Page 2]
Internet-Draft    Unicast Service Discovery Autoconfig     November 2018
Show full document text