Advertising Proxy for DNS-SD Service Registration Protocol
draft-sctl-advertising-proxy-00

Document Type Active Internet-Draft (individual)
Last updated 2020-07-13
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
DNSSD                                                        S. Cheshire
Internet-Draft                                                  T. Lemon
Intended status: Standards Track                              Apple Inc.
Expires: 14 January 2021                                    13 July 2020

       Advertising Proxy for DNS-SD Service Registration Protocol
                    draft-sctl-advertising-proxy-00

Abstract

   An Advertising Proxy allows a device that accepts service registra-
   tions using Service Registration Protocol (SRP) to make those regis-
   trations visible to legacy clients that only implement Multicast DNS.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 https://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 14 January 2021.

Copyright Notice

   Copyright (c) 2020 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 (https://trustee.ietf.org/
   license-info) in effect on the date of publication of this document.
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.  Code Components
   extracted from this document must include Simplified BSD License text
   as described in Section 4.e of the Trust Legal Provisions and are
   provided without warranty as described in the Simplified BSD License.

Cheshire & Lemon         Expires 14 January 2021                [Page 1]
Internet-Draft      Advertising Proxy for DNS-SD SRP           July 2020

1.  Introduction

   DNS-Based Service Discovery [RFC6763] [ROADMAP] was designed to
   facilitate Zero Configuration IP Networking [RFC6760] [ZC].
   When used with Multicast DNS [RFC6762] with ".local" domain names
   [RFC6761] this works well on a single link (a single broadcast
   domain).

   There is also a desire to have DNS-Based Service Discovery work
   between multiple links that aren't part of the same broadcast domain
   [RFC7558].  Even within a single Wi-Fi broadcast domain it is
   beneficial to reduce multicast traffic, because, in comparison to
   Wi-Fi unicast traffic, Wi-Fi multicast is inefficient, slow, and
   unreliable [MCAST].

   There are three variant ways that this move to greater use of unicast
   is achieved.

   One variant is pure end-to-end unicast, with services using unicast
   Service Registration Protocol [SRP] to register with a service
   registry, and clients using unicast DNS Push Notifications [RFC8765]
   over DNS Stateful Operations [RFC8490] to communicate with the
   service registry to discover and track changes to those registered
   services.

   A second variant is a hybrid approach that facilitates legacy devices
   that only implement link-local Multicast DNS (like your ten-year-old
   network laser printer) having their services discovered by remote
   clients, using a unicast DNS Push Notifications session to a
   Discovery Proxy [RFC8766].

   The third variant, documented here, is a logical complement to the
   second variant.  It enables legacy clients (that only implement link-
   local Multicast DNS) to discover services registered (using unicast)
   with a service registry.  The service registry accepts service
   registrations using unicast Service Registration Protocol [SRP], and
   makes those service registrations visible, both to remote clients
   using unicast DNS Push Notifications [RFC8765] and, using the
   Advertising Proxy mechanism documented here, to local clients using
   Multicast DNS [RFC6762].

1.1.  Conventions and Terminology Used in This Document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in
   BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

Cheshire & Lemon         Expires 14 January 2021                [Page 2]
Internet-Draft      Advertising Proxy for DNS-SD SRP           July 2020

2.  Advertising Proxy

   An Advertising Proxy can be a component of any DNS authoritative
   server, though it logically makes most sense as a component of a
   service registry (a DNS authoritative server that implements Service
   Registration Protocol [SRP]).  A client can send registration
Show full document text