Simple Homenet Naming and Service Discovery Architecture
draft-tldm-simple-homenet-naming-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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)
Network Working Group                                           T. Lemon
Internet-Draft                                             Nominum, Inc.
Intended status: Informational                                D. Migault
Expires: September 14, 2017                                     Ericsson
                                                          March 13, 2017

        Simple Homenet Naming and Service Discovery Architecture
                  draft-tldm-simple-homenet-naming-00

Abstract

   This document describes a simple name resolution and service
   discovery architecture for homenets.  This architecture covers local
   publication of names, as well as name resolution for local and global
   names.

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 14, 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.

Lemon & Migault        Expires September 14, 2017               [Page 1]
Internet-Draft        Simple Homenet Naming/SD Arch           March 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Existing solutions  . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Name Resolution . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Configuring Resolvers . . . . . . . . . . . . . . . . . .   4
     3.2.  Configuring Service Discovery . . . . . . . . . . . . . .   5
     3.3.  Resolution of local names . . . . . . . . . . . . . . . .   5
     3.4.  DNSSEC Validation . . . . . . . . . . . . . . . . . . . .   6
     3.5.  Support for Multiple Provisioning Domains . . . . . . . .   6
     3.6.  Using the Local Namespace While Away From Home  . . . . .   7
   4.  Management Considerations . . . . . . . . . . . . . . . . . .   7
   5.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   8
   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   Associating domain names with hosts on the Internet is a key factor
   in enabling communication with hosts, particularly for service
   discovery.  This document describes a simple way of providing name
   service and service discovery for homenets.  In principle, it may
   make sense to be able to publish names of devices on the homenet, so
   that services on the homenet can be accessed outside of the homenet.
   Such publication is out of scope for this document.  It may be
   desirable to secure the homenet zone using DNSSEC.  This is likewise
   out of scope for this document.

   In order to provide name service, several provisioning mechanisms
   must be available:

   o  Provisioning of a domain name under which names can be published
      and services advertised

   o  Associating names that are subdomains of that name with hosts.

   o  Advertising services available on the local network by publishing
      resource records on those names.

   o  Distribution of names published in that namespace to servers that
      can be queried in order to resolve names

   o  Correct advertisement of name servers that can be queried in order
      to resolve names

Lemon & Migault        Expires September 14, 2017               [Page 2]
Internet-Draft        Simple Homenet Naming/SD Arch           March 2017
Show full document text