Security option extensions for DHCP
draft-bi-dhc-sec-option-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Emily Bi , Serge Manning , Marcus Wong , Yang Cui | ||
| Last updated | 2013-01-17 (Latest revision 2012-07-16) | ||
| 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 defines a new option that can be used by DHCP servers to provision with DHCP clients specific security configuration information. It has been known that DHCP protocol typically works at the very beginning stage of the access to networks, thus lack of security protection. However, although it is difficult to set up some security mechanism for DHCP protocol solely, it is able to play a key role for DHCP server to provide configuration information to help building security mechanism within those pre-configured DHCP clients and devices. This new option defines a simple extension to current standard format and benefits to those who need to activate security mechanism in an early stage and interoperate within devices from multiple vendors.
Authors
Emily Bi
Serge Manning
Marcus Wong
Yang Cui
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)