Architecture of PSN Independent Overlay Network(PION)
draft-kj-nvo3-pion-architecture-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Lizhong Jin , Bhumip Khasnabish | ||
| Last updated | 2012-11-12 (Latest revision 2012-05-11) | ||
| 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
This draft introduces PSN independent overlay network (PION) architecture for intra- and inter-datacenter (DC) connections. The motivations, protocol layers, applications, and etc, for PION are also discussed. PION provides a virtualized underlying-PSN- independent network in order to maximize the reuse of IETF protocol definitions and implementations. The inter- and intra-DC connection provided by PION could be from endpoint to endpoint, or endpoint to network, or network to network. The packet transport capabilities provided by the overlay network are determined by the capability of the underlying PSN.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)