HDTenEightyP/NetNews huggingface dataset:
From: jcarroll@jacc.com (Jim Carroll)
Reply-To: jcarroll@jacc.com
Newsgroups: comp.protocols.iso.x400
Subject: Re: X400 Vendor in Western Canada      
Keywords: X400 Canada
Date: 18 Dec 92 13:16:50 GMT
Organization: J.A.CarrollConsulting

grant@shamin.genie.uottawa.ca (Grant Henderson @ MCRLab - University of Ottawa) once wrote....
>
>I am looking for the name and number of a company in Western Canada
>which is developing or has developed an X.400 product suite similar
>to ISOCOR's. I have been told that such a company exists and was 
>purchased by foreign investors in the past year. Unfortunately,
>my source could not remember the name of the company. 
>
>Thanks
>
>------------------------------------------------------------------------
>Grant Henderson                            grant@shamin.genie.uottawa.ca
>Multimedia Communications Research Lab            Ottawa, Ontario Canada
>Univerity of Ottawa                                       (613) 564-9247        


The company you are looking for is OSIWARE, at 4400 Dominion St. Suite
210, Burnaby BC. I don't have a phone number handy.
jc

----
        ____     ___ ___       Jim Carroll, J.A. Carroll Consulting
          / /\  /   /          _____________________________________
         / /__\/   /           Internet            jcarroll@jacc.com 
     \__/ /    \___\___        Voice or Fax        +1.416.855.2950   
                                  Mississauga, Ontario, Canada                                                
                                  (in the suburbs of Toronto)

Newsgroups: comp.protocols.iso.x400
From: lmiller@scum.ssc.gov (Lee Miller)
Subject: array
   Is there way to create a array in ASN1.  I know about set of and sequence of
Organization: Superconducting Super Collider Laboratory
Date: Fri, 11 Dec 1992 22:38:09 GMT

but create array of some primitive data type.

                 struct val
                    {
                    int value [100];
                      }

can this be done, makeing the array of int(s)

Thanks for anyhelp


lmiller@slug.ssc.gov


Lee Miller

Keywords: 

Newsgroups: comp.protocols.iso.x400
From: jdale@cos.com (John H. Dale)
Subject: Re: X.400 and multimedia mail
Keywords: X.400
Organization: Corporation for Open Systems
Date: Fri, 11 Dec 1992 19:51:01 GMT

In <Bz2nu0.LCM@wimsey.bc.ca> sl@wimsey.bc.ca (Stuart Lynne) writes:

>In article <1g4h48EINNt1v@uni-erlangen.de> mskuhn@immd4.informatik.uni-erlangen.de writes:
>>bakker@cs.rulimburg.nl (Harm Bakker) writes:
>>
>>  rare escape sequences, ...). Messages are streams of bytes delimited by
>>  length indicators, the easiest, most efficient and most robust
>>  method possible.

>Not too quible too much. But I'd hesitate to say that it's the easiest. 

>If a data producer must know exactly how much data he's going to produce
>he will have to buffer it before sending so he can count it. If you have a
>method of indicating end of data you can simply send it as you produce it.

X.400 is for messaging, so you normally have the whole message before
you start sending.  However, the BER encoding technique uses the lengths
in a way that does not require you to know before you start sending.
Your are allowed to send the string as a series of short strings.
Each substring has a specific length indicator chosen at the convenience
of the sender, but the overall string constructed from all these
substrings does not have the length specified in advance.  If you have
access to a presentation on BER, look up constructed encoding of strings.

(I don't know X.400, but I don't think the length is carried in
the message header, so I doubt you need to know the length before
you start sending.)

>For a real life example, when receive incoming fax images I don't know
>ahead of time how big a received image will be. If I can't save the image
>until I know how big it is then I'm constrained to bufferring it and then
>writing it out in one large chunk instead of small chunks as I receive it.
>This impacts further on the design because I must now ensure that I can
>keep the remote fax station online without sending new data while I save
>the previous page. Which if it's very large may take some time. Or be 
>prepared to buffer multiple pages. 

