HDTenEightyP/NetNews huggingface dataset:
From: husemann@camelot.informatik.uni-erlangen.de (Dirk Husemann)
Subject: Re: TCP/IP over ISDN: Who's done it?
Organization: CSD., University of Erlangen
Date: Tue, 17 Nov 1992 10:29:14 GMT

huntting@advtech.uswest.com (Brad Huntting) writes:

>In article <bmcqgd+@Stollmann.DE> Helge.Oldach@Stollmann.DE (Helge Oldach) writes:
>> Of course our (Stollmann's) STIX software is available not only for SCO,
>> but for other operating systems as well, in particular for Interactive
>> Unix.

>Any plans to support BSD386?

I'm at writing a driver for BSD386 (and 386/BSD) for the CNS-ISDN/1B, 
CNS-ISDN/2B and 4B boards manufactured by Teleprocessing Systeme in Cadolzburg
here in Germany. They sell boards for the PC ISA bus. They have been very
open and cooperative, and the boards look quite nice.

If you are interested I can mail their address to you.

	Dirk
---

Newsgroups: comp.dcom.isdn
From: rbc@cbnewsh.cb.att.com (robert.connaghan)
Newsgroups: comp.dcom.isdn
Subject: ISDN Book from NIST
Keywords: ISDN, NIUF, NIST
Date: 23 Nov 92 18:12:48 GMT
Distribution: usa
Organization: AT&T

The NIST (National Institute of Standards and Technology) is offering 
a 384 page catalog of ISDN solutions conforming to National ISDN 1.
It was created by NIUF (North American ISDN User's Forum).

Title: A Catalog of National ISDN Solutions for Selected NIUF Applications.
Price: Free

To quote:
  it  details 35 ways to implement 17 applications, including
  video conferencing, telecommuting, file sharing, and access to 
  local-area networks and frame relay


To Order:
	Write:	NIUF secretariat c/o NIST
		Building 223, Room B364
		Gaithersburg, Md, 20899
	Phone:	301-975-2937
	Fax:	301-926-9675

----------------
Robert Connaghan
AT&T Bell Labs
rbc@vax135.att.com
Newsgroups: comp.dcom.isdn
From: "Bob Larribeau" <p00136@psilink.com>
Subject: Re: bri lengths
Organization: Consultant
Date: Sat, 21 Nov 1992 22:33:47 GMT
X-Mailer: PSILink-DOS (3.3)

>DATE:   21 Nov 92 01:44:10 EST
>FROM:   chris strawser <chris.strawser@channel1.com>
>
>I understand that the maximum distance an ISDN U-interface can
>be run is 6 kilometers.  If this is so, how do you run a BRI
>over longer distances?  Just for fun, let's say my local telco
>wants to supply ISDN to all who ask for it.  If I want a BRI
>to my house, and the CO is 10 kilometers away, how does it
>happen?  Is there another interface that's good for longer
>distances, or does the telco have to plant repeaters all
>over the place?
>--
>Channel 1 (R)   Cambridge, MA
>
The maximum length for a 2B1Q loop is 18,000 feet, which is about the 
same as 6 kilometers.

There are various technologies available for extending loops.  The 
simplest is a loop extender that gives you another 18,000 feet.  Some 
RBOCs will include the loop extender in their tariff and others will 
charge extra for it.

		Bob Larribeau
		San Francisco
Newsgroups: comp.dcom.isdn
From: bjork@telebit.com (Steven Bjork)
Subject: Open market versus monopoly, was Re: Obtaining ISDN
Organization: Telebit Corporation; Sunnyvale, CA, USA
Date: Tue, 17 Nov 1992 16:06:14 GMT

In article <1992Nov17.145659.5823@bmerh85.bnr.ca>,
 coghlan@bnr.ca (Patrick Coghlan) writes:

>You need a NT1 and a terminal adapter or ISDN card for your PC.  You
>can get both for around $1000 today.  I paid $3000 for an original IBM
>PC with 16K memory and no disk drives in 1983.  I can get a 386 for
>around $1000 today.  Would you care to guess what it will cost to have
>ISDN in a few years?

More than it costs today (no smiley).

Your PC clone is the result of an *open market* and competition.

There is *no* effective competition in either the telco local loop
or the cable tv local loop.

This is why telephone charges are so outrageous, not to mention the
plundering done by cable tv systems.

For an example of serious rate discrimination, it costs me as much
money to call across the San Francisco bay as it does to call
Montana.

AT&T is so cash rich they have nothing better to do than buy
computer companies and pay off lawyers. I'd much rather see that
money go towards fiber to the demarc, or not taken in the first
place (ie, rate reductions).

--Steven
From: res@cbnewsc.cb.att.com (Rich Strebendt)
Newsgroups: comp.dcom.isdn
Subject: Re: Open market versus monopoly, was Re: Obtaining ISDN
Date: 19 Nov 92 00:19:20 GMT
Distribution: usa
Organization: AT&T

In article <1992Nov17.160614.10428@telebit.com>, bjork@telebit.com (Steven Bjork) writes:
> In article <1992Nov17.145659.5823@bmerh85.bnr.ca>,
>  coghlan@bnr.ca (Patrick Coghlan) writes:
> 
> >You need a NT1 and a terminal adapter or ISDN card for your PC.  You
> >can get both for around $1000 today.  I paid $3000 for an original IBM
> >PC with 16K memory and no disk drives in 1983.  I can get a 386 for
> >around $1000 today.  Would you care to guess what it will cost to have
> >ISDN in a few years?
> 
> More than it costs today (no smiley).
> Your PC clone is the result of an *open market* and competition.
> There is *no* effective competition in either the telco local loop
> or the cable tv local loop.
> This is why telephone charges are so outrageous, not to mention the
> plundering done by cable tv systems.
> For an example of serious rate discrimination, it costs me as much
> money to call across the San Francisco bay as it does to call
> Montana.

Up to this point you express unhappiness (which I share) with the
result of the lack of competition for the providers of local telephone
service (your local telephone company).

> AT&T is so cash rich they have nothing better to do than buy
> computer companies and pay off lawyers. I'd much rather see that
> money go towards fiber to the demarc, or not taken in the first
> place (ie, rate reductions).

WHOA !!!!

What has AT&T got to do with the rest of your posting?  As you said
yourself -- it costs you as little to call halfway across the
continent on AT&T or one of its competitors as it does to make a local
call.  THIS IS A RESULT of the introduction of competition into the
LONG DISTANCE CARRIER MARKET -- the market AT&T competes in.  AT&T has
NOTHING to do with your cross-town local call!

The days of Ma Bell are PAST -- Long Live the International AT&T!!!

					Rich Strebendt
					...!att!ihlpb!res
					r.strebendt@att.com
Newsgroups: comp.dcom.isdn
From: deej@cbnewsf.cb.att.com (david.g.lewis)
Subject: Re: Obtaining ISDN
Organization: AT&T
Distribution: usa
Date: Mon, 16 Nov 1992 14:57:09 GMT

In article <bob1.721664568@cos> bob1@cos.com (Bob Blackshaw) writes:
>In <1dualuINNmks@agate.berkeley.edu> cliff@garnet.berkeley.edu (Cliff Frost) writes:
>>I heard a rumor (at an Interop BOF on ISDN) that not all implementations
>>of National ISDN-1 are compatible yet...
>>  Is this true?  If so, how serious are the differences and
>>will this be fixed with NI-2?
>
>NI-2 so far as I am aware (I don't work for Bellcore) only adds the
>PRI interface specs.

I don't work for Bellcore either, but I do have SR-2120 (NI-2).  NI-2 adds
the following BRI capabilities:

3.2 Uniform Interface Configurations for BRI
3.2.1 Support of More than 2 B-Channel Terminals on a BRI
3.2.2 Support of DN Sharing over Multiple Call Types on an Integrated
Terminal

3.3 Uniformity of Basic Rate Interface Services:
3.3.1 Electronic Key Telephone Service
3.3.2 ISDN Call Forwarding
3.3.3 ISDN Call Hold
3.3.4 Additional Call Offering
3.3.5 Flexible Calling
3.3.6 Calling Number Identification Services for BRI
3.3.7 ISDN Display Services

3.5 Improved Data Capabilities
3.5.1 User-Originated, On-Demand B-channel Packet on BRI
3.5.2 Public Packet Switched Network Capabilities
3.5.3 ISDN X.25 Local Charging Prevention

3.6 Operations Support Capabilities
3.6.1 Parameter Downloading
and 10 other operations capabilities appropriate to BRI.


For more info, buy the SR...

David G Lewis                              AT&T Bell Laboratories
david.g.lewis@att.com or !att!goofy!deej     Switching & ISDN Implementation
Newsgroups: comp.dcom.isdn
From: billp@Syntex.COM (Bill Putney)
Subject: Re: PacBell ISDN?
Reply-To: billp@Syntex.COM
Organization: Syntex U.S.A. - Palo Alto, CA
Distribution: usa
Date: Tue, 17 Nov 1992 01:53:24 GMT

BRI ISDN is here!  We have three lines connected here for video conf.

PacBell's only existing service is ISDN Centrex.  That means that you
have to have at least two BRI's to start with since it isn't a Centrex 
until you have two "phones" that can talk to eachother.

There is coming (March `93) a single line business ISDN they say.  This
would be a measured business 2B+D ISDN line.  

I asked about a flat rate residential ISDN and the story I get is that 
since an ISDN TA isn't line powered they can't offer ISDN as a residential 
service.  The problem (they say) is that if the power was off a person 
couldn't call 911.  This seems to me to be a very poor excuse.  They 
would of course hook a measured business line up at your house as your 
only phone without a moments thought.  Point being that PacBell doesn't 
like flat rate services and if they can figure out a way to avoid offering 
it they will.  Seems a little deceitful to me.  If they don't want to offer
flat rate services they should say that and have it out with the CPUC in 
an open forum.  I wouldn't mind if they required an analog line at any location
(I have 4 at my house anyway) before they would connect an ISDN line but I
would think that a business is in just as much (or as little) need to call 
911 with the power out as I would at home.

Oh well...  Maybe I should crosspost this to alt.braindead.tarrif.offering

- Bill

---
=====================================================================
#  Bill Putney                     |  billp@Syntex.COM              #
#  Syntex U.S.A.                   |  {oliveb|decwrk}!synseer!billp #
#  M.S. A5-6                       |--------------------------------#
#  3401 Hillview Ave.              |  P.O.T.S.  (415) 855-1259      #
#  Palo Alto, CA  94303            |  FAX       (415) 855-5301      #
=====================================================================
From: imhw400@indyvax.iupui.edu
Newsgroups: comp.dcom.isdn
Subject: Re: PacBell ISDN?READ/NEW/FOLLOWUP
Date: 17 Nov 92 12:53:18 -0500
Distribution: usa

In article <1992Nov17.015324.13170@synseer.Syntex.COM>, billp@Syntex.COM (Bill Putney) writes:
[deletia]
> I asked about a flat rate residential ISDN and the story I get is that 
> since an ISDN TA isn't line powered they can't offer ISDN as a residential 
> service.  The problem (they say) is that if the power was off a person 
> couldn't call 911.  This seems to me to be a very poor excuse.

To me, too.  Gee, I thought that the telcos had all heard about float-charged
batteries.  Especially since they own millions of dollars' worth of them.  A
simple law requiring a $5.00 battery for your $200.00 phone is not too
much to ask, IMHO.  (Come to think of it, why don't the manufacturers put the
battery in the phone to begin with?  It's not as though there will be *any*
customer who won't need one.)
-- 
Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
Celebrate freedom:  read a banned newsgroup.
Newsgroups: comp.dcom.isdn
From: "Bob Larribeau" <p00136@psilink.com>
Subject: Re: PacBell ISDN?READ/NEW/FOLLOWUP
Organization: Consultant
Date: Wed, 18 Nov 1992 16:13:24 GMT
X-Mailer: PSILink-DOS (3.3)

>DATE:   17 Nov 92 12:53:18 -0500
>FROM:   imhw400@indyvax.iupui.edu
>
>In article <1992Nov17.015324.13170@synseer.Syntex.COM>, billp@Syntex.COM (Bill Putney) writes:
>[deletia]
>> I asked about a flat rate residential ISDN and the story I get is that 
>> since an ISDN TA isn't line powered they can't offer ISDN as a residential 
>> service.  The problem (they say) is that if the power was off a person 
>> couldn't call 911.  This seems to me to be a very poor excuse.
>
>To me, too.  Gee, I thought that the telcos had all heard about float-charged
>batteries.  Especially since they own millions of dollars' worth of them.  A
>simple law requiring a $5.00 battery for your $200.00 phone is not too
>much to ask, IMHO.  (Come to think of it, why don't the manufacturers put the
>battery in the phone to begin with?  It's not as though there will be *any*
>customer who won't need one.)
>-- 
>Mark H. Wood, Lead Analyst/Programmer    +1 317 274 0749   [@disclaimer@]
>Internet:  IMHW400@INDYVAX.IUPUI.EDU     BITNET:  IMHW400@INDYVAX
>Celebrate freedom:  read a banned newsgroup.

According to the CCITT standards and ISDN terminal can take up to 7 
watts at 24 to 48 volts.  Many ISDN phones now operate in the 2-3 watt range.
It seems to take more than a simple battery.  They only individual terminal 
battery backup system I am aware of costs around $150 list price.

		Bob Larribeau
		San Francisco
From: jhl@eecae.msu.edu (John Lawitzke)
Newsgroups: comp.dcom.isdn
Subject: ISDN bandwidth analysis
Date: 17 Nov 92 15:05:21 GMT
Distribution: na
Organization: Michigan State University, East Lansing
Originator: jhl@eecae.ee.msu.edu

Could someone supply me with references to articles which analyze what
the bandwidth requirements of various network usages are?  Or: What
applications the available bandwidth of ISDN is useful for?

Advance thanx,

-- 
John Lawitzke
Manager of Product Management
Dale Computer Corp.
Internet: jhl@frith.egr.msu.edu
Newsgroups: comp.dcom.isdn
From: ariel@world.std.com (Robert L Ullmann)
Subject: Re: X.25 over ISDN Addressing
Organization: The World in Boston
Date: Tue, 24 Nov 1992 01:50:03 GMT

According to the interworking plan, described in E.166 and in Q.931,
a PSPDN, using X.121 addressing, must provide (eventually :-) a
prefix code that is effectively an escape to E.164 addressing.

Likewise, the E.164 line may provide an escape to the X.121 numbering
plan, but this isn't really part of what is specified.

Like everything else in CCITT, the actual _values_ which you need
to do something are "a national matter". (Political doubletalk for
"we weren't willing to let the international authority decide this,
even if they is us. So suffer." :-) :-)

Typically, a PSPDN line uses only the national number for "local"
calls (;-), with either 0 or 1 prefix for other networks (in X.121,
other DNICS). One of those 2 prefixes is for E.164, one for X.121;
the "local" or "national" numbers are often chosen to be common to
both schemes.

So for example, NYNEX provides X.121 PSPDN service ("INFONET") here;
the line is (E.164) +1 617 235 3970, (X.121) 3144 6172353970. On calls
within INFOPATH, we may not use either full code, but have to just
use the "national" number, e.g. 6172353970. On calls outside that,
we use either prefix 1, (13110 is Sprintnet, 12080 is TRANSPAC) meaning
following number is X.121, or prefix 0 (044 is UK, 033 is France/Numeris)
meaning E.164. For the most part, the E.164 prefix doesn't work
yet. (*sigh*)

You will find the same thing almost anywhere: if you consider the
field lengths, there is only 1 digit available in the (un-extended)
X.25 call request calling address element, and only the digits 1
and 0 are available. So one will mean X.121, and one will mean E.164

Rob
--
Robert Ullmann		Ariel@World.STD.COM	+1 508 879 6994 x226
Quand Maigret poussa la porte du Tabac Fontaine, vers une heure et demie,
le patron du bar, qui venait de se lever, descendait lentement un escalier
en colimaon qui s'amorait dans l'arrire-salle. ... Arriv derrire le
comptoir, il repousa le garon d'un geste ngligent de la main, saisit
une bouteille de vin blanc, un verre, mlangea au vin de l'eau minrale et,
la tte renverse en arrire, se gargarisa.  -- Simenon
Date: Fri, 20 Nov 1992 09:17:00 CET
From: o.roehrig@link-hh.comlink.de
Reply-To: o.roehrig@link-hh.comlink.de
Distribution: world
Newsgroups: comp.dcom.isdn
Subject: ISDN in USA and Germany
Organization: Freies Telekommunikations-Zentrum Hamburg e.V., Port 1
Content-Length: 507     
X-Gateway: UC xclhh [UZERCP V3.99]

------------------------------------------------- Hamburg, 20.11.92 09:16 ----

Sorry if this is a FAQ, but are the ISDNs from Germany and USA
"compatible" ? So, may I call from an ISDN-site here right away over
the big pond and get all the ISDN-features? 


Ottmar Roehrig

Zerberus: O.ROEHRIG@LINK-HH.ZER | UUCP: ottmar@ajberl.adsp.sub.org
                                  DE: O.ROEHRIG@LINK-HH.COMLINK.DE

    Woodstock aus Traum gerissen... Prinzessin verschwunden!

-- MPoint 2.0 Pro  (C)1992 M.Aberle
Xref: sparky comp.dcom.servers:156 comp.dcom.lans:1982 comp.dcom.sys.cisco:1648 comp.protocols.tcp-ip:5215 comp.sys.mips:1051
From: ajudge@maths.tcd.ie (Alan Judge)
Newsgroups: comp.dcom.servers,comp.dcom.lans,comp.dcom.sys.cisco,comp.protocols.tcp-ip,comp.sys.mips
Subject: Routing using a dual-homed machine vs a router
Keywords: routing tcp-ip networks subnetting
Date: 18 Nov 92 17:06:22 GMT
Organization: Dept. of Maths, Trinity College, Dublin, Ireland.

Does anybody have any comments on the performance of a Unix machine
as a router vs that of a dedicated router, such as a Cisco?
How much delay is imposed by each solution?

Are there any other issues here that I am missing?  (I realise that
a Unix box is likely to be down more than a dedicated router.)

Given the simple nature of our setup (no fancy leased lines, only
one ethernet at present), what models of router should I be
considering if I go for a router?  What do these models cost?
[I am asked the net, as I need the answer in a hurry.]

Background:
	We are connected to the campus fibre-optic backbone using a bridge at
	present.  There is a possibility that we will switch to using
	subnetting and routing instead.  If that happens, we will either
	purchase a router or install a second ethernet into one of our
	machines.

	There is little bulk traffic between the department and the rest of
	College, mainly NNTP, SMTP, NTP, telnet, rlogin.  No NFS or other
	file sharing.

	The machine in question is likely to be an R4000 based MIPS server
	(a Millenium 4000 SC-50).  We would probably run gated.


Please reply by email and I will summarise.
-- 
Alan Judge   ajudge@maths.tcd.ie  a.k.a. amjudge@dsg.cs.tcd.ie +353-1-7021782

A year spent in Artificial Intelligence is enough to make one believe in God.
						-- Alan Perlis
From: rdempste@unpcs1.cs.unp.ac.za (Rob Dempster)
Newsgroups: comp.dcom.servers
Subject: Disk Cache on PC work station for Novell server drives????
Keywords: disk cache network
Date: 21 Nov 92 14:05:15 GMT
Article-I.D.: unpcs1.rdempste.10.722354715
Organization: Dept. Computer Science, UNP
NNTP-Posting-Host: pc089.cc.unp.ac.za

I am currently in the process of considering migrating to Windows 3.1
I am running Windows 3.1 on a 25Mhz 80486SX with 8 MB of RAM and a 40 MB hard
disk. I have a 2 MB SMARTDRV disk cache running and this makes the software
that I run from the hard drive very snappy. Unfortunately I also have to pull
some applications of a Novell LAN server and this really slows things down.
I have tried some fixes such as putting my Borland C include files on the
local hard drive. I would have put the library files there as well but don't 
have the space. So at the moment it seems that I will have to get a larger 
drive or find a driver similar to SMARTDRV that works with Novell file 
server drives? I would be most interested to hear whether such a driver 
exists or alternatively any other advice that would be useful.
Please email the address given below. Thanks!!

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
rdempste@unpcs1.cs.unp.ac.za          department of computer science
dempster@unpsun1.cc.unp.ac.za         university of natal
                                      p o box 375
fax : +27 331 955599                  3200 pietermaritzburg
ph :  +27 331 955645/46/50            south africa
Newsgroups: comp.dcom.servers
From: antenna@well.sf.ca.us (Robert Horvitz)
Subject: DOS mailservers?
Organization: Internews
Date: Sun, 15 Nov 1992 21:36:27 GMT


The organization I work for has two dozen field offices around the world
and makes increasing use of email to connect them.  Some of the routine
communications seem like they could be automated:  like having a
mailserver at HQ be able to process simple requests like GET SCHEDULE
JSMITH  or  GET BUDGET FORM  or  UPDATE DIRLISTING  or SEND WEEKLY
NEWSLTTR
 
Is there anything like a mailserver for DOS computers that could do
this?  Anything in the shareware/freeware world?
 
Answer please by email and I'll compile the answers and post them to
comp.dcom.servers.  Thanks in advance.
 
-- 
!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|.!.|
        Robert Horvitz, Radio Consultant, The Soros Foundations          
        Karlovo nam. 15     121 27 Praha 2      Czecho-Slovakia
antenna@earn.cvut.cs     antenna@csearn.bitnet    antenna@well.sf.ca.us
Newsgroups: comp.dcom.servers
From: alexis@panix.com (Alexis Rosen)
Subject: Desparately seeking... transparent connection from Annex 3 to Sun
Date: Tue, 17 Nov 1992 10:48:17 GMT
Organization: PANIX Public Access Unix, NYC

We recently bought an Annex III. We were assured by various people at
Xylogics that we would have "no problem" doing 8-bit clean connections to our
Sun so that users could download binaries with zmodem or xmodem or whatever.

Well, now we have this very fine expensive server and no way to do what we
need. Xylogics tech support is trying, but so far none of their ideas seem
to work. I am _not_ using Xon/xoff or telnet_crlf, and the attention char
is turned off (by being set to "" or to ^@, I've tried both) as it the
telnet escape char (set to u). Flow control is "eia" in both directions, as
we use hardware flow control. Rlogin just doesn't do the trick- zmodem
downloads fail instantly- and telnet isn't any better.

I don't understand why telnet isn't doing the trick- there shouldn't be any
in-band data that matters to it at this point. Anyone know what's wrong? If
you are successfully doing 8-bit xfers, what is your port setup and what
macro (if any) are you using?

Thanks,
--
Alexis Rosen   Owner/Sysadmin,
PANIX Public Access Unix & Internet, NYC.
alexis@panix.com
{uupsi,cmcl2}!panix!alexis
Newsgroups: comp.dcom.servers
From: baker@nodecg.ncc.telecomwa.oz.au (Mark Baker +61 9 4916081)
Subject: Datability won't work - what will?
Organization: Network Computer Centre
Date: Tue, 17 Nov 1992 08:07:58 GMT

I need to purchase some terminal servers that will work in the reverse Telnet
mode and handle the BREAK signal. At the moment, I have some VCP 1000's and,
although they will encode the BREAK signal, they won't decode it. I have been
led to believe that Datability aren't interested in solving this problem.

Is there any other product I can buy?

_______________________________________________________________________________
Mark Baker                             Phone: +61 9 4916081
Network Computer Centre                Fax:   +61 9 2212560
5th Floor Telecom Centre               ACSNET: baker@telecomwa.oz.au
80 Stirling Street, Perth              Inet:  baker%telecomwa.oz.au@uunet.uu.net
Western Australia 6000
Newsgroups: comp.dcom.servers
From: gintsu@pisces.acns.nwu.edu (Ginstu)
Subject: Formal definition of a server?
Followup-To: comp.dcom.servers
Organization: Northwestern University
Date: Sun, 22 Nov 1992 21:50:52 GMT

There seems to be a great deal of diversity regarding the definition of a
server.  The term "Client Server Computing" has definitely been bastardized
by the fashion rags of the industry.  Certainly the definition of a server
must be sensitive to the give context, but there must be some common ground
that encompasses the essence of a server.  So lets get to it!  What the
hell is a server?  What type of behavior is common to all types of servers?
 What are the different types of servers (i.e. connection, connectionless,
statefull, stateless, database, compute, etc.)?

Thanx
gintsu@pisces.acns.nwu.edu