[55746] in North American Network Operators' Group
Re: VoIP QOS best practices
daemon@ATHENA.MIT.EDU (Leo Bicknell)
Mon Feb 10 14:06:19 2003
Date: Mon, 10 Feb 2003 13:43:48 -0500
From: Leo Bicknell <bicknell@ufp.org>
To: nanog@nanog.org
Mail-Followup-To: nanog@nanog.org
In-Reply-To: <003001c2d130$e8261340$b3a623c0@klunkyw>
Errors-To: owner-nanog-outgoing@merit.edu
--OXfL5xGRrasGEqWY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In a message written on Mon, Feb 10, 2003 at 01:19:08PM -0500, chaim fried =
wrote:
> happens). There is no reason to implement QOS on the Core. Having said
> that, there still seems to be too many issues on the tier 1 networks
> with pacekt reordering as they affect h.261/h.263 traffic.=20
I've got a question about this issue. Many networks reorder packets
for a number of reasons. At least once before I've attempted to
measure the effects of this reordering on a number of forms of
traffic, but I have never understood the particular effects on VOIP
traffic.
Indeed, the two times I was asked to investigate this for video
people it turns out the video receivers /had no ability to handle
out of order frames/. That's right, get one packet out of order
and the video stream goes away until it resynchronizes. Now, I
realize reordering should not happen to a large percentage of the
packets out there, but it also seems to me any IP application has
to handle reordering or it's not really doing IP.
So what's the real problem here? Are the VOIP boxes unable to
handle out of order packets? Do the out of order packets simply
arrive far enough delayed to blow the delay budget? What percentage of
reordered packets starts to cause issues?
--=20
Leo Bicknell - bicknell@ufp.org - CCIE 3440
PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - tmbg-list-request@tmbg.org, www.tmbg.org
--OXfL5xGRrasGEqWY
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (FreeBSD)
Comment: For info see http://www.gnupg.org
iD8DBQE+R/LkNh6mMG5yMTYRAsn4AJ9Y1vO1RILDjvGdTJUPmiiknUlpHgCfedQm
rOH5KvKO+PVnSVoLPZkG4zI=
=LCXI
-----END PGP SIGNATURE-----
--OXfL5xGRrasGEqWY--
