HDTenEightyP/NetNews huggingface dataset:
From: bob1@cos.com (Bob Blackshaw)
Newsgroups: comp.protocols.iso
Subject: Re: Two questions..
Date: 16 Oct 92 13:24:29 GMT
Organization: Corporation for Open Systems

In <1992Oct15.213513.4034@chsun.chuug.ch> mpeters@pax.eunet.ch (MBX Michael Peters) writes:

>Can somebody give me a one line definition of what the difference between
>X.25 and X.75? As near as I can gather (I don't have CCITT red books) it 
>lies in the fact that X.75 is a network to network X.25. 

You win the teddy bear. :-) Yes, X.75 was designed to operate
between two packet networks while X.25 is user-network. Now it
has been a few years, but X.75 includes a multi-link procedure
at layer 2 (link level) which is basically an inverse mux. With
this, the network operators can combine several data links to
increase throughput, and also make the link more reliable.

>What I really need to know, is there any appreciable difference besides the
>international calling procedure in X.75?

As I said, haven't looked at X.25 since 1984, so maybe they have
added the multi-link procedure to it as well, but that was the
only basic difference in addition to the calling.

>2nd question is methods of throughput computation. If you've got a router
>with say 20 ports at 19.2kbs max. What is the throughput? (WAN router for
>X.25, SNA SDLC, and ASYNC, for example) 

>I've heard some people say 650pps. Others say 16 ports at 64kps is 1000. Is
>it just the packet size you pick? And, if so, what is typical packet size
>for the above example (64 bytes seems way to small)? 

That is rather small, when we started DATApac in Canada there were
two sizes. 128 bytes was for international (cause that was the CCITT
setting) and 256 bytes was the national and normal size. Interestingly
enough, that is why the ISDN D-channel is set at 260 bytes - so that
it can take a 256 byte packet plus the 4 byte header.


>Okay, so it's more than one quetion, but hey..

>Oh, don't flame the sig.. I just wanted to try it out okay. (4 line, I know.)

>Thanx in advance, 
>Mike.

