Performance-based BGP Routing Mechanism
draft-xu-idr-performce-routing-00

Document Type Replaced Internet-Draft (individual)
Last updated 2014-06-12 (latest revision 2013-12-09)
Replaced by draft-ietf-idr-performance-routing
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
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
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-xu-idr-performce-routing-00.txt

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

Xiaohu Xu (xuxiaohu@huawei.com)
Hui Ni (nihui@huawei.com)
Fan Yongbing (fanyb@gsta.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)