Re: Last Call for draft-ietf-rolc-apr-00.txt
Curtis Villamizar <curtis@ans.net> Thu, 26 October 1995 19:38 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa21894; 26 Oct 95 15:38 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa21888; 26 Oct 95 15:38 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id PAA27500; Thu, 26 Oct 1995 15:09:38 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id PAA13455 for rolc-out; Thu, 26 Oct 1995 15:18:41 -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 PAA13439 for <rolc@nexen.com>; Thu, 26 Oct 1995 15:18:37 -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 PAA27476 for <rolc@nexen.com>; Thu, 26 Oct 1995 15:07:07 -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 PAA23759; Thu, 26 Oct 1995 15:18:37 -0400
Message-Id: <199510261918.PAA23759@brookfield.ans.net>
To: Yakov Rekhter <yakov@cisco.com>
cc: curtis@ans.net, 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:16:03 PDT." <199510261716.KAA09024@hubbub.cisco.com>
Date: Thu, 26 Oct 1995 15:18:36 -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 <199510261716.KAA09024@hubbub.cisco.com>, Yakov Rekhter writes: > Curtis, > > > The remaining > > difference may be that I wish to document the desirable case to be a > > standardized parameterization which could be used to allow indirection > > in cases where it was needed. I'd like to document the case where no > > appropriate parameterization is available in a standard protocol > > making it necessary to restrict SVC management for an application > > class as a practical reality that is less desirable and hopefully > > temporary situation as the reservation parameterization can be > > expected to evolve slowly but steadily. Some vendors may decide they > > don't want their proprietary local/remote "trick" standardized. IMO > > the architecture document can acknowlege this (if you insist) but > > strongly discourage the practice. > > While I would agree with what you said here, I am not sure whether this > belongs to the APR document. So, I'd like to get a feedback from other > folks on the list whether they think this should be included in the > document, or whether this issue should be addressed in some other > WG, like rsvp or int-serv. > > Yakov. Then this document should be reviewed by those WGs as well since it relates to communicating QoS needs from the application in order to obtain specific service. It absolutely should NOT document the case where an application makes a direct SVC management decision as the default. If anything it should not mention that case at all, and simply describe the communication of application characteristics to another layer which can act on it directly or pass the information on through a reservation protocol. Then leave the details of characterizing the application and requirements to int-serv and the details of passing the information on to RSVP. It should not try to circumvent those efforts. Curtis
- Last Call for draft-ietf-rolc-apr-00.txt Andrew G. Malis
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Andrew Smith
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Dilip Kandlur
- Re: Last Call for draft-ietf-rolc-apr-00.txt Andrew Smith
- Re: Last Call for draft-ietf-rolc-apr-00.txt Dilip Kandlur
- Re: Last Call for draft-ietf-rolc-apr-00.txt Andrew Smith
- Re: Last Call for draft-ietf-rolc-apr-00.txt Dilip Kandlur
- Re: Last Call for draft-ietf-rolc-apr-00.txt Andrew Smith
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Andrew Smith
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Joel Halpern
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Steve Deering
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Tim Salo
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Tim Salo
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Tim Salo
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Juha Heinanen
- Re: Last Call for draft-ietf-rolc-apr-00.txt Juha Heinanen
- Re: Last Call for draft-ietf-rolc-apr-00.txt Juha Heinanen
- Re: Last Call for draft-ietf-rolc-apr-00.txt Juha Heinanen
- Re: Last Call for draft-ietf-rolc-apr-00.txt Juha Heinanen
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Lixia Zhang
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Juha Heinanen
- int-serv Cspecs (was Re: Last Call for draft-ietf… Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Hiroshi Esaki
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Joel Halpern
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Yakov Rekhter
- Re: Last Call for draft-ietf-rolc-apr-00.txt Fred Baker
- Re: Last Call for draft-ietf-rolc-apr-00.txt Fred Baker
- Re: Last Call for draft-ietf-rolc-apr-00.txt Andrew Smith
- Re: Last Call for draft-ietf-rolc-apr-00.txt Andrew G. Malis
- Re: Last Call for draft-ietf-rolc-apr-00.txt Curtis Villamizar
- Re: Last Call for draft-ietf-rolc-apr-00.txt Andrew Smith