draft-ietf-homenet-redact-02.txt   draft-ietf-homenet-redact-03.txt 
Home Networking T. Lemon Home Networking T. Lemon
Internet-Draft Nominum, Inc. Internet-Draft Nominum, Inc.
Updates: RFC7788 (if approved) January 19, 2017 Updates: RFC7788 (if approved) March 13, 2017
Intended status: Standards Track Intended status: Standards Track
Expires: July 23, 2017 Expires: September 14, 2017
Redacting .home from HNCP Redacting .home from HNCP
draft-ietf-homenet-redact-02 draft-ietf-homenet-redact-03
Abstract Abstract
This document updates the Home Networking Control Protocol, This document updates the Home Networking Control Protocol,
eliminating the recommendation for a default top-level name for local eliminating the recommendation for a default top-level name for local
name resolution. name resolution.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 23, 2017. This Internet-Draft will expire on September 14, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Updates to Home Networking Control Protocol . . . . . . . . . 2 2. Updates to Home Networking Control Protocol . . . . . . . . . 2
3. Normative References . . . . . . . . . . . . . . . . . . . . 2 3. Normative References . . . . . . . . . . . . . . . . . . . . 3
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction 1. Introduction
The Homenet working group has defined a mechanism for sharing The Homenet working group has defined a mechanism for sharing
information between homenet routers, in Home Networking Control information between homenet routers, in Home Networking Control
Protocol [2]. That document recommends the use of the ".home" top- Protocol [2]. That document recommends the use of the ".home" top-
level name as a locally-resolved domain name. level name as a locally-resolved domain name.
RFC7788 did not follow the process defined in Special Use Domain RFC7788 did not follow the process defined in Special Use Domain
Names [1]. It is likely that, had this process been followed, it Names [1], or specify how other software should deal with the
would not have been possible to gain consensus on the use of '.home' allocated name. It is likely that, had this process been followed,
as the locally-resolved special-use top-level name for homenets, it would not have been possible to gain consensus on the use of
because this name is known to be informally in use by sites on the '.home' as the locally-resolved special-use top-level name for
internet, and the use to which this name has been put is not well homenets, because this name is known to be informally in use by sites
documented; it is impossible to say that there are no conflicting on the internet, and the use to which this name has been put is not
uses for the name, and so getting consensus to use it anyway would well documented; it is impossible to say that there are no
have been controversial, time consuming, and possibly futile. 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 The RFC6761 process is not well-understood within the IETF, and the
authors of RFC7788 were not aware of it. Normally, authors are not 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 expected to know all there is to know about IETF process, and IETF
leadership, specifically working group chairs, area directors and leadership, specifically working group chairs, area directors and
directorate members are expected to engage in a review process that directorate members are expected to engage in a review process that
notices oversights of this sort. notices oversights of this sort.
Unfortunately, in the case of RFC7788, none of the people who should Unfortunately, in the case of RFC7788, none of the people who should
have caught the missing RFC6761 reference did catch it, and RFC 7788 have caught the missing RFC6761 reference did catch it, and RFC 7788
 End of changes. 6 change blocks. 
13 lines changed or deleted 15 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/