RATES: a server for MPLS traffic engineering
RATES: a server for MPLS traffic engineering
复制标题
RATES：MPLS 流量工程服务器
DOI：
10.1109/65.826370
复制
发表时间：
2000
期刊：
影响因子：
--
通讯作者：
B. Suter
中科院分区：
文献类型：
--
作者：
P. Aukia;M. Kodialam;P. Koppol;T. V. Lakshman;H. Sarin;B. Suter
有人认为，多协议标签交换（MPLS）网络部署的最重要原因之一是网络流量工程。流量工程的目标是充分利用网络基础设施，MPLS 的显式路由功能可以促进这一点，从而解决与当前 IP 路由方案相关的许多缺点。本文介绍了一个为 MPLS 流量工程开发的名为路由和流量工程服务器 (RATES) 的软件系统。它还描述了纳入 RATES 中用于 MPLS 显式路径选择的一些新路由思想。 RATES 实现包括策略和流数据库、用于策略定义和输入资源供应请求的基于浏览器的界面，以及用于将路径和资源信息传送到边缘路由器的通用开放策略服务协议服务器-客户端实现。 RATES 还使用 OSPF 拓扑数据库来动态获取链路状态信息。 RATES 可以在指定的入口-出口对之间建立带宽保证的标签交换 (LSP)。 LSP 的路径选择基于一种新的最小干扰路由算法，旨在在 LSP 请求一个接一个到达且没有关于未来请求的先验信息的在线环境中充分利用网络基础设施。尽管是为 MPLS 应用程序开发的，但 RATES 实现在组件方面与域内差异化服务带宽代理有许多相似之处。
It has been suggested that one of the most significant reasons for multiprotocol label switching (MPLS) network deployment is network traffic engineering. The goal of traffic engineering is to make the best use of the network infrastructure, and this is facilitates by the explicit routing feature of MPLS, which allows many of the shortcomings associated with current IP routing schemes to be addressed. This article describes a software system called Routing and Traffic Engineering Server (RATES) developed for MPLS traffic engineering. It also describes some new routing ideas incorporated in RATES for MPLS explicit path selection. The RATES implementation consists of a policy and flow database, a browser-based interface for policy definition and entering resource provisioning requests, and a Common Open Policy Service protocol server-client implementation for communicating paths and resource information to edge routers. RATES also uses the OSPF topology database for dynamically obtaining link state information. RATES can set up bandwidth-guaranteed label-switched (LSPs) between specified ingress-egress pairs. The path selection for LSPs is on a new minimum-interference routing algorithm aimed at making the best use of network infrastructure in an online environment where LSP requests arrive one by one with no a priori information about future requests. Although developed for an MPLS application, the RATES implementation has many similarities in components to an intradomain differentiated services bandwidth broker.