draft-ietf-homenet-simple-naming-01.txt   draft-ietf-homenet-simple-naming-02.txt 
Network Working Group T. Lemon Network Working Group T. Lemon
Internet-Draft Nibbhaya Consulting Internet-Draft Nibbhaya Consulting
Intended status: Informational D. Migault Intended status: Informational D. Migault
Expires: September 6, 2018 Ericsson Expires: January 3, 2019 Ericsson
S. Cheshire S. Cheshire
Apple Inc. Apple Inc.
March 5, 2018 July 2, 2018
Simple Homenet Naming and Service Discovery Architecture Simple Homenet Naming and Service Discovery Architecture
draft-ietf-homenet-simple-naming-01 draft-ietf-homenet-simple-naming-02
Abstract Abstract
This document describes how names are published and resolved on This document describes how names are published and resolved on
homenets, and how hosts are configured to use these names to discover homenets, and how hosts are configured to use these names to discover
services on homenets. It presents the complete architecture, and services on homenets. It presents the complete architecture, and
describes a simple subset of that architecture that can be used in describes a simple subset of that architecture that can be used in
low-cost homenet routers. low-cost homenet routers.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 37
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 6, 2018. This Internet-Draft will expire on January 3, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 20 skipping to change at page 2, line 20
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Requirements . . . . . . . . . . . . . . . . . . . . . . . . 3
2.1. Managed LAN versus Homenet . . . . . . . . . . . . . . . 4 2.1. Managed LAN versus Homenet . . . . . . . . . . . . . . . 4
2.2. Homenet-specific considerations . . . . . . . . . . . . . 4 2.2. Homenet-specific considerations . . . . . . . . . . . . . 4
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
5. Authority . . . . . . . . . . . . . . . . . . . . . . . . . . 6 5. Authority . . . . . . . . . . . . . . . . . . . . . . . . . . 6
6. Resolution . . . . . . . . . . . . . . . . . . . . . . . . . 7 6. Resolution . . . . . . . . . . . . . . . . . . . . . . . . . 7
7. Publication . . . . . . . . . . . . . . . . . . . . . . . . . 7 7. Publication . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. DNS Service Discovery Registration Protocol . . . . . . . 7 7.1. DNS Service Discovery Registration Protocol . . . . . . . 7
7.2. Configuring Service Discovery . . . . . . . . . . . . . . 7 7.2. Configuring Service Discovery . . . . . . . . . . . . . . 8
8. Host Configurtion . . . . . . . . . . . . . . . . . . . . . . 10 8. Host Configurtion . . . . . . . . . . . . . . . . . . . . . . 10
9. Globally Unique Name . . . . . . . . . . . . . . . . . . . . 10 9. Globally Unique Name . . . . . . . . . . . . . . . . . . . . 10
10. DNSSEC Validation . . . . . . . . . . . . . . . . . . . . . . 10 10. DNSSEC Validation . . . . . . . . . . . . . . . . . . . . . . 10
11. Support for Multiple Provisioning Domains . . . . . . . . . . 11 11. Support for Multiple Provisioning Domains . . . . . . . . . . 11
12. Using the Local Namespace While Away From Home . . . . . . . 11 12. Using the Local Namespace While Away From Home . . . . . . . 11
13. Management Considerations . . . . . . . . . . . . . . . . . . 11 13. Management Considerations . . . . . . . . . . . . . . . . . . 11
14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12 14. Privacy Considerations . . . . . . . . . . . . . . . . . . . 12
15. Security Considerations . . . . . . . . . . . . . . . . . . . 12 15. Security Considerations . . . . . . . . . . . . . . . . . . . 12
16. IANA considerations . . . . . . . . . . . . . . . . . . . . . 12 16. IANA considerations . . . . . . . . . . . . . . . . . . . . . 12
17. Normative References . . . . . . . . . . . . . . . . . . . . 12 17. Normative References . . . . . . . . . . . . . . . . . . . . 12
skipping to change at page 3, line 23 skipping to change at page 3, line 23
are discussed in this document, but explained in more detail in the are discussed in this document, but explained in more detail in the
Advanced Homenet Naming Architecture document, which is to follow. Advanced Homenet Naming Architecture document, which is to follow.
2. Requirements 2. Requirements
Name service on a local area network (LAN) requires the following: Name service on a local area network (LAN) requires the following:
o Name: a forward domain under which information about local o Name: a forward domain under which information about local
services will be published services will be published
o Authority: a name server that is authoritative for at least a o Authority: a name server that is authoritative for at least one
forward and one or two reverse domains that are applicable to that forward domain and one or two reverse domains that are applicable
network to that network and is capable of signing and publishing the zones
using DNSSEC
o Resolution: a full-service caching DNS resolver o Resolution: a full-service caching DNS resolver that fully
supports EDNS(0) and queries with the DO bit set
o Publication: a mechanism that o Publication: a mechanism that
* allows services on the LAN to publish information about the * allows services on the LAN to publish information about the
services they provide services they provide
* allows services to publish information on how to reach them * allows services to publish information on how to reach them
* manages the lifetime of such information, so that it persists * manages the lifetime of such information, so that it persists
long enough to prevent spoofing, but protects end users from long enough to prevent spoofing, but protects end users from
skipping to change at page 4, line 7 skipping to change at page 4, line 7
* caching resolver information to hosts on the LAN * caching resolver information to hosts on the LAN
* information about how services on the LAN can publish * information about how services on the LAN can publish
information information
o Trust: some basis for trusting the information that is provided by o Trust: some basis for trusting the information that is provided by
the service discovery system the service discovery system
2.1. Managed LAN versus Homenet 2.1. Managed LAN versus Homenet
A managed network is one that has a (human) manager, or operator.
The operator has authority over the network, and the authority to
publish names in a forward DNS tree, and reverse names in the reverse
tree. The operator has the authority to sign the respective trees
with DNSSEC, and acquire TLS certificates for hosts/servers within
the network.
On a managed LAN, many of these services can be provided by On a managed LAN, many of these services can be provided by
operators. When a new printer is added to the network, it can be operators. When a new printer is added to the network, it can be
added to the service discovery system (the authoritative server) added to the service discovery system (the authoritative server)
manually. When a printer is taken out of service, it can be removed. manually. When a printer is taken out of service, it can be removed.
In this scenario, the role of "publisher" is filled by the network In this scenario, the role of "publisher" is filled by the network
operator. operator.
In many managed LANs, establishment of trust for service discovery is In many managed LANs, establishment of trust for service discovery is
simply on the basis of a belief that the local resolver will give a simply on the basis of a belief that the local resolver will give a
correct answer. Once the service has been discovered and chosen, correct answer. Once the service has been discovered and chosen,
skipping to change at page 13, line 37 skipping to change at page 13, line 37
[9] Anipko, D., Ed., "Multiple Provisioning Domain [9] Anipko, D., Ed., "Multiple Provisioning Domain
Architecture", RFC 7556, DOI 10.17487/RFC7556, June 2015, Architecture", RFC 7556, DOI 10.17487/RFC7556, June 2015,
<https://www.rfc-editor.org/info/rfc7556>. <https://www.rfc-editor.org/info/rfc7556>.
[10] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, [10] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli,
"IPv6 Router Advertisement Options for DNS Configuration", "IPv6 Router Advertisement Options for DNS Configuration",
RFC 8106, DOI 10.17487/RFC8106, March 2017, RFC 8106, DOI 10.17487/RFC8106, March 2017,
<https://www.rfc-editor.org/info/rfc8106>. <https://www.rfc-editor.org/info/rfc8106>.
[11] Cheshire, S., "Discovery Proxy for Multicast DNS-Based [11] Cheshire, S., "Discovery Proxy for Multicast DNS-Based
Service Discovery", draft-ietf-dnssd-hybrid-07 (work in Service Discovery", draft-ietf-dnssd-hybrid-08 (work in
progress), September 2017. progress), March 2018.
[12] Cheshire, S. and T. Lemon, "Multicast DNS Discovery [12] Cheshire, S. and T. Lemon, "Multicast DNS Discovery
Relay", draft-sctl-dnssd-mdns-relay-02 (work in progress), Relay", draft-sctl-dnssd-mdns-relay-04 (work in progress),
November 2017. March 2018.
[13] Cheshire, S. and T. Lemon, "Service Registration Protocol [13] Cheshire, S. and T. Lemon, "Service Registration Protocol
for DNS-Based Service Discovery", draft-sctl-service- for DNS-Based Service Discovery", draft-sctl-service-
registration-00 (work in progress), July 2017. registration-00 (work in progress), July 2017.
[14] Korhonen, J., Krishnan, S., and S. Gundavelli, "Support [14] Korhonen, J., Krishnan, S., and S. Gundavelli, "Support
for multiple provisioning domains in IPv6 Neighbor for multiple provisioning domains in IPv6 Neighbor
Discovery Protocol", draft-ietf-mif-mpvd-ndp-support-03 Discovery Protocol", draft-ietf-mif-mpvd-ndp-support-03
(work in progress), February 2016. (work in progress), February 2016.
[15] Popov, A., Nystrom, M., Balfanz, D., Langley, A., Harper, [15] Popov, A., Nystrom, M., Balfanz, D., Langley, A., Harper,
N., and J. Hodges, "Token Binding over HTTP", draft-ietf- N., and J. Hodges, "Token Binding over HTTP", draft-ietf-
tokbind-https-12 (work in progress), January 2018. tokbind-https-18 (work in progress), June 2018.
[16] Pfister, P. and T. Lemon, "Special Use Domain [16] Pfister, P. and T. Lemon, "Special Use Domain
'home.arpa.'", draft-ietf-homenet-dot-14 (work in 'home.arpa.'", draft-ietf-homenet-dot-14 (work in
progress), September 2017. progress), September 2017.
[17] Cheshire, S. and T. Lemon, "Service Discovery Broker", [17] Cheshire, S. and T. Lemon, "Service Discovery Broker",
draft-sctl-discovery-broker-00 (work in progress), July draft-sctl-discovery-broker-00 (work in progress), July
2017. 2017.
Appendix A. Existing solutions Appendix A. Existing solutions
 End of changes. 11 change blocks. 
14 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/