draft-ietf-homenet-dot-01.txt   draft-ietf-homenet-dot-02.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: July 23, 2017 January 19, 2017 Expires: August 3, 2017 January 30, 2017
Special Use Top Level Domain '.homenet' Special Use Top Level Domain '.homenet'
draft-ietf-homenet-dot-01 draft-ietf-homenet-dot-02
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 July 23, 2017. This Internet-Draft will expire on August 3, 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 3, line 48 skipping to change at page 3, line 48
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 that 3. Name resolution APIs and libraries MUST NOT recognize names that
end in '.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 names to a recursive DNS server that is configured to be
recursive resolver other than the resolver(s) offered by the home authoritative for the .homenet zone appropriate to the home
network will result in failure to correctly resolve queries for network. One or more IP addresses for recursive DNS servers will
subdomains of '.homenet'. If a host is configured to always use usually be supplied to the client through router advertisements
a recursive resolver other than the one offered by the local or DHCP. If a host is configured to use a resolver other than
network, it will be unable to resolve queries that are subdomains one that is authoritative for the appropriate .homenet zone, the
of '.homenet'. client may be unable to resolve, or may receive incorrect results
for, names in sub domains of ".homenet".
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 '.homenet' domain, or proxying the request through a
different mechanism. different mechanism.
 End of changes. 4 change blocks. 
10 lines changed or deleted 11 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/