The Reliable Transfer Service protocol that X.400 uses explicitly deals
with breaking the data up into conventient chunks, and provides for
starting where you left off if you lose your connection or interrupt
the transmission for some reason.

>-- 
>Stuart Lynne <sl@wimsey.com> ......................... UNIX Facsimile Software
>Wimsey Information Technologies ................... moderator biz.sco.binaries
>uucp login:nuucp passwd:nuucp .................... ftp.wimsey.com:~ftp/ls-lR.Z
>PD Software for SCO UNIX .................... ftp.wimsey.com:~ftp/pub/wimseypd

John Dale
Corporation for Open Systems
jdale@cos.com
Newsgroups: comp.protocols.iso.x400
From: siili@sumppu.fmi.fi (Tero Siili)
Subject: Compulsory address fields
Organization: Finnish Meteorological Institute
Date: Wed, 16 Dec 92 10:21:32 GMT


Question: what are the compulsory X.400 address fields?  Specifically,
can an address contain C, ADMD, PRMD, OU and PN but NOT ORG?

Tero Siili
Tero.Siili@fmi.fi
From: roy.pereira@devcan.ca (ROY PEREIRA)
Subject: LOOKING FOR TOUCH COMMUN
Newsgroups: comp.protocols.iso.x400
Organization: Canadian International Development Agency
Date: 15 Dec 92 18:49:43 GMT

-> Does anyone know if Touch (the makers of an X.400 gateway for MS Mail
-> for the Mac and other mailing systems) are accessible via Internet
-> Mail?

The last I've heard of them, they went chapter 11 (bankrupt).
Newsgroups: comp.protocols.iso.x400
From: hta@boheme.er.sintef.no (Harald Tveit Alvestrand)
Subject: Re: X.400-SMTP Gateway
Keywords: X.400, SMTP, Gateway
Reply-To: harald.alvestrand@delab.sintef.no
Organization: SINTEF DELAB, Norway
Date: Fri, 18 Dec 92 13:22:37 GMT

The ISODE Consortium release of PP will in the near future
support gatewaying between MIME and X.400 according to the
MIME-MHS Internet-Drafts.
-- 
                   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.x400
From: grant@shamin.genie.uottawa.ca (Grant Henderson)
Subject: X400 Vendor in Western Canada	
Followup-To: author 
Originator: grant@shamin.genie.uottawa.ca
Keywords: X400 Canada
Reply-To: grant@shamin.genie.uottawa.ca
Organization: MCRLab - University of Ottawa
Date: Wed, 16 Dec 92 14:40:08 GMT


I am looking for the name and number of a company in Western Canada
which is developing or has developed an X.400 product suite similar
to ISOCOR's. I have been told that such a company exists and was 
purchased by foreign investors in the past year. Unfortunately,
my source could not remember the name of the company. 

Thanks

------------------------------------------------------------------------
Grant Henderson                            grant@shamin.genie.uottawa.ca
Multimedia Communications Research Lab            Ottawa, Ontario Canada
Univerity of Ottawa                                       (613) 564-9247        
Newsgroups: comp.protocols.iso.x400
From: timwi@microsoft.com (Tim Williams)
Subject: Re: Compulsory address fields
Date: 17 Dec 92 18:43:04 GMT
Organization: Microsoft Corporation

In article <1992Dec16.102132.23668@nic.funet.fi> siili@sumppu.fmi.fi (Tero Siili) writes:
>
>Question: what are the compulsory X.400 address fields?  Specifically,
>can an address contain C, ADMD, PRMD, OU and PN but NOT ORG?
>
>Tero Siili
>Tero.Siili@fmi.fi

According to the '88 XAPIA docs, none of them are compulsory.  Section 5.2.31
describes the om object representing an OR address, and all attributes are
listed as optional.  Best I can figure, what attributes are necessary
depends on the routing that the mail implementation you are using uses.
From: gbk@calmasd.prime.com
Newsgroups: comp.protocols.iso.x400
Subject: Ireland address .x400/email?? please help
Date: 10 Dec 92 02:30:59 GMT
Organization: Computervision, San Diego CA

