Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!CHEETAH.NYSER.NET!mrose
From: mrose@CHEETAH.NYSER.NET (Marshall Rose)
Newsgroups: comp.protocols.iso.dev-environ
Subject: Re: Encoding RFC1006 Addresses
Message-ID: <27027.632598415@cheetah.nyser.net>
Date: 17 Jan 90 17:46:55 GMT
References: <9001171721.AA07180@rhino.ncsl.nist.gov>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: isode@nic.ddn.mil
Distribution: inet
Organization: The Internet
Lines: 22

The algorithmic interpretation of interim network addresses is fully
implemented in ISODE 6.0.

Basically, if you look at Kille's format, you notice that there is a
community name field that is a number.  In 5.0, this was the only format
understood and the number mapped to a TS-stack.

Further, in 6.0, the ISODE lets you define your own formats (within
certain limits), and as a part of that you define the community name and
the TS-stack to use.

With this, you now have a fairly generic approach.  For example, if you
have an isolated TCP/IP LAN, you can easily define an OSI community for
it.

As an application process, you are supposed to treat network addresses
as opaque.

I suggest you read the 6.0 documentation set (when 6.0 is out next week)
to get the answers to the rest of your questions.

/mtr