Considerations for DNA Schemes with Multiple Interfaces and Layer 2 Technologies
draft-hong-dna-if-l2-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Yong-Geun Hong | ||
| Last updated | 2004-10-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
In this document we consider and analyze various environments for applying Detecting Network Attachment (DNA) schemes. Although DNA schemes are typically run for each interface and a host separately checks for link changes on each interface when the host has multiple interfaces, DNA schemes in the host must be considered to check the multiple interfaces at the same time for a seamless service. In addition, DNA schemes in the host must be capable of managing together each DNA scheme on each interface. Current DNA schemes only rely on 'Break before Make' L2 technology such as 802.11. But now and in future, there will be other 'Make before break' L2 technologies such as CDMA. In these L2 technologies, DNA schemes must be operated differently in order to make use of their characteristics.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)