I have mail address from a company letterhead
which I belive to be X.400 The company letter head specifically
says it is email as follows:

E-Mail ITT Dialcom 74 EIM680

This address is from the letter head of:
O'Carroll International Ltd
Eagle House 
Roscommon Ireland phone 353-0903 26350

I would like to correspond with this address thru email
from the US (gbk@calmasd.prime.com)

I understand that I may be able to do it as a SMTP mailer
as discussed in News comp.protocols.iso.x400

Can anyone advise me if I can do this and a example of what a
message address would appear as to accomplish.

This would be greatly appreciated,
Thank you 

Gerry Kirkpatrick
ComputerVision
San Diego, Ca 
phone 619-587-3083
(gbk@calmasd.prime.com)
From: /PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com
Subject: Touch Communications Phone Number
Newsgroups: comp.protocols.iso.x400
X-Message-Id: <"512611171292"*/PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com>
Date: 17 Dec 92 16:49:46 GMT

    Further info on Touch communications:

    Touch customer support can be reached at 408 374 2500.


                                Thomas K Hinders
                       Martin Marietta Computing Standards
                             4795 Meadow Wood Lane
                               Chantilly, VA 22021
                        703.802.5593 (v) 703.802.5027 (f)

Newsgroups: comp.protocols.iso.x400
From: hta@boheme.er.sintef.no (Harald Tveit Alvestrand)
Subject: Re: Compulsory address fields
Reply-To: harald.alvestrand@delab.sintef.no
Organization: SINTEF DELAB, Norway
Date: Wed, 16 Dec 92 13:13:41 GMT

In article <1992Dec16.102132.23668@nic.funet.fi>, siili@sumppu.fmi.fi (Tero Siili) writes:
|> 
|> Question: what are the compulsory X.400 address fields?  Specifically,
|> can an address contain C, ADMD, PRMD, OU and PN but NOT ORG?
|> 
Yes. Look at the addresses used by German academic sites.
(PRMD=university;OU1=university OU)
I personally think that it is a bad idea, but they do not agree with me.
-- 
                   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
From: /PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com
Subject: Touch Communications
Newsgroups: comp.protocols.iso.x400
X-Message-Id: <"103512161292"*/PN=Thomas.K.Hinders/OU=CCMAIL/O=CHAN.IS/PRMD=MMC/ADMD=TELEMAIL/C=US/@sprint.com>
Date: 17 Dec 92 16:55:25 GMT

    Several messages/responses concerning Touch Communications.

    - Touch did go chap 11, then reappreared as WorldTalk (internet address
    unknown, but I did see WorldTalk in the FAQ message).

    - Our Denver facility runs the Touch set up with cc:Mail and MS Mail
    (Mac)

    - I run a Retix <==> cc:Mail setup here in Chantilly.

    You can drop a note to the admin in Denver using the X400 address:

    c=us/a=telemail/p=mmc/o=den.mmag/ou=msmail/s=dodge/g=steve/i=w

    Steve can probably give you a lead.

                                Thomas K Hinders
                       Martin Marietta Computing Standards
                             4795 Meadow Wood Lane
                               Chantilly, VA 22021
                        703.802.5593 (v) 703.802.5027 (f)
From: satish@terminus.ericsson.se (Satish Popat)
Newsgroups: comp.protocols.iso.dev-environ
Subject: ISODE V8.0
Date: 18 Dec 92 16:45:04 GMT
Reply-To: satish@terminus.ericsson.se
Distribution: world
Organization: Camtec Electronics (Ericsson), Leicester, England

I am new to ISODE, so apologies first if this is a FAQ but could someone tell me 
a site from where I can ftp ISODE V8.0 sources please.

Thanks.

---


Satish Popat
Ericsson
18 Melton Street
Leicester LE1 3NB
England
Tel +44 533 537534
email: satish@terminus.ericsson.se
From: wchoe@iss.nus.sg (Winston Choe)
Subject: Re: Problems building 8.0p1 under SunOS 4.1.2
Reply-To: wchoe@iss.nus.sg
Organization: Institute Of Systems Science, NUS.
Date: Fri, 18 Dec 1992 12:03:30 GMT

