|
|
| About site: Internet/RFCs/0001 - 0100 - RFC 0065 |
Return to Computers also Computers
|
| About site: http://www.faqs.org/rfcs/rfc65.html |
Title: Internet/RFCs/0001 - 0100 - RFC 0065 Comments on Host/Host Protocol Document #1. D.C. Walden. August 1970.
|
|
|
|
|
WeDo_Hosting_com_Inc_ Provides shared web hosting and dedicated hosting services. Based in Victoria, British Columbia, Canada.
| The_Kiosk_Factory Manufacturers of custom designed interactive touch-screen kiosks and terminals for sports venues, entertainment facilities, educational, tourism, and museums. Based in Canada.
| Cyberlife_Research A research, development and consultancy company devoted to the creation of artificial lifeforms. Includes robotic gliders and alife research based on the "creatures" games but now independent.
| Struts_Framework An open source framework for building Servlet/JSP based web applications based on the Model-View-Controller (MVC) design paradigm [Open Source, BSD-like]
| Cprogramming_com_-_Source_Code A collection of source code including graphics,game,and sound source.
| RFC_2465 Management Information Base for IP Version 6: Textual Conventions and General Group. D. Haskin, S. Onishi. December 1998.
|
|
| Alexa statistic for http://www.faqs.org/rfcs/rfc65.html |
Please visit: http://www.faqs.org/rfcs/rfc65.html
|
| Related sites for http://www.faqs.org/rfcs/rfc65.html |
| SQL_Dumpster Free SQL scripts for website and application developers. | | Lighttek_Software Products include Talisman, a program that replaces the standard Windows Desktop through the creation of a new interface and IconTOY designed specifically to extract the icons from any file containing | | MagicQ_Technologies_Inc_ The home site of the first start up company devoted entirely to quantum computing. No patents or products to date, but of interest by virtue of being first off the block. | | HomePage_MadeEasy Resources for amateur and beginner webmasters. | | Dart Open Source - Client/server, multiplatform build reporting system runs predefined builds and sends build results to a central server which displays build histories. No documentation. Part of the GE | | Health_Squared_Communications Online design and development in web and mobile for the healthcare market. | | BJDC_Music_Librarian Catalogs paper music libraries, for churches and schools. | | YourShop Virtually hosted online payment facilities. | | P_A__Semi,_Inc_ Fabless semiconductor firm, designs PWRficient family of 64-bit multicore processors, based on POWER design. California, USA. | | Ceol_Mor_Software_Ltd_ [Win] Drag and drop bagpipe and drum score writing software. Suitable for beginners and advanced users. | | RSS_Submit Software tool to automatically submit your RSS feeds to over 50 RSS directories and search engines. | | Tab_Mix_Plus Enhances Firefox's tab browsing capabilities with lots of options. | | Page_Arnold Northamptonshire, UK-based website design and promotion; including site maintenance, training and internet consultancy. | | Fleming_Studios Offers web design services and business card designs. | | Orange_House_Design Offers web design as well as search engine submission. | | Blitzed Website providing live chat, user profiles and help to new users. | | Dynaweb_Design Website design, search engine positioning and complete on-line marketing services in Sydney, Australia. | | Public_Domain_Backgrounds Free backgrounds for commercial or personal web sites. | | N1busVerticalCounter Displays counter vertically. | | Flash_Video_Blog Flash Video Blog covering information, knowledge and skills relating to Flash and Flash Video. |
|
This is websites2007.org cache of m/ as retrieved on 2008.08.21 websites2007.org's cache is the snapshot that we took of the page as we crawled the web. The page may have changed since that time.
|
RFC 65 (rfc65) - Comments on Host/Host Protocol document #1@import 'http://faqs.org/abstracts/css/default.css';@import 'http://faqs.org/search.css';function erfc(s){document.write("[ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ]Alternate Formats: rfc65.txt | rfc65.txt.pdfRFC 65 - Comments on Host/Host Protocol document #1Search the Archives  Display RFC by number RFC65 - Comments on Host/Host Protocol document #1Network Working Group Dave WaldenRequest for Comments: 65 A/S Norsk Data-Elektonikk August 29, 1970 Comments on Host-Host Protocol Document No. 1 (S. Crocker - 8/3/70) Page 3. Eliminate marking. Instead, make all regular messages into two message: The first containing just the leader and indicating that the data follows in the second (next) message. Do this both from the source Host to its IMP and from the destination IMP to its Host. Thus, no more hunting for the beginning of the data is necessary. Once this adjustment is made, an additional simplification is available. If the maximum message length is a common multiple of the word sizes of all the computers in the network (perhaps 2880*2 bits), successive messages of long files can be dropped in place without shifting. Page 4. Control messages should be sent to and from the _control socket_ -- not over the control link. The concept of the control link causes a great big, unnecessary special case. Page 5. Assigning sockets permanently to certain network resources should be encouraged and a directory of the socket/resource associations should be available somewhere in the network, perhaps in physical book form at each site. Page 6. Links have no Host-Host purpose other than identifying a connection so that socket numbers don't have to be included in all messages and to simplify table look-ups in the NCPs. However, since there are possibly 512 links* with the same number, links don't aid table look-ups very much. Also finding the next available link to a particular destination is very ugly . Therefore, I suggest limiting the number of links to a total of n (where n = 32, 64, or 256 or some other good number) for all destinations. In other words, a particular link is only in use to one destination at a time(actually from one destination at a time since the receiver picks the link to be used for a connection). This change makes picking the next available link very simple and,I feel,is a worthwhile change if only for this reason. The question of simplifying table look-ups is a little more complex. It is easy to use the link directly as an index into tables in the receive portion of the NCP since the receiver picks the link. But a hash table or linear search or something is still necessary in the send portion of the NCP. This too can be fixed with the following changes. Add to STR a _pseudo link_ chosen by the sender. This link is sent in all non-control messages in the 8 -------------------------------------- *A destination number is 9 bits. bits to the right of the link in the leader. The IMP must preserve these bits and return them with RFNMs and the receiver must use the pseudo link instead of the link in RET and INR. The extra memory necessary to store the pseudo link in the NCP receive tables (which are indexed by link) and the link in the NCP send tables (which are indexed by pseudo link) is certainly less than the overhead necessary to maintain associative tables. Page 8. The allocate mechanism seems very inconvenient for the receive portion of the NCP to use. The receiver wants the allocation to be used up in units of the receiver's buffer size not in units of sender messages which may be variable length. Otherwise the receiver has a memory compaction problem. Page 9. The new irregular message to make the "cease" mechanism work are unnecessary, I think. The sender can keep track (probably with a one bit counter) of ALLs and GVBs and ignore GVB 0s for which resume ALLs have already arrived. This the receiver need not know whether the cease has been sent or not. Page 15. If I implemented an NCP, all ERRs would be treated like NOP. As an error control mechanism ERR is complicated and insufficient. Who wants to debug a complicated mechanism which only catches bugs due to the primary mechanism being undebugged. The one error control mechanism I would provide is a receive process to send process acknowledgment on every message. If this is not received for too long, the send process can send the message again if it has been saving it. This acknowledgment catches errors causing message loss at the process/NCP, NCP/NCP, Host/IMP, IMP/IMP, etc. levels. Currently the Host/IMP interface is particularly lacking in useful error controls. I wouldn't worry about kinds of errors check-sums are designed to pick up. If dropped and picked up bits ever become a problem either add hardware to more interfaces or let the receive process not send the process to process acknowledgment if a software checksum does not check. The page 3 and page 6 comments involve a change to the IMP program. I feel a tiny bit guilty suggesting changes I don't have to implement any more. However, I trust Crowther and Cosell will, as always, resist bad changes while making sensible ones. The page 9 comment is aimed at avoiding a change in the IMP program. [ This RFC was put into machine readable form for entry ] [ into the online RFC archives by Luke Hollins 8/99] Previous: RFC 0064 - Getting rid of marking Next: RFC 0066 - NIC - third level ideas and other noise [ RFC Index | RFC Search | Usenet FAQs | Web FAQs | Documents | Cities ] © 2008 FAQS.ORG. All rights reserved. |
|
| |
Comments | on | Host/Host | Protocol | Document | #1. | D.C. | Walden. | August | 1970. |
|
http://www.faqs.org/rfcs/rfc65.html
RFC 0065 2008 August
dvd rental
dvd
Comments on Host/Host Protocol Document #1. D.C. Walden. August 1970.
Rules
|
© 2008 Internet Explorer 5+ or Netscape 6+
|
|
Recommended Sites: 1.
Arts -
Business -
Computers -
Games -
Health -
Home -
Kids and Teens -
News -
Recreation -
Reference -
Regional -
Science -
Shopping -
Society -
Sports -
World
Miss Gallery
- Top Anime Hentai
- DVD rental by mail
- Remortgages - Mortgages - Online Loans - Mortgage Calculator - Mortgage News
|
