About: Zero-configuration networking is a research topic. Over the lifetime, 93 publications have been published within this topic receiving 2540 citations. The topic is also known as: DNS-SD & zero-configuration networking.
TL;DR: This document defines the concept of a signed zone, along with the requirements for serving and resolving by using DNSSEC, which allow a security-aware resolver to authenticate both DNS resource records and authoritative DNS error indications.
Abstract: This document is part of a family of documents that describe the DNS
Security Extensions (DNSSEC). The DNS Security Extensions are a
collection of new resource records and protocol modifications that add
data origin authentication and data integrity to the DNS. This
document describes the DNSSEC protocol modifications. This document
defines the concept of a signed zone, along with the requirements for
serving and resolving by using DNSSEC. These techniques allow a
security-aware resolver to authenticate both DNS resource records and
authoritative DNS error indications. This document obsoletes RFC 2535
and incorporates changes from all updates to RFC 2535. [STANDARDS-
TRACK]
TL;DR: In this paper, a self-reconfiguring name service that distributes workload among the available servers in a system is described, where a Service Monitor for each host system of a site periodically broadcasts information about available servers.
Abstract: A self-reconfiguring name service that distributes workload among the available servers in a system. A Service Monitor for each host system of a site periodically broadcasts information about available servers. The broadcast message also indicates the workload of the host. Each name service (DNS) has an associated process called a Name Binder Modifier that receives the broadcast messages from the Service Monitors. Periodically, each Name Binder Modifier reviews the information it has received from various Service Monitors and updates zones that are used by the DNS to perform load balancing. The Service Monitor and the Name Binding Modifier have associated configuration files.
TL;DR: This RFC defines a proposed standard protocol to support NetBIOS services in a TCP/IP environment and various node types are defined to accommodate local and internet topologies and to allow operation with or without the use of IP broadcast.
Abstract: This RFC defines a proposed standard protocol to support NetBIOS
services in a TCP/IP environment. Both local network and internet
operation are supported. Various node types are defined to accommodate
local and internet topologies and to allow operation with or without
the use of IP broadcast. This RFC describes the NetBIOS-over-TCP
protocols in a general manner, emphasizing the underlying ideas and
techniques. Detailed specifications are found in a companion RFC,
"Protocol Standard For a NetBIOS Service on a TCP/UDP Transport:
Detailed Specifications".
TL;DR: This document describes Dynamic Host Configuration Protocol for IPv6 (DHCPv6) options for passing a list of available DNS recursive name servers and a domain search list to a client.
Abstract: This document describes Dynamic Host Configuration Protocol for IPv6 (DHCPv6) options for passing a list of available DNS recursive name servers and a domain search list to a client.
TL;DR: The Zeroconfiguration Routing Information Protocol (ZRIP) as mentioned in this paper employs a NORMAL/CHANGE status flag associated with each routing table entry to resolve ambiguity between normal routing advertisements and conflict notifications.
Abstract: The Routing Information Protocol [RIP] is extended to include a network-wide unique interface identifier [UID] that allows the zeroconfiguration multiple router [R1, R2] network to detect subnet conflicts. Detected conflicts are automatically repaired by the respective routers assigning and advertising new subnet mappings. The extended, Zeroconfiguration Routing Information Protocol [ZRIP] employs a NORMAL/CHANGE status flag associated with each routing table entry to resolve ambiguity between normal routing advertisements and conflict notifications. Address re-mapping and name-to-address resolution is provided to support both network address translation [NAT] and virtualized address paradigms.