I'm trying to build ISODE-8.0 on an R4000 Silicon Graphics Indigo Elan running
IRIX 4.0.5F. 

Does anyone know which MAKE and H files to use in config?


Regards, Winston Choe.



Newsgroups: comp.protocols.iso
From: hcb@world.std.com (Howard C Berkowitz)
Subject: Re: Book or docs for X.25 implementers?
Organization: The World Public Access UNIX, Brookline, MA
Date: Fri, 18 Dec 1992 14:12:47 GMT

In article <1992Dec16.230520.9801@nosc.mil> psm@nosc.mil (Scot Mcintosh) writes:
>Does anyone know of books, articles, or other kinds of
>documents that would be of help to someone implementing
>the X.25 protocol? In particular, somento excruciating detail in terms of how to handle
>the interface for each state and event that could
>take place would be of great benefit. ...



When SPRINT was TELENET, there used to be a loose-leaf document
called the [GTE]TELENET X.25 Implementors' Guide.  It did give
guidance on buffer management, etc.  I don't know if it 
still is available, and it was about $1000 in the 1980s.
   Another, less obvious, is the conformance test suite,
ISO 8882-2 for the frame layer and ISO 8882-3.  This will give
an example of virtually every state transition, and a test for
it.  This standard will not help with internal implementation,
but it is a much better specification than the base protocol.
   I was the development team leader for the Corporation for
Open Systems' X.25 tester, and formerly network management
architect for TELENET.  Given this and other experience, I
would hesitate to start an X.25 implementation from scratch,
simply because the size of the task.  There are decent portable
software packages commercially available (e.g., Spider Systems).
I would tend to start with one of those as a base, and customize
from there. 
   Since I've done X.25 implementation, I would not personally
need a consultant during the implementation,but I would suggest
some source of advice for a first-timer.  An OEM software 
vendor may be able to give you enough support, or there are
qualified consultants.

Howard


From: mds@hpcndaw.CND.HP.COM (Mark Smith)
Date: Fri, 18 Dec 1992 16:22:53 GMT
Subject: Latest BER document ??
Organization: HP Network and System Management Division
Newsgroups: comp.protocols.iso

I just received a copy of ISO 8825, the BER specification, from
Omnicom. This document is a DIS version of 8825 dated 1990-04-30.

Is this really the most recent version of BER?? 
If so - why has this been stuck in DIS form for so long?


Mark
Newsgroups: comp.protocols.iso
From: goebbels@col01.enet.dec.com (My name is fp goebbels)
Subject: cmis problem on RO-REJECT
Organization: Digital Equipment Corporation
Date: Mon, 14 Dec 1992 21:24:27 GMT




Due to ISO 9596-1 (see for example chapter 6.6: Action procedure, 
6.6.4: Receipt of response) the following scenario may occur:

     Invoker                         Performer 

     M-Action-req  -------------->   M-Action-ind

                  <--------------    M-Action-rsp
       (*1)
	 

     RO-Reject-U   ------------->     ?????????


(*1): As some special error occur (APDU not well formed) no confirmation
      is delivered to the invoker. An APDU ist sent to the Performer 
      using the RO-REJECT-U procedure.

      This scenario holds true for the following RO-Reject parameters:

          duplicate-invocation, mistyped-argument, resource-limitation,
	  unrecognized-operation.

Problems:
 	  
     I.) There is no description of the behaviour of the Performers CMIPM 
         on receipt of RO-REJECT-APDU. 

     II.) No confirmation is delivered to the invoking entity.

     III.) ISO 9596-1 defines a mapping of the above mentioned RO-Reject
         parameters to CMIS-Service Confirmation parameters (see 6.2.2 in
	 ISO 9596-1). But a description when the CMIPM shall deliver
	 this parameters is missing.
	 
