[Docs] [txt|pdf|xml] [Tracker] [WG] [Email] [Nits]

Versions: 00 01 02 03

Home Networking                                                 T. Lemon
Internet-Draft                                             Nominum, Inc.
Updates: RFC7788 (if approved)                           August 26, 2016
Intended status: Informational
Expires: February 27, 2017


                       Redacting .home from HNCP
                      draft-ietf-homenet-redact-00

Abstract

   This document updates the Home Networking Control Protocol,
   eliminating the recommendation for a default top-level name for local
   name resolution.

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 February 27, 2017.

Copyright Notice

   Copyright (c) 2016 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                   Expires February 27, 2017               [Page 1]


Internet-Draft                 HNCP Redact                   August 2016


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Updates to Home Networking Control Protocol . . . . . . . . .   2
   3.  Normative References  . . . . . . . . . . . . . . . . . . . .   3
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   3

1.  Introduction

   The Homenet working group has defined a mechanism for sharing
   information between homenet routers, in Home Networking Control
   Protocol [2].  This document recomments the use of the ".home" top-
   level name as a locally-resolved domain name.

   RFC7788 did not follow the process defined in Special Use Domain
   Names [1].  It is likely that, had this process been followed, it
   would not have been possible to gain consensus on the use of '.home'
   as the locally-resolved special-use top-level name for homenets,
   because this name is known to be informally in use by sites on the
   internet, and the use to which this name has been put is not well
   documented; it is impossible to say that there are no conflicting
   uses for the name, and so getting consensus to use it anyway would
   have been controversial, time consuming, and possibly futile.

   The RFC6761 process is not well-understood within the IETF, and the
   authors of RFC7788 were not aware of it.  Normally, authors are not
   expected to know all there is to know about IETF process, and IETF
   leadership, specifically working group chairs, area directors and
   directorate members are expected to engage in a review process that
   notices oversights of this sort.

   Unfortunately, in the case of RFC7788, none of the people who should
   have caught the missing RFC6761 reference did catch it, and RFC 7788
   was published as a consensus document that uses '.home' without ever
   reserving it in the RFC6761 Special-Use Domain Names registry.

   This document updates RFC 7788 to remove the specification to use
   '.home' for site-local name resolution within the homenet.

2.  Updates to Home Networking Control Protocol

   The final paragraph of RFC 7788, section 8, is updated as follows:

   OLD:

      Names and unqualified zones are used in an HNCP network to provide
      naming and service discovery with local significance.  A network-
      wide zone is appended to all single labels or unqualified zones in



Lemon                   Expires February 27, 2017               [Page 2]


Internet-Draft                 HNCP Redact                   August 2016


      order to qualify them. ".home" is the default; however, an
      administrator MAY configure the announcement of a Domain-Name TLV
      (Section 10.6) for the network to use a different one.  In case
      multiple are announced, the domain of the node with the greatest
      node identifier takes precedence.

   NEW: (deleted)

3.  Normative References

   [1]        Cheshire, S. and M. Krochmal, "Special-Use Domain Names",
              RFC 6761, DOI 10.17487/RFC6761, February 2013,
              <http://www.rfc-editor.org/info/rfc6761>.

   [2]        Stenberg, M., Barth, S., and P. Pfister, "Home Networking
              Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April
              2016, <http://www.rfc-editor.org/info/rfc7788>.

Author's Address

   Ted Lemon
   Nominum, Inc.
   800 Bridge Parkway
   Redwood City, California  94065
   United States of America

   Phone: +1 650 381 6000
   Email: ted.lemon@nominum.com























Lemon                   Expires February 27, 2017               [Page 3]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/