draft-ietf-homenet-hybrid-proxy-zeroconf-00.txt   draft-ietf-homenet-hybrid-proxy-zeroconf-01.txt 
Homenet Working Group M. Stenberg Homenet Working Group M. Stenberg
Internet-Draft Internet-Draft Independent
Intended status: Standards Track March 5, 2015 Intended status: Standards Track September 2, 2015
Expires: September 6, 2015 Expires: March 5, 2016
Auto-Configuration of a Network of Hybrid Unicast/Multicast DNS-Based Auto-Configuration of a Network of Hybrid Unicast/Multicast DNS-Based
Service Discovery Proxy Nodes Service Discovery Proxy Nodes
draft-ietf-homenet-hybrid-proxy-zeroconf-00 draft-ietf-homenet-hybrid-proxy-zeroconf-01
Abstract Abstract
This document describes how a proxy functioning between Unicast DNS- This document describes how a proxy functioning between Unicast DNS-
Based Service Discovery and Multicast DNS can be automatically Based Service Discovery and Multicast DNS can be automatically
configured using an arbitrary network-level state sharing mechanism. configured using an arbitrary network-level state sharing mechanism.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 September 6, 2015. This Internet-Draft will expire on March 5, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 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 2, line 17 skipping to change at page 2, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements language . . . . . . . . . . . . . . . . . . . . 3
3. Hybrid proxy - what to configure . . . . . . . . . . . . . . 3 3. Hybrid proxy - what to configure . . . . . . . . . . . . . . 3
3.1. Conflict resolution within network . . . . . . . . . . . 4 3.1. Conflict resolution within network . . . . . . . . . . . 4
3.2. Per-link DNS-SD forward zone names . . . . . . . . . . . 4 3.2. Per-link DNS-SD forward zone names . . . . . . . . . . . 4
3.3. Reasonable defaults . . . . . . . . . . . . . . . . . . . 5 3.3. Reasonable defaults . . . . . . . . . . . . . . . . . . . 5
3.3.1. Network-wide unique link name (scheme 1) . . . . . . 5 3.3.1. Network-wide unique link name (scheme 1) . . . . . . 5
3.3.2. Node name (scheme 2) . . . . . . . . . . . . . . . . 5 3.3.2. Node name (scheme 2) . . . . . . . . . . . . . . . . 5
3.3.3. Link name (scheme 2) . . . . . . . . . . . . . . . . 5 3.3.3. Link name (scheme 2) . . . . . . . . . . . . . . . . 5
4. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4. TLVs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4.1. DNS Delegated Zone TLV . . . . . . . . . . . . . . . . . 5 4.1. DNS Delegated Zone TLV . . . . . . . . . . . . . . . . . 6
4.2. Domain Name TLV . . . . . . . . . . . . . . . . . . . . . 7 4.2. Domain Name TLV . . . . . . . . . . . . . . . . . . . . . 7
4.3. Node Name TLV . . . . . . . . . . . . . . . . . . . . . . 7 4.3. Node Name TLV . . . . . . . . . . . . . . . . . . . . . . 7
5. Desirable behavior . . . . . . . . . . . . . . . . . . . . . 7 5. Desirable behavior . . . . . . . . . . . . . . . . . . . . . 7
5.1. DNS search path in DHCP requests . . . . . . . . . . . . 7 5.1. DNS search path in DHCP requests . . . . . . . . . . . . 8
5.2. Hybrid proxy . . . . . . . . . . . . . . . . . . . . . . 8 5.2. Hybrid proxy . . . . . . . . . . . . . . . . . . . . . . 8
5.3. Hybrid proxy network zeroconf daemon . . . . . . . . . . 8 5.3. Hybrid proxy network zeroconf daemon . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative references . . . . . . . . . . . . . . . . . . 9 8.1. Normative references . . . . . . . . . . . . . . . . . . 9
8.2. Informative references . . . . . . . . . . . . . . . . . 9 8.2. Informative references . . . . . . . . . . . . . . . . . 9
Appendix A. Example configuration . . . . . . . . . . . . . . . 10 Appendix A. Example configuration . . . . . . . . . . . . . . . 10
A.1. Used topology . . . . . . . . . . . . . . . . . . . . . . 10 A.1. Used topology . . . . . . . . . . . . . . . . . . . . . . 10
A.2. Zero-configuration steps . . . . . . . . . . . . . . . . 10 A.2. Zero-configuration steps . . . . . . . . . . . . . . . . 10
A.3. TLV state . . . . . . . . . . . . . . . . . . . . . . . . 11 A.3. TLV state . . . . . . . . . . . . . . . . . . . . . . . . 11
A.4. DNS zone . . . . . . . . . . . . . . . . . . . . . . . . 12 A.4. DNS zone . . . . . . . . . . . . . . . . . . . . . . . . 12
A.5. Interaction with hosts . . . . . . . . . . . . . . . . . 12 A.5. Interaction with hosts . . . . . . . . . . . . . . . . . 13
Appendix B. Implementation . . . . . . . . . . . . . . . . . . . 12 Appendix B. Implementation . . . . . . . . . . . . . . . . . . . 13
Appendix C. Why not just proxy Multicast DNS? . . . . . . . . . 13 Appendix C. Why not just proxy Multicast DNS? . . . . . . . . . 13
C.1. General problems . . . . . . . . . . . . . . . . . . . . 13 C.1. General problems . . . . . . . . . . . . . . . . . . . . 14
C.2. Stateless proxying problems . . . . . . . . . . . . . . . 14 C.2. Stateless proxying problems . . . . . . . . . . . . . . . 14
C.3. Stateful proxying problems . . . . . . . . . . . . . . . 14 C.3. Stateful proxying problems . . . . . . . . . . . . . . . 15
Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 14 Appendix D. Acknowledgements . . . . . . . . . . . . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 15 Appendix E. Changelog [RFC Editor: please remove] . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 16
1. Introduction 1. Introduction
Section 3 ("Hybrid Proxy Operation") of [I-D.cheshire-dnssd-hybrid] Section 3 ("Hybrid Proxy Operation") of [I-D.ietf-dnssd-hybrid]
describes how to translate queries from Unicast DNS-Based Service describes how to translate queries from Unicast DNS-Based Service
Discovery described in [RFC6763] to Multicast DNS described in Discovery described in [RFC6763] to Multicast DNS described in
[RFC6762], and how to filter the responses and translate them back to [RFC6762], and how to filter the responses and translate them back to
unicast DNS. unicast DNS.
This document describes what sort of configuration the participating This document describes what sort of configuration the participating
hybrid proxy servers require, as well as how it can be provided using hybrid proxy servers require, as well as how it can be provided using
any network-wide state sharing mechanism such as link-state routing any network-wide state sharing mechanism such as link-state routing
protocol or Home Networking Control Protocol [I-D.ietf-homenet-hncp]. protocol or Home Networking Control Protocol [I-D.ietf-homenet-hncp].
The document also describes a naming scheme which does not even need The document also describes a naming scheme which does not even need
skipping to change at page 3, line 34 skipping to change at page 3, line 37
2. Requirements language 2. Requirements language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
3. Hybrid proxy - what to configure 3. Hybrid proxy - what to configure
Beyond the low-level translation mechanism between unicast and Beyond the low-level translation mechanism between unicast and
multicast service discovery, the hybrid proxy draft multicast service discovery, the hybrid proxy draft
[I-D.cheshire-dnssd-hybrid] describes just that there have to be NS [I-D.ietf-dnssd-hybrid] describes just that there have to be NS
records pointing to hybrid proxy responsible for each link within the records pointing to hybrid proxy responsible for each link within the
covered network. covered network.
In zero-configuration case, choosing the links to be covered is also In zero-configuration case, choosing the links to be covered is also
non-trivial choice; we can use the border discovery functionality (if non-trivial choice; we can use the border discovery functionality (if
available) to determine internal and external links. Or we can use available) to determine internal and external links. Or we can use
some other protocol's presence (or lack of it) on a link to determine some other protocol's presence (or lack of it) on a link to determine
internal links within the covered network, and some other signs internal links within the covered network, and some other signs
(depending on the deployment) such as DHCPv6 Prefix Delegation (as (depending on the deployment) such as DHCPv6 Prefix Delegation (as
described in [RFC3633]) to determine external links that should not described in [RFC3633]) to determine external links that should not
skipping to change at page 9, line 13 skipping to change at page 9, line 17
share fate with border discovery (and also security issues if any). share fate with border discovery (and also security issues if any).
7. IANA Considerations 7. IANA Considerations
This document has no actions for IANA. This document has no actions for IANA.
8. References 8. References
8.1. Normative references 8.1. Normative references
[I-D.cheshire-dnssd-hybrid] [I-D.ietf-dnssd-hybrid]
Cheshire, S., "Hybrid Unicast/Multicast DNS-Based Service Cheshire, S., "Hybrid Unicast/Multicast DNS-Based Service
Discovery", draft-cheshire-dnssd-hybrid-01 (work in Discovery", draft-ietf-dnssd-hybrid-00 (work in progress),
progress), January 2014. November 2014.
[RFC1035] Mockapetris, P., "Domain names - implementation and [RFC1035] Mockapetris, P., "Domain names - implementation and
specification", STD 13, RFC 1035, November 1987. specification", STD 13, RFC 1035, DOI 10.17487/RFC1035,
November 1987, <http://www.rfc-editor.org/info/rfc1035>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/
RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC6762] Cheshire, S. and M. Krochmal, "Multicast DNS", RFC 6762, [RFC6762] Cheshire, S. and M. Krochmal, "Multicast DNS", RFC 6762,
February 2013. DOI 10.17487/RFC6762, February 2013,
<http://www.rfc-editor.org/info/rfc6762>.
[RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service [RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service
Discovery", RFC 6763, February 2013. Discovery", RFC 6763, DOI 10.17487/RFC6763, February 2013,
<http://www.rfc-editor.org/info/rfc6763>.
8.2. Informative references 8.2. Informative references
[I-D.ietf-homenet-hncp] [I-D.ietf-homenet-hncp]
Stenberg, M., Barth, S., and P. Pfister, "Home Networking Stenberg, M., Barth, S., and P. Pfister, "Home Networking
Control Protocol", draft-ietf-homenet-hncp-03 (work in Control Protocol", draft-ietf-homenet-hncp-09 (work in
progress), January 2015. progress), August 2015.
[RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
Host Configuration Protocol (DHCP) version 6", RFC 3633, Host Configuration Protocol (DHCP) version 6", RFC 3633,
December 2003. DOI 10.17487/RFC3633, December 2003,
<http://www.rfc-editor.org/info/rfc3633>.
[RFC3646] Droms, R., "DNS Configuration options for Dynamic Host [RFC3646] Droms, R., Ed., "DNS Configuration options for Dynamic
Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3646,
December 2003. DOI 10.17487/RFC3646, December 2003,
<http://www.rfc-editor.org/info/rfc3646>.
8.3. URIs 8.3. URIs
[1] https://github.com/sbyx/hnetd/ [1] https://github.com/sbyx/hnetd/
Appendix A. Example configuration Appendix A. Example configuration
A.1. Used topology A.1. Used topology
Let's assume home network that looks like this: Let's assume home network that looks like this:
skipping to change at page 15, line 5 skipping to change at page 15, line 42
Appendix D. Acknowledgements Appendix D. Acknowledgements
Thanks to Stuart Cheshire for the original hybrid proxy draft and Thanks to Stuart Cheshire for the original hybrid proxy draft and
interesting discussion in Orlando, where I was finally convinced that interesting discussion in Orlando, where I was finally convinced that
stateful Multicast DNS proxying is a bad idea. stateful Multicast DNS proxying is a bad idea.
Also thanks to Mark Baugher, Ole Troan, Shwetha Bhandari and Gert Also thanks to Mark Baugher, Ole Troan, Shwetha Bhandari and Gert
Doering for review comments. Doering for review comments.
Appendix E. Changelog [RFC Editor: please remove]
draft-ietf-homenet-hybrid-proxy-zeroconf-01:
o Refreshed the draft while waiting on progress of draft-ietf-dnssd-
hybrid.
Author's Address Author's Address
Markus Stenberg Markus Stenberg
Independent
Helsinki 00930 Helsinki 00930
Finland Finland
Email: markus.stenberg@iki.fi Email: markus.stenberg@iki.fi
 End of changes. 21 change blocks. 
28 lines changed or deleted 44 lines changed or added

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