Manual Configuration of Security Associations for IPv6 Neighbor Discovery
draft-arkko-manual-icmpv6-sas-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Jari Arkko | ||
Last updated | 2003-03-07 | ||
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 informational document discusses the use of manually configured IPsec security associations to protect IPv6 Neighbor Discovery (ND) messages. IPsec security associations are generally identified by the triple (security parameters index, destination address, protocol). In the case of Neighbor Discovery, configuring these associations requires some effort, however. There are multiple known destination addresses plus a number of addresses that depend on the physical link addresses. This document describes the security implications of protecting or not protecting the Neighbor Discovery messages and lists the security associations that must be configured manually. The presented method is applicable only in small networks, but some approaches for reducing the configuration effort are discussed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)