<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3059" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>Why the new Expedited Forwarding PHB (RFC 3246)
memo regards Expedited Forwarding PHB concept as a service which offers QoS
guarantee with bounded delay and bounded jitter (see section 2.4)?</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>But on refering to original memo RFC 2598, the
service for offering low loss, low<BR>latency, low jitter, and assured bandwidth
through DS domains. It says nothing about bounding the delay or bounding jitter.
This is also stated in the 1st page of RFC 3246.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>RFC 3246 states that eq. 3 on page 5 must be
satisfied which makes it sounds more like delivering hard type of QoS rather
than soft. In my imagination, low latency means offering latency at it best
(subject to instantenous conditions or other constraints) but not
guaranteeing it.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Was this what the original definition of Expedited
Forwarding supposed to be?</FONT></DIV></BODY></HTML>