Proactive Routing Network Architecture
draft-tan-rtgwg-proactive-routing-network-arch-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Tan Xuefei | ||
| Last updated | 2016-12-23 (Latest revision 2016-06-21) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-tan-rtgwg-proactive-routing-network-arch-00.txt
Abstract
Proactive Routing Network (PRN), which runs on conventional network, is user and service experience oriented; and provides a set of E2E Pipes for the two End Systems of communication named Requester and Source. The E2E Pipe have deterministic path learned from the trace of the Request sent by Requester, and is QOS guaranteed by resource reservation. Addressing issue is solved by recording the labeled interfaces or Local Pipes taken along with the Request to the Source. Each Pipe is protocol oblivious, application aware, elastic and visible for users and operators. PRN is not a new network, rather, it is a service attached to the conventional network. Therefore it does not affect the operation business of the conventional networks, so it is very conducive to the deployment and smooth evolution. PRN is valuable for users who want deterministic network service, and is helpful for operators to simplify the service management and easy for fault location and billing, and is helpful for vendors to solve the addressing issue which is one of the biggest challenges of increasing device throughput at a reasonable cost.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)