draft-ietf-homenet-dot-08.txt   draft-ietf-homenet-dot-09.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: January 4, 2018 July 3, 2017 Expires: January 4, 2018 July 3, 2017
Special Use Domain '.home.arpa' Special Use Domain '.home.arpa'
draft-ietf-homenet-dot-08 draft-ietf-homenet-dot-09
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 domain as a special-use domain '.home.arpa.', and designates this domain as a special-use domain
name. 'home.arpa' is designated for non-unique use in residential name. 'home.arpa' is designated for non-unique use in residential
home networks. Home Networking Control Protocol (HNCP) is updated to home networks. Home Networking Control Protocol (HNCP) is updated to
use the '.home.arpa' domain instead of '.home'. use the '.home.arpa' domain instead of '.home'.
skipping to change at page 2, line 15 skipping to change at page 2, line 15
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. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. General Guidance . . . . . . . . . . . . . . . . . . . . . . 3 3. General Guidance . . . . . . . . . . . . . . . . . . . . . . 3
4. Domain Name Reservation Considerations . . . . . . . . . . . 3 4. Domain Name Reservation Considerations . . . . . . . . . . . 3
5. Updates to Home Networking Control Protocol . . . . . . . . . 5 5. Updates to Home Networking Control Protocol . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Delegation of 'home.arpa' . . . . . . . . . . . . . . . . . . 6 7. Delegation of 'home.arpa' . . . . . . . . . . . . . . . . . . 7
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 7
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 7
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
10.1. Normative References . . . . . . . . . . . . . . . . . . 7 10.1. Normative References . . . . . . . . . . . . . . . . . . 7
10.2. Informative References . . . . . . . . . . . . . . . . . 8 10.2. Informative References . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction 1. Introduction
Users and devices within a home network (hereafter "homenet") require Users and devices within a home network (hereafter "homenet") require
skipping to change at page 4, line 39 skipping to change at page 4, line 39
for that particular homenet's instance of the domain for that particular homenet's instance of the domain
'.home.arpa', and, when so configured, MUST NOT attempt to look '.home.arpa', and, when so configured, MUST NOT attempt to look
up a delegation for '.home.arpa' in the public DNS. Of course, up a delegation for '.home.arpa' in the public DNS. Of course,
from an implementation standpoint it may be that a hybrid name from an implementation standpoint it may be that a hybrid name
server acts as a caching resolver or DNS proxy for non-local server acts as a caching resolver or DNS proxy for non-local
domains and as an authoritative server for '.home.arpa' and other domains and as an authoritative server for '.home.arpa' and other
locally served zones, responding directly to queries for locally served zones, responding directly to queries for
subdomains of '.home.arpa' rather than using a delegation. subdomains of '.home.arpa' rather than using a delegation.
5. No special processing of '.home.arpa' is required for 5. No special processing of '.home.arpa' is required for
authoritative DNS server implementations. However, if an authoritative DNS server implementations. However, it is
authoritative DNS server does any sort of sanity checking of the possible that an authoritative DNS server might attempt to
delegation for zones for which it is configured to be validate the delegation for a zone before answering
authoritative, it must be possible to disable this sanity check authoritatively for that zone. In this situation, it would find
for '.home.arpa' or ignore the results. an invalid delegation, and would not answer authoritatively. A
server that implements this sort of check MUST be configurable so
that either it does not do this check for the 'home.arpa' domain,
or it ignores the results of the check.
6. DNS server operators MAY configure an authoritative server for 6. DNS server operators MAY configure an authoritative server for
'.home.arpa' for use in homenets and other home networks. The '.home.arpa' for use in homenets and other home networks. The
operator for the DNS servers authoritative for '.home.arpa' in operator for the DNS servers authoritative for '.home.arpa' in
the global DNS will configure any such servers as described in the global DNS will configure any such servers as described in
Section 7. Section 7.
7. 'home.arpa' is a subdomain of the 'arpa' top-level domain, which 7. 'home.arpa' is a subdomain of the 'arpa' top-level domain, which
is operated by IANA under the authority of the Internet is operated by IANA under the authority of the Internet
Architecture Board according to the rules established in Architecture Board according to the rules established in
 End of changes. 3 change blocks. 
7 lines changed or deleted 10 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/