RFC729 Telnet byte macro option

0729 Telnet byte macro option. D. Crocker. May 1977. (Format: TXT=6509 bytes) (Obsoleted by RFC0735) (Status: UNKNOWN)

日本語訳
RFC一覧

参照

Network Working Group				 Dave Crocker, Rand-ISD
Request for Comments: 729			 (Dcrocker at Rand-Unix)
NlC: 40306					 13 May l977




			TELNET Byte Macro Option


1. Command name and code:

   BM 19

2. Command Meanings:

   IAC WILL BM

	The sender of this  command REQUESTS or AGREES  to use the  BM
	option, and will send sing1e  data characters which are to  be
	interpreted as if longer data strings had been sent.

   IAC WON'T BM

	The  sender  of  this  option  REFUSES  to  send  single  data
	characters which  are  to be  interpreted  as if  longer  data
	strings had been sent.

   IAC DO BM

	The sender REQUESTS or AGREES to have the other side (send  of
	WILL BM) issue  send single  data characters which  are to  be
	interpreted as if longer data strings had been sent.

   IAC DON'T BM

	The sender REFUSES to allow the other side to send single data
	characters which  are  to be  interpreted  as if  longer  data
	strings had been sent.

   IAC SB BM   
                    IAC SE
	where:

	    is the  data byte actually  to be sent  across
	   the network; it may NOT be Telnet IAC (decimal 255).


RFC #729 Telnet Byte Macro Option				 Page 2



	    is a  one-byte binary number,  indicating how  many
	    characters follow, up to the ending  IAC
	   SE, but not including it.

	    is a string of one or more Telnet  ASCII
	   characters and/or commands,  which the  is  to
	   represent; any  character may  occur within  an  .

	The indicated    will  be  sent  instead  of  the
	indicated . The receiver of the 
	(the sender  of the  DO BM)  is to  behave EXACTLY  as if  the
	 of bytes had instead been received from the
	network. This  interpretation is  to  occur before  any  other
	Telnet interpretations, unless the  occurs as part
	of a BM subcommand; in this case no special interpretation  is
	to be made.

	Note that the effect of a particular  may be
	negated by reseting it to "expand" into itself.

	 is decimal 01.


   IAC SB BM   IAC SE

	The receiver  of the   for    accepts  the
	requested definition and will perform the indicating expansion
	whenever a   is received and is  not part of a  BM
	subcommand.

	 is decimal 02.


   IAC SB BM    IAC SE

	The receive  of  the   for    refuses  to
	perform  the  indicated  translation  from     to
	 either because the particular 
	is not  an acceptable  choice  or because  the length  of  the
	 exceeds available storage.

    is decimal 03.

    may be

	    which is decimal 01; or

	    which is decimal 02.


RFC #729 Telnet Byte Macro Option				 Page 3




   IAC SB BM   IAC SE

	The  is to be treated as real data, rather than as
	representative of the 

	 is decimal 03.




3. Default:

   WON'T BM -- DON'T BM

	No reinterpretation of data is allowed.

4. Motivation for the option:

   Subcommands for Telnet options currently require a minimum of  five
   characters to be sent over the network (i.e., IAC SB 

一覧

 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 

スポンサーリンク

RENAME オブジェクト名を変更する

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

上に戻る