draft-ietf-homenet-dot-02.txt   draft-ietf-homenet-dot-03.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: August 3, 2017 January 30, 2017 Expires: September 14, 2017 March 13, 2017
Special Use Top Level Domain '.homenet' Special Use Top Level Domain '.homenet'
draft-ietf-homenet-dot-02 draft-ietf-homenet-dot-03
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 August 3, 2017. This Internet-Draft will expire on September 14, 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 4, line 28 skipping to change at page 4, line 28
configured to be authoritative for '.homenet' or a subdomain of configured to be authoritative for '.homenet' or a subdomain of
'.homenet' will ever answer a query about '.homenet.' In both of '.homenet' will ever answer a query about '.homenet.' In both of
these cases, the server should simply answer as configured: no these cases, the server should simply answer as configured: no
special handling is required. 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 .homenet.
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' '.homenet' in the normal way to any person or entity. '.homenet'
is registered in perpetuity to IANA: MUST BE registered in perpetuity to IANA, and IANA MUST maintain
nameservers for the zone.
Domain Name: HOMENET
Registrar: RESERVED-INTERNET ASSIGNED NUMBERS AUTHORITY
Whois Server: whois.iana.org
Referral URL: http://res-dom.iana.org
Name Server: A.IANA-SERVERS.NET
Name Server: B.IANA-SERVERS.NET
Status: clientDeleteProhibited
Status: clientTransferProhibited
Status: clientUpdateProhibited
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 49 skipping to change at page 5, line 40
In order to enable DNSSEC validation of a particular '.homenet', it In order to enable DNSSEC validation of a particular '.homenet', 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. IANA Considerations
IANA is requested to record the top-level domain ".homenet" in the IANA is requested to record the top-level domain ".homenet" in the
Special-Use Domain Names registry [SUDN]. Special-Use Domain Names registry [SUDN].
IANA is requested to set up insecure delegation for '.homenet' in the IANA is requested to arrange for an insecure delegation for
root zone pointing to the AS112 service [RFC7535], to break the '.homenet' in the root zone. This delegation MUST NOT be signed, and
DNSSEC chain of trust. 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
Understanding [RFC2860] between IETF and ICANN; the IETF considers
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 7. 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.
8. References 8. References
8.1. Normative References 8.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>.
[RFC7535] Abley, J., Dickson, B., Kumari, W., and G. Michaelson,
"AS112 Redirection Using DNAME", RFC 7535,
DOI 10.17487/RFC7535, May 2015,
<http://www.rfc-editor.org/info/rfc7535>.
[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-01 (work in progress), November 2016. homenet-redact-02 (work in progress), January 2017.
8.2. Informative References 8.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,
 End of changes. 8 change blocks. 
23 lines changed or deleted 25 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/