Performance-based BGP Routing Mechanism
draft-xu-idr-performce-routing-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Xiaohu Xu , Hui Ni , Fan Yongbing | ||
Last updated | 2014-06-12 (Latest revision 2013-12-09) | ||
Replaced by | draft-ietf-idr-performance-routing | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-idr-performance-routing | |
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
Network performance, especially network latency is widely recognized as one of major obstacles in adopting public cloud services (e.g., cloud desktop service), especially in the scenario where the network paths between cloud end-users and cloud data centers traverse more than one Autonomous System (AS). However, the current Border Gateway Protocol (BGP) specification [RFC4271] doesn't use network performance metrics (e.g., network latency) in the route selection decisions. This document describes a performance-based BGP routing mechanism in which network latency metric is taken as one of the route selection criteria.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)