IETF Logo Mail Archive

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

Tim Salo <salo@msc.edu> Thu, 26 October 1995 03:50 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03751; 25 Oct 95 23:50 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa03742; 25 Oct 95 23:50 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id XAA21428; Wed, 25 Oct 1995 23:16:44 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id XAA03406 for rolc-out; Wed, 25 Oct 1995 23:27:44 -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 XAA03397 for <rolc@nexen.com>; Wed, 25 Oct 1995 23:27:41 -0400
Received: from noc.msc.edu (noc.msc.edu [137.66.12.254]) by guelah.nexen.com (8.6.12/8.6.12) with SMTP id XAA21424 for <rolc@nexen.com>; Wed, 25 Oct 1995 23:16:20 -0400
Received: from uh.msc.edu by noc.msc.edu (5.65/MSC/v3.0.1(920324)) id AA15846; Wed, 25 Oct 95 22:24:03 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tim Salo <salo@msc.edu>
Received: (salo@localhost) by uh.msc.edu (8.7.1/8.6.6) id WAA04904; Wed, 25 Oct 1995 22:24:03 -0500 (CDT)
Date: Wed, 25 Oct 1995 22:24:03 -0500 (CDT)
Message-Id: <199510260324.WAA04904@uh.msc.edu>
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/

> To: curtis@ans.net
> Cc: rolc@nexen.com
> Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt 
> Date: Wed, 25 Oct 95 19:31:00 PDT
> From: Yakov Rekhter <yakov@cisco.com>
> 	[...]
> And I'd like to finess the issue of whether this control is done directly
> or indirectly. I think it should be sufficient if we'll just say that
> "SVC management should be driven by the QoS and/or traffic requriements
> of the application".

In an environment where some SVCs cost money and others don't, _products_
will need to ensure that SVC management takes costs into account.

Whether or not this _product_ requirement receives support from
_architectural_ requirements remains to be seen.

-tjs

v2.8.7 | Report a Bug | By Email