Thanks in advance for any comments.
Newsgroups: comp.protocols.iso
From: hcb@world.std.com (Howard C Berkowitz)
Subject: Re: X.25 header compression
Organization: The World Public Access UNIX, Brookline, MA
Date: Wed, 16 Dec 1992 22:12:47 GMT

In article <1992Dec16.162940.10991@nosc.mil> gutman@nosc.mil (Lew Gutman) writes:
>I am looking for information on X.25 header compression for slow links.  Does 
>

I'm a little confused what you mean by a "link" here.  If you are using 
the packet layer of X.25 on a point-to-point link, and performance really
is an issue, using a null packet layer is the immediate first thought.

If the link provides access to a packet network, other considerations would
apply.  If the link is slow but relatively error-free, frame relay, with
translation to X.25 at the endpoints, comes to mind.  

If the slowness comes from delay in getting packet or frame acknowledgements,
and you have tuned the packet data size and window size, most pure 
X.25 tuning has been done.  In a RF or similar environment, I might then
consider a forward error correction code to reduce retransmissions.  

As long as you need true X.25 (i.e., you need direct access to a packet
network), the data packet headers are fairly compressed.  You could, I
suppose, strip out the first four bits of the GFID and make the modulus
default, but I'm not sure how much this would help.  

Another approach is to use a point-to-point link protocol, a null packet
layer, and have the endpoints examine higher-layer protocol addresses
(I assume you have some) to determine the packet layer address needed.


><gutman@nosc.mil>
>
>
>


Newsgroups: comp.protocols.iso
From: alvarado@cbnewsb.cb.att.com (victor.m.alvarado)
Subject: multicast address in 8473 data packet
Organization: AT&T
Distribution: usa
Date: Wed, 16 Dec 1992 20:16:33 GMT



Does anyone know where I can find information about using
a multicast address in an 8473 data packet? I also need the
definition of the "multicast Group address". Is this a
recent development? I couldn't find it in my copies of
8348 AD1 and AD2, although they might be out of date.

Thanks,
Victor Alvarado
vma@mvuts.att.com
att!mvuts!vma
508-960-5932
Xref: sparky comp.protocols.iso:1419 comp.std.misc:163
From: sawyers@trl.OZ.AU (Greg Sawyers)
Subject: Correct use of the SEL field of NSAP addresses
Followup-To: comp.protocols.iso
Reply-To: g.sawyers@trl.oz.au
Organization:  Telecom Australia Research Laboratories
Date: Thu, 17 Dec 1992 08:45:12 GMT

Hi folks,

I have a question about the SEL field of OSI NSAP addresses. I
know that it is used within End Systems to select between different
transport entities, but are there any standard values for it?

For example, I seem to remember reading that 0 is used to address
the network entity itself (i.e. the Network Entity Title). Are there
values for, say TP0-4?

Is there a standard or some other document that I should be looking 
at?

Thanks, 
Greg
 
-----------------------------------------------------------------------
Greg Sawyers                              Internet: g.sawyers@trl.oz.au
Telecom Australia Research Laboratories		 Phone: +61 3 253 6454
P.O. Box 249 Clayton, Victoria 3168,		   Fax: +61 3 253 6362
Australia                        
X400:  g=greg s=sawyers ou=trl o=telecom p=telecom006 a=telememo c=au
From: J.Crowcroft@cs.ucl.ac.uk (Jon Crowcroft)
Newsgroups: comp.protocols.iso
Subject: Re: ATM
Date: 18 Dec 92 12:00:29 GMT



 >First , is this an appropriate newgroup to talk about ATM networks?

no
try
comp.dcom.cell-relay

 jon

Newsgroups: comp.protocols.iso
From: gutman@nosc.mil (Lew Gutman)
Subject: X.25 header compression
Reply-To: gutman@nosc.mil (Lew Gutman)
Organization: Naval Ocean Systems Center, San Diego, CA
Date: Wed, 16 Dec 1992 16:29:40 GMT

I am looking for information on X.25 header compression for slow links.  Does 
anyone know any vendors that supply X.25 products providing this feature or 
any other feature which increases the efficiency of X.25 on slow serial or RF 
links?

