Re: int-serv over e.g. ATM
Lixia Zhang <lixia@parc.xerox.com> Tue, 07 November 1995 03:33 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa29217;
6 Nov 95 22:33 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa29213;
6 Nov 95 22:33 EST
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.99.5]) by
guelah.nexen.com (8.6.12/8.6.12) with ESMTP id UAA24064;
Mon, 6 Nov 1995 20:31:23 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id
UAA29484 for rolc-out; Mon, 6 Nov 1995 20:38:57 -0500
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 UAA29475;
Mon, 6 Nov 1995 20:38:54 -0500
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by
guelah.nexen.com (8.6.12/8.6.12) with SMTP id UAA23991;
Mon, 6 Nov 1995 20:25:17 -0500
Received: from redwing.parc.xerox.com ([13.2.116.19]) by alpha.xerox.com with
SMTP id <16563(4)>; Mon, 6 Nov 1995 17:32:27 PST
Received: by redwing.parc.xerox.com id <177521>; Mon, 6 Nov 1995 17:32:08 -0800
Date: Mon, 6 Nov 1995 17:31:56 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Lixia Zhang <lixia@parc.xerox.com>
To: owner-rolc@nexen.com
Cc: berson@isi.edu, mwg@faline.bellcore.com, int-serv@isi.edu,
rolc@nexen.com, rsvp@isi.edu
Subject: Re: int-serv over e.g. ATM
In-Reply-To: Your message of Mon, 6 Nov 1995 15:59:15 -0800
Message-ID: <CMM.0.88.815707916.lixia@parc.xerox.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/
> The RSVP group at ISI is looking at these issues. Right now we are
> concentrating on the second issue ("reference configurations" other
> than #1). We will be talking about our status in the IP over ATM
> working group meeting at the Dallas IETF.
>
> Steve:
>
> Now that's interesting, since I've always thought IP QoS over ATM
> was an INT SERV problem to solve. Basically RSVP (like any other
> reservation protocol) tells the IP layer what service it wants, and the
> IP layer negotiates with ATM to get the right thing underneath.
>
> Why is RSVP directly involved with ATM? (I'm curious here, not
> trying to pick a turf war -- trying to understand where our architectural
> views differ).
Craig,
Notice that he said the "RSVP group at ISI", not RSVP WG.
I assume it is an ISI internal work.
Lixia
- int-serv over e.g. ATM Mark W Garrett
- Re: int-serv over e.g. ATM berson
- Re: int-serv over e.g. ATM Craig Partridge
- Re: int-serv over e.g. ATM Craig Partridge
- Re: int-serv over e.g. ATM Curtis Villamizar
- Re: int-serv over e.g. ATM berson
- Re: int-serv over e.g. ATM Lixia Zhang
- Re: int-serv over e.g. ATM Steve Deering
- Re: int-serv over e.g. ATM Alagu Periyannan
- Re: int-serv over e.g. ATM Mark W Garrett
- Re: int-serv over e.g. ATM Walter Milliken
- Re: int-serv over e.g. ATM Steve Deering
- Re: int-serv over e.g. ATM Mark W Garrett
- Re: int-serv over e.g. ATM Juha Heinanen
- Re[2]: int-serv over e.g. ATM Charlie Tai
- Re: int-serv over e.g. ATM Curtis Villamizar
- Re: int-serv over e.g. ATM Juha Heinanen
- Re: int-serv over e.g. ATM Mark W Garrett
- Re: int-serv over e.g. ATM Juha Heinanen
- Re: int-serv over e.g. ATM Jon Crowcroft
- Re: int-serv over e.g. ATM Juha Heinanen
- Re: int-serv over e.g. ATM Jon Crowcroft
- Re: int-serv over e.g. ATM Curtis Villamizar
- Re: int-serv over e.g. ATM John Krawczyk
- Re: int-serv over e.g. ATM Noel Chiappa
- Re: int-serv over e.g. ATM Andrew Smith
- Re: int-serv over e.g. ATM Andrew Smith
- Re: int-serv over e.g. ATM Curtis Villamizar