>BTW If anybody knows a group that these types of questions might be more
>appropriate let me know that too. B`> (I broke my nose last week!!)

Sorry about your pretty bipe :-)

Bob
Newsgroups: comp.protocols.iso
From: bob1@cos.com (Bob Blackshaw)
Subject: Re: X200?
Organization: Corporation for Open Systems
Distribution: world 
Date: Tue, 13 Oct 1992 21:16:58 GMT

In <BvyDrp.1n3@immd4.informatik.uni-erlangen.de> mskuhn@immd4.informatik.uni-erlangen.de (Markus Kuhn) writes:

>kbs@ccr-p6.ccr.jussieu.fr (An OCR-IP fan) writes:

>>Apart from asking you what is X200 8)

>X.200 is the CCITT standard describing the OSI Reference Model
>(the famous seven layers of networking). The whole X.2?? series of
>recommendations describe the OSI protocols, ASN.1, etc. There are
>equivalent versions of these standards from ISO.

As a matter of fact, except for the CCITT boilerplate, X.200 is
identical with IS 7498, at least it was in 1984 when I was the
editor of X.200. The advantage of the CCITT versions is, as
Markus states, that they are all in the X.2nn series and are
likely to be contained in a single bluebook volume (read
cheaper :-) ).

>>I'd like to know where I can get info on 
>>ISO stacks and protocols.

>>Also is there a FAQ...

>I hope that most of your questions will be answered by the FAQ that I am
>preparing (it has already >600 lines :-). But I won't have the time to
>finish it in the next 3-4 weeks, so stay tuned ...

>You might of course use this time for reading a good book, eg.

>Marshall Rose, The Open Book
>Uyless Black, OSI -- A Model for Computer Comunication Standards
>Andrew Tannenbaum, Computer Networks

>Markus

Bob

Newsgroups: comp.protocols.iso
From: kenr@laibor-in-vain.ima.isc.com (Ken Rossen)
Subject: Re: X.500 DUA API
Reply-To: kenr@isc.com (Ken Rossen)
Organization: INTERACTIVE Systems Corporation
Date: Fri, 09 Oct 1992 14:07:50 GMT

In article <1992Oct9.043136.18295@mel.dit.csiro.au> brian@mel.dit.csiro.au  
(Brian May) writes about Directory APIs:

[...]
> From IEEE/POSIX
> 
> P1224		Generic OSI data management API
> P1003.17	X.500 API (which needs P1224)

In fact, as a result of realignment in the POSIX committee structure, the  
document previously knowns as P1003.17 will be instead published as IEEE  
standard 1224.2.  The draft 4 I have just been forwarded for review is marked  
this way.

Brian is correct that 1224 and 1224.2 are based on XOM and XDS.  However, the  
standard is in its very final stages of balloting and is being modified during  
this (?) month's meeting in Utrecht only in order to resolve oustanding ballot  
comments, so I would say it's relatively stable at this point, and looks a lot  
liek XDS.  

I am not a member of the 1003.17/1224.2 committee, but my information is fairly  
current.  

As to other Directory APIs, I know of no other standard DAP API in progress,  
but the "lightweight" access protocol LDAP being addressed in the IETF OSI-DS  
Working Group does include a correspondingly "lightweight" API.
--
KENR@ISC.COM	ANSI ASC X3T5.4 / OIW DS SIG
Newsgroups: comp.protocols.iso
From: brian@mel.dit.csiro.au (Brian May)
Subject: XOM and XDS - more info
Organization: CSIRO DIT (Melb.)
Date: Tue, 13 Oct 92 02:09:01 GMT


A couple of people have expressed interest in further explanation.  Most of
those are lucky enough to have the task of implementing (at least) XOM for
support of other X/Open APIs.

-----

First of all, a little about XOM - as all X/Open OSI Application APIs require
it.

The specification/definition for XOM is text based with C like definitions
of the functions.  The descriptions of those functions are fairly sparse and
leave a fair amount open to interpretation.  A very brief description 
follows.

Comments/corrections welcome.

XOM
---

XOM manages 'OSI' or 'ASN.1' data objects for an application API.  XOM has
2 different concepts of these objects which it calls PUBLIC and PRIVATE.

Public & Private objects
------------------------
PUBLIC objects are those which the client can modify the contents of.  
PUBLIC objects are basically arrays of descriptors (which hold type, syntax
and value of attributes).  This obviously makes insertion/deletion/allocation
of attributes within the object a pain!

A PRIVATE object's structure is implementation dependent.  Only the header
to an object must have a common structure.  The attribute descriptors can
be implemented any way you wish (eg doubly linked list).

Clients of this API can only use PUBLIC objects and have to create a PRIVATE
object, and subsequently take a PUBLIC copy for use.

EG.  When a DUA wishes to create a bind argument, it must first directly
use XOM to create the object, take a public copy of the object, then use
the XOM encode function before it can send the bind request via XDS and
the protocol stack.

OIDs and Class Tables
---------------------

XOM holds a _static_ class table containing all the OIDs it knows about.
If you want to dynamically use/create a new object, it'll have to be 
re-compiled into XOM's class tables.

Class table structure is left up to the implementor.

Encode/Decode
-------------

These merely create the relevant structures for sending/receiving ASN.1
data relevant to the protocol stack in use.  (We use PEPSY for ISODE)

Diagrams
--------

I have a couple of MacDraw diagrams available which show the relationship
between a DUA, XDS, XOM and a protocol stack (ISODE).  They are available
via anonymous ftp from:

mel.dit.csiro.au	 in the directory 	staff/brian/API

I'll put TIFF and PostScript versions there also.


---------------

brian
--
| Brian.May@mel.dit.csiro.au |           Open Systems Program           |
| CSIRO/DIT, 723 Swanston st | TEL +61 3 282 2613 -- FAX +61 3 282 2600 |
|Carlton, VIC 3053, Australia|          Experimental Scientist          |
Newsgroups: comp.protocols.iso
From: mskuhn@immd4.informatik.uni-erlangen.de (Markus Kuhn)
Subject: Re: X200?
Reply-To: mskuhn@immd4.informatik.uni-erlangen.de
Organization: CSD., University of Erlangen, Germany
Date: Sun, 11 Oct 1992 10:43:01 GMT

kbs@ccr-p6.ccr.jussieu.fr (An OCR-IP fan) writes:

>Apart from asking you what is X200 8)

X.200 is the CCITT standard describing the OSI Reference Model
(the famous seven layers of networking). The whole X.2?? series of
recommendations describe the OSI protocols, ASN.1, etc. There are
equivalent versions of these standards from ISO.

>I'd like to know where I can get info on 
>ISO stacks and protocols.

>Also is there a FAQ...

I hope that most of your questions will be answered by the FAQ that I am
preparing (it has already >600 lines :-). But I won't have the time to
finish it in the next 3-4 weeks, so stay tuned ...

You might of course use this time for reading a good book, eg.

Marshall Rose, The Open Book
Uyless Black, OSI -- A Model for Computer Comunication Standards
Andrew Tannenbaum, Computer Networks

Markus

-- 
Markus Kuhn, Computer Science student -=-=- University of Erlangen, Germany
Internet: mskuhn@immd4.informatik.uni-erlangen.de  |  X.500 entry available
-A distributed system is one in which the failure of a computer you didn't-
-even know existed can render your own computer unusable. (Leslie Lamport)-
Newsgroups: comp.protocols.iso
From: jdc@cyclone.mitre.org (John D. Cappelletti)
Subject: ADCCP - X.25
Organization: Mitre Corporation, McLean, VA
Date: Fri, 16 Oct 1992 19:16:36 GMT



I am looking for a bridge/gateway to interconnect equipment using X.25 and 
ADCCP (Advanced Data Communication Control Procedures) protocols.  
A commercial product is preferred but public domain is ok (even if it 
represents only a portion of the needed software).
If you can suggest a source, please drop me a note.

Thanks,

* John Cappelletti
* MITRE Corp.
* McLean Va.  USA
*
* tel:      (703) 883-6514
* ARPA-net: jcappell@mitre.org
From: dfauvarq@vulcain.France.Sun.COM (Daniel Fauvarque - Sun ICNC)
Newsgroups: comp.protocols.iso
Subject: Re: XOM and XDS - more info
Date: 16 Oct 92 00:08:31 GMT
Reply-To: dfauvarq@vulcain.France.Sun.COM
Organization: Sun Microsystems, Inc.
NNTP-Posting-Host: vulcain.france.sun.com

|> Encode/Decode
|> -------------
|> 
|> These merely create the relevant structures for sending/receiving ASN.1
|> data relevant to the protocol stack in use.  (We use PEPSY for ISODE)
|> 

As far as I know, the om_encode, om_decode functions are used only for transferring
an XOM ASN1 encoded object between two packages in the same application with the 
two packages written by different suppliers (they need to use the external ASN1 
representation to understand the content of the object).

The real encoding shall be performed automatically by the transfer functions
when you send your object to the remote.

On reception the reception function decodes the received object before to allow
the application to consult it.
Newsgroups: comp.protocols.iso
From: zpope@osf.org (William Pope)
Subject: Re: X.500 DUA API
Followup-To: comp.protocols.iso
Reply-To: zpope@osf.org
Organization: Open Software Foundation
Date: 8 Oct 92 10:23:18


In article <ctw-071092151351@bacchus.aero.org> ctw@aero.org (Charles Wolverton) writes:
>
>Other than the OSF's XDS, does anyone know of emerging "standard" APIs for
>X.500 DUAs?? (cf. MAPI, VIM, XAPIA for X.400.)

XDS and XOM are the work of X/Open.  The OSF DCE name service does support
the XDS API.  I know of no other standard X.500 API.

--
============================================================================
William Z. Pope                                     Phone: +1 (617) 621-8889 
Open Software Foundation                              Fax: +1 (617) 621-0584
11 Cambridge Center                                     Email: zpope@osf.org
Cambridge, MA  02142                             OSF DME Integration Project
From: ses@cmns-sun.think.com (Simon Edward Spero)
Newsgroups: comp.protocols.iso
Subject: Re: OSI Information Retrieval Protocol
Date: 7 Oct 92 13:47:36
Organization: What's your clearance, citizen?
NNTP-Posting-Host: cmns-sun.think.com
In-reply-to: mskuhn@cip.informatik.uni-erlangen.de's message of Wed, 7 Oct 1992 15:48:52 GMT

In article <BvrD9G.KpL@immd4.informatik.uni-erlangen.de> mskuhn@cip.informatik.uni-erlangen.de (Markus Kuhn) writes:
   Does anyone know the current status of

     ISO 10162     Bibliographic Search, Retrieval and Update Service
     ISO 10163     Bibliographic Search, Retrieval and Update Protocol

   and the technical contents of these standards? Is this the new version of the
   WAIS protocol (Z??.?? Sorry, I forgot the numbers)?

I'm not sure if the new version of SR has been balloted or not; SR is the
international version of NISO Z39.50/1992, possibly with a few minor 
differences (they are supposed to be interoperable, but there might be 
a little bit of overshoot). 

Apart from one project in Scandanavia, I thing that everybody is coding to 
Z39.50, not SR, so this is somewhat moot; the standard profile for running 
Z39.50 over TCP/IP is to discard the presentation and session layers, and 
transmit BER encoded PDUs over IP directly.

Z39.50 allows a client to search for and retrieve documents in a variety of
formats; originally intended to be used just to access library catalogs, it
now handles any kind of data, including full text and multi-media. 

The 1988 version of the protocol was used as the basis for WAIS, and has 
become one of the most widely installed (the most widely installed?) OSI
application layer protocols.


--
-----
Guest account at TMC 	|	Just Another  WAIS Hacker | DOD# 0612
Newsgroups: comp.protocols.iso
From: brian@mel.dit.csiro.au (Brian May)
Subject: XOM/XDS diagrams
Organization: CSIRO DIT (Melb.)
Date: Tue, 13 Oct 92 05:07:15 GMT


Apologies to those who just tried to ftp them.  Mac/Telnet problems have
delayed their transfer to a suitable ftp directory!

brian
--
| Brian.May@mel.dit.csiro.au |           Open Systems Program           |
| CSIRO/DIT, 723 Swanston st | TEL +61 3 282 2613 -- FAX +61 3 282 2600 |
|Carlton, VIC 3053, Australia|          Experimental Scientist          |
From: J.Crowcroft@cs.ucl.ac.uk (Jon Crowcroft)
Newsgroups: comp.protocols.iso
Subject: Re: Proposal: OSI Addressing on AARnet
Date: 12 Oct 92 16:23:51 GMT



 >megabyte of so of the big-internet archives before giving up but I didn't
 >see anything that looked promising. Looked to me like the anti-OSI
 >prejudices were so intense they are going to come up with some sort of
 >new ersatz IP that still won't scale, or, almost as bad, the US (and 
 >Australian) GOSIP WAN approach of running CLNP over a WAN. 

well, i think you should look furtehr through the big-internet
archives - there are several excellent proposals all of which will
scale to very large Internets - the problem is too many, not too
bad...
 
 >[Translation: Not just AARNET but also the Internet generally could do
 >with some research funds spent on how to upgrade and extend it and
 >increase its capacity. It won't happen without making use of the results
 >of research.]
 
well said! - the surpirsing success of the Internet was not least due
to DARPA forsoight in funding the bsd tcp/ip and other projects

maybe someone will do the same for IPv7 (or for clnp with 
go-faster/bigger-stripes)

some people say we just have to weait for ATM, but atm has none of the
dynamic routing or other level 3 services (or directory stuff) defined
at all...its just another subnet at the moment, so the same research
is needed to get it to come up to IP functionality in this sense ...
 jon
Xref: sparky comp.protocols.iso:1237 comp.protocols.misc:771 comp.protocols.nfs:2504 comp.protocols.tcp-ip:4664
From: mpeters@pax.eunet.ch (MBX Michael Peters)
Newsgroups: comp.protocols.iso
Subject: Two questions..
Date: 15 Oct 92 21:35:13 GMT
Organization: EUnet Login/Mailbox Service
X-Newsreader: Tin 1.1 PL3

Can somebody give me a one line definition of what the difference between
X.25 and X.75? As near as I can gather (I don't have CCITT red books) it 
lies in the fact that X.75 is a network to network X.25. 

What I really need to know, is there any appreciable difference besides the
international calling procedure in X.75?

2nd question is methods of throughput computation. If you've got a router
with say 20 ports at 19.2kbs max. What is the throughput? (WAN router for
X.25, SNA SDLC, and ASYNC, for example) 

I've heard some people say 650pps. Others say 16 ports at 64kps is 1000. Is
it just the packet size you pick? And, if so, what is typical packet size
for the above example (64 bytes seems way to small)? 

Okay, so it's more than one quetion, but hey..

Oh, don't flame the sig.. I just wanted to try it out okay. (4 line, I know.)

Thanx in advance, 
Mike.

BTW If anybody knows a group that these types of questions might be more
appropriate let me know that too. B`> (I broke my nose last week!!)

