On Interoperation of Labels Between mDNS and DNS
draft-ietf-dnssd-mdns-dns-interop-01

The information below is for an old version of the document
Document Type Active Internet-Draft (dnssd WG)
Last updated 2015-07-04
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
DNSSD                                                        A. Sullivan
Internet-Draft                                                       Dyn
Intended status: Informational                              July 4, 2015
Expires: January 5, 2016

            On Interoperation of Labels Between mDNS and DNS
                  draft-ietf-dnssd-mdns-dns-interop-01

Abstract

   Despite its name, DNS-Based Service Discovery can use naming systems
   other than the Domain Name System when looking for services.
   Moreover, when it uses the DNS, DNS-Based Service Discovery uses the
   full capability of DNS, rather than using a subset of available
   octets.  In order for DNS-SD to be used effectively in environments
   where multiple different name systems and conventions for their
   operation are in use, it is important to attend to differences in the
   underlying technology and operational environment.  This memo
   presents an outline of the requirements for selection of labels for
   conventional DNS and other resolution systems when they are expected
   to interoperate in this manner.

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 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 January 5, 2016.

Copyright Notice

   Copyright (c) 2015 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

Sullivan                 Expires January 5, 2016                [Page 1]
Internet-Draft            mDNS and DNS Interop                 July 2015

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions and terms used in this document . . . . . . .   3
   2.  Why there could be a problem at all . . . . . . . . . . . . .   4
   3.  Requirements for a profile for label interoperation . . . . .   5
   4.  DNS-SD portions . . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  The <Instance> Portion of the Service
           Instance Name . . . . . . . . . . . . . . . . . . . . . .   6
     4.2.  The <Service> Portion of the Service
           Instance Name . . . . . . . . . . . . . . . . . . . . . .   7
     4.3.  The <Domain> Portion of the             Service Instance
           Name  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  Informative References  . . . . . . . . . . . . . . . . . . .   8
   Appendix A.  Change History . . . . . . . . . . . . . . . . . . .  10
     A.1.  draft-ietf-dnssd-mdns-dns-interop-01  . . . . . . . . . .  10
     A.2.  draft-ietf-dnssd-mdns-dns-interop-00  . . . . . . . . . .  10
     A.3.  draft-sullivan-dnssd-mdns-dns-interop-01  . . . . . . . .  10
     A.4.  draft-sullivan-dnssd-mdns-dns-interop-00  . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   DNS-Based Service Discovery (DNS-SD, [RFC6763]) specifies a mechanism
   for discovering services using queries to the Domain Name System
   (DNS, [RFC1034], [RFC1035]); and to any other system that uses domain
   names, such as Multicast DNS (mDNS, [RFC6762]).  Conventional use of
   the DNS generally follows the host name rules [RFC0952] for labels --
   the so-called LDH rule.  That convention is the reason behind the
   development of Internationalized Domain Names for Applications
   (IDNA2008, [RFC5890], [RFC5891], [RFC5892], [RFC5893], [RFC5894],
   [RFC5895]).  It is worth noting that the LDH rule is a convention,
   and not a rule of the DNS; this is made entirely plain by [RFC2181],
   section 11.  Nevertheless, there is a widespread belief that in many
   circumstances domain names cannot be used in the DNS unless they
Show full document text