CoRE Resource Directory: DNS-SD mapping
draft-ietf-core-rd-dns-sd-00

Document Type Active Internet-Draft (core WG)
Last updated 2017-07-03
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html bibtex
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)
CoRE                                                             K. Lynn
Internet-Draft                                              Verizon Labs
Intended status: Standards Track                         P. van der Stok
Expires: January 4, 2018                                      consultant
                                                               M. Koster
                                                             SmartThings
                                                         C. Amsuess, Ed.
                                             Energy Harvesting Solutions
                                                           July 03, 2017

                CoRE Resource Directory: DNS-SD mapping
                      draft-ietf-core-rd-dns-sd-00

Abstract

   TBD

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 4, 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
   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

Lynn, et al.             Expires January 4, 2018                [Page 1]
Internet-Draft   CoRE Resource Directory: DNS-SD mapping       July 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  New Link-Format Attributes  . . . . . . . . . . . . . . . . .   3
     2.1.  Resource Instance attribute 'ins' . . . . . . . . . . . .   3
     2.2.  Export attribute 'exp'  . . . . . . . . . . . . . . . . .   3
   3.  DNS-SD Mapping  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  DNS-based Service discovery . . . . . . . . . . . . . . .   4
     3.2.  mapping ins to <Instance> . . . . . . . . . . . . . . . .   5
     3.3.  Mapping rt to <ServiceType> . . . . . . . . . . . . . . .   5
     3.4.  Domain mapping  . . . . . . . . . . . . . . . . . . . . .   6
     3.5.  TXT Record key=value strings  . . . . . . . . . . . . . .   6
     3.6.  Importing resource links into DNS-SD  . . . . . . . . . .   6
   4.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  DNS entries . . . . . . . . . . . . . . . . . . . . . . .   7
   5.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   8
   6.  Security considerations . . . . . . . . . . . . . . . . . . .   8
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   8
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   9
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   TBD ... [RFC7252] ... [I-D.ietf-core-resource-directory] ... DNS-SD

1.1.  Terminology

   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
   [RFC2119].  The term "byte" is used in its now customary sense as a
   synonym for "octet".

   This specification requires readers to be familiar with all the terms
   and concepts that are discussed in [RFC5988] and [RFC6690].  Readers
   should also be familiar with the terms and concepts discussed in
   [RFC7252].  To describe the REST interfaces defined in this
   specification, the URI Template format is used [RFC6570].
Show full document text