RFC562 Modifications to the TELNET Specification

0562 Modifications to the TELNET Specification. A.M. McKenzie. August 1973. (Format: TXT=2760, PDF=79307 bytes) (Updates RFC0495) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group                                        A. McKenzie
Request for Comments: 562                                      BBN-TENEX
NIC: 18638                                                28 August 1973
Updates: RFC 495
References: RFCs 513, 529


               Modifications to the TELNET Specification

   Almost four months have passed since the new TELNET Protocol
   specification was published.  Since then, only two RFCs have been
   issued suggesting modifications, and the most recent of these was
   distributed two months ago.  Further, the date from the old TELNET to
   the new TELNET (1 January 1974) is only four months away.  It
   therefore seems appropriate to officially modify the specification to
   account for the suggested modifications, and to declare a moratorium
   on the incorporation of additional suggestions until after the
   switchover. (Of course, no moratorium on the specification of
   additional options is required.)

   The two attached documents represent the revised TELNET Protocol
   specifications; they replace NIC #15372, TELNET Protocol
   Specification, and NIC #15373, TELNET Option Specifications.  The
   remainder of this RFC summarizes the changes.  Page numbers refer to
   the earlier documents.

Changes to TELNET Protocol Specification

   Page 8        - The phrase "blocked on input" is removed (see RFC
                   #513).

   Page 9, 10    - An additional use of IP is mentioned (see RFC #529).

   Page 10       - The explanation of AO is expanded (see RFC #513).

   Page 11       - The definition of "'print position' (e.g., an
                   overstrike)" is clarified (see RFC #513).

   Page 11, 12   - The description of the TELNET Synch Signal is
                   reworked to be in conformance with the ideas of RFC
                   #529 (also see RFC #513).

   Page 14       - The explanation of the CR-NUL convention is expanded
                   (see RFC #513).

   Page 16       - An additional command, End of Subnegotiation
                   Parameters (SE) is defined (see RFCs 513, 529).




A. McKenzie                                                     [Page 1]

RFC 562        Modifications to the TELNET Specification  28 August 1973


Changes to TELNET Option Specifications

   Pages 2, 3    - Use of the command SE is explained (see RFCs 513,
                   529).

   Page 3        - Doubling of IAC in subnegotiation parameters is
                   required (see RFC #513).


          [This RFC was put into machine readable form for entry]
      [into the online RFC archives by Helene Morin, Via Genie 12/99]








































A. McKenzie                                                     [Page 2]

一覧

 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 

スポンサーリンク

Nucleus

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

上に戻る