Securing Zeroconf Networks
draft-williams-zeroconf-security-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Aidan Williams | ||
| Last updated | 2000-11-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
Devices using zeroconf networking protocols can communicate using IP without requiring user configuration or infrastructure services like DHCP and DNS. The options available to secure zeroconf networks are canvassed. A comparison is made between bootstrapping IPSec and securing sample protocols from each area listed in the zeroconf working group charter. This shows IPSec to be the most promising approach for securing zeroconf protocols.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)