Service-Oriented Address Assignment using DHCPv4
draft-syam-dhc-soav4-option-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Syam Madanapalli , Soohong Daniel Park | ||
| Last updated | 2005-02-03 | ||
| 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
This document introduces a new option in DHCPv4 for Service-Oriented Address assignment for a particular type of service that DHCPv4 Clients provide. The Service-Oriented Address can be either Anycast/Shared Unicast or a Well-known Unicast Addresses. This address assignment is much similar to other address type assignments, except that Service-Oriented Address assignment requires the specification of Service Type of the node that is requesting the address.
Authors
Syam Madanapalli
Soohong Daniel Park
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)