Secure DHCPv6
draft-ietf-dhc-sedhcpv6-21
| Document | Type | Expired Internet-Draft (dhc WG) | |
|---|---|---|---|
| Last updated | 2017-08-25 (latest revision 2017-02-21) | ||
| Replaces | draft-jiang-dhc-sedhcpv6 | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | Tomek Mrugalski | ||
| Shepherd write-up | Show (last changed 2015-01-29) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | Suresh Krishnan | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-dhc-sedhcpv6-21.txt
Abstract
DHCPv6 includes no deployable security mechanism that can protect end-to-end communication between DHCP clients and servers. This document describes a mechanism for using public key cryptography to provide such security. The mechanism provides encryption in all cases, and can be used for authentication based on pre-sharing of authorized certificates.
Authors
Lishan Li
(lilishan48@gmail.com)
Sheng Jiang
(jiangsheng@huawei.com)
Yong Cui
(yong@csnet1.cs.tsinghua.edu.cn)
Tatuya Jinmei
(jinmei@wide.ad.jp)
Ted Lemon
(ted.lemon@nominum.com)
Dacheng Zhang
(dacheng.zhang@gmail.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)