idnits 2.17.1 draft-lemon-homenet-dns-requirements-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 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (November 16, 2016) is 2715 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- No issues found here. Summary: 1 error (**), 0 flaws (~~), 1 warning (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group T. Lemon 3 Internet-Draft Nominum, Inc. 4 Intended status: Informational November 16, 2016 5 Expires: May 20, 2017 7 Requirements for Homenet Naming Architecture 8 draft-lemon-homenet-dns-requirements-00 10 Abstract 12 This document describes options for how naming could be done in a 13 homenet, and lists requirements for each solution. 15 Status of This Memo 17 This Internet-Draft is submitted in full conformance with the 18 provisions of BCP 78 and BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF). Note that other groups may also distribute 22 working documents as Internet-Drafts. The list of current Internet- 23 Drafts is at http://datatracker.ietf.org/drafts/current/. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 This Internet-Draft will expire on May 20, 2017. 32 Copyright Notice 34 Copyright (c) 2016 IETF Trust and the persons identified as the 35 document authors. All rights reserved. 37 This document is subject to BCP 78 and the IETF Trust's Legal 38 Provisions Relating to IETF Documents 39 (http://trustee.ietf.org/license-info) in effect on the date of 40 publication of this document. Please review these documents 41 carefully, as they describe your rights and restrictions with respect 42 to this document. Code Components extracted from this document must 43 include Simplified BSD License text as described in Section 4.e of 44 the Trust Legal Provisions and are provided without warranty as 45 described in the Simplified BSD License. 47 Table of Contents 49 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 50 2. Security Considerations . . . . . . . . . . . . . . . . . . . 3 51 3. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 3 52 4. Informative References . . . . . . . . . . . . . . . . . . . 3 53 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 3 55 1. Introduction 57 The homenet working group is trying to develop a suite of 58 specifications that, when implemented together, will produce home 59 routers that are capable of supporting fully-featured end-to-end 60 routed internet service. Of course, fully-featured could mean a lot 61 of things, and at present the homenet naming architecture is stalled 62 over the question of what it means. 64 There are a few things it could mean. At the most basic level, it 65 could mean simply that devices that publish services using mDNS are 66 reachable from anywhere on the home network using dnssd hybrid proxy, 67 that caching name service [RFC1035] or DNS Proxy service is provided 68 for off-network queries, and that no other naming is available on the 69 homenet. This is fairly easy to implement, and likely would address 70 all use cases addressed by existing home routers, but would support 71 service discovery across routers, which current home routers do not 72 support. We'll call this option 1. 74 A second option would be to provide fully-featured name service, 75 using DNS updates with mDNS as a backup. This differs from option 1 76 in that there would have to be one or more stateful DNS authoritative 77 servers on the homenet. It would require additional bookkeeping work 78 on the part of the infrastructure to delete stale names. It would 79 require some form of quorum detection and election for cases where 80 the end user decommissions devices without telling the network, and 81 adds devices without telling the network. In order to actually add 82 value, this option requires that it be possible for the homenet to 83 acquire a global DNS delegation somehow. 85 A third option would be to provide the second option with DNSSEC, 86 including a secure delegation from the root. 88 In order to make anything other than option 1 work, some interaction 89 with the end user would be required. In order to support DNSSEC, 90 some sort of secure pairing process would be necessary. Supporting 91 either of these options requires either that we pass the buck on how 92 to do this to router vendors and hope for the best, or that we 93 specify some sort of management API that allows for these functions 94 to be done in a standards-compliant way, so apps can be written for 95 smart devices that will support any homenet router that an end user 96 purchases. 98 2. Security Considerations 100 3. Acknowledgments 102 4. Informative References 104 [RFC1035] Mockapetris, P., "Domain names - implementation and 105 specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, 106 November 1987, . 108 Author's Address 110 Ted Lemon 111 Nominum, Inc. 112 800 Bridge Parkway 113 Redwood City, California 94065 114 United States of America 116 Phone: +1 650 381 6000 117 Email: ted.lemon@nominum.com