|
Publications
|
Operating Systems are now attempting to support ad-hoc networks of two or more systems, while keeping user configuration at a minimum. To accommodate this, in the absence of a central configuration mechanism (DHCP), some OS's are automatically choosing a link-local IP address which will allow them to communicate only with other hosts on the same link. This address will not allow the OS to communicate with anything beyond a router. However, some sites depend on the fact that a host with no DHCP response will have no IP address. This document describes a mechanism by which DHCP servers are able to tell clients that they do not have an IP address to offer, and that the client should not generate an IP address it's own.
The ACAP [ACAP] Dataset Model is very extensible, and allows
applications to easily share options and information. With this
extensibility comes a complexity that an application designer must
fully understand in order to interoperate while using ACAP.
This document will help the reader understand and visualize the ACAP
hierarchy, come to a better understanding of how to design and access
ACAP datasets, and understand the relationship between attributes,
entries, datasets, and dataset classes.
With operating systems appearing in more and more devices, as well
as computers appearing in more and more aspects of everyday life,
communication between networked devices is increasingly important.
The communication mechanism between these devices must be able to
not only support the office LAN environment, but must also scale to
larger WANS and the internet.
This draft describes a method by which a host may automatically give
itself a link-local IPv4 address, so that it will be able to use IP
applications in the absence of an IP address management mechanism,
such as DHCP. This mechanism is in use today by a few operating
systems, and additional information on those implementations is also
provided.
The Application Configuration Access Protocol [ACAP] is designed to support remote storage and access of common application option, configuration and preference information. Once such piece of information is the "Message of the Day" greeting, used by system administrators to communicate important information to all users when they begin to use a system. This document describes a common format for storing MOTD information in ACAP, how site administrators may configure their ACAP MOTD service to allow multiple groups within the site to provide custom MOTD information, and how a client should access and use this information.