draft-ietf-homenet-dot-00.txt   draft-ietf-homenet-dot-01.txt 
Network Working Group P. Pfister Network Working Group P. Pfister
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Updates: RFC7788 (if approved) T. Lemon Updates: RFC7788 (if approved) T. Lemon
Intended status: Standards Track Nominum, Inc. Intended status: Standards Track Nominum, Inc.
Expires: May 19, 2017 November 15, 2016 Expires: July 23, 2017 January 19, 2017
Special Use Top Level Domain '.homenet' Special Use Top Level Domain '.homenet'
draft-ietf-homenet-dot-00 draft-ietf-homenet-dot-01
Abstract Abstract
This document specifies the behavior that is expected from the Domain This document specifies the behavior that is expected from the Domain
Name System with regard to DNS queries for names ending with Name System with regard to DNS queries for names ending with
'.homenet.', and designates this top-level domain as a special-use '.homenet.', and designates this top-level domain as a special-use
domain name. The '.homenet' top-level domain replaces '.home' as the domain name. The '.homenet' top-level domain replaces '.home' as the
default domain used by the Home Networking Control Protocol (HNCP). default domain used by the Home Networking Control Protocol (HNCP).
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
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 May 19, 2017. This Internet-Draft will expire on July 23, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 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. General Guidance . . . . . . . . . . . . . . . . . . . . . . 3 2. General Guidance . . . . . . . . . . . . . . . . . . . . . . 3
3. Domain Name Reservation Considerations . . . . . . . . . . . 3 3. Domain Name Reservation Considerations . . . . . . . . . . . 3
4. Updates to Home Networking Control Protocol . . . . . . . . . 4 4. Updates to Home Networking Control Protocol . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . 5 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 5 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
Users and devices within a home network require devices and services Users and devices within a home network require devices and services
to be identified by names that are unique within the boundaries of to be identified by names that are unique within the boundaries of
the home network [RFC7368]. The naming mechanism needs to function the home network [RFC7368]. The naming mechanism needs to function
without configuration from the user. While it may be possible for a 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 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 the absence of such a delegation. A default name with a scope
limited to each individual home network needs to be used. limited to each individual home network needs to be used.
The '.homenet' top-level domain replaces '.home' which was specified The '.homenet' top-level domain replaces '.home' which was specified
in [RFC7788] as the default domain-name for home networks. '.home' in [RFC7788] as the default domain-name for home networks. '.home'
had been selected as the most user-friendly option, but evidence had been selected as the most user-friendly option. However, there
indicates that '.home' queries frequently leak out and reach the root are existing uses of '.home' that may be in conflict with this use:
name servers [ICANN1] [ICANN2]. As a result, the use of '.home' has evidence indicates that '.home' queries frequently leak out and reach
been deprecated; this document updates [RFC7788] to replace '.home' the root name servers [ICANN1] [ICANN2]. Also, ICANN has about a
with '.homenet', while another document, [I-D.ietf-homenet-redact] 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. deprecates the use of the '.home' TLD.
This document registers the top-level domain '.homenet.' as a This document registers the top-level domain '.homenet.' as a
special-use domain name [RFC6761] and specifies the behavior that is special-use domain name [RFC6761] and specifies the behavior that is
expected from the Domain Name System with regard to DNS queries for expected from the Domain Name System with regard to DNS queries for
names whose rightmost non-terminal label is 'homenet'. Queries for names whose rightmost non-terminal label is 'homenet'. Queries for
names ending with '.homenet.' are of local significance within the names ending with '.homenet.' are of local significance within the
scope of a home network, meaning that identical queries will result scope of a home network, meaning that identical queries will result
in different results from one home network to another. In other in different results from one home network to another. In other
words, a name ending in '.homenet' is not globally unique. words, a name ending in '.homenet' is not globally unique.
2. General Guidance 2. General Guidance
The top-level domain name '.homenet.' is to be used for naming within The top-level domain name '.homenet.' is to be used for naming within
a home network. Names ending with '.homenet.' MUST refer to a home network. Names ending with '.homenet.' reference a locally-
services that are located within a home network (e.g., a printer, or served zone, the contents of which are unique only to a particular
a toaster). home network, and are not globally unique. Such names refer to nodes
and/or services that are located within a home network (e.g., a
printer, or a toaster).
DNS queries for names ending with '.homenet.' are resolved using DNS queries for names ending with '.homenet.' are resolved using
local resolvers on the homenet. Such queries MUST NOT be recursively local resolvers on the homenet. Such queries MUST NOT be recursively
forwarded to servers outside the logical boundaries of the home forwarded to servers outside the logical boundaries of the home
network. network.
Although home networks most often provide one or more service Some service discovery user interfaces that are expected to be used
discovery mechanisms, it is still expected that some users will see, on homenets conceal information such as domain names from end users.
remember, and sometimes even type, names ending with '.homenet'. It However, it is still expected that in some cases, users will need to
is therefore desireable that users identify the top-level domain and see, remember, and even type, names ending with '.homenet'. It is
therefore desirable that users identify the top-level domain and
understand that using it expresses the intention to connect to a understand that using it expresses the intention to connect to a
service that is specific to the home network to which they are service that is specific to the home network to which they are
connected. Enforcing the fulfillment of this intention is out of connected. Enforcing the fulfillment of this intention is out of
scope for this document. scope for this document.
3. Domain Name Reservation Considerations 3. Domain Name Reservation Considerations
This section defines the behavior of systems involved in domain name This section defines the behavior of systems involved in domain name
resolution when serving queries for names ending with '.homenet.' (as resolution when serving queries for names ending with '.homenet.' (as
per [RFC6761]). per [RFC6761]).
skipping to change at page 3, line 42 skipping to change at page 3, line 45
1. Users can use names ending with '.homenet.' just as they would 1. Users can use names ending with '.homenet.' just as they would
use any other domain name. The '.homenet' name is chosen to be use any other domain name. The '.homenet' name is chosen to be
readily recognized by users as signifying that the name is readily recognized by users as signifying that the name is
addressing a service on the homenet to which the user's device is addressing a service on the homenet to which the user's device is
connected. connected.
2. Applications SHOULD treat domain names ending with '.homenet.' 2. Applications SHOULD treat domain names ending with '.homenet.'
just like any other FQDN, and MUST NOT make any assumption on the just like any other FQDN, and MUST NOT make any assumption on the
level of additional security implied by its presence. level of additional security implied by its presence.
3. Name resolution APIs and libraries MUST NOT recognize names 3. Name resolution APIs and libraries MUST NOT recognize names that
ending with '.homenet.' as special and MUST NOT treat them end in '.homenet.' as special and MUST NOT treat them
differently. Name resolution APIs MUST send queries for such differently. Name resolution APIs MUST send queries for such
names to their configured caching DNS server(s). Using a caching names to their configured caching DNS server(s). Using a
server other than the server or servers offered by the home recursive resolver other than the resolver(s) offered by the home
network will result in failure to correctly resolve queries for network will result in failure to correctly resolve queries for
'.homenet'. subdomains of '.homenet'. If a host is configured to always use
a recursive resolver other than the one offered by the local
network, it will be unable to resolve queries that are subdomains
of '.homenet'.
4. Unless configured otherwise, Caching DNS servers MUST behave as 4. Unless configured otherwise, recursive resolvers and DNS proxies
described in Locally Served Zones ([RFC6303] Section 3). Caching MUST behave as described in Locally Served Zones ([RFC6303]
DNS Servers that are part of a home network MAY be configured Section 3). Recursive resolvers that are part of a home network
manually or automatically (e.g., for auto-configuration purposes) MAY be configured manually or automatically (e.g., for auto-
to act differently, e.g., by querying another name server configuration purposes) to act differently, e.g., by querying
configured as authoritative for part of the domain, or proxying another name server configured as authoritative for part or all
the request through a different mechanism. of the '.homenet' domain, or proxying the request through a
different mechanism.
5. Authoritative DNS Servers SHOULD recognize such names as special- 5. Only a DNS server that is authoritative for the root ('.') or is
use and SHOULD NOT, by default, attempt to look up NS records for configured to be authoritative for '.homenet' or a subdomain of
these names. Servers that are part of a home network or '.homenet' will ever answer a query about '.homenet.' In both of
providing name resolution services for a home network MAY be these cases, the server should simply answer as configured: no
configured to act as authoritative for the whole top-level domain special handling is required.
or a part of it.
6. DNS server operators should not configure DNS servers to act as 6. DNS servers outside a home network should not be configured to be
authoritative for any name ending in '.homenet'. authoritative for .homenet.
7. DNS Registries/Registrars MUST NOT grant requests to register 7. DNS Registries/Registrars MUST NOT grant requests to register
'.homenet' in the normal way to any person or entity. '.homenet' '.homenet' in the normal way to any person or entity. '.homenet'
is registered in perpetuity to IANA: is registered in perpetuity to IANA:
Domain Name: HOMENET Domain Name: HOMENET
Registrar: RESERVED-INTERNET ASSIGNED NUMBERS AUTHORITY Registrar: RESERVED-INTERNET ASSIGNED NUMBERS AUTHORITY
Whois Server: whois.iana.org Whois Server: whois.iana.org
Referral URL: http://res-dom.iana.org Referral URL: http://res-dom.iana.org
Name Server: A.IANA-SERVERS.NET Name Server: A.IANA-SERVERS.NET
Name Server: B.IANA-SERVERS.NET Name Server: B.IANA-SERVERS.NET
Status: clientDeleteProhibited Status: clientDeleteProhibited
Status: clientTransferProhibited Status: clientTransferProhibited
Status: clientUpdateProhibited Status: clientUpdateProhibited
4. Updates to Home Networking Control Protocol 4. Updates to Home Networking Control Protocol
The final paragraph of Homenet Considerations Protocol [RFC7788], The final paragraph of Homenet Considerations Protocol [RFC7788],
section 8, is updated as follows: section 8, is updated as follows:
OLD: OLD:
Names and unqualified zones are used in an HNCP network to provide Names and unqualified zones are used in an HNCP network to provide
naming and service discovery with local significance. A network- naming and service discovery with local significance. A network-
skipping to change at page 5, line 35 skipping to change at page 5, line 39
Because '.homenet' is not globally scoped and cannot be secured using Because '.homenet' is not globally scoped and cannot be secured using
DNSSEC based on the root domain's trust anchor, there is no way to DNSSEC based on the root domain's trust anchor, there is no way to
tell, using a standard DNS query, in which home network scope an tell, using a standard DNS query, in which home network scope an
answer belongs. Consequently, users may experience surprising answer belongs. Consequently, users may experience surprising
results with such names when roaming to different home networks. To results with such names when roaming to different home networks. To
prevent this from happening, it may be useful for the resolver to prevent this from happening, it may be useful for the resolver to
identify different home networks on which it has resolved names, but identify different home networks on which it has resolved names, but
this is out of scope for this document. this is out of scope for this document.
In order to enable DNSSEC validation of a particular '.homenet', it
might make sense to configure a trust anchor for that homenet. How
this might be done is out of scope for this document.
6. IANA Considerations 6. IANA Considerations
IANA is requested to record the top-level domain ".homenet" in the IANA is requested to record the top-level domain ".homenet" in the
Special-Use Domain Names registry [SUDN]. Special-Use Domain Names registry [SUDN].
IANA is requested to set up insecure delegation for '.homenet' in the IANA is requested to set up insecure delegation for '.homenet' in the
root zone pointing to the AS112 service [RFC7535], to break the root zone pointing to the AS112 service [RFC7535], to break the
DNSSEC chain of trust. DNSSEC chain of trust.
7. Acknowledgments 7. Acknowledgments
skipping to change at page 6, line 24 skipping to change at page 6, line 29
RFC 6761, DOI 10.17487/RFC6761, February 2013, RFC 6761, DOI 10.17487/RFC6761, February 2013,
<http://www.rfc-editor.org/info/rfc6761>. <http://www.rfc-editor.org/info/rfc6761>.
[RFC7535] Abley, J., Dickson, B., Kumari, W., and G. Michaelson, [RFC7535] Abley, J., Dickson, B., Kumari, W., and G. Michaelson,
"AS112 Redirection Using DNAME", RFC 7535, "AS112 Redirection Using DNAME", RFC 7535,
DOI 10.17487/RFC7535, May 2015, DOI 10.17487/RFC7535, May 2015,
<http://www.rfc-editor.org/info/rfc7535>. <http://www.rfc-editor.org/info/rfc7535>.
[I-D.ietf-homenet-redact] [I-D.ietf-homenet-redact]
Lemon, T., "Redacting .home from HNCP", draft-ietf- Lemon, T., "Redacting .home from HNCP", draft-ietf-
homenet-redact-00 (work in progress), September 2016. homenet-redact-01 (work in progress), November 2016.
8.2. Informative References 8.2. Informative References
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, DOI 10.17487/RFC1035, specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <http://www.rfc-editor.org/info/rfc1035>. November 1987, <http://www.rfc-editor.org/info/rfc1035>.
[RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J. [RFC7368] Chown, T., Ed., Arkko, J., Brandt, A., Troan, O., and J.
Weil, "IPv6 Home Networking Architecture Principles", Weil, "IPv6 Home Networking Architecture Principles",
RFC 7368, DOI 10.17487/RFC7368, October 2014, RFC 7368, DOI 10.17487/RFC7368, October 2014,
 End of changes. 17 change blocks. 
47 lines changed or deleted 61 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/