Thanks, 

Lew Gutman
NRaD, Code 834
San Diego

<gutman@nosc.mil>
From: unrza3@cd4680fs.rrze.uni-erlangen.de (Markus Kuhn)
Newsgroups: comp.protocols.iso
Subject: Re: X.25 header compression
Date: 17 Dec 1992 16:17:36 +0100
Organization: Regionales Rechenzentrum Erlangen
Reply-To: mskuhn@immd4.informatik.uni-erlangen.de
NNTP-Posting-Host: cd4680fs.rrze.uni-erlangen.de

gutman@nosc.mil (Lew Gutman) writes:

>I am looking for information on X.25 header compression for slow links.  Does 
>anyone know any vendors that supply X.25 products providing this feature or 
>any other feature which increases the efficiency of X.25 on slow serial or RF 
>links?

Why this? X.25 uses 3 header bytes per data packet. What else to you want to
compress? Where header compression would really make sense in the OSI
world is the connectionless network protocol (CLNP). There each packet
(even if it is only a VT keystroke) carries a complete NSAP pair and a lot
of other stuff which could be removed in a locally connection orientated
header compression system.

BTW: I heard about plans, that V.42bis/LZBT will be included in LAPB, so you'll
get compression for the whole PDU including the header! Has anyone more
details on this?

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: unrza3@cd4680fs.rrze.uni-erlangen.de (Markus Kuhn)
Newsgroups: comp.protocols.iso
Subject: Re: Book or docs for X.25 implementers?
Date: 18 Dec 1992 18:12:25 +0100
Organization: Regionales Rechenzentrum Erlangen
Reply-To: mskuhn@immd4.informatik.uni-erlangen.de
NNTP-Posting-Host: cd4680fs.rrze.uni-erlangen.de

psm@nosc.mil (Scot Mcintosh) writes:

>Does anyone know of books, articles, or other kinds of
>documents that would be of help to someone implementing
>the X.25 protocol?

I wrote a demo implementation of LAPB and X.25 and I found the ISO standards
ISO 7776 (LAPB) and ISO 8208 (X.25 PLE) much more readable (I implemented a
DTE and not a DCE) than CCITT X.25(88). Both standards are technically
aligned and compatible, but the details of LAPB retransmission and timeout
handling are described in a brain washing way in the CCITT doc. In the
ISO 7776 standard, they describe the meaning of the poll/final cyclus and the
rest is pretty easy if you understood the basic principles of sliding
window protocols (e.g. as described in Andrew Tannenbaum's "Computer
Networks").

ISO 8208 is over 100 pages long, but you'll understand the protocol
after reading the first 30 pages. You'll see, that X.25 is a very simple
and easy to understand protocol, even if you learn it from the official
specification. The rest of ISO 8208 are lot's of tables where you can
look at the state machine if you have any doubts about the English
description and a number of obscure optional features (closed user groups etc.)
that are not necessary in all applications and may only be used after
facility negotiation.

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: baos@caip.rutgers.edu (Bancroft Scott)
Newsgroups: comp.protocols.iso
Subject: Re: Latest BER document ??
Date: 19 Dec 92 18:44:28 GMT
Organization: Rutgers Univ., New Brunswick, N.J.

mds@hpcndaw.CND.HP.COM (Mark Smith) writes:

>I just received a copy of ISO 8825, the BER specification, from
>Omnicom. This document is a DIS version of 8825 dated 1990-04-30.
>Is this really the most recent version of BER?? 
>If so - why has this been stuck in DIS form for so long?

The latest version of BER is ISO DIS 8825-1 dated 1992-08-19.

There are now two additional parts to 8825, namely ISO CD 8825-2.2 (PER)
dated 1992-08-14, and ISO DIS 8825-3 (DER & CER) dated 1992-08-19.

=====================================|========================================
Bancroft Scott			     |		Open Systems Solutions, Inc.
609-987-9073			     |		Princeton, N.J.
=====================================|========================================