Re: int-serv over e.g. ATM

Steve Deering <deering@parc.xerox.com> Wed, 08 November 1995 06:41 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa06146; 8 Nov 95 1:41 EST
Received: from guelah.nexen.com by IETF.CNRI.Reston.VA.US id aa06141; 8 Nov 95 1:41 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 BAA01218; Wed, 8 Nov 1995 01:13:08 -0500
Received: (from root@localhost) by maelstrom.nexen.com (8.6.12/8.6.12) id BAA14200 for rolc-out; Wed, 8 Nov 1995 01:20:33 -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 BAA14180 for <rolc@nexen.com>; Wed, 8 Nov 1995 01:19:48 -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 BAA01206 for <rolc@nexen.com>; Wed, 8 Nov 1995 01:05:57 -0500
Received: from digit.parc.xerox.com ([13.2.117.114]) by alpha.xerox.com with SMTP id <16042(6)>; Tue, 7 Nov 1995 22:14:23 PST
Received: from localhost by digit.parc.xerox.com with SMTP id <75270>; Tue, 7 Nov 1995 22:14:15 -0800
To: Mark W Garrett <mwg@faline.bellcore.com>
Cc: int-serv@isi.edu, rolc@nexen.com, rsvp@isi.edu, deering@parc.xerox.com
Subject: Re: int-serv over e.g. ATM
In-reply-to: mwg's message of Tue, 07 Nov 95 08:31:57 -0800. <199511071631.LAA26738@faline.bellcore.com>
Date: Tue, 7 Nov 1995 22:14:13 PST
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Deering <deering@parc.xerox.com>
Message-Id: <95Nov7.221415pst.75270@digit.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/

Mark,

> ...The only way to get productive, I think, is to go through a bit of
> identifying the obvious.

Good.  I was worried that you might take offence at me stating the obvious
(at least, what I hoped was the obvious).

> For example, one of the logical conclusions [of the pure IP model] is
> that ATM is just another subnet du jour. ...  While ATM *can* be
> deployed that way, it is also expected to be deployed in ways that
> will challenge the subnet model.  Imagine ATM LANs connected to ATM
> public networks with ATM over satellite to the All-Europe ATM cloud,
> with connections to the proper Internet at multiple points.  As a
> subnet, it's not pretty.

It's not especially uglier than any other VC-oriented, large-cloud
technology, like X.25 or ISDN.

>  Maybe we can ignore this aspect of ATM, or maybe some small but elegant
> feature in the routing tables will make it all work right, but I'm not
> prepared to call it a non-problem.

What's your idea of "working right"?  Why should the Internet architecture
be changed to accommodate ATM, when we didn't feel compelled to change it
to accommodate X.25 or ISDN?  What's so special about ATM that should
cause us to treat it as anything *other* than just another subnet du jour?

> Again, I probably don't have the best vocabulary handy for this, but I
> would recommend a distinction between the piece of the "IP layer" that
> slaps a header on the data and forwards it through the network, and
> the function in the router (or elsewhere) that receives an RSVP
> message and translates it appropriately into control messages (i.e.
> other than encapsulated user data) for the next subnet.  OK (reading
> another message), you're calling this "the subnet interface".  Still,
> the name doesn't strongly distinguish between "in the data path" and not.

I agree with your distinction.  In my previous message, I used the phrase
"the module that processes RSVP", as an attempt to avoid layer connotations.
Does that help?

Steve