--- 1/draft-ietf-dnssd-hybrid-06.txt 2017-09-13 17:13:12.313980088 -0700 +++ 2/draft-ietf-dnssd-hybrid-07.txt 2017-09-13 17:13:12.377981620 -0700 @@ -1,18 +1,18 @@ Internet Engineering Task Force S. Cheshire Internet-Draft Apple Inc. -Intended status: Standards Track March 13, 2017 -Expires: September 14, 2017 +Intended status: Standards Track September 13, 2017 +Expires: March 17, 2018 Discovery Proxy for Multicast DNS-Based Service Discovery - draft-ietf-dnssd-hybrid-06 + draft-ietf-dnssd-hybrid-07 Abstract This document specifies a mechanism that uses Multicast DNS to automatically populate the wide-area unicast Domain Name System namespace with records describing devices and services found on the local link. Status of This Memo @@ -22,21 +22,21 @@ Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." - This Internet-Draft will expire on September 14, 2017. + This Internet-Draft will expire on March 17, 2018. Copyright Notice Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents @@ -126,21 +126,21 @@ expensive multicast traffic, but limits the discoverability of services. Using a very large local link with thousands of hosts enables better service discovery, but at the cost of larger amounts of multicast traffic. Performing DNS-Based Service Discovery using purely Unicast DNS is more efficient and doesn't require excessively large multicast domains, but requires that the relevant data be available in the Unicast DNS namespace. The Unicast DNS namespace in question could fall within a traditionally assigned globally unique domain name, or - could use a private local unicast domain name such as ".home" + could use a private local unicast domain name such as ".home.arpa" [HOME].) In the DNS-SD specification [RFC6763], Section 10 ("Populating the DNS with Information") discusses various possible ways that a service's PTR, SRV, TXT and address records can make their way into the Unicast DNS namespace, including manual zone file configuration [RFC1034] [RFC1035], DNS Update [RFC2136] [RFC3007] and proxies of various kinds. Making the relevant data available in the Unicast DNS namespace by @@ -1169,27 +1169,27 @@ Interchange", RFC 5198, DOI 10.17487/RFC5198, March 2008, . [RFC6762] Cheshire, S. and M. Krochmal, "Multicast DNS", RFC 6762, December 2012. [RFC6763] Cheshire, S. and M. Krochmal, "DNS-Based Service Discovery", RFC 6763, December 2012. [PUSH] Pusateri, T. and S. Cheshire, "DNS Push Notifications", - draft-ietf-dnssd-push-09 (work in progress), October 2016. + draft-ietf-dnssd-push-12 (work in progress), July 2017. 13.2. Informative References - [HOME] Cheshire, S., "Special Use Top Level Domain 'home'", - draft-cheshire-homenet-dot-home (work in progress), - November 2015. + [HOME] Pfister, P. and T. Lemon, "Special Use Domain + '.home.arpa'", draft-ietf-homenet-dot-07 (work in + progress), June 2017. [IPR2119] "Apple Inc.'s Statement about IPR related to Hybrid Unicast/Multicast DNS-Based Service Discovery", . [ohp] "Discovery Proxy (Hybrid Proxy) implementation for OpenWrt", . [LLQ] Sekar, K., "DNS Long-Lived Queries", draft-sekar-dns- llq-01 (work in progress), August 2006.