RFC748 Telnet randomly-lose option

0748 Telnet randomly-lose option. M.R. Crispin. April 1 1978. (Format: TXT=2741 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

NWG/RFC# 748                                          MRC 1-APR-78 44125
Telnet Randomly-Lose Option



Network Working Group                                         M. Crispin
Request for Comments 748                                           SU-AI
NIC 44125                                                   1 April 1978

                      TELNET RANDOMLY-LOSE Option

1.  Command name and code.

   RANDOMLY-LOSE        256

2.  Command meanings.

   IAC WILL RANDOMLY-LOSE

      The sender  of this command  REQUESTS  permission  to, or confirms
      that it will, randomly lose.

   IAC WON'T RANDOMLY-LOSE

      The sender of this command REFUSES to randomly lose.

   IAC DO RANDOMLY-LOSE

      The sender  of this command  REQUESTS that the receiver, or grants
      the receiver permission to, randomly lose.

   IAC DON'T RANDOMLY-LOSE

      The command sender DEMANDS that the receiver not randomly lose.

3.  Default.

   WON'T RANDOMLY-LOSE

   DON'T RANDOMLY-LOSE

   i.e., random lossage will not happen.

4.  Motivation for the option.

   Several  hosts appear  to provide  random  lossage,  such  as  system
   crashes,  lost data,  incorrectly functioning programs, etc., as part
   of their services.   These services are often undocumented and are in
   general  quite confusing  to the novice  user.   A general  means  is
   needed to allow the user to disable these features.







                                 - 1 -

NWG/RFC# 748                                          MRC 1-APR-78 44125
Telnet Randomly-Lose Option



5.  Description of the option.

   The normal  mode does not allow random  lossage; therefore the system
   is not allowed  to crash,  mung user files, etc.  If the server wants
   to provide  random lossage, it must first ask for permission from the
   user by sending IAC WILL RANDOMLY-LOSE.

   If the user wants  to permit  the server  to randomly lose, it replys
   with  IAC  DO   RANDOMLY-LOSE.    Otherwise   it   sends   IAC   DONT
   RANDOMLY-LOSE, and the server is forbidden from randomly losing.

   Alternatively, the user could request the server to randomly lose, by
   sending  IAC DO RANDOMLY-LOSE,  and the server will either reply with
   IAC WILL RANDOMLY-LOSE,  meaning that it will then proceed to do some
   random  lossage  (garbaging  disk files is recommended for an initial
   implementation).   Or,  it could send IAC WONT RANDOMLY-LOSE, meaning
   that it insists upon being reliable.

   Since  this is implemented  as a TELNET  option,  it is expected that
   servers  which do not implement  this option  will not randomly lose;
   ie, they will provide 100% reliable uptime.






























一覧

 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 

スポンサーリンク

$security_settingsクラス変数 セキュリティ設定の指定や、オーバーライドの指定

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

上に戻る