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

Dilip Kandlur <kandlur@watson.ibm.com> Tue, 24 October 1995 22:05 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa22885; 24 Oct 95 18:05 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa22879; 24 Oct 95 18:05 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id RAA10912; Tue, 24 Oct 1995 17:37:15 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id RAA16970 for rolc-out; Tue, 24 Oct 1995 17:47:54 -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 RAA16961 for <rolc@nexen.com>; Tue, 24 Oct 1995 17:47:51 -0400
Received: from watson.ibm.com (watson.ibm.com [129.34.139.4]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id RAA10908 for <rolc@nexen.com>; Tue, 24 Oct 1995 17:36:44 -0400
Received: from WATSON by watson.ibm.com (IBM VM SMTP V2R3) with BSMTP id 9999; Tue, 24 Oct 95 17:33:36 EDT
Received: from YKTVMV by watson.vnet.ibm.com with "VAGENT.V1.02 on VAGENT2" id 7236; Tue, 24 Oct 1995 17:33:36 EDT
Received: from vindhya.watson.ibm.com by yktvmv.watson.ibm.com (IBM VM SMTP V2Rx) with TCP; Tue, 24 Oct 95 17:33:36 EDT
Received: by vindhya.watson.ibm.com (AIX 3.2/UCB 5.64/950830) id AA12251; Tue, 24 Oct 1995 17:33:15 -0400
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Dilip Kandlur <kandlur@watson.ibm.com>
Message-Id: <9510242133.AA12251@vindhya.watson.ibm.com>
X-Sender-Data: Phone: 914-784 7722 or 8-863 7722
To: Andrew Smith <asmith@baynetworks.com>
Cc: kandlur@watson.ibm.com, rolc@nexen.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
In-Reply-To: (Your message of Tue, 24 Oct 95 14:22:39 PDT.) <9510242122.AA21967@milliways-le0.engwest>
Reply-To: kandlur@watson.ibm.com
Date: Tue, 24 Oct 95 17:33:15 -0500
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/

Andrew,

 > The implication is that QoS requirements would be considered as a
 > guide to setup SVCs.  Yes, there is also a belief that an SVC would
 > provide better QoS (e.g. delay) since it avoids IP level handling
 > costs at intermediate nodes.

 I don't think we should be making assumptions like that in an architectural
 document: that is an implementation issue. I certainly know of some ATM switches
 with higher latency (under some traffic conditions) than routers .... :-)

We can, however, make the assertion that the QoS characteristics of
the ATM SVC would be based on the QoS requirements of the higher
layers.  The belief that ATM SVCs are more desirable than multiple IP
hops is one that is in line with the objectives of ROLC.

-- Dilip.