--
 \ Michael C. Peters / mpeters@pax.eunet.ch  \           _         ______ |
  \    V: 41 52 213 93 47                     \        /X25\___-=0`/|0`/__|     
   \  X.400 C=CH A=arCom P=EUnet O=EUnet       \_______\    USA   / | /    )
   /        OU=PAX S=mpeters                   /        `/-==__ _/__|/__=-|     
  /   Franklin Datacom, Inc.                  /         *             \ | |     
 / V: 1 805 373 8688  Fax: 1 805 373 7373    /                        (o)
Newsgroups: comp.protocols.iso
From: tain@wrench.bae.bellcore.com (Tai Nguyen)
Subject: Re: XOM and XDS - more info
Organization: Bell Communications Research
Date: Wed, 14 Oct 92 19:56:12 GMT

In article <1992Oct13.020901.3410@mel.dit.csiro.au>, brian@mel.dit.csiro.au (Brian May) writes:

  ... Stuff deleted 

|> 
|> OIDs and Class Tables
|> ---------------------
|> 
|> XOM holds a _static_ class table containing all the OIDs it knows about.
|> If you want to dynamically use/create a new object, it'll have to be 
|> re-compiled into XOM's class tables.
|> 
|> Class table structure is left up to the implementor.
|> 
|> Encode/Decode
|> -------------
|> 
|> These merely create the relevant structures for sending/receiving ASN.1
|> data relevant to the protocol stack in use.  (We use PEPSY for ISODE)
|> 

I think what said above is not enough.
The function om_encode must encode an OM object such that its peer can decode
it and its peer can use different stack. Thus, the encoding must be based on
ASN.1 syntax understood by both sides.

______________________________________________________________________________
Tai Nguyen				Email: ...!bae.bellcore.com!tain
Bell Communication Research 		Phone: (908) 699-7934
444 Hoes Lane Room RRC 1B210
Piscataway NJ, 08854
Newsgroups: comp.protocols.iso
From: ROESSLER@nvdv01.ind.e-technik.uni-stuttgart.de (GEORG ROESSLER)
Subject: Naming of application processes
Organization: University of Stuttgart, IND (FRG)
Date: Tue, 13 Oct 1992 10:01:03 GMT
X-News-Reader: VMS NEWS 1.23

The object definition for an application process in CCITT X.521 (object
definitions for the directory service) contains the attribute commonName, 
which should be used for naming, but there is no attribute APtitle.

I wonder about the relationship between commonName and APtitle. Are they
the same? Or is the APtitle simply missing in CCITT X.521?

In CCITT X.228 (ACSE) the ASN.1 definitions for APtitle and AEtitle are
left open. Is there any other standard that gives syntaxes for these
attributes?

Georg



-----------------------------------------------------------------------------
Georg Roessler
Institut fuer Nachrichtenvermittlung und Datenverarbeitung -- IND
Seidenstrasse 36  
W - 7000 Stuttgart 1
E-mail: S=roessler; OU=nvdv; OU=e-technik; P=uni-stuttgart; A=dbp; C=de
***  Sapientia prima est stultitia caruisse.   Christoph Martin Wieland  ***
From: uprao@mcl.ucsb.edu (Parik Rao)
Newsgroups: comp.protocols.snmp
Subject: HP OpenView 3.0 - automating startup
Date: 10 Oct 92 18:50:29 GMT
Reply-To: uprao@mcl.ucsb.edu
Organization: U.C. Santa Barbara


 Forgive me if the answer to this question is located somewhere in the
 manuals, but I'm getting eyestrain for poring over them (they are
 actually very good).  We're running an evaluation copy of OV 3.0
 (expires 12/05/92) and I was wondering if any of the experienced
 OpenViewer's know how to automate the startup procedure.

 Ideally, I would like a script, when run, that brings up OpenView,
 the default map, and then opens up a bunch of graphics, statistics,
 MIB walks, etc.  All pre-defined.  For example, on the current map,
 I would want it to automatically open up the IP sub-map, then
 the segment1 sub-map, and then automatically bring up the graph of
 interface traffic for Wabbit (an example machine/object).  

 I believe this may be possible thru manipulation of the .LRF files
 in the /usr/OV/lrf subdirectory, and will continue to look thru
 the manuals.  But if anyone has this sort of setup already done,
 I would love to know how.  It is to be used for a sales presentation,
 so a person could quickly run OV and bring up pertinent information
 without wasting time on highlighting objects, adding them to the
 selection list, etc., etc.

--
parik rao				        prao@cs.ucsb.edu or rao@cmc.com
Newsgroups: comp.protocols.snmp
From: chapin@ssvax.gte.com (Barry Chapin)
Subject: Info on SMP?
Organization: GTE/SCSD
Date: Mon, 12 Oct 1992 21:28:54 GMT

Hello,

Can someone let me know where to find information on SMP.
I looked at the ftp site, east coast, in the rfc and fyi directories,
in the index files, and found nothing about SMP.  I got the files,
and grep'ed them for SMP, but found nothing.  Thanks in advance.
I will post my results.  Please Email to me at
chapin%scsd@gte.com

Thanks again.
Barry Chapin
System Administrator
GTE Government Systems
Waltham, MA  02159    617-466-3464
"I am who I am"
From: hoffmann@sctc.com (Teri Hoffmann)
Newsgroups: comp.protocols.snmp
Subject: CORRECTION: SNMP DISC GROUP real addr
Date: 13 Oct 92 14:43:53 GMT
Article-I.D.: sctc.1992Oct13.144353.18061
Organization: SCTC

CORRECTION:
  I screwed up.  To be added to the SNMP discussion group,
do NOT send mail to the before mentioned address with help
as the subject line.  That group is getting flooded with mail.

  To be added to the discussion group, send mail to
     snmp-request@uu.psi.com and ask to be added to
     the snmp@uu.psi.com    list.

I apologize for all the problems.
Newsgroups: comp.protocols.snmp