The Local Domain Name DHCP Option
draft-wu-hokey-ldn-discovery-01
Document | Type | Replaced Internet-Draft (individual) | |
---|---|---|---|
Last updated | 2010-02-10 | ||
Replaced by | draft-ietf-hokey-ldn-discovery | ||
Stream | (None) | ||
Intended RFC status | (None) | ||
Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
Stream | Stream state | (No stream defined) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-hokey-ldn-discovery | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
https://www.ietf.org/archive/id/draft-wu-hokey-ldn-discovery-01.txt
Abstract
In order to derive a Domain-Specific Root Key (DSRK) from the Extended Master Session Key (EMSK) generated as a side-effect of an Extensible Authentication Protocol (EAP) method, the EAP peer must discover the name of the domain to which it is attached. This document specifies a Dynamic Host Configuration Protocol (DHCP) option designed to allow a DHCP server to inform clients of the name of the local domain..
Authors
Glen Zorn
(gwz@net-zen.net)
Qin Wu
(sunseawq@huawei.com)
Yungui Wang
(w52006@huawei.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)