IETF Logo Mail Archive

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

Yakov Rekhter <yakov@cisco.com> Thu, 26 October 1995 20:35 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa23631; 26 Oct 95 16:35 EDT
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa23627; 26 Oct 95 16:35 EDT
Received: from maelstrom.nexen.com ([204.249.99.5]) by guelah.nexen.com (8.6.12/8.6.12) with ESMTP id QAA28150; Thu, 26 Oct 1995 16:09:42 -0400
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id QAA14257 for rolc-out; Thu, 26 Oct 1995 16:19:31 -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 QAA14248 for <rolc@nexen.com>; Thu, 26 Oct 1995 16:19:28 -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 QAA28133 for <rolc@nexen.com>; Thu, 26 Oct 1995 16:07:59 -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 NAA28419; Thu, 26 Oct 1995 13:15:17 -0700
Message-Id: <199510262015.NAA28419@hubbub.cisco.com>
To: curtis@ans.net
cc: rolc@nexen.com
Subject: Re: Last Call for draft-ietf-rolc-apr-00.txt
In-reply-to: Your message of "Thu, 26 Oct 95 15:18:36 EDT." <199510261918.PAA23759@brookfield.ans.net>
Date: Thu, 26 Oct 1995 13:15:17 -0700
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/

Curtis,

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

Agreed. We are working on a revised document that would reflect this.

Yakov.

v2.23.0 | Report a Bug | By Email