draft-ietf-homenet-dot-04.txt   draft-ietf-homenet-dot-05.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: October 8, 2017 April 6, 2017 Expires: October 22, 2017 April 20, 2017
Special Use Domain '.home.arpa' Special Use Domain '.home.arpa'
draft-ietf-homenet-dot-04 draft-ietf-homenet-dot-05
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
'.home.arpa.', and designates this top-level domain as a special-use '.home.arpa.', and designates this domain as a special-use domain
domain name. The '.home.arpa' top-level domain replaces '.home' as name. The '.home.arpa' domain replaces '.home' as the default domain
the default domain used by the Home Networking Control Protocol used by the Home Networking Control Protocol (HNCP).
(HNCP).
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
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 October 8, 2017. This Internet-Draft will expire on October 22, 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
skipping to change at page 2, line 32 skipping to change at page 2, line 32
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 '.home.arpa' top-level domain replaces '.home' which was The '.home.arpa' domain replaces '.home' which was specified in
specified in [RFC7788] as the default domain-name for home networks. [RFC7788] as the default domain-name for home networks. '.home' had
'.home' had been selected as the most user-friendly option. However, been selected as the most user-friendly option. However, there are
there are existing uses of '.home' that may be in conflict with this existing uses of '.home' that may be in conflict with this use:
use: evidence indicates that '.home' queries frequently leak out and evidence indicates that '.home' queries frequently leak out and reach
reach the root name servers [ICANN1] [ICANN2]. Also, ICANN has about the root name servers [ICANN1] [ICANN2]. Also, ICANN has about a
a dozen applicants for the '.home' top-level domain name, which dozen applicants for the '.home' top-level domain name, which creates
creates a significant risk of litigation if it were claimed by the a significant risk of litigation if it were claimed by the IETF
IETF outside of that process. As a result, the use of '.home' has outside of that process. As a result, the use of '.home' has been
been deprecated; this document updates [RFC7788] to replace '.home' deprecated; this document updates [RFC7788] to replace '.home' with
with '.home.arpa', while another document, [I-D.ietf-homenet-redact] '.home.arpa', 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 '.home.arpa.' as a This document registers the domain '.home.arpa.' as a special-use
special-use domain name [RFC6761] and specifies the behavior that is domain name [RFC6761] and specifies the behavior that is expected
expected from the Domain Name System with regard to DNS queries for from the Domain Name System with regard to DNS queries for names
names whose rightmost non-terminal label is 'homenet'. Queries for whose rightmost non-terminal label is 'homenet'. Queries for names
names ending with '.home.arpa.' are of local significance within the ending with '.home.arpa.' are of local significance within the scope
scope of a home network, meaning that identical queries will result of a home network, meaning that identical queries will result in
in different results from one home network to another. In other different results from one home network to another. In other words,
words, a name ending in '.home.arpa' is not globally unique. a name ending in '.home.arpa' is not globally unique.
2. General Guidance 2. General Guidance
The top-level domain name '.home.arpa.' is to be used for naming The domain name '.home.arpa.' is to be used for naming within a home
within a home network. Names ending with '.home.arpa.' reference a network. Names ending with '.home.arpa.' reference a locally-served
locally-served zone, the contents of which are unique only to a zone, the contents of which are unique only to a particular home
particular home network, and are not globally unique. Such names network, and are not globally unique. Such names refer to nodes and/
refer to nodes and/or services that are located within a home network or services that are located within a home network (e.g., a printer,
(e.g., a printer, or a toaster). or a toaster).
DNS queries for names ending with '.home.arpa.' are resolved using DNS queries for names ending with '.home.arpa.' 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.
Some service discovery user interfaces that are expected to be used Some service discovery user interfaces that are expected to be used
on homenets conceal information such as domain names from end users. on homenets conceal information such as domain names from end users.
However, it is still expected that in some cases, users will need to However, it is still expected that in some cases, users will need to
see, remember, and even type, names ending with '.home.arpa'. It is see, remember, and even type, names ending with '.home.arpa'. It is
therefore desirable that users identify the top-level domain and therefore desirable that users identify the domain and understand
understand that using it expresses the intention to connect to a that using it expresses the intention to connect to a service that is
service that is specific to the home network to which they are specific to the home network to which they are connected. Enforcing
connected. Enforcing the fulfillment of this intention is out of 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 '.home.arpa.' resolution when serving queries for names ending with '.home.arpa.'
(as per [RFC6761]). (as per [RFC6761]).
1. Users can use names ending with '.home.arpa.' just as they would 1. Users can use names ending with '.home.arpa.' just as they would
use any other domain name. The '.home.arpa' name is chosen to be use any other domain name. The '.home.arpa' 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
skipping to change at page 4, line 29 skipping to change at page 4, line 28
5. Only a DNS server that is authoritative for the '.arpa' zone or 5. Only a DNS server that is authoritative for the '.arpa' zone or
is configured to be authoritative for '.home.arpa' or a subdomain is configured to be authoritative for '.home.arpa' or a subdomain
of '.home.arpa' will ever answer a query about '.home.arpa.' In of '.home.arpa' will ever answer a query about '.home.arpa.' In
both of these cases, the server should simply answer as both of these cases, the server should simply answer as
configured: no special handling is required. configured: no special handling is required.
6. DNS servers outside a home network should not be configured to be 6. DNS servers outside a home network should not be configured to be
authoritative for .home.arpa. authoritative for .home.arpa.
7. DNS Registries/Registrars MUST NOT grant requests to register 7. 'home.arpa' is a subdomain of the 'arpa' top-level domain, which
'.home.arpa' in the normal way to any person or entity. is entirely operated by the Internet Architecture Board. As
'.home.arpa' MUST BE registered in perpetuity to IANA, and IANA such, no new advice for registrars is required here.
MUST maintain nameservers for the zone.
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 6, line 21 skipping to change at page 6, line 21
The authors would like to thank Stuart Cheshire for his prior work on The authors would like to thank Stuart Cheshire for his prior work on
'.home', as well as the homenet chairs: Mark Townsley and Ray Bellis. '.home', as well as the homenet chairs: Mark Townsley and Ray Bellis.
We would also like to thank Paul Hoffman for providing review and We would also like to thank Paul Hoffman for providing review and
comments on the IANA considerations section. comments on the IANA considerations section.
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
Understanding Concerning the Technical Work of the
Internet Assigned Numbers Authority", RFC 2860,
DOI 10.17487/RFC2860, June 2000,
<http://www.rfc-editor.org/info/rfc2860>.
[RFC6303] Andrews, M., "Locally Served DNS Zones", BCP 163, [RFC6303] Andrews, M., "Locally Served DNS Zones", BCP 163,
RFC 6303, DOI 10.17487/RFC6303, July 2011, RFC 6303, DOI 10.17487/RFC6303, July 2011,
<http://www.rfc-editor.org/info/rfc6303>. <http://www.rfc-editor.org/info/rfc6303>.
[RFC6761] Cheshire, S. and M. Krochmal, "Special-Use Domain Names", [RFC6761] Cheshire, S. and M. Krochmal, "Special-Use Domain Names",
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>.
[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-
 End of changes. 10 change blocks. 
47 lines changed or deleted 38 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/