On Interoperation of Labels Between DNS and Other Resolution Systems
draft-ietf-dnssd-mdns-dns-interop-02
| Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 8222.
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Sullivan | ||
| Last updated | 2016-05-04 (Latest revision 2015-11-01) | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
ARTART Telechat review
(of
-04)
by Eliot Lear
Ready w/issues
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)