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

Andrew Smith <asmith@baynetworks.com> Wed, 25 October 1995 01:52 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa25141; 24 Oct 95 21:52 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa25137; 24 Oct 95 21:52 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id VAA12114; Tue, 24 Oct 1995 21:16:29 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id VAA18453 for rolc-out; Tue, 24 Oct 1995 21:24:40 -0400
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.6.12/8.6.12) with ESMTP id VAA18444 for <rolc@nexen.com>; Tue, 24 Oct 1995 21:24:37 -0400
Received: from lightning.synoptics.com (lightning.synoptics.com [134.177.3.18]) by nexen.nexen.com (8.6.12/8.6.12) with SMTP id VAA29721 for <rolc@nexen.com>; Tue, 24 Oct 1995 21:23:33 -0400
Received: from pobox.synoptics.com ([134.177.1.95]) by lightning.synoptics.com (4.1/SMI-4.1) id AA27019; Tue, 24 Oct 95 18:18:20 PDT
Received: from milliways-le0.engwest (milliways-le0.synoptics.com) by pobox.synoptics.com (4.1/SMI-4.1) id AA01181; Tue, 24 Oct 95 18:19:42 PDT
Received: by milliways-le0.engwest (4.1/SMI-4.1) id AA22267; Tue, 24 Oct 95 18:19:42 PDT
Date: Tue, 24 Oct 95 18:19:42 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Andrew Smith <asmith@baynetworks.com>
Message-Id: <9510250119.AA22267@milliways-le0.engwest>
To: yakov@cisco.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
Cc: rolc@nexen.com
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/

> From yakov@cisco.com Tue Oct 24 17:13:09 1995
> To: asmith@BayNetworks.COM (Andrew Smith)
> Cc: rolc@nexen.com
> Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt 
> Date: Tue, 24 Oct 95 17:09:30 PDT
> From: Yakov Rekhter <yakov@cisco.com>

Yakov,

> > > The belief that ATM SVCs are more desirable than multiple IP
> > > hops is one that is in line with the objectives of ROLC.
> > 
> > I disagree: I thought the objective of ROLC was to provide a protocol mechanism 
> > which would *allow* for shortcut VCCs. There is nothing in the ROLC charter (and
> > there is certainly nothing in the NHRP draft) about whether that is always 
> > the desirable outcome or not. The charter needs updating if you think that this
> > assumption is an implicit part of ROLC's work.
> 
> While it would be hard to say that the ATM SVCs are *always* more desirable,
> I think it would be fair to say that there are QoS requirements where ATM SVC
> would be preferred to IP hop-by-hop resource reservations.  It all depends
> on the QoS requirements.

You are missing my point: Dilip asserted that "ATM SVCs are more desirable ...".
All I am saying is that "ATM SVCs may be more desirable in some cases ...". 
It would be useful to know whether other rolc listeners are assuming what Dilip
asserted to be true or not.

BTW, this is really an int-serv or ip-atm issue just as much as a rolc issue.


Andrew


********************************************************************************
Andrew Smith					TEL:	+1 408 764 1574
Technology Synergy Unit				FAX:	+1 408 988 5525
Bay Networks, Inc.				E-m:	asmith@baynetworks.com
Santa Clara, CA
********************************************************************************