Re: Last Call for draft-ietf-rolc-apr-00.txt

Curtis Villamizar <curtis@ans.net> Thu, 26 October 1995 16:46 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa16602; 26 Oct 95 12:46 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa16598; 26 Oct 95 12:46 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id MAA25313; Thu, 26 Oct 1995 12:17:13 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id MAA11051 for rolc-out; Thu, 26 Oct 1995 12:28:06 -0400
Received: from guelah.nexen.com (guelah.nexen.com [204.249.96.19]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id MAA11042 for <rolc@nexen.com>; Thu, 26 Oct 1995 12:28:03 -0400
Received: from brookfield.ans.net (brookfield-ef0.brookfield.ans.net [204.148.1.20]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id MAA25305 for <rolc@nexen.com>; Thu, 26 Oct 1995 12:16:35 -0400
Received: from brookfield.ans.net (localhost.brookfield.ans.net [127.0.0.1]) by brookfield.ans.net (8.6.12/8.6.12) with ESMTP id MAA23060; Thu, 26 Oct 1995 12:27:48 -0400
Message-Id: <199510261627.MAA23060@brookfield.ans.net>
To: Juha Heinanen <jh@lohi.dat.tele.fi>
cc: curtis@ans.net, yakov@cisco.com, rolc@nexen.com
Reply-To: curtis@ans.net
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
In-reply-to: Your message of "Thu, 26 Oct 1995 10:21:41 +0200." <199510260821.KAA02422@lohi.dat.tele.fi>
Date: Thu, 26 Oct 1995 12:27:47 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Curtis Villamizar <curtis@ans.net>
X-Orig-Sender: owner-rolc@nexen.com
Precedence: bulk
X-Info: Submissions to rolc@nexen.com
X-Info: [Un]Subscribe requests to rolc-request@nexen.com
X-Info: Archives for rolc via ftp://ietf.cnri.reston.va.us/ietf-mail-archive/rolc/

In message <199510260821.KAA02422@lohi.dat.tele.fi>fi>, Juha Heinanen writes:
>    If the application specifies QoS and traffic characteristics and
>    indirectly controls SVC management, then we are in agreement.  Then it
>    doesn't matter if the box it is running on sets up a VC or if it sits
>    on an ethernet and the next hop sets up a VC.  Are we in agreement on
>    this?
> 
> this is what i have never understod about rsvp.  how can a host sitting
> on a shared media, like ethernet, make any reservation whatsoever.  so
> isn't it a requirement for rsvp to work that the hosts are directly
> connected to such a link layer network, eg. atm, that supports
> reservation requests?  what does it help if all the routers in the whole
> internet are rsvp capable if the last hop isn't?
> 
> -- juha

The application states a traffic characterization and requirement.  If
the ethernet is thought to be uncongested, the traffic must then make
a one hop "leap of faith".  It can then go through a congested T1
(assuming RSVP is supported and the reservation is accepted) without
further loss, or traverse an NBMA.  If the ethernet is not
uncongested, things don't work very well.  If we are talking about a
fairly dedicated ethernet segment, or somewhat traffic isolated by
10baseX hub, then the "uncongested" assumption may be close enough.

Curtis