DECADE Server Discovery
draft-pentikousis-decade-discovery-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Kostas Pentikousis | ||
| Last updated | 2013-03-17 (Latest revision 2012-09-13) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
A DECADE system must provide discovery mechanisms which enable the automatic configuration of DECADE clients with all information necessary to contact appropriate DECADE servers in the network. Typically, this configuration information would include the domain name or IP address of each DECADE server that should be considered by the client. Ideally, a DECADE discovery mechanism should capitalize upon existing Internet protocols, such as DHCP, which is widely deployed today. This document discusses DECADE server discovery and, as a first step towards automatic discovery, specifies how a DECADE client can obtain server location information using DHCP. To this end, it defines two DHCPv6 options which can be used to automatically provision the domain name or IP address of suitable servers in a DECADE system.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)