Framework for latency and loss traffic engineering application
draft-fuxh-rtgwg-delay-loss-te-framework-00

Document Type Expired Internet-Draft (individual)
Last updated 2011-07-04
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 Expired
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-fuxh-rtgwg-delay-loss-te-framework-00.txt

Abstract

Latency and packet loss is such requirement that must be achieved according to the Service Level Agreement (SLA) / Network Performance Objective (NPO) between customers and service providers. Latency and packet loss can be associated with different service level. The user may select a private line provider based on the ability to meet a latency and loss SLA. The key driver for latency and loss is stock/commodity trading applications that use data base mirroring. A few milli seconds and packet loss can impact a transaction. Financial or trading companies are very focused on end-to-end private pipe line latency optimizations that improve things 2-3 ms. Latency/loss and associated SLA is one of the key parameters that these "high value" customers use to select a private pipe line provider. Other key applications like video gaming, conferencing and storage area networks require stringent latency, loss and bandwidth. This document describes requirements to communicate latency and packet loss as a traffic engineering performance metric in today's network which is consisting of potentially multiple layers of packet transport network and optical transport network in order to meet the latency/loss SLA between service provider and his customers.

Authors

Xihua Fu (fu.xihua@zte.com.cn)
Malcolm Betts (malcolm.betts@zte.com.cn)
Dave McDysan (dave.mcdysan@verizon.com)
Qilei Wang (wang.qilei@zte.com.cn)
Andrew Malis (andrew.g.malis@verizon.com)

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