RE: IP QoS issues

To: Reni.Ninan.rninan at nt.com (Reni Ninan)
Subject: RE: IP QoS issues
From: Masataka Ohta <mohta at necom830.hpcl.titech.ac.jp>
Date: Tue, 7 Jul 98 9:20:54 JST
Cc: mohta at necom830.hpcl.titech.ac.jp, karl at CaveBear.com, wiztech at CMPNETMAIL.COM, ietf at ietf.org
Delivery-date: Mon, 06 Jul 1998 20:55:52 -0400
In-reply-to: <81AE5015B592D111B75808002BB91BE474FC2C@zrtpd002.us.nortel.com>; from "Reni Ninan" at Jul 6, 98 9:56 am

Reni;

> I agree with Karl that IP QoS is still quite a long way off. It's not as
> easy as reusing ATM techniques. Instability of routes is bound to maintain
> QoS difficult and it's not a solved problem.

Red herring are aggregation, policy and MPLS.

Also, diff serve is just as bad as ABR/VBR.

Once you forget all of them, stable routing of qos assured
traffic (which is different from stable routing of best effort
traffic) is easy and solved.

							Masataka Ohta

Follow-Ups:
- RE: IP QoS issues
  - From: Karl Auerbach
- RE: IP QoS issues
  - From: FUJIKAWA Kenji

References:
- RE: IP QoS issues
  - From: Reni Ninan

Prev by Date: Re: GSSAPI v2 gss_process_context_token() inconsistency
Next by Date: Re: Where is the RFC editor?
Previous by thread: RE: IP QoS issues
Next by thread: RE: IP QoS issues
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

RE: IP QoS issues

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.