RFC1096 Telnet X display location option

1096 Telnet X display location option. G.A. Marcy. March 1989. (Format: TXT=4634 bytes) (Status: PROPOSED STANDARD)

日本語訳
RFC一覧

参照

Network Working Group                                           G. Marcy
Request for Comments: 1096                    Carnegie Mellon University
                                                              March 1989


                    Telnet X Display Location Option

Status of This Memo

   This RFC specifies a standard for the Internet community.  Hosts on
   the Internet that transmit the X display location within the Telnet
   protocol are expected to adopt and implement this standard.
   Distribution of this memo is unlimited.

   This standard is modelled on RFC 1079 [1], the telnet terminal speed
   option.  Much of the text of this document is copied from that RFC.

Motivation

   When a user is running the Telnet client under the X window system,
   it is useful for the remote Telnet to know the X display location of
   that client.  For example, the user might wish to start other X
   applications from the remote host using the same display location as
   the Telnet client.  The purpose of this option is to make this
   information available through telnet connections.

1. Command Name and Code

      X-DISPLAY-LOCATION (XDISPLOC)

      Code = 35

2. Command Meanings

      IAC WILL X-DISPLAY-LOCATION

         Sender is willing to send the X display location in a
         subsequent sub-negotiation.

      IAC WON'T X-DISPLAY-LOCATION

         Sender refuses to send the X display location.

      IAC DO X-DISPLAY-LOCATION

         Sender is willing to receive the X display location in a
         subsequent sub-negotiation.




Marcy                                                           [Page 1]

RFC 1096            Telnet X Display Location Option          March 1989


      IAC DON'T X-DISPLAY-LOCATION

         Sender refuses to accept the X display location.

      IAC SB X-DISPLAY-LOCATION SEND IAC SE

         Sender requests receiver to transmit his (the receiver's) X
         display location.  The code for SEND is 1.  (See below.)

      IAC SB X-DISPLAY-LOCATION IS ... IAC SE

         Sender is stating his X display location.  The code for IS is
         0.  (See below.)

3. Default

      WON'T X-DISPLAY-LOCATION

         The X display location will not be exchanged.

      DON'T X-DISPLAY-LOCATION

         The X display location will not be exchanged.

4. Description of the Option

   WILL and DO are used only to obtain and grant permission for future
   discussion.  The actual exchange of status information occurs within
   option subcommands (IAC SB X-DISPLAY-LOCATION...).

   Once the two hosts have exchanged a WILL and a DO, the sender of the
   DO X-DISPLAY-LOCATION is free to request the X display location.
   Only the sender of the DO may send requests (IAC SB X-DISPLAY-
   LOCATION SEND IAC SE) and only the sender of the WILL may transmit
   actual X display location (within an IAC SB X-DISPLAY-LOCATION IS ...
   IAC SE command).  The X display location may not be sent
   spontaneously, but only in response to a request.

   The X display location is an NVT ASCII string.  This string follows
   the normal Unix convention used for the DISPLAY environment variable,
   e.g.,

         :[.]

   No extraneous characters such as spaces may be included.

      The following is an example of use of the option:




Marcy                                                           [Page 2]

RFC 1096            Telnet X Display Location Option          March 1989


         Host1: IAC DO X-DISPLAY-LOCATION

         Host2: IAC WILL X-DISPLAY-LOCATION

      (Host1 is now free to request status information at any time.)

         Host1: IAC SB X-DISPLAY-LOCATION SEND IAC SE

         Host2: IAC SB X-DISPLAY-LOCATION IS "SRI-NIC.ARPA:0.0" IAC SE

      (This command is 22 octets.)

5. Implementation Suggestions

   Since the X display location may not contain a hostname on the client
   host, i.e., ":0" or "unix:0.0", the Telnet client will need to modify
   the location appropriately before sending it on to the remote Telnet.

Reference

   [1]  Hedrick, C., "Telnet Terminal Speed Option", RFC 1079,
        Rutgers University, December, 1988.

Author's Address:

   Glenn A. Marcy
   Carnegie Mellon University
   School of Computer Science
   Pittsburgh, PA 15213-3890

   Phone: (412) 268-7669

   Email: Glenn.Marcy@CS.CMU.EDU


















一覧

 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 

スポンサーリンク

特定のスタイルを指定すると省略した終了タグが正しい位置に補われない

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

上に戻る