Naming and Discovery

Homenet Interim ‘11

2

Naming Requirements

• (Some) devices and hosts need names• In the Homenet context, names (and services)

should be resolvable from anywhere on the network

• Some devices need names that can be used from outside– implies distribution into the global DNS

• Some devices need names that cannot be used from outside– privacy, security

3

Existing Protocols

• DNS-SD / mDNS• LLMNR (RFC 4795)• SSDP (UPnP)• SLP (RFC 2608)

All are typically link-local only• Unicast DNS• Anything else?

4

Other Requirements?

• Do Unicast DNS and the local naming protocol need to interoperate?– How can a unicast-only client reach a multicast-

advertised service?• If so, can they (or should they) share the same

namespace?– mDNS uses “.local”, Microsoft Active Directory

admins also use “.local” or just make something up!• Do we need site-wide multicast routing support?

5

More Namespace Stuff

• Are DNS search suffixes obsolete?– i.e. is “canon” a single-label “New gTLD” or the

name of a printer on the local LAN?– An unscientific poll of IETF DNS folk unanimously

said we should deprecate search suffixes.