Requirements for Labels to Interoperate Between mDNS and DNS
draft-sullivan-dnssd-mdns-dns-interop-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Sullivan | ||
| Last updated | 2014-07-26 (Latest revision 2014-01-22) | ||
| Replaced by | draft-ietf-dnssd-mdns-dns-interop, RFC 8222 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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. Different name systems use different conventions for the characters allowed in any name. In order for DNS-SD to be used effectively in environments where multiple different name systems are in use, it is important to follow a common set of conventions for naming. This memo presents an outline of the reqiurements for selection of labels for mDNS and DNS 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.)