idnits 2.17.1 draft-ietf-homenet-redact-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 98: '... administrator MAY configure the ann...' == The 'Updates: ' line in the draft header should list only the _numbers_ of the RFCs which will be updated by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (August 26, 2016) is 2800 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 3 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Home Networking T. Lemon 3 Internet-Draft Nominum, Inc. 4 Updates: RFC7788 (if approved) August 26, 2016 5 Intended status: Informational 6 Expires: February 27, 2017 8 Redacting .home from HNCP 9 draft-ietf-homenet-redact-00 11 Abstract 13 This document updates the Home Networking Control Protocol, 14 eliminating the recommendation for a default top-level name for local 15 name resolution. 17 Status of This Memo 19 This Internet-Draft is submitted in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF). Note that other groups may also distribute 24 working documents as Internet-Drafts. The list of current Internet- 25 Drafts is at http://datatracker.ietf.org/drafts/current/. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 This Internet-Draft will expire on February 27, 2017. 34 Copyright Notice 36 Copyright (c) 2016 IETF Trust and the persons identified as the 37 document authors. All rights reserved. 39 This document is subject to BCP 78 and the IETF Trust's Legal 40 Provisions Relating to IETF Documents 41 (http://trustee.ietf.org/license-info) in effect on the date of 42 publication of this document. Please review these documents 43 carefully, as they describe your rights and restrictions with respect 44 to this document. Code Components extracted from this document must 45 include Simplified BSD License text as described in Section 4.e of 46 the Trust Legal Provisions and are provided without warranty as 47 described in the Simplified BSD License. 49 Table of Contents 51 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 52 2. Updates to Home Networking Control Protocol . . . . . . . . . 2 53 3. Normative References . . . . . . . . . . . . . . . . . . . . 3 54 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 56 1. Introduction 58 The Homenet working group has defined a mechanism for sharing 59 information between homenet routers, in Home Networking Control 60 Protocol [2]. This document recomments the use of the ".home" top- 61 level name as a locally-resolved domain name. 63 RFC7788 did not follow the process defined in Special Use Domain 64 Names [1]. It is likely that, had this process been followed, it 65 would not have been possible to gain consensus on the use of '.home' 66 as the locally-resolved special-use top-level name for homenets, 67 because this name is known to be informally in use by sites on the 68 internet, and the use to which this name has been put is not well 69 documented; it is impossible to say that there are no conflicting 70 uses for the name, and so getting consensus to use it anyway would 71 have been controversial, time consuming, and possibly futile. 73 The RFC6761 process is not well-understood within the IETF, and the 74 authors of RFC7788 were not aware of it. Normally, authors are not 75 expected to know all there is to know about IETF process, and IETF 76 leadership, specifically working group chairs, area directors and 77 directorate members are expected to engage in a review process that 78 notices oversights of this sort. 80 Unfortunately, in the case of RFC7788, none of the people who should 81 have caught the missing RFC6761 reference did catch it, and RFC 7788 82 was published as a consensus document that uses '.home' without ever 83 reserving it in the RFC6761 Special-Use Domain Names registry. 85 This document updates RFC 7788 to remove the specification to use 86 '.home' for site-local name resolution within the homenet. 88 2. Updates to Home Networking Control Protocol 90 The final paragraph of RFC 7788, section 8, is updated as follows: 92 OLD: 94 Names and unqualified zones are used in an HNCP network to provide 95 naming and service discovery with local significance. A network- 96 wide zone is appended to all single labels or unqualified zones in 97 order to qualify them. ".home" is the default; however, an 98 administrator MAY configure the announcement of a Domain-Name TLV 99 (Section 10.6) for the network to use a different one. In case 100 multiple are announced, the domain of the node with the greatest 101 node identifier takes precedence. 103 NEW: (deleted) 105 3. Normative References 107 [1] Cheshire, S. and M. Krochmal, "Special-Use Domain Names", 108 RFC 6761, DOI 10.17487/RFC6761, February 2013, 109 . 111 [2] Stenberg, M., Barth, S., and P. Pfister, "Home Networking 112 Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April 113 2016, . 115 Author's Address 117 Ted Lemon 118 Nominum, Inc. 119 800 Bridge Parkway 120 Redwood City, California 94065 121 United States of America 123 Phone: +1 650 381 6000 124 Email: ted.lemon@nominum.com