Architectural Considerations for the use of Endpoint Identifiers in Delay Tolerant Networking
draft-eddy-dtnrg-eid-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Wesley Eddy | ||
| Last updated | 2006-05-26 | ||
| 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 architecture for Delay Tolerant Networking includes a type of address called an Endpoint Identifier. This document describes some of the remaining issues regarding Endpoint Indentifiers, and how they can be configured and used in bundle forwarding. These either imply directions for future work or highlight clarifications that should be made in the current architecture and protocol documents.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)