★ wanayoo — archive 1999 http://sun.icsnet.com/rfc/rfc567.shtmlNouvelle recherche | Portail wanayoo

News
  Headlines
  Scoop
  Submit News

Man Pages
To look up the Solaris manual page for a command, type it in and press GO.

Advanced Search

Resources
  Online Man Pages
  Reviews
  QuickGuides™
  SysAdmin Quiz
  Articles
  Forums
  Essential Ref
  FAQs
  Software
  Hardware
  Usenet
  ISP-Solaris
  Server Daemons
  Feedback
  About

RFC's
To look up an Internet RFC, type in the rfc number or a keyword and hit GO.

RFC Index
Services
  Consulting
  Hardware

Search
To search for a topic type it in and press GO.

Advanced Search

Link to us
  Ultramode
  Banners

internet.com
  Internet News
  Internet Investing
  Internet Technology
  Windows Internet Tech.
  Linux/Open Source
  Web Developer
  E-Commerce/Marketing
  ISP Resources
  ASP Resources
  Wireless Resources
  Downloads
  Internet Resources
  Internet Lists
  International

  Search internet.com
  Advertising Info
  Corporate Info
  Internet Trade Shows

internet.commerce
  Be a Commerce Partner
  Computer Help
  Affiliate Solutions
  Talk to Your Users
  Freelancer Exchange
  Free virtual office
  Get e-Biz Intell.
  IT Products and Svcs
  Build Sticky eStores
  Accept Credit Cards
  Software Specials

Tell A Friend!
If you've got a friend you think would enjoy our site, let them know!
Your name

Your email address

Your friends email address



* Solaris and all Solaris-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. SolarisGuide.com is independent of Sun Microsystems, Inc.



Internet Newsradio

THE UNOFFICIAL GUIDE TO THE SOLARIS™ OPERATING ENVIRONMENT

>>> rfc567

Network Working Group                             L. Peter Deutsch  (PARC-MAXC)
Request for Comments: 567			              September 6, 1973
NIC #18970



            CROSS-COUNTRY NETWORK BANDWIDTH



The following computation of cross-country network bandwidth was
contributed by Butler Lampson of PARC.

Consider what happens when a TIP user on the West Coast, connected to a
full-duplex Host on the East Coast, strikes a key on his terminal.

The TIP sends a one-character message (1 packet).

The destination IMP sends a RFNM (1 packet).

The destination Host sends an ALLocate - this seems to be the strategy
used by TENEX Hosts, at least (1 packet).

Thc TIP sends a RFNM for the ALLocate (1 packet).

The same sequence repeats itself, with roles interchanged, for the echo
character (4 packets).

This constitutes 4 packets or 4OOO bits in each direction. The current
cross-country transmission capability of the ARPANET is 3 5OKb phone
lines; ergo, it can only support 3*50000/4000=37.5 such characters per
second!

It may be that RFNMs are transmitted between IMPs more efficiently; at
best this can only double the network capacity.

This computation may help explain why cross-country TIP users (e.g. the
substantial West Coast community of BBN-TENEX users) experience such
bad echo response, at least in bursts: the network itself may be
experiencing momentary peak loads.

If this argument is correct, the proposed remote echoing facilities of
the new TELNET protocol could have a major effect on network operation.

Printable Output

Grow your revenue stream!


© 2000 internet.com

About internet.com Corp. | Press Releases
Privacy Policy | Advertising Information