Outsourcing Home Network Authoritative Naming Service
draft-ietf-homenet-front-end-naming-delegation-06

Document Type Active Internet-Draft (homenet WG)
Last updated 2017-10-27
Replaces draft-mglt-homenet-front-end-naming-delegation
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
HOMENET                                                  D. Migault (Ed)
Internet-Draft                                                  Ericsson
Intended status: Standards Track                                R. Weber
Expires: April 30, 2018                                          Nominum
                                                               R. Hunter
                                                    Globis Consulting BV
                                                            C. Griffiths

                                                             W. Cloetens
                                                              SoftAtHome
                                                        October 27, 2017

         Outsourcing Home Network Authoritative Naming Service
           draft-ietf-homenet-front-end-naming-delegation-06

Abstract

   Designation of services and devices of a home network is not user
   friendly, and mechanisms should enable a user to designate services
   and devices inside a home network using names.

   In order to enable internal communications while the home network
   experiments Internet connectivity shortage, the naming service should
   be hosted on a device inside the home network.  On the other hand,
   home networks devices have not been designed to handle heavy loads.
   As a result, hosting the naming service on such home network device,
   visible on the Internet exposes this device to resource exhaustion
   and other attacks, which could make the home network unreachable, and
   most probably would also affect the internal communications of the
   home network.

   As result, home networks may prefer not serving the naming service
   for the Internet, but instead prefer outsourcing it to a third party.
   This document describes a mechanisms that enables the Home Network
   Authority (HNA) to outsource the naming service to the Outsourcing
   Infrastructure.

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/.

Migault (Ed), et al.     Expires April 30, 2018                 [Page 1]
Internet-Draft  Outsourcing Authoritative Naming Service    October 2017

   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 30, 2018.

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
   (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.

Table of Contents

   1.  Requirements notation . . . . . . . . . . . . . . . . . . . .   3
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Architecture Description  . . . . . . . . . . . . . . . . . .   6
     4.1.  Architecture Overview . . . . . . . . . . . . . . . . . .   6
     4.2.  Example: Homenet Zone . . . . . . . . . . . . . . . . . .   8
     4.3.  Example: HNA necessary parameters for outsourcing . . . .  10
   5.  Synchronization between HNA and the Synchronization Server  .  11
     5.1.  Synchronization with a Hidden Primary . . . . . . . . . .  11
     5.2.  Securing Synchronization  . . . . . . . . . . . . . . . .  12
     5.3.  HNA Security Policies . . . . . . . . . . . . . . . . . .  14
   6.  DNSSEC compliant Homenet Architecture . . . . . . . . . . . .  14
     6.1.  Zone Signing  . . . . . . . . . . . . . . . . . . . . . .  14
     6.2.  Secure Delegation . . . . . . . . . . . . . . . . . . . .  16
   7.  Handling Different Views  . . . . . . . . . . . . . . . . . .  17
     7.1.  Misleading Reasons for Local Scope DNS Zone . . . . . . .  17
     7.2.  Consequences  . . . . . . . . . . . . . . . . . . . . . .  18
     7.3.  Guidance and Recommendations  . . . . . . . . . . . . . .  18
Show full document text