Service-Oriented Address Assignment using DHCPv6
draft-ietf-dhc-soa-option-00
| Document | Type | Expired Internet-Draft (dhc WG) | |
|---|---|---|---|
| Author | Syam Madanapalli | ||
| Last updated | 2005-01-20 | ||
| Stream | Internent Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-dhc-soa-option-00.txt
Abstract
This document introduces a new option in DHCPv6 for Service-Oriented Address assignment for a particular type of service that DHCPv6 Clients provide. The Service-Oriented Address can be either Anycast/Shared Unicast or a Well-known Unicast Address. 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 (smadanapalli@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)