RFC747 Recent extensions to the SUPDUP Protocol

0747 Recent extensions to the SUPDUP Protocol. M.R. Crispin. March 1978. (Format: TXT=2870 bytes) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

NWG/RFC# 747                                         MRC 21-MAR-78 44015
Recent Extensions to the SUPDUP Protocol



Network Working Group                                       Mark Crispin
Request for Comments 747                                           SU-AI
NIC 44015                                                  21 March 1978

Updates: RFC 734.  See also RFC 746.

                Recent Extensions to the SUPDUP Protocol

Recently,  some extensions  have been made to the SUPDUP protocol.   RFC
746,  by Richard   Stallman, documented  the SUPDUP  graphics extension.
In addition, a TTYOPT  bit has  been added and  two more  variables have
been added to the initial  negotiation.   This RFC describes the changes
from  RFC 734,  but excludes  the  detailed  information  in   RFC  746.
These  extensions  are  upwards  and   downwards  compatable,   and  are
completely  optional.    For most  SUPDUP   user  and  server  programs,
RFC   734   remains    an   adequate   description  of   the   protocol.
However,   it  is  suggested   that  if  the  console's  line  speed  is
known,  the  user SUPDUP  should be modified to  send the new ISPEED and
OSPEED  variables   (sending  0 for SMARTS if the  graphics extension is
not to  be used)  so  the server can  handle buffering for  the terminal
better.

Since these changes  are compatable  and optional, and since the  SUPDUP
protocol is being actively worked on at the present time, I have elected
to issue  this  update  RFC  rather  than  an  updated  version   of RFC
734.   An updated 734 will be issued when the protocol stabilizes again.

Three new variables  have  been added to  the initial  negotiation.   In
order,  they are SMARTS,  ISPEED,  and OSPEED.   Consequently, the count
should now be -10,,0, or, in octal, 777770000000.

The SMARTS  variable  specifies what "smarts" (in general, what graphics
capabilities)  the terminal  has.  Like the TTYOPT variable, a bit being
true implies  that the terminal has this option.  RFC 746 describes this
variable  and the  SUPDUP   graphics   option  in complete  detail.   If
the  graphics extension is not to be used, SMARTS should be set to 0.

The ISPEED  and OSPEED  variables are respectively the input and  output
baud rates  of the  terminal,  if  known.   For  example,  a  150./1200.
baud terminal  would  have an ISPEED of 150.   and an OSPEED of 1200.  A
speed  of zero means the line speed is indeterminate.

The %TPPRN   TTYOPT   bit  (value  0,,200) has  been  added.   This  bit
specifies  that the system should  swap parenthesis with square brackets
on input.   This is  often  desirable  for  LISP users  who  are using a
terminal  which has  parenthesis   as   a   shift  character   but   not
square   brackets. This bit is normally off and servers are not required
to implement it.



一覧

 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 

スポンサーリンク

mask マスク効果を指定する

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

上に戻る