Multihoming using 64-bit Crypto-based IDs
draft-nordmark-multi6-cb64-00
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Erik Nordmark | ||
Last updated | 2003-11-19 | ||
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 outlines a potential solution to IPv6 multihoming in order to stimulate discussion. This proposal is a middle ground between the NOID and CB128 proposals. This proposed solution relies on verification the crypto-based identifier properties (using public-key crypto during uncommon operations), while allowing locator rewriting by (border) routers, with no per-packet overhead. The solution does have something which could be viewed as a 'stack name' type of identifier, but this isn't exposed to upper layer protocols. Instead it ensures that all upper layer protocols can operate unmodified in a multihomed setting while still seeing a stable IPv6 address, even though the address internally consists of 64-bits worth of subnet locator plus 64-bits of crypto-based identifier. This solution (and this draft) is remarkably similar to draft- nordmark-multi6-noid-00.txt; only issues related to prevention of redirection attacks differ.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)