draft-ietf-homenet-dot-03.txt   draft-ietf-homenet-dot-04.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: September 14, 2017 March 13, 2017 Expires: October 8, 2017 April 6, 2017
Special Use Top Level Domain '.homenet' Special Use Domain '.home.arpa'
draft-ietf-homenet-dot-03 draft-ietf-homenet-dot-04
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 '.home.arpa.', and designates this top-level domain as a special-use
domain name. The '.homenet' top-level domain replaces '.home' as the domain name. The '.home.arpa' top-level domain replaces '.home' as
default domain used by the Home Networking Control Protocol (HNCP). the default domain used by the Home Networking Control Protocol
(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 September 14, 2017. This Internet-Draft will expire on October 8, 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 14 skipping to change at page 2, line 14
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. Delegation of 'home.arpa' . . . . . . . . . . . . . . . . . . 5
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 6 9.1. Normative References . . . . . . . . . . . . . . . . . . 6
9.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 '.home.arpa' top-level domain replaces '.home' which was
in [RFC7788] as the default domain-name for home networks. '.home' specified in [RFC7788] as the default domain-name for home networks.
had been selected as the most user-friendly option. However, there '.home' had been selected as the most user-friendly option. However,
are existing uses of '.home' that may be in conflict with this use: there are existing uses of '.home' that may be in conflict with this
evidence indicates that '.home' queries frequently leak out and reach use: evidence indicates that '.home' queries frequently leak out and
the root name servers [ICANN1] [ICANN2]. Also, ICANN has about a reach the root name servers [ICANN1] [ICANN2]. Also, ICANN has about
dozen applicants for the '.home' top-level domain name, which creates a dozen applicants for the '.home' top-level domain name, which
a significant risk of litigation if it were claimed by the IETF creates a significant risk of litigation if it were claimed by the
outside of that process. As a result, the use of '.home' has been IETF outside of that process. As a result, the use of '.home' has
deprecated; this document updates [RFC7788] to replace '.home' with been deprecated; this document updates [RFC7788] to replace '.home'
'.homenet', while another document, [I-D.ietf-homenet-redact] with '.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 '.homenet.' as a This document registers the top-level domain '.home.arpa.' 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 '.home.arpa.' 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 '.home.arpa' 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 '.home.arpa.' is to be used for naming
a home network. Names ending with '.homenet.' reference a locally- within a home network. Names ending with '.home.arpa.' reference a
served zone, the contents of which are unique only to a particular locally-served zone, the contents of which are unique only to a
home network, and are not globally unique. Such names refer to nodes particular home network, and are not globally unique. Such names
and/or services that are located within a home network (e.g., a refer to nodes and/or services that are located within a home network
printer, or a toaster). (e.g., a printer, or a toaster).
DNS queries for names ending with '.homenet.' 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 '.homenet'. 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 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 '.home.arpa.'
per [RFC6761]). (as per [RFC6761]).
1. Users can use names ending with '.homenet.' just as they would 1. Users can use names ending with '.home.arpa.' just as they would
use any other domain name. The '.homenet' 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
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 '.home.arpa.'
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 that 3. Name resolution APIs and libraries MUST NOT recognize names that
end in '.homenet.' as special and MUST NOT treat them end in '.home.arpa.' 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 a recursive DNS server that is configured to be names to a recursive DNS server that is configured to be
authoritative for the .homenet zone appropriate to the home authoritative for the .home.arpa zone appropriate to the home
network. One or more IP addresses for recursive DNS servers will network. One or more IP addresses for recursive DNS servers will
usually be supplied to the client through router advertisements usually be supplied to the client through router advertisements
or DHCP. If a host is configured to use a resolver other than or DHCP. If a host is configured to use a resolver other than
one that is authoritative for the appropriate .homenet zone, the one that is authoritative for the appropriate .home.arpa zone,
client may be unable to resolve, or may receive incorrect results the client may be unable to resolve, or may receive incorrect
for, names in sub domains of ".homenet". results for, names in sub domains of ".home.arpa".
4. Unless configured otherwise, recursive resolvers and DNS proxies 4. Unless configured otherwise, recursive resolvers and DNS proxies
MUST behave as described in Locally Served Zones ([RFC6303] MUST behave as described in Locally Served Zones ([RFC6303]
Section 3). Recursive resolvers that are part of a home network Section 3). Recursive resolvers that are part of a home network
MAY be configured manually or automatically (e.g., for auto- MAY be configured manually or automatically (e.g., for auto-
configuration purposes) to act differently, e.g., by querying configuration purposes) to act differently, e.g., by querying
another name server configured as authoritative for part or all another name server configured as authoritative for part or all
of the '.homenet' domain, or proxying the request through a of the '.home.arpa' domain, or proxying the request through a
different mechanism. different mechanism.
5. Only a DNS server that is authoritative for the root ('.') or is 5. Only a DNS server that is authoritative for the '.arpa' zone or
configured to be authoritative for '.homenet' or a subdomain of is configured to be authoritative for '.home.arpa' or a subdomain
'.homenet' will ever answer a query about '.homenet.' In both of of '.home.arpa' will ever answer a query about '.home.arpa.' In
these cases, the server should simply answer as configured: no both of these cases, the server should simply answer as
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 .homenet. authoritative for .home.arpa.
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' '.home.arpa' in the normal way to any person or entity.
MUST BE registered in perpetuity to IANA, and IANA MUST maintain '.home.arpa' MUST BE registered in perpetuity to IANA, and IANA
nameservers for the zone. 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 5, line 4 skipping to change at page 5, line 8
administrator MAY configure the announcement of a Domain-Name TLV administrator MAY configure the announcement of a Domain-Name TLV
(Section 10.6) for the network to use a different one. In case (Section 10.6) for the network to use a different one. In case
multiple are announced, the domain of the node with the greatest multiple are announced, the domain of the node with the greatest
node identifier takes precedence. node identifier takes precedence.
NEW: NEW:
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-
wide zone is appended to all single labels or unqualified zones in wide zone is appended to all single labels or unqualified zones in
order to qualify them. ".homenet" is the default; however, an order to qualify them. ".home.arpa" is the default; however, an
administrator MAY configure the announcement of a Domain-Name TLV administrator MAY configure the announcement of a Domain-Name TLV
(Section 10.6) for the network to use a different one. In case (Section 10.6) for the network to use a different one. In case
multiple are announced, the domain of the node with the greatest multiple are announced, the domain of the node with the greatest
node identifier takes precedence. node identifier takes precedence.
The '.homenet' special-use name does not require a special The '.home.arpa' special-use name does not require a special
resolution protocol. Names for which the rightmost non-terminal resolution protocol. Names for which the rightmost non-terminal
label is 'homenet' are resolved using the DNS protocol [RFC1035]. label is 'homenet' are resolved using the DNS protocol [RFC1035].
5. Security Considerations 5. Security Considerations
Although a DNS record returned as a response to a query ending with A DNS record that is returned as a response to a query ending with
'.homenet.' is expected to have local significance and be returned by '.home.arpa.' is expected to have local significance. It is expected
a server involved in name resolution for the home network the device to be returned by a server involved in name resolution for the home
is connected in, such response MUST NOT be considered more network the device is connected in. However, such response MUST NOT
trustworthy than would be a similar response for any other DNS query. be considered more trustworthy than would be a similar response for
any other DNS query.
Because '.homenet' is not globally scoped and cannot be secured using Because '.home.arpa' is not globally scoped and cannot be secured
DNSSEC based on the root domain's trust anchor, there is no way to using DNSSEC based on the root domain's trust anchor, there is no way
tell, using a standard DNS query, in which home network scope an to 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 In order to enable DNSSEC validation of a particular '.home.arpa', it
might make sense to configure a trust anchor for that homenet. How might make sense to configure a trust anchor for that homenet. How
this might be done is out of scope for this document. this might be done is out of scope for this document.
6. IANA Considerations 6. Delegation of 'home.arpa'
IANA is requested to record the top-level domain ".homenet" in the In order to be fully functional, there must be a delegation of
Special-Use Domain Names registry [SUDN]. 'home.arpa' in the '.arpa' zone. This delegation MUST NOT be signed,
MUST NOT include a DS record, and MUST point to one or more black
hole servers, for example BLACKHOLE-1.IANA.ORG and BLACKHOLE-
2.IANA.ORG. The reason that this delegation must not be signed is
that not signing the delegation breaks the DNSSEC chain of trust,
which prevents a validating stub resolver from rejecting names
published under 'home.arpa' on a homenet name server.
IANA is requested to arrange for an insecure delegation for 7. IANA Considerations
'.homenet' in the root zone. This delegation MUST NOT be signed, and
MUST point to some IANA-operated black hole servers, for example
BLACKHOLE-1.IANA.ORG and BLACKHOLE-2.IANA.ORG. Not signing the
delegation breaks the DNSSEC chain of trust, which prevents a
validating stub resolver from rejecting names on a local homenet.
This request is being made under the terms of the Memorandum of IANA is requested to record the domain name ".home.arpa" in the
Understanding [RFC2860] between IETF and ICANN; the IETF considers Special-Use Domain Names registry [SUDN].
the use of '.homenet' to be a "technical use" under the terms of the
MoU. The working group understands that there is no precedent for
such a request and that some process may have to be developed for
addressing it.
7. Acknowledgments 8. Acknowledgments
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
comments on the IANA considerations section.
8. References 9. References
8.1. Normative References 9.1. Normative References
[RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of [RFC2860] Carpenter, B., Baker, F., and M. Roberts, "Memorandum of
Understanding Concerning the Technical Work of the Understanding Concerning the Technical Work of the
Internet Assigned Numbers Authority", RFC 2860, Internet Assigned Numbers Authority", RFC 2860,
DOI 10.17487/RFC2860, June 2000, DOI 10.17487/RFC2860, June 2000,
<http://www.rfc-editor.org/info/rfc2860>. <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-
homenet-redact-02 (work in progress), January 2017. homenet-redact-03 (work in progress), March 2017.
8.2. Informative References 9.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,
<http://www.rfc-editor.org/info/rfc7368>. <http://www.rfc-editor.org/info/rfc7368>.
[RFC7788] Stenberg, M., Barth, S., and P. Pfister, "Home Networking [RFC7788] Stenberg, M., Barth, S., and P. Pfister, "Home Networking
Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April Control Protocol", RFC 7788, DOI 10.17487/RFC7788, April
2016, <http://www.rfc-editor.org/info/rfc7788>. 2016, <http://www.rfc-editor.org/info/rfc7788>.
[ICANN1] "New gTLD Collision Risk Mitigation", October 2013, [ICANN1] "New gTLD Collision Risk Mitigation", October 2013,
<https://www.icann.org/en/system/files/files/resolutions- <https://www.icann.org/en/system/files/files/new-gtld-
new-gtld-annex-1-07oct13-en.pdf>. collision-mitigation-05aug13-en.pdf>.
[ICANN2] "New gTLD Collision Occurence Management", October 2013, [ICANN2] "New gTLD Collision Occurence Management", October 2013,
<https://www.icann.org/en/system/files/files/resolutions- <https://www.icann.org/en/system/files/files/resolutions-
new-gtld-annex-1-07oct13-en.pdf>. new-gtld-annex-1-07oct13-en.pdf>.
[SUDN] "Special-Use Domain Names Registry", July 2012, [SUDN] "Special-Use Domain Names Registry", July 2012,
<http://www.iana.org/assignments/special-use-domain-names/ <http://www.iana.org/assignments/special-use-domain-names/
special-use-domain-names.xhtml>. special-use-domain-names.xhtml>.
Authors' Addresses Authors' Addresses
 End of changes. 38 change blocks. 
87 lines changed or deleted 89 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/