IRON and MOBIKE
draft-templin-ironmike-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Templin | ||
| Last updated | 2011-05-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
The Internet Routing Overlay Network (IRON) is a new routing and addressing architecture based on encapsulation of inner network layer packets within outer network layer headers using a non-broadcast, multiple access (NBMA) virtual interface model. The IKEv2 Mobility and Multihoming Protocol (MOBIKE) allows a Virtual Private Network (VPN) client to keep a connection to a VPN gateway active across multiple network points of attachment or while moving from one network point of attachment to another. This document examines the similarities between IRON and MOBIKE, and observes that they are addressing the same fundamental networking objectives. It further proposes ways in which the basic MOBIKE model could be extended through adoption of IRON architectural constructs.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)