From Dave Osborne · 1996-04-04 02:35 · #75334 in CYBERSPACE
a NT1. Also w/o a NT2 only one set can be connected to a B channel at a time. This prevents 2 sets from participating in the same voice call.
pturner@eng.auburn.edu ( Patton M. Turner)
spike@coke.std.com (Joe Ilacqua)
------------------------------
2.11) What is National ISDN?
Because of the breadth of the international ISDN standards, there are a
number of implementation choices that vendors of ISDN equipment can
make. Given the number of choices vendors can make, different vendors
equipment may not interoperate. In the United States, Bellcore has
released a series of specifications to try to avoid these
interoperability problems. These are the National ISDN
specifications. Contact the Bellcore ISDN hot line listed below for
more information.
kumquat@hill.com (Gary C. Kessler)
cherkus@UniMaster.COM (Dave Cherkus)
------------------------------
2.12) What is the NIUF?
North American ISDN Users Forum (NIUF) is an org. of ISDN-interested
parties, coordinated by NIST (National Institute of Stds. and Tech.)
Contact:
NIUF Secretariat
National Institute of Standards and Technology
Building 223, Room B364
Gaithersberg, MD 20899
(301) 975-2937 voice
(301) 926-9675 fax
(301) 869-7281 BBS 8N1 2400 bps
Bellcore has made the PostScript files for "A Catalog of National
ISDN Solutions for Selected NIUF Applications, Second Edition"
accessable via anonymous ftp from the machine info.bellcore.com.
This document has a tremendous amount of information about
ISDN products and vendors, among many other things. See the item
below for details.
The currently approved documents for the Application Software
Interface (ASI) from the North American ISDN User's Forum (NIUF)
are available via anonymous FTP from dsys.ncsl.nist.gov. The
documents are in Postscript and found in uncompressed ASCII (foo.ps),
compressed (foo.Z) and zipped (foo.zip) files.
These documents describe the Implementation Agreements made by the
NIUF for an API to ISDN services.
The file sizes are approximate and intended to help determine space
requirements for transfer.
Part 1: Overview and Protocols - Approved: 10/4/91, Updated: 10/30/92
~ftp/asi/docs/part1.ps - 347853 bytes
~ftp/asi/docs/part1.Z - 119655 bytes
~ftp/asi/docs/part1.zip - 89545 bytes
Part 2: MS-DOS Access Method - Approved: 6/5/92
~ftp/asi/docs/part2.ps - 146474 bytes
~ftp/asi/docs/part2.Z - 44450 bytes
~ftp/asi/docs/part2.zip - 31599 bytes
Part 3: Enhanced DOS/Protected Mode Shell Access Method -
Approved: June 5, 1992, Updated: 10/30/92
~ftp/asi/docs/part3.ps - 285344 bytes
~ftp/asi/docs/part3.Z - 91273 bytes
~ftp/asi/docs/part3.zip - 68331 bytes
Part 4: UNIX Access Method - Approved: 10/30/92
~ftp/asi/docs/part4.ps - 151809 bytes
~ftp/asi/docs/part4.Z - 47765 bytes
~ftp/asi/docs/part4.zip - 33465 bytes
For further information regarding these documents please contact
Robert Toense (rtoense@nist.gov) (phone: +1 301 975 2930).
cherkus@UniMaster.COM (Dave Cherkus)
vances@xenitec.on.ca (Vance Shipley)
------------------------------
2.13) What is ATM?
ATM (Asynchronous Transfer Mode) is a switching/transmission technique
where data is transmitted in small, fixed sized cells (5 byte header,
48 byte payload). The cells lend themselves both to the time-division-
multiplexing characteristics of the transmission media, and the packet
switching characteristics desired of data networks. At each switching
node, the ATM header identifies a "virtual path" or "virtual circuit"
that the cell contains data for, enabling the switch to forward the
cell to the correct next-hop trunk. The "virtual path" is set up
through the involved switches when two endpoints wish to communicate.
This type of switching can be implemented in hardware, almost essential
when trunk speed range from 45Mb/s to 1Gb/s.
One use of ATM is to serve as the core technology for a new set of ISDN
offerings known as Broadband ISDN (B-ISDN).
For more information, read comp.dcom.cell-relay.
This group has a Frequently Asked Questions list; it is posted
to news.answers and is in various archives as cell-relay-faq.
art@acc.com (Art Berggreen)
cherkus@UniMaster.COM (Dave Cherkus)
------------------------------
2.14) What is B-ISDN?
Broadband ISDN refers to services that require channel rates greater than
a single primary rate channel. While this does not specificially imply
any particular technology, ATM will be used as the switching infrastructure
for B-ISDN services.
B-ISDN services are categorized as:
INTERACTIVE
Conversational -- such as videotelephony, videoconferencing, ...
Messaging -- such as electronic mail for images, video, graphics,...
Retrieval -- such as teleshopping, news retrieval, remote education,...
DISTRIBUTION
Without user presentation control -- electronic newspaper, electronic
newspaper, TV distribution
With user presentation control -- remote education, teleadvertising,
news retrieval
More information: ITU ITU-T Rec. I.211.
kumquat@hill.com (Gary C. Kessler)
------------------------------
2.15) What is BONDING?
An inverse multiplexing method of the Bandwidth ON Demand
INteroperability Group, implemented by most (all?) inverse multiplexor
vendors to interoperate with inverse multiplexors of other vendors.
BONDING is a set of protocols developed by U.S. inverse multiplexor
that supports communication over a set of separate channels as if their
bandwidth were combined into a single coherent channel. For example it
supports a single 384 kb/s data stream over 6 64 kb/s channels.
The specification defines a way of calculating relative delay between
multiple network channels and ordering data such that what goes in one
end comes out the other.
Most (all?) vendors also have their own proprietary methods that
usually add features and functions not present in BONDING mode 1. Mode
1 is the mode used for recent interoperability testing between vendors.
Chip Sharp at Teleos has made available electronic copies of the
BONDING (Bandwidth on Demand Interoperability Group) 1.0 and 1.1
specifications. The specs are available via WWW, gopher, anonymous
FTP, DECnet COPY, and AFS (see instructions below).
The following files are available:
- aaareadme-networks help file (in ascii text)
- bdmain.doc main body of BONDING 1.0 specification
(Word for Windows 2.0 format)
- bdmain.ps main body of BONDING 1.0 specification (Postscript)
- bdannex.doc annex of BONDING 1.0 specification (Word
for Windows 2.0 format)
- bdannex.ps annex of BONDING 1.0 specification (Postscript)
- bd_v1_1.doc changes for BONDING 1.1 specification (Word
for Windows 2.0 format)
- bd_v1_1.ps changes for BONDING 1.1 specification (Postscript)
Transfer Instructions:
WWW:
server: www.hep.net
URL: gopher://www.hep.net:70/11/info_center/networks/bonding
Gopher:
server: gopher.hep.net
Bookmark:
Name=Bandwidth on Demand Interoperability Group (BONDING) Documents
Type=1
Port=70
Path=1/info_center/networks/bonding
Host=gopher.hep.net
Anonymous FTP:
server: ftp.hep.net
directory: networks/bonding
DECnet COPY (only for those on HEP-NSI DECnet):
HEPNET::[ANON_FTP.NETWORKS.BONDING]
AFS:
/afs/hepafs1.hep.net/public/anon_ftp/networks/bonding
marc@dumbcat.sf.ca.us (Marco S Hyman)
--- MsgPost 1.1
* Origin: Center Field ISDN 901.368.4702 (1:123/301)