Selecting a Direct Provider
draft-rekhter-direct-provider-01
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Author | Yakov Rekhter | ||
Last updated | 1994-04-25 | ||
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
Within the existing Internet routing architecture/protocols different hosts within a domain (autonomous system) usually can't control the choice of adjacent domains for forwarding of the inter-domain traffic originated by the hosts. In this document we describe a simple mechanism that provides hosts with such control. The proposed scheme can be realised with the existing technology, off-the shelf components, and minor tweaking of forwarding algorithm by border routers. The scheme doesn't require any new routing protocols.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)