Multi-link Subnet Support in IPv6
draft-ietf-ipv6-multilink-subnets-00
| Document | Type |
Expired Internet-Draft
(ipv6 WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dave Thaler , Christian Huitema | ||
| Last updated | 2002-07-08 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
Bridging multiple links into a single entity has several operational advantages. A single subnet prefix is sufficient to support multiple physical links. There is no need to allocate subnet numbers to the different networks, simplifying management. This document introduces the concept of a 'multilink subnet', defined as a collection of independent links, connected by routers, but sharing a common subnet prefix. It then specifies the behavior of multilink subnet routers so that no changes to host behavior are needed.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)