HDTenEightyP/NetNews huggingface dataset:
From: tcheung@framsparc.ocf.llnl.gov (Terry C Cheung)
Newsgroups: comp.protocols.iso
Subject: Questions about Directory Bind Operation (X.500)
Keywords: X.500, ISODE, Bind
Date: 26 Jan 93 00:41:17 GMT
Followup-To: comp.protocols.iso
Organization: LLNL

Hi,

The APDU associated with the ISODE directory bind operation seems to
have an extra "CONTEXT 16" tag associated with the argument for bind.
(I've included part of an ISODE log file below)

While Section 11.2.1.1.1 of X.219 says that "the argument value of the 
bind-operation is mapped on the User Information parameter of the
services primitives, I couldn't find out exactly how the mapping
is done.  Does anyone know how the extra "context 16" tag get in
there and where in the standards is the mapping defined?

Thanks in advance.

--Terry

----------------Begin log file------------------
( UNIV SET
    ( CONT 0x0
        ( CONT 0x0 0x1
            0x01
        )
    )
    ( CONT 0x2
        ( CONT 0x4
            ( UNIV SEQ
                ( UNIV INT 0x1
                    0x01
                )
                ( UNIV OID 0x3
                    0x550901
                )
                ( UNIV SEQ
                    ( UNIV OID 0x2
                        0x5101
                    )
                )
            )
            ( UNIV SEQ
                ( UNIV INT 0x1
                    0x03
                )
                ( UNIV OID 0x4
                    0x52010001
                )
                ( UNIV SEQ
                    ( UNIV OID 0x2
                        0x5101
                    )
                )
            )
        )
        ( APPL 0x1
            ( UNIV SEQ
                ( UNIV INT 0x1
                    0x03
                )
                ( CONT 0x0
                    ( APPL 0x0
                        ( CONT 0x1
                            ( UNIV OID 0x3
                                0x550301
                            )
                        )
                        ( CONT 0x1e
                            ( UNIV EXTN
                                ( UNIV OID 0x2
                                    0x5101
                                )
                                ( UNIV INT 0x1
                                    0x01
                                )
                                ( CONT 0x0	      <-----Start of User
							    Information encoding
                                    ( CONT 0x10	      <-----Context 16 tag
                                        ( UNIV SET )  <-----Directory Bind
                                                            Argument
                                    )
                                )
                            )
                        )
                    )
                )
            )
        )
    )
)
--------------End log file

-- 
Terry Cheung
tcheung@ramius.ocf.llnl.gov
Newsgroups: comp.protocols.iso
From: rhp@base.bellcore.com (Randy Parker)
Subject: Re: CMIS get-response question - please help !
Organization: Bellcore, Livingston, NJ
Date: Wed, 27 Jan 93 15:14:53 GMT

|> 	The issue comes up when you have errors related to some attributes
|> of an object. If the answer to the question above is 'yes', one could send
|> back a 'GET-LIST-ERROR' as a CMIS-LINKED-REPLY. If the answer is 'no', one
|> has to send back a CMIS-SERVICE-ERROR if the reply involves one objext, but
|> a CMIS-LINKED-REPLY if the reply involves more than one object.
 
This issue came up during interoperability testing.  I do not believe there is
anything in the standard preventing you from sending the linked error rsp.

|> 	I like to have just one type of reply in this case and let that be
|> a CMIS-LINKED-REPLY whether the reply involves one object or more.

This is how the agent did it.  They used the process fail error instead of
the get list error.  I do not know if this was officially clarified (from ISO).
I can just say that my experience is that your interpretation is ok.
Newsgroups: comp.protocols.iso
From: harvey@mesa.cs.psu.edu (Alicia E Harvey)
Subject: Request for STREAMS under XTI/TLI.
Organization: Penn State Computer Science
Distribution: USA
Date: Mon, 25 Jan 1993 14:02:10 GMT

Hi.  I would like to find some code that utilizes STREAMS via either
the XTI or TLI interfaces.  Is anyone aware of where I could pick up
such a thing?

                        Thanks in advance,
                                        Alicia E. Harvey
                                        harvey@cs.psu.edu
From: ketil@edb.tih.no (Ketil Albertsen,TIH)
Newsgroups: comp.protocols.iso
Subject: Re: What is Q3?
Date: 27 Jan 93 07:38:00 GMT
Organization: T I H / T I S I P
Posting-Front-End: Winix Conference v 92.05.15  1.20 (running under MS-Windows)

In article <CMM.0.90.2.728041349.jon@gode.ifi.uio.no>, "Jon \\lnes" 
<jon@ifi.uio.no> writes:

>In article <1993Jan26.075848.28882W@lumina.edb.tih.no> ketil@edb.tih.no (Ketil 
>Albertsen,TIH) writes:

>> I suspect that the Q3 you are referring to is the *reference point* Q3, it
>> is not a standard itself, but defined by Q.941 or thereabouts (Q.94?).

>Wrong, although not entirely wrong. The base document to ce
>is CCITT's TMN (Telecommunications Management Network) architecture,
>described in the M.3010 document (formerly M.30). 

Mea culpa. I checked my stack of old notes, and a lot of the TMN stuff
WERE labelled Q.942. But those were 1987 working drafts, and the info was
reorganized (into the M series) before the 1988 CCITT pleanry assembly.

But:

>If two functional blocks are realized within one piece of equipment, the
>reference point between them is an internal interface, and its implementation
>is not standardized. If the blocks are in different pieces of equipment,
>the reference point must be realized as a standardized communication inter-
>face, denoted by a capitalization of the letter, e.g. 'Q3'.

Are you certain that you are not turning it upside-down? I have always
been told (by telecom people) that conceptual reference points are labelled
with uppercase letters, while physical interfaces are labelled with
lowercase ones. If you look in the ISDN standards, eg. I.210, the ref
points are consistenly called R, S, T (defining *functionality*); if an
NT2 and an operator TE1 is physically integrated you still have an S
reference point but no physical "s" interface. Or is it me turning it
around? (I am not a telecom man myself!)
Newsgroups: comp.protocols.iso
From: brian@mel.dit.csiro.au (Brian May)
Subject: OSI API list members uncontactable
Organization: CSIRO DIT (Melb.)
Date: Tue, 26 Jan 93 01:05:59 GMT


Hello,

Could listmembers

J.Wain@frec.bull.fr (Jez.Wain)        (mail bounced from chenas.inria.fr)
jliu%opencon.com@srmftp.psi.com (Jing Liu)

please contact me. The email addresses given to me are being refused
by the machines in question. Do you have suitable alternatives?

regards,

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: danielh@hpber199.swiss.hp.com (Daniel Huber)
Subject: What is Q3?
Date: Mon, 25 Jan 1993 06:38:11 GMT
Organization: Swiss Response Center
X-Newsreader: TIN [version 1.1 PL8.1]

Hi there,

As I know, Q3 is a CCITT standart for network management of
telecommunications environments.

Is there somwhere more info to find about this topic? Is there an RFC?
Is Q3 somehow related to CMIP or CMOT?

Thanks for any hint!

Regards

Daniel

--
Daniel Huber, RCO, HP Niederwangen (8700), Switzerland
SMTP: danielh@hpber010.swiss.hp.com (or Daniel_Huber@hp8700.hp.com)
X.400: /G=Daniel/S=Huber/OU=HP8700/O=HP/P=HP/A=ArCom/C=CH/
UNIX is the answer. What was the question?
From: J.Crowcroft@cs.ucl.ac.uk (Jon Crowcroft)
Newsgroups: comp.protocols.iso
Subject: standards - research, education & developement
Date: 28 Jan 93 17:10:57 GMT


as an academic researcher, i was amused recently to be giving a 
course on ISO standards  to a group of developers from
the computing and telecommunications industry, and having to come up
with excuses for the concrete baroqueness of ASN.1 and obfuscation
that is the Session Layer Protocol.

is there a FAQ or better still a Frequently Given Excuse for these?

 jon

Newsgroups: comp.protocols.iso
From: giand@opencon.com (Deepak S. Gianchandani)
Subject: Re: Where to get DIS 8886 and DIS 8802/2?
Followup-To: comp.protocols.iso
Summary: I also need to know
Organization: OpenCon Systems, Inc.
Date: Fri, 15 Jan 1993 22:18:17 GMT

In article <1993Jan12.011959.6718@mprgate.mpr.ca> dyck@mpr.ca (Trevor Dyck) writes:
>
>
>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.
>
>
>-- 
	I would also be intereseted in this; but I would like to
	limmit it to "ONLINE", ftp, etc.
	Thanks in advance.
	-Deepak

-- 
____________________   .    .   __         .       | Deepak S. Gianchandani
\___________________|) .____.--"--"---._____       | E-mail:giand@opencon.com
     .      ||       /_____/  NCC_1701  __/ .  . . |   To Boldly Go Where 
