DNS-Based Service Discovery

Krochmal, Marc; Cheshire, Stuart

doi:10.17487/rfc6763

Cited by 210 publications

(123 citation statements)

References 15 publications

Supporting

Mentioning

116

Contrasting

Unclassified

Order By: Relevance

“…It is worth observing that a portion may be more than one label long. See Section 4.1 of [RFC6763]. Further discussion of the parts is found in Section 4.…”

Section: Conventions and Terms Used In This Documentmentioning

confidence: 99%

See 1 more Smart Citation

Selecting Labels for Use with Conventional DNS and Other Resolution Systems in DNS-Based Service Discovery

Sullivan¹

2017

View full text Add to dashboard Cite

Despite its name, DNS-Based Service Discovery (DNS-SD) can use naming systems other than DNS when looking for services. Moreover, when it uses DNS, DNS-SD uses the full capability of DNS, rather than using a subset of available octets. This is of particular relevance where some environments use DNS labels that conform to Internationalized Domain Names for Applications (IDNA), and other environments use labels containing Unicode characters (such as containing octets corresponding to characters encoded as UTF-8). 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 the selection of labels for conventional DNS and other resolution systems when they are expected to interoperate in this manner.

show abstract

“…It is worth observing that a portion may be more than one label long. See Section 4.1 of [RFC6763]. Further discussion of the parts is found in Section 4.…”

Section: Conventions and Terms Used In This Documentmentioning

confidence: 99%

“…For example, mDNS encourages the use of spaces and punctuation in mDNS names (see Section 4.2.3 of [RFC6763]). It does not restrict which Unicode code points may be used in those labels, so long as the code points are UTF-8 in Net-Unicode [RFC5198] format.…”

mentioning

confidence: 99%

Selecting Labels for Use with Conventional DNS and Other Resolution Systems in DNS-Based Service Discovery

Sullivan¹

2017

View full text Add to dashboard Cite

show abstract

“…To enable that, this specification uses a TXT RR that follows the syntax defined in Section 6 of [RFC6763] and defines a "path" key for use in that record. The value of the key MUST be the actual "context path" to the corresponding service on the server.…”

Section: Txt Records For a Time Zone Data Distribution Servicementioning

confidence: 99%

Time Zone Data Distribution Service

Douglass¹,

Daboo²

2016

View full text Add to dashboard Cite

show abstract

“…The possible DNS methods include DNS SRV [RFC2782] or DNS-SD [RFC6763]. If port lookup is not supported or not provided by DNS, the default CoAP port (5683) For the 'gp' variable, it is recommended to use the path "coap-group" by default.…”

Section: Coap-group Resource Type and Media Typementioning

confidence: 99%