RFC355 Response to NWG/RFC 346

0355 Response to NWG/RFC 346. J. Davidson. June 1972. (Format: TXT=3717 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                 John Davidson
Request for Comments #355                             UH-ALOHA SYSTEM
NIC # 10597                                           9 June 72
Category:  Local Echoing, Remote Echoing, Satellite
References:  RFC 346














                        RESPONSE TO NWG/RFC 346

















                             John Davidson

                              June 9, 1972











                                                                [Page 1]

   Long transmission delays such as those inherent in satellite
   communication are most certainly a cause for concern among users of
   remote interactive systems.  Since the University of Hawaii will, by
   the end of this year, be linked to the ARPANET via satellite, the
   consequences of such delays are perhaps of more immediate concern to
   us than to current members of the surface net.  Consequently the BCC
   500 research group here has been studying various solutions to the
   problems of buffer allocation, partitioned echoing, etc. re-introduced
   in RFC 346.

        Generally, the solutions come from extensions to the original
   design concepts of the BCC 500 distributed communication system.  The
   500 was designed to serve a large number of geographically-scattered
   users each of whom accessed the central computing facility through one
   of several remote concentrators.  [The concept is not too unlike that
   of users at different TIPs all accessing a single host.] Since it was
   felt that in full-duplex, character-by-character interaction, echo
   delays of any noticeable length should not be tolerated, a facility
   was provide whereby the concentrator could provide local (to the
   terminal) echoing when deemed appropriate.  (A character input/output
   microprocessor, the CHIO, in implicit conjunction with the terminal
   user's process executing in the CPU dictated when it was appropriate.)
   The problems associated with coordinating the concentrator and CHIO in
   the partioning of echoing were solved for the BCC 500, but are not
   immediately extensible to the asynchronous message transmissions of
   the ARPANET - especially with the introduction of satellite delays.
   As stated, we are working on some viable alternatives.

        It is not known, at present, what effects the incorporation of
   these partitioned echoing techniques might have on the existing net.
   Perhaps local echoing will become a function of User TELNETs; most
   certainly local echoing should be available in the TIP.  But could it
   be incorporated into the IMP so that TIP and User TELNETs can be used
   without change?  If so, what happens to the concentrator's local
   echoing capability in a system such as the BCC 500?

        These questions do not have immediate answers.  Other problems
   obviously exist because of the differences in serving system
   conventions for terminal control.  We, in conjunction with the ILLIAC
   group at NASA-AMES, are seeking solutions to such problems in general,
   with an eye toward their implementation








                                                                [Page 2]

   on the net.  I would appreciate hearing of any other research being
   performed in this area, and will be happy to discuss the findings of
   our group with any interested parties.















         [ This RFC was put into machine readable form for entry ]
         [ into the online RFC archives by BBN Corp. under the   ]
         [ direction of Alex McKenzie.                      1/97 ]






























                                                                [Page 3]

一覧

 RFC 1〜100  RFC 1401〜1500  RFC 2801〜2900  RFC 4201〜4300 
 RFC 101〜200  RFC 1501〜1600  RFC 2901〜3000  RFC 4301〜4400 
 RFC 201〜300  RFC 1601〜1700  RFC 3001〜3100  RFC 4401〜4500 
 RFC 301〜400  RFC 1701〜1800  RFC 3101〜3200  RFC 4501〜4600 
 RFC 401〜500  RFC 1801〜1900  RFC 3201〜3300  RFC 4601〜4700 
 RFC 501〜600  RFC 1901〜2000  RFC 3301〜3400  RFC 4701〜4800 
 RFC 601〜700  RFC 2001〜2100  RFC 3401〜3500  RFC 4801〜4900 
 RFC 701〜800  RFC 2101〜2200  RFC 3501〜3600  RFC 4901〜5000 
 RFC 801〜900  RFC 2201〜2300  RFC 3601〜3700  RFC 5001〜5100 
 RFC 901〜1000  RFC 2301〜2400  RFC 3701〜3800  RFC 5101〜5200 
 RFC 1001〜1100  RFC 2401〜2500  RFC 3801〜3900  RFC 5201〜5300 
 RFC 1101〜1200  RFC 2501〜2600  RFC 3901〜4000  RFC 5301〜5400 
 RFC 1201〜1300  RFC 2601〜2700  RFC 4001〜4100  RFC 5401〜5500 
 RFC 1301〜1400  RFC 2701〜2800  RFC 4101〜4200 

スポンサーリンク

各メーカーのルーターのID・パスワードの一覧 I

ホームページ製作・web系アプリ系の製作案件募集中です。

上に戻る