Re: Question about use of RSVP in Production Networks

Dean Anderson <dean@av8.com> Wed, 11 August 2004 23:03 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA29043; Wed, 11 Aug 2004 19:03:31 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bv2Cv-0006Fp-32; Wed, 11 Aug 2004 19:08:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv1qE-0000iB-V2; Wed, 11 Aug 2004 18:45:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bv1je-0007FF-2q for ietf@megatron.ietf.org; Wed, 11 Aug 2004 18:38:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27460 for <ietf@ietf.org>; Wed, 11 Aug 2004 18:38:13 -0400 (EDT)
Received: from cirrus.av8.net ([130.105.36.66]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bv1oO-0005kM-Uy for ietf@ietf.org; Wed, 11 Aug 2004 18:43:16 -0400
Received: from cirrus.av8.net (cirrus.av8.net [130.105.36.66]) (authenticated bits=0) by cirrus.av8.net (8.12.11/8.12.11) with ESMTP id i7BMbVRY029260 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 11 Aug 2004 18:37:34 -0400
Date: Wed, 11 Aug 2004 18:37:31 -0400
From: Dean Anderson <dean@av8.com>
X-X-Sender: dean@cirrus.av8.net
To: "Fleischman, Eric" <eric.fleischman@boeing.com>
In-Reply-To: <5B58696DB20B9140AD20E0685C573A6404FDD6BB@xch-nw-09.nw.nos.boeing.com>
Message-ID: <Pine.LNX.4.44.0408111821280.28896-100000@cirrus.av8.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: ietf@ietf.org
Subject: Re: Question about use of RSVP in Production Networks
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
X-Spam-Score: 2.7 (++)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64

RSVP is a idea that doesn't cut the mustard in the real world. There are 
several show-stopper problems with RSVP.

1) somewhat like multicast, anyone using RSVP is vulnerable to others
mis-using or mis-configuring RSVP. ISPs several AS's away can really screw
up things for other ISPs. Because of this, it is unwise to deploy it
because it requires too much trust in other ISPs.

That relegates RSVP to the enterprise Lan, where it usually isn't needed.  
Remember, RSVP is only useful if you have a congestion problem and need to
choose which packets to discard.  If you have no congestion problem, then
you have no need of RSVP. However, having a congestion problem also opens
the question of the nature of the congestion and what is the best way to
deal that problem.  I was involved in a study done by Genuity and Cisco in
which the congestion problem was found to most often involve the tail
circuit--the link between the customer and the ISP.  The best solution for
this problem was found to be low latency queuing, not RSVP.

2) Unlike multicast, every hop end-to-end must use RSVP for it to be 
useful. An RSVP tunnel is useless.

3) RSVP doesn't detect certain kinds of problems that are important. For
example, a mid-span failure is not visible to RSVP.

While RSVP is important research, it is not a widely deployable
technology.

What I-D's are you encountering that depend on RSVP?

		--Dean

On Tue, 10 Aug 2004, Fleischman, Eric wrote:

> I am aware of some use of RSVP in labs but I am not aware of any use of
> RSVP in production networks (i.e., real life networks people connect to
> the Internet with). Simultaneously, I am encountering I-Ds and other
> work planning to use RSVP. This possible disconnect concerns me.
> Therefore, I would appreciate being educated by anybody using RSVP in
> production settings. Would you please let me know how many devices, what
> applications, and how successful these deployments (if any) are? Thank
> you.
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf