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

Yakov Rekhter <yakov@cisco.com> Wed, 25 October 1995 00:41 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa24462; 24 Oct 95 20:41 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa24456; 24 Oct 95 20:41 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id UAA11862; Tue, 24 Oct 1995 20:04:41 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id UAA18071 for rolc-out; Tue, 24 Oct 1995 20:14:08 -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 UAA18062 for <rolc@nexen.com>; Tue, 24 Oct 1995 20:14:05 -0400
Received: from hubbub.cisco.com (hubbub.cisco.com [198.92.30.32]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id UAA11850 for <rolc@nexen.com>; Tue, 24 Oct 1995 20:02:57 -0400
Received: from puli.cisco.com (puli.cisco.com [171.69.1.174]) by hubbub.cisco.com (8.6.12/CISCO.GATE.1.1) with SMTP id RAA29542; Tue, 24 Oct 1995 17:09:30 -0700
Message-Id: <199510250009.RAA29542@hubbub.cisco.com>
To: Andrew Smith <asmith@baynetworks.com>
cc: rolc@nexen.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
In-reply-to: Your message of "Tue, 24 Oct 95 15:23:36 PDT." <9510242223.AA22044@milliways-le0.engwest>
Date: Tue, 24 Oct 95 17:09:30 PDT
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Yakov Rekhter <yakov@cisco.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/

Andrew,

> > 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.

> I repeat, this draft is an architectural draft with much wider implications
> than the narrow focus of ROLC. That was the gist of my previous posting
> asking that this draft be posted much more widely than just the ROLC group.
> There is an implicit assumption being made that this draft represents the 
> views of the IAB (same as 1620), not just the ROLC group. 

The only correlation between this I-D and the IAB is that one of the co-authors
of this document (myself) is an IAB member. So, would you also implicitly
assume that all the other I-Ds I authored/co-authored represent the views of the
IAB ? 

Yakov.