HDTenEightyP/NetNews huggingface dataset:
From: john@citr.uq.oz.au (John Gottschalk)
Subject: Re: TCP/IP has SLIP, OSI has ???
Organization: Prentice Centre, University of Queensland
Date: Thu, 7 Jan 1993 03:03:51 GMT

roseberry@taney.uscghq.uscg.mil writes:


>	If there is a system running OSI in one location and another
>	system also running OSI in another location, is it possible
>	to do transfer files via FTAM (or send mail via X.400) using
>	something other than X.25 or a LAN ?

You could use ISDN, for example.

>	In other words is there something for making temporary connections
>	over phone lines for OSI much like SLIP does for TCP/IP (and
>	async DECNET does for DECNET) ?

I do not know much about it, but X.32 is a protocol for use over phone lines. 
My understanding is that it offers similar services to X.25 and so is
effectively a "dial-up X.25", and some telecommunications service providers
offer a service whereby you can access their X.25 network via X.32.


>	I understand that whatever connection is set up, it will be very
>	slow in comparison to X.25 or LAN.

>	Thanks for any answers.

>	- Bert Roseberry
>	  roseberry@taney.uscghq.uscg.mil


			-- regards, John Gottschalk

===================================================================== 
     John Gottschalk (john@citr.uq.oz.au) 
     Project Manager,
     Centre for Information Technology Research,
     The University of Queensland, 4072, 
     Brisbane, Queensland, Australia,
     +61 7 365 4321 (phone), +61 7 365 4399 (fax)
=====================================================================
From: roger@bjcong.bj.co.uk (ROGER JAMES)
Newsgroups: comp.protocols.iso
Subject: Re: TCP/IP has SLIP, OSI has ???
Date: 7 Jan 93 08:33:03 GMT
Reply-To: roger@bjcong.UUCP (ROGER JAMES)
Organization: Boldon James Limited (UK)

In article <1993Jan6.202505.26759@twg.com> david@twg.com (David Herron) writes:
>Conversion-With-Loss: Prohibited
>
>The fact that the APS Alliance (or so I understand) voted down a PPP
>based proposal at their meeting is alarming.  It would be synchronistically
>groovy if the ISO crowd would recognize the wide availablility of PPP
>and `allow' for TP0..4 to traverse PPP-OSI paths.  Since PPP supports
>

The APS alliance "voted down" OSI-PPP because we thought it would happen
anyway. If I remember the conference call correctly it will be mentioned
as one of the recommended profiles. The "voting down" was to do with
the technical group doing work on it, we will be working on other profiles.
-- 
roger@bj.co.uk
Newsgroups: comp.protocols.iso
From: hta@boheme.er.sintef.no (Harald Tveit Alvestrand)
Subject: Re: TCP/IP has SLIP, OSI has ???
Reply-To: harald.alvestrand@delab.sintef.no
Organization: SINTEF DELAB, Norway
Date: Wed, 6 Jan 93 09:06:27 GMT

There is the APS Alliance working on this problem.
Contact Frode Hernes <Frode.Hernes@maxware.noprmd.telemax.no> for details.

-- 
                   Harald Tveit Alvestrand
Harald.Alvestrand@delab.sintef.no
C=no;PRMD=uninett;O=sintef;OU=delab;S=alvestrand;G=harald
+47 7 59 70 94
Newsgroups: comp.protocols.iso
Subject: DEC OSI Application Developers Toolkit
From: srajen@cstp.umkc.edu (Saravanakumar Rajendran)
Date: 8 Jan 1993 22:21:15 GMT
Distribution: world
Organization: University of Missouri Kansas City
Keywords: OSI, DEC OSAK, APIs
NNTP-Posting-Host: eos.umkc.edu
Originator: srajen@eos.cstp.umkc.edu

Hi everyone,

	I have few basic questions about the DEC OSI Application Developers
	Toolkit (In DEC literature, it is called as DEC OSI Applications Kernel
	(OSAK) Interface).  Has anyone had some experience with this product?
	If so, please reply to me by email and I need some help badly.

	Thanks in advance,

-- Saravan.

Saravanakumar Rajendran		|	BELLNET : (816)-235-2996
OSI Lab, Dept. of Comp. Science	|	INTERNET: srajen@cstp.umkc.edu
Univ. Of Missouri-Kansas City	|	USnail	: 4747 Troost # 222
				|	 	  Kansas City MO 64110.

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

Saravanakumar Rajendran		|	BELLNET : (816)-235-2996
Research Associate		|	BITNET	: srajen@UMKCVAX2
From: unrza3@cd4680fs.rrze.uni-erlangen.de (Markus Kuhn)
Newsgroups: comp.protocols.iso
Subject: Re: DEFAULT attributes with OBJECT-CLASS macro in X.521
Date: 6 Jan 1993 15:37:24 +0100
Organization: Regionales Rechenzentrum Erlangen
Reply-To: mskuhn@immd4.informatik.uni-erlangen.de
NNTP-Posting-Host: cd4680fs.rrze.uni-erlangen.de

jpalme@dsv.SU.SE (Jacob Palme DSV) writes:

>Question: Is it possible, with this representation, to represent
>DEFAULT attributes, i.e. attributes which need not be included
>in the object, but which always must have a value, and where
>a default value, defined somewhere (where??) is used if the
>are not explicitly stored in the object.

>If not: How should the notation be extended to be able to
>handle DEFAULTed attributes?

Shall the values of these defauls be considered by DSAs, e.g. should they
be transmitted in answers to querries and should the default values be
considered in searches? This would be a major change in the current X.500
functionality, that could often break interoperability (which DSA knows about
default values and which one does not?).

If the values shall not be considered by DSAs, than the default values are
something that need not at all be known to the whole X.500 system. Then
default values are application specific. If one application considers the
absence of a certain attribute as an indicator for a default value, than
no other application of different type has to do this. E.g. if a group 
communication user agent interpretes the absence of an attribute
notInterestedInCommercialJunkMail = Yes as nIICJM = No, than my standard
person lookup user agent should not be forced to display the same
interpretation, as the interpretation of the default value is application
specific.

If you extend the CLASS notation by a DEFAULT part, than you should take
care in your notation, that it becomes obvious to which type of application
this default value is relevant. If the classes you define are only subclasses
relevant to your application, than there would be no problem, if the defaults 
are indicated in the CLASS macro notation.

BTW: X.500(92) will allow you to use default attribute inheritance for subtrees.
This is already common practice in some existing applications (e.g. QUIPU),
but still has to be standardized. Attribute inheritance might in some
situations be an alternative for DEFAULT values ...

Just a few ideas ...

Markus

BTW: Is there a more recent version of the X.gc standard available online?
The Microsoft RTF file that I have found is version 8 and perhaps already quite
out of date.

-- 
Markus Kuhn, Computer Science student -=-=- University of Erlangen, Germany
Internet: mskuhn@immd4.informatik.uni-erlangen.de  |  X.500 entry available
--- Wer, wie, was? Wieso, weshalb, warum? Wer nichts fragt bleibt dumm. ---
From: lagemaat@cs.utwente.nl (Jeroen van de Lagemaat)
Newsgroups: comp.protocols.iso
Subject: Re: Formal Specifications of ISO Protocols
Date: 6 Jan 93 09:21:56 GMT
Organization: University of Twente, Dept. of Computer Science


There are several "large" OSI LOTOS specs published as technical reports
by ISO.

ISO 10023 Transport service in LOTOS

I do not know the numbers of the specs in LOTOS of Transport protocol, Session
protocol, session service and network service, but they are there.

Furthermore, in an ESPRIT project we developed several specs of 
ISDN  L3, an ISDN application (small email facility in ISDN phone),
Transaction processing specs (ACSE, CCR, TP).

Regards

-- 
    ___
 __/   \__________  Jeroen van de Lagemaat    <lagemaat@cs.utwente.nl>
|  \___/          |         
|___     __   ___ | University of Twente     
| |  |  /  \ (__  | Tele-Informatics & Open Systems
| |__|__\__/____) | P.O. Box 217  NL-7500 AE Enschede  The Netherlands
|_________________| tel. +31 53 893684              tfx. +31 53 333815

                    Humour, you're making me laugh.
                                    - Herman Finkers, Dutch comedian -
Newsgroups: comp.protocols.iso
Subject: Estelle Specification of the ACSE protocol.
From: jira@elc1.lat.oz.au (Ajin Jirachiefpattana)
Date: Tue, 5 Jan 1993 06:20:19 GMT
Organization: Comp Sci, La Trobe Uni, Australia

Hi everybody,

I am looking for the complete Estelle specification of the ACSE
(Association Control Service Element) protocol. Any pointer would
be greatly appreciated.

Regards,

Ajin Jirachiefpattana,

jira@latcs1.lat.oz.au
Department of Computer Science & Computer Engineering,
La Trobe University,
Bundoora, Vic., 3083.
Australia.
From: unrza3@cd4680fs.rrze.uni-erlangen.de (Markus Kuhn)
Newsgroups: comp.protocols.iso
Subject: Re: TCP/IP has SLIP, OSI has ???
Date: 6 Jan 1993 15:11:10 +0100
Organization: Regionales Rechenzentrum Erlangen
Reply-To: mskuhn@immd4.informatik.uni-erlangen.de
NNTP-Posting-Host: cd4680fs.rrze.uni-erlangen.de

roseberry@taney.uscghq.uscg.mil writes:

>	If there is a system running OSI in one location and another
>	system also running OSI in another location, is it possible
>	to do transfer files via FTAM (or send mail via X.400) using
>	something other than X.25 or a LAN ?

>	In other words is there something for making temporary connections
>	over phone lines for OSI much like SLIP does for TCP/IP (and
>	async DECNET does for DECNET) ?

The next version of X.25 is said to include an async version of LAPB.
The async HDLC variant is already defined in the 1991 Version of 
ISO 3309, so I don't expect anything revolutionaly new in X.25(92). 
Contact me, if you want a short description of async HDLC framing.

If you want to use the telephone net for CONS, check ISO 10732. For
CONS over ISDN, look at ISO 9574. They mostly refer to X.25 and define
a few additional details.

A work group (APS Aliance) is working on additional specifications for
using X.400 over the telephone net. This will perhaps eventually result
in a CCITT standard. 

If you prefer CLNP, check the latest PPP version. It supports OSI in addition
to TCP/IP.

Markus

-- 
Markus Kuhn, Computer Science student -=-=- University of Erlangen, Germany
Internet: mskuhn@immd4.informatik.uni-erlangen.de  |  X.500 entry available
----- Anyone participating in the use of MS-DOS, Heroin or Cocaine is -----
---- simply not getting the most out of life possible. (Brian Downing) ----
From: sailesh@litsun.epfl.ch (Sailesh Chutani)
Newsgroups: comp.protocols.iso
Subject: question on performance and fault management in networks
Date: 8 Jan 93 15:40:42 GMT
Organization: Ecole polytechnique federale de Lausanne DI-LIT


 

Greetings !

I am trying to identify the problems that are considered to be the key
problems in the area of Network Management, going beyond CMIP, DME,
and SNMP etc.  In particular, I am focusing attention on fault and
performance management issues at the transport layer. I would 
like to hear from people who are working in the related areas
or have some experience and/or ideas on the topic that they would like to
share.

The problems of interest for example, could be related to :
	- abstractions used to describe the system
	- protocol design, specification, and validation techniques
	- modelling and statistical techniques
	- framework for dealing with incomplete and erroneous information
	  on problems
	- gathering and analyis of problem related data
	- automation of detection and recovery
	- design of suitable interfaces to aid discovery, diagnosis, and
	  recovery

I would prefer any feedback via e-mail. I shall post a summary
of the information thus collected.

Thanks for your help.

-Sailesh
From: cirpka@idca.tds.philips.nl (Jan R. Cirpka)
Newsgroups: comp.protocols.iso
Subject: Re: NetBIOS/SMB on top of CNLP/TP4
Date: 8 Jan 93 17:22:40 GMT

joet@digilog.UUCP (Joe Torjman) writes:

>i need protocol specifications for CNLP/TP4 on how it carries
>Microsoft's NetBios.  i believe this is how AT&T implements
>LAN Manager on top of ISO protocols.
>thanks.    Joe Torjman.

Yes, AT&T supports (probably among others) TOP NetBIOS, which
is a mappimng of NetBIOS on top of CLNP/TP4.

TOP NetBIOS is included next to the SMB protocols in

X/Open CAE (Common Application Environment) Specification:
Protocols for X/Open PC Interworking: SMB, Version 2
ISBN: 1 872630 45 6
X/Open Document # C209

This book is an excellent description of the SMB and LAN Manager
file- and print-sharing protocols and can be ordered at X/Open 

in the US:

X/Open Company Ltd.       or   X/Open Company Ltd.
1010 El Camino Real            3141 Fairview Park Drive
Suite 380                      Suite 670
Menlo Park, CA 94025           Falls Church, VA 22042-4501
Tel: (415) 323 7992            Tel: (703) 876 0044
Fax: (415) 323 8204            Fax: (703) 876 0050

in Europe:
X/Open Company Ltd.
Apex Plaza, Forbury Road
Reading, Berkshire RG1 1AX
United Kingdom

Tel: +44 734 508311
Fax: +44 734 500110

------------------------------------------------------------------------
Jan R. Cirpka                         Digital Equipment Enterprise bv
                                      PAPER MAIL:
TEL:       +31 55 433180               Dept. IISS/V1-A04
FAX:       +31 55 432103               P.O. Box 245
TELEX:     36345 PHLA NL               7300 AE Apeldoorn
                                       The Netherlands

EMAIL:                                VISIT AND COURIER ADDRESS: 
 Domain:   cirpka@idca.tds.philips.nl  Oude Apeldoornseweg 41-45
                                       7333 NR Apeldoorn
                                       The Netherlands
------------------------------------------------------------------------
From: joet@digilog.UUCP (Joe Torjman)
Newsgroups: comp.protocols.iso
Subject: NetBIOS/SMB on top of CNLP/TP4
Date: Wed, 06 Jan 93 09:47:53 EST
Organization: Digilog, Horsham PA

i need protocol specifications for CNLP/TP4 on how it carries
Microsoft's NetBios.  i believe this is how AT&T implements
LAN Manager on top of ISO protocols.
thanks.    Joe Torjman.
From: jpalme@dsv.SU.SE (Jacob Palme DSV)
Newsgroups: comp.protocols.iso
Subject: DEFAULT attributes with OBJECT-CLASS macro in X.521
Date: 6 Jan 93 10:01:07 GMT

X.521 uses the OBJECT-CLASS macro, an example is:

person OBJECT-CLASS
        SUBCLASS OF top
        MUST CONTAIN {
                commonName,
                surname}
        MAY CONTAIN {
                description,
                seeAlso,
                telephoneNumber,
                userPassword}
        ::= {objectClass 6}

Question: Is it possible, with this representation, to represent
DEFAULT attributes, i.e. attributes which need not be included
in the object, but which always must have a value, and where
a default value, defined somewhere (where??) is used if the
are not explicitly stored in the object.

If not: How should the notation be extended to be able to
handle DEFAULTed attributes?
Newsgroups: comp.protocols.iso
From: kremer@cs.utwente.nl (Harro Kremer)
Subject: Re: Formal Specifications of ISO Protocols
Organization: University of Twente, Dept. of Computer Science
Date: Tue, 5 Jan 1993 08:14:47 GMT

In article <C0C1FG.AL9@world.std.com>, hcb@world.std.com (Howard C Berkowitz)
writes:
|> Remember that the formal language specifications of such protocolos as
|> Transport are advisory.  The formal specification remains the natural
			        ^^^^^^
	What interpretation are you using here? Shouldn't this be "official"

|> language document, with all its ambiguities.

|> A compromise position may be to look at the abstract test suites,
|> written in TTCN, as a "more formal" specification which actually
|> will be used.  I recognize TTCN is an informal language and a cumbersome
|> one, but it does have somewhat more formalism than an English-language
|> specificatin.

[ Flames omitted ]
-- 
     ___            Harro Kremer                  <kremer@cs.utwente.nl>
 ___/   \_______
|   \___/       | Univ. of Twente,   Dept. Computer Science,  TIOS-group
| ___    _   __ | P.O. Box 217,   NL-7500 AE  Enschede,  The Netherlands
|  |  | / \ (_  |                 tel: +31 53 89 3703 fax: +31 53 333815
|  |  | \_/ __) | 
|_______________| Freedom's just another word for nothing left to loose.
                                   - Kris Kristofferson & Janis Joplin -
From: dyck@mpr.ca (Trevor Dyck)
Newsgroups: comp.protocols.iso
Subject: Where to get DIS 8886 and DIS 8802/2?
Date: 12 Jan 93 01:19:59 GMT
Organization: MPR Teltech Ltd., Burnaby, B.C., Canada



Hi!

Does anyone know where I can get 

	o ISO Data Link Service Definition DIS 8886
	o Logical Link Control DIS 8802/2 (LLC) 

An online source sould be great, but if you know where I can even get
printed copies of these draft standards, that is fine too.

Any info is GREATLY appreciated!!

Thanks,
Trevor.


-- 
Trevor Dyck (dyck@mpr.ca)      | "The number of Unix installations has grown 
Advanced Technology Division   |  to 10, with more expected" 
MPR Teltech Ltd. 	       |  -- The Unix Programmer's Manual, 2nd Edition,
8999 Nelson Way, Burnaby, BC   |     June, 1972 
Newsgroups: comp.protocols.snmp
From: johnb@kalpana.com (John Bartas)
Subject: Re: Standard MIB object ?
Organization: Kalpana Inc
Date: Wed, 6 Jan 93 00:49:27 GMT

In article <1i7tptINNbau@meaddata.meaddata.com> rfrink@meaddata.com (Rick Frink) writes:
>In article <1992Dec17.235732.25543@kalpana.com>, johnb@kalpana.com (John Bartas) writes:
>|> In article <1goqabINN84h@meaddata.meaddata.com> rfrink@meaddata.com (Rick Frink) writes:
>|> >   Why isn't the object 'collisions' part of either MIB I/II ?  It seems
>|> >   very basic, yet essential.  ( If collisions is not relevant, then either
>|> >   populate with something similar or nothing ).
>|> >
>|> 

<My response deleted>

>
>  By the way, does Kalpana implement the Ethernet MIB or something similar ?
>

Something similar. We have a enterprise MIB wich keeps  a table of stats
for each of the boxes ports. It is not quite the same as the Ethernet MIB
since we want to keep track of some things that a reqular MAC interface
wouldn't need to. If you want detailed info (ie a MIB) drop me a line and
I'll e-mail it.

>-- 
>Rick Frink                                              (513) 865-1645
>Mead Data Central                             Telecomm/Campus Networks
>P.O. Box 933                                       rfrink@meaddata.com
>Dayton, Ohio  45401                          ...!uunet!meaddata!rfrink

Cheers, 
-JB-

======================================================================
John Bartas                     | Disclaimer - I don't speak for Kalpana
Pricipal Software Engineer      | in any official capacity. I'm just
Kalpana, Inc. (408)988-1600x141 | an employee who reads the net.

"We have met the enemy, and he is us." -Pogo
From: smartin@Canada.lsil.com (Stephen Martin)
Newsgroups: comp.protocols.snmp
Subject: SNM Questions/Wish List
Date: 7 Jan 93 13:54:21 GMT
Distribution: comp
Organization: LSI Logic Corporation of Canada, Inc.

Here are a couple of things that I haven't been able to do in SNM. If there
is a way to do this could someone let me know, if not I hope someong from
Sun reads this group and takes them into consideration.

o The event form has two threshold values that you can set to generate the
  event, according to the manual if either of those thresholds is met the
  event is generated. What I would like is to get the event only if both are
  met.

o In the props you can tell SNM what to do when you receive a trap, this works
  but there does not seem to be any way to differentiate between different
  traps from differnet devices. Suppose you have a machine that keeps rebooting
  and you want to be specifically alerted when it does, you either get the
  same alert from any device that causes a trap or you have to go and
  disable traps on everything else.

o Better labeling of graphs or the facility to change the label of a graph
  under the props form.

o Access to resources so that you can control the size and colour of graphs
  from your .Xdefaults file.
--
---
Stephen Martin               -------    LSI Logic Corporation of Canada, Inc.
Phone: (416) 620-7400     LSI|LOGIC|    Suite 1110, 401 The West Mall,        
Fax:   (416) 620-5005        |     |    Etobicoke, Ontario, Canada.
Email: smartin@lsican.uucp   -------    M9C 5J5
 or    smartin@Canada.lsil.com
From: swilhelm@chnews  (Spence Wilhelm)
Newsgroups: comp.protocols.snmp
Subject: SVR4.1 mib
Date: Tue, 12 Jan 1993 16:24:06
Organization: Intel Corporation, Chandler, AZ
Distribution: inet
Reply-To: spence_s_wilhelm@fmccm.intel.com
NNTP-Posting-Host: notvms.intel.com
Keywords: SVR4
NNTP-Software: PC/TCP NNTP

Does anyone know what MIBs are available for UNIX SVR4.1?

Thanks,

Spence Wilhelm
Intel Corporation
From: afyke@orion.oac.uci.edu (Andrew Fyke)
Subject: Repeater MIB Tools
Newsgroups: comp.protocols.snmp
Organization: University of California, Irvine
Date: 10 Jan 93 01:14:31 GMT

Does anyone know of any Network Management Stations that
supports the Repeater MIB (RFC 1368)? We are looking for a
grphical user interface to use to monitor and control 
a device that supports this MIB.

Thanks in Advance,
Andy
afyke@orion.oac.uci.edu

Newsgroups: comp.protocols.snmp
From: chris@ods.com (Chris Atkins)
Subject: readOnly errors?
Organization: Optical Data Systems, Inc.
X-Newsreader: TIN [version 1.1 PL8]
Date: Mon, 4 Jan 1993 17:31:15 GMT


I have been working with several agents from multiple vendors and have seen a
common occurance of receiving noSuchName errors for set-requests when using
the read only community string.  Frequently, I try to perform sets on variables
with a community string which does not have the variable as read-write in the
associated community profile.  My first response is to validate the variable 
name and indices and retry the request.  Finally, I check the community string
and discover the true problem.

It seems that in the above situation that a more informative and correct 
approach would be to return a readOnly error.  Since a successful get-request
could be performed on the variable in the original community profile, the agent
is not identifying any new mib variable names and this would not appear to be
a security problem.

I then began looking for instruction on when the protocol specifies that a
readOnly error should be returned.  The Simple Book indicates that readOnly 
should be returned when "the requested operation tried to modify a variable 
that, according to the community profile, may not be written:".  This seems to
make sense.

I then began looking for an RFC supporting the above use of the readOnly error
status.  RFC 1157 indicates that readOnly is a valid error status, but in 
section 4.1.5 (The SetRequest-PDU) does not provide a rule for the receiving
entity to return a readOnly error.  In fact no mention is made as to when 
a readOnly error is to be returned.  This is the only error status which does
not have any mention of when it is to be returned.

My questions are:
1) Have I overlooked an RFC which specifies when to return readOnly errors?
2) if not, why is readOnly a valid value for ErrorStatus?

Chris Atkins
chris@ods.com
From: jwang@pyramid.com (Jiann Wang)
Newsgroups: comp.protocols.snmp
Subject: SNMP 1.0 and 2.0 releases
Date: 12 Jan 93 17:35:06 GMT
Distribution: usa
Organization: Pyramid Technology


Can anyone tell me what is the difference between CMU SNMP 1.0 and 2.0
releases ? What functions are in 2.0 but not in 1.0.
If possible, where I can find more information about this.
Thanks in advance.

--jwang--
jwang@pyramid.com
Newsgroups: comp.protocols.snmp