Special-Use Domain 'home.arpa.'
RFC 8375
| Document | Type |
RFC - Proposed Standard
(May 2018; No errata)
Updates RFC 7788
|
|
|---|---|---|---|
| Last updated | 2018-05-17 | ||
| Replaces | draft-pfister-homenet-dot | ||
| Stream | IETF | ||
| Formats | plain text pdf html bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Ray Bellis | ||
| Shepherd write-up | Show (last changed 2017-07-25) | ||
| IESG | IESG state | RFC 8375 (Proposed Standard) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Terry Manderson | ||
| Send notices to | Ray Bellis <ray@bellis.me.uk> | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) P. Pfister
Request for Comments: 8375 Cisco Systems
Updates: 7788 T. Lemon
Category: Standards Track Nibbhaya Consulting
ISSN: 2070-1721 May 2018
Special-Use Domain 'home.arpa.'
Abstract
This document specifies the behavior that is expected from the Domain
Name System with regard to DNS queries for names ending with
'.home.arpa.' and designates this domain as a special-use domain
name. 'home.arpa.' is designated for non-unique use in residential
home networks. The Home Networking Control Protocol (HNCP) is
updated to use the 'home.arpa.' domain instead of '.home'.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8375.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Pfister & Lemon Standards Track [Page 1]
RFC 8375 home.arpa. May 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 4
3. General Guidance . . . . . . . . . . . . . . . . . . . . . . 4
4. Domain Name Reservation Considerations . . . . . . . . . . . 4
5. Updates to Home Networking Control Protocol . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 7
6.1. Local Significance . . . . . . . . . . . . . . . . . . . 7
6.2. Insecure Delegation . . . . . . . . . . . . . . . . . . . 8
6.3. Bypassing Manually Configured Resolvers . . . . . . . . . 9
7. Delegation of 'home.arpa.' . . . . . . . . . . . . . . . . . 9
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 10
9.1. Normative References . . . . . . . . . . . . . . . . . . 10
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
Pfister & Lemon Standards Track [Page 2]
RFC 8375 home.arpa. May 2018
1. Introduction
Users and devices within a home network (hereafter referred to as
"homenet") require devices and services to be identified by names
that are unique within the boundaries of the homenet [RFC7368]. The
naming mechanism needs to function without configuration from the
user. While it may be possible for a name to be delegated by an ISP,
homenets must also function in the absence of such a delegation.
This document reserves the name 'home.arpa.' to serve as the default
name for this purpose, with a scope limited to each individual
homenet.
This document corrects an error in [RFC7788] by replacing '.home'
with 'home.arpa.' as the default domain name for homenets. '.home'
was selected as the most user-friendly option; however, there are
existing uses of '.home' that may be in conflict with this use.
Evidence indicates that '.home' queries frequently leak out and reach
the root name servers [ICANN1] [ICANN2].
In addition, for compatibility with DNSSEC (see Section 6), it's
necessary that an insecure delegation (see Section 4.3 of [RFC4035])
be present for the name. There is an existing process for allocating
names under '.arpa.' [RFC3172]. No such process is available for
requesting a similar delegation in the root at the request of the
IETF, which does not administer that zone. As a result, all
Show full document text