.       .   ||      /--/--._________.----/   .     | No One Has Gone BEFORE
Newsgroups: comp.protocols.iso
From: donp@novell.com (don provan)
Subject: Re: standards - research, education & developement
Organization: Novell, Inc., San Jose, California
Date: Thu, 28 Jan 1993 23:13:22 GMT

In article <3411@ucl-cs.uucp> J.Crowcroft@cs.ucl.ac.uk (Jon Crowcroft) writes:
>...come up with excuses for the concrete baroqueness of ASN.1...

So flexible it can handle anything that comes at it, even things
too complicated to understand or implement.

>...and obfuscation that is the Session Layer Protocol.

Error recovery features that would really knock your socks off if
everyone could justify the high cost of supporting them.

Don't bother thanking me.  I'm happy to help.
						don provan
						donp@novell.com
From: prabha@nsmdserv.CND.HP.COM (Prabha Chadayammuri)
Date: Tue, 26 Jan 1993 00:35:44 GMT
Subject: CMIS get-response question - please help !
Organization: HP Network and System Management Division
Newsgroups: comp.protocols.iso

Hi,
	Could one of you CMIS experts please clarify this, please ?

	Is it ok to send a linked-reply (followed by an end-of-replies)
back to a get-request that results in exactly one object ? That is after
scoping, there is one object on which to do the 'get'.

	The issue comes up when you have errors related to some attributes
of an object. If the answer to the question above is 'yes', one could send
back a 'GET-LIST-ERROR' as a CMIS-LINKED-REPLY. If the answer is 'no', one
has to send back a CMIS-SERVICE-ERROR if the reply involves one objext, but
a CMIS-LINKED-REPLY if the reply involves more than one object.

	I like to have just one type of reply in this case and let that be
a CMIS-LINKED-REPLY whether the reply involves one object or more.
Organization: Ege University - Computing Center
Date: Friday, 22 Jan 1993 14:52:00 TUR
From: Atilla OZERDIM <ATILLA@TREARN.BITNET>
Newsgroups: comp.protocols.iso
Subject:    test.. please ignore this

test...test...
From: cja@castle.ed.ac.uk (C Adie)
Newsgroups: comp.protocols.iso
Subject: DISTRIBUTED MULTIMEDIA SURVEY
Summary: Available now!
Date: 27 Jan 93 10:50:55 GMT
Organization: Edinburgh University


                      SURVEY OF NETWORKED MULTIMEDIA
                      ------------------------------

The survey of distributed multimedia comissioned by RARE, for which
information was solicited recently, has been completed.  The final
survey report is called:

"A Survey of Distributed Multimedia Research, Standards and Products",
First Edition, 25 January 1993. 

The final report contains responses received up to 22 January 1993.  It
is over 150 pages long, and contains information on over 50 research
projects, 40 standards and 35 products. 

By agreement with the chair of the RARE Multimedia Working Group, the
survey report is now available by anonymous ftp.  It may be found on:

           ftp.ed.ac.uk         129.215.146.5

in directory

           pub/mmsurvey

in files:

 mmsurvey.doc         Word for Windows 2 document (binary)
 mmsurvey.doc.Z       Compressed Word for Windows 2 document (binary)
 mmsurvey.ps          Postscript of document (ascii)
 mmsurvey.ps.Z        Compressed postscript of document (binary)
 mmsurvey.txt         Text form of document (ascii)
 mmsurvey.txt.Z       Compressed text form of document (binary)

Chris Adie                                   Phone:  +44 31 650 3363
Edinburgh University Computing Service       Fax:    +44 31 662 4809
University Library, George Square            Email:  C.J.Adie@edinburgh.ac.uk
Edinburgh EH8 9LJ, United Kingdom
Newsgroups: comp.protocols.iso
Newsgroups: comp.protocols.iso
Subject: TLI Programming on SunOS
From: lo@ipc5.lat.oz.au (Anthony C C Lo)
Date: Wed, 20 Jan 1993 04:32:01 GMT
Organization: Comp Sci, La Trobe Uni, Australia


Hello all,

Recently, I've been trying to write communication programs using the 
SunOS 4.1.1 Transport Layer Interface (TLI). I'm using asynchronous 
mode. The SunOS manuals mentioned about asynchronous execution mode,
and the examples given made some assumptions like "/dev/tivc" which
is fake. 

Does anybody have experience with this and be able to program the 
TLI? Any ideas and suggestions are most welcome.

Thanks in advance.


Anthony LO
Dept. of Computer Science &
Computer Engineering,
La Trobe University,
Bundoora 3083
Australia.

E-mail: lo@latcs1.lat.oz.au

Newsgroups: comp.protocols.iso
From: jose@nosc.mil (Jose R. Vazquez)
Subject: Help needed with Sun OSI package
Keywords: nsel
Organization: Naval Ocean Systems Center, San Diego, CA
Distribution: usa
Date: Thu, 28 Jan 1993 18:16:39 GMT

I'm having a problem converting an application that uses
TCP-IP to run under OSI.  I'm using SunNet OSI version 7.
I can open a socket but I can't bind it.  I always get
the following error:

    NSEL (0) is already in use => errno: 48

I'm following one their examples.  Some C code follows.

	.
	.
	.
/* Get socket */
if (sd = socket(AF_OSI, SOCK_DGRAM, OSIPROTO_IND) < 0 ) 
{
	perror("socket");
	exit(1);
}

/* Get NSEL from OSI address */

len = OSI_SAP_LEN(&my_addr, OSI_NSAP);
addr = OSI_SAP_ADDR(&my_addr, OSI_NSAP);
nsel = addr[len-1];

/* Set up adddresses and bind to the socket with src. */

if (bind(sd, (struct sockaddr *)&nsel, sizeof(nsel)) < 0 ) 
{
	printf("%s:\tNSEL (%d) is already in use => errno: %d\n",
		me, nsel, errno);
	close(sd);
	exit(1);
}
	.
	.
	.

my_addr already contain the right ISO address of the computer.
I didn't set-up the system, so, I'm not sure if the isoentities
file need to be modify.  Any help will be appreciated.

Thanks.

**************************************************************
*                           *                                *
* Jose R. Vazquez           * Phone: (619) 553-6337          *
* NCCOSC RDT&E DIV          * Email:                         *
* Code 847                  *        DDN: jose@nosc.mil      *
* San Diego, CA  92152-5000 *        UUCP: sdcsvax!nosc!jose *
*                           *                                *
**************************************************************
From: M.R.Schenk@research.ptt.nl (Mike Schenk +31 70 33 23926)
Newsgroups: comp.protocols.iso
Subject: Re: What is Q3?
Date: 27 Jan 93 18:39:59 GMT
Organization: PTT Research, The Netherlands
Originator: mrs@athena.research.ptt.nl

In article <1993Jan26.075848.28882W@lumina.edb.tih.no> ketil@edb.tih.no (Ketil Albertsen,TIH) writes:
>In article <C1ED3n.7yv@hpwin052.uksr.hp.com>, danielh@hpber199.swiss.hp.com 
>(Daniel Huber) writes:
>
>>As I know, Q3 is a CCITT standart for network management of
>>telecommunications environments.
>>
>I suspect that the Q3 you are referring to is the *reference point* Q3, it
>is not a standard itself, but defined by Q.941 or thereabouts (Q.94?).

No, this might seem trivial but it is not. The Q3 is an interface
whereas the reference point is called q3. (Capital Q versus little q)

The Q.xxx recommendation (can't check at home) describes protocol stacks
for the Q3 interface and not for the reference point. See also my
earlier posting for the difference between the reference point and the
interface (posted under the name of mschenk@research.ptt.nl because of a
change in posting software).

>There is also a Q1 and Q2 reference point. There is no connection between
>the Q in Q3 and the Q in Q.941, that is purely coincidal. (The I series
>recommendations define similar R, S and T reference points.)

The Q1 and Q2 interfaces are not used anymore. The Qx interface is.
>
>I do not have Q.941 available right now, but as far as I remember, Q3
>defines the lowest level functionality between a switch and an "MD" (Mediation
>Device, something like a concentrator), on the way to the management system,
>while Q1 is the functionality available at the user level system management.
>
>If you are not accustomed to reading CCITT recommendations, Q.94? is
>NOT the place to start!

You should try to get hold of M.3010 which defines the entire TMN
concept. This recommendation also refers to other documents.

	Mike
Newsgroups: comp.protocols.iso
From: mschenk@research.ptt.nl (Mike Schenk +31 70 33 23926)
Subject: Re: What is Q3?
Organization: PTT Research
Date: Mon, 25 Jan 1993 21:29:07 GMT

In article <C1ED3n.7yv@hpwin052.uksr.hp.com>, danielh@hpber199.swiss.hp.com (Daniel Huber) writes:
> Hi there,
> 
> As I know, Q3 is a CCITT standart for network management of
> telecommunications environments.

The q3-reference point is part of the concept of the
Telecommunications Management Network (TMN) as it is defined in
CCITT Recommendation M.3010. A q3-reference point "connects" two
function blocks. If these functions blocks are implemented in two
different physical systems (operations systems or network
elements) then the q3-refence points are implemented as a
Q3-interface. This interface takes care of the exchange of
management information between operations systems and network
elements. 

> Is there somwhere more info to find about this topic? Is there an RFC?

Yes, CCITT recommendation M.3010 and related recommendations. No  
there is no RFC since it is a CCITT recommendation.

> Is Q3 somehow related to CMIP or CMOT?

Yes it is. An OSI stack witk CMIP in layer 7 is used for a 
Q3-interface.

    Mike
Newsgroups: comp.protocols.iso
From: lochrin@titan.alcatel.oz.au (Nick Lochrin)
Subject: Re: What is Q3?
Organization: Alcatel Australia Limited, Alexandria
Date: Thu, 28 Jan 1993 03:22:22 GMT
Disclaimer: The views expressed herein are those of the author only

In article <C1ED3n.7yv@hpwin052.uksr.hp.com> danielh@hpber199.swiss.hp.com (Daniel Huber) writes:
>Hi there,
>
>As I know, Q3 is a CCITT standart for network management of
>telecommunications environments.
>
>Is there somwhere more info to find about this topic? Is there an RFC?
>Is Q3 somehow related to CMIP or CMOT?
>

Please refer to following ISO/OSI Standards:
	M.3010	Principles for a telecommunications management network
	M.3020	TMN interface specification methodology
	M.3100	Generic network information model
	M.3180	Catalogue of TMN management information
	M.3200	TMN Management service overview
	M.3300	TMN Management facilities presented at the F interface
	M.3400	TMN Management functions

regards,
Nique.
-- 
Nick Lochrin                 nick@titan.alcatel.oz.au
Alcatel Australia Limited    ...!uunet!titan.alcatel.oz!nick
252-280 Botany Road,         nick%titan.alcatel.oz@uunet.UU.NET
ALEXANDRIA  NSW  2015        Alcanet memo: AALC.LOCHRINN
Newsgroups: comp.protocols.iso
From: ketil@edb.tih.no (Ketil Albertsen,TIH)
Subject: Re: What is Q3?
Organization: T I H / T I S I P 
Posting-Front-End: Winix Conference v 92.05.15  1.20 (running under MS-Windows)
Date: Tue, 26 Jan 1993 07:58:43 GMT

In article <C1ED3n.7yv@hpwin052.uksr.hp.com>, danielh@hpber199.swiss.hp.com 
(Daniel Huber) writes:

>As I know, Q3 is a CCITT standart for network management of
>telecommunications environments.
>
>Is there somwhere more info to find about this topic? Is there an RFC?
>Is Q3 somehow related to CMIP or CMOT?

I suspect that the Q3 you are referring to is the *reference point* Q3, it
is not a standard itself, but defined by Q.941 or thereabouts (Q.94?).
There is also a Q1 and Q2 reference point. There is no connection between
the Q in Q3 and the Q in Q.941, that is purely coincidal. (The I series
recommendations define similar R, S and T reference points.)

I do not have Q.941 available right now, but as far as I remember, Q3
defines the lowest level functionality between a switch and an "MD" (Mediation
Device, something like a concentrator), on the way to the management system,
while Q1 is the functionality available at the user level system management.

If you are not accustomed to reading CCITT recommendations, Q.94? is
NOT the place to start!
Newsgroups: comp.protocols.iso
From: donp@novell.com (don provan)
Subject: Re: What is Q3?
Organization: Novell, Inc., San Jose, California
Date: Thu, 28 Jan 1993 07:35:12 GMT

In article <1993Jan27.183959.14698@spider.research.ptt.nl> M.R.Schenk@research.ptt.nl (Mike Schenk +31 70 33 23926) writes:
>No, this might seem trivial but it is not. The Q3 is an interface
>whereas the reference point is called q3. (Capital Q versus little q)

Just when i thought they couldn't possibly make things any more confusing....
Newsgroups: comp.protocols.snmp
From: klosp@rimail.interlan.com (Patrick Klos)
Subject: Looking for MOSY for DOS
Organization: Klos Technologies, Inc. (603) 424-0138
Date: Fri, 22 Jan 1993 20:04:52 GMT

I hope this isn't a FAQ, but if anyone can direct to a location where I can 
find MOSY (MIB compiler for DOS), I'd really appreciate it!

Patrick
========================================================================
        Patrick Klos                 Internet: klosp@rimail.interlan.com
        Klos Technologies, Inc.      Compuserve: 71521,145
        Voice: (603) 881-7777 FAX: (603) 881-7123
========================================================================
Newsgroups: comp.protocols.snmp