🚀 go-pugleaf

Actually, my original post was not purely academic. I do indeed need to
transport IP traffic across a network that only understands ISO. In fact,
I also need to be able to transport DECnet (phase IV), IPX, XNS, ... across
the same network.

AT&T Tridom provides satellite communications products and services using
VSAT technology. Our satellite network is based on routers that run CLNP at
the network level and proprietary, satellite-related data link protocols.

VSAT networks are usually economically justifiable only for customers with a 
lot of remote sites (hundreds, thousands, and more). Historically, therefore,
our data communications services have concentrated on SNA. Most organizations
with that many sites have, in the past, been true blue. (Yes, the functions
that cisco, etc. are bragging about -- routing SDLC traffic across a router-
based WAN -- we've been doing for years.)

We've now added support for LAN routing to our product line. Since we can't
make all of our nodes understand IP, DECnet, IPX, XNS, ..., we have to 
encapsulate these other protocols within CLNP. (To use IP as an example,
we could not even get a large enough address space to give all our nodes
IP addresses.)

Our current method for encapsulating these protocols is to use "well-known"
Transport selectors and the ISO connectionless transport protocol. I posted
my question orginally to find out if there were any other implementations that
solved the same problem in different ways. I was particularly hoping for
a response from DEC, since DEC has to have solved this problem with 
AdvantageNetworks (unless their TCP/IP support is still just vaporware). If
another vendor or product uses a different encapsulation, I would be interested
in exploring what it would take to make our products interoperate.