Secure NEighbor Discovery (SEND) over OMNI Interfaces
draft-templin-omni-send-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2021-07-26 (Latest revision 2021-01-22) | ||
| 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
The Overlay Multilink Network Interface (OMNI) specification can be used by nodes on public Internetworks when a suitable security service is provided to authenticate IPv6 Neighbor Discovery (IPv6 ND) control messages. The basic OMNI security service for transmission of IPv6 ND messages over public Internetworks uses a Hashed Message Authentication Code (HMAC) based on a shared secret. This document specifies use of the Secure NEighbor Discovery (SEND) protocol over OMNI interfaces which can provide a more flexible and robust service.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)