Special Use Top Level Domain '.homenet'
draft-ietf-homenet-dot-03

Document Type Active Internet-Draft (homenet WG)
Last updated 2017-03-13
Replaces draft-pfister-homenet-dot
Stream IETF
Intended RFC status Proposed Standard
Formats plain text xml pdf html bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Ray Bellis
Shepherd write-up Show (last changed 2017-03-02)
IESG IESG state AD Evaluation
Consensus Boilerplate Yes
Telechat date
Responsible AD Terry Manderson
Send notices to Ray Bellis <ray@bellis.me.uk>
Network Working Group                                         P. Pfister
Internet-Draft                                             Cisco Systems
Updates: RFC7788 (if approved)                                  T. Lemon
Intended status: Standards Track                           Nominum, Inc.
Expires: September 14, 2017                               March 13, 2017

                Special Use Top Level Domain '.homenet'
                       draft-ietf-homenet-dot-03

Abstract

   This document specifies the behavior that is expected from the Domain
   Name System with regard to DNS queries for names ending with
   '.homenet.', and designates this top-level domain as a special-use
   domain name.  The '.homenet' top-level domain replaces '.home' as the
   default domain used by the Home Networking Control Protocol (HNCP).

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

Pfister & Lemon        Expires September 14, 2017               [Page 1]
Internet-Draft                 dot homenet                    March 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  General Guidance  . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Domain Name Reservation Considerations  . . . . . . . . . . .   3
   4.  Updates to Home Networking Control Protocol . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   6
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   Users and devices within a home network require devices and services
   to be identified by names that are unique within the boundaries of
   the home network [RFC7368].  The naming mechanism needs to function
   without configuration from the user.  While it may be possible for a
   name to be delegated by an ISP, home networks must also function in
   the absence of such a delegation.  A default name with a scope
   limited to each individual home network needs to be used.

   The '.homenet' top-level domain replaces '.home' which was specified
   in [RFC7788] as the default domain-name for home networks. '.home'
   had been selected as the most user-friendly option.  However, there
   are existing uses of '.home' that may be in conflict with this use:
   evidence indicates that '.home' queries frequently leak out and reach
   the root name servers [ICANN1] [ICANN2].  Also, ICANN has about a
   dozen applicants for the '.home' top-level domain name, which creates
   a significant risk of litigation if it were claimed by the IETF
   outside of that process.  As a result, the use of '.home' has been
   deprecated; this document updates [RFC7788] to replace '.home' with
   '.homenet', while another document, [I-D.ietf-homenet-redact]
   deprecates the use of the '.home' TLD.

   This document registers the top-level domain '.homenet.' as a
   special-use domain name [RFC6761] and specifies the behavior that is
   expected from the Domain Name System with regard to DNS queries for
Show full document text