分享
 
 
 

RFC860 - Telnet Timing Mark Option

王朝other·作者佚名  2008-05-31
窄屏简体版  字體: |||超大  

Network Working Group J. Postel

Request for Comments: 860 J. Reynolds

ISI

Obsoletes: NIC 16238 May 1983

TELNET TIMING MARK OPTION

This RFCspecifies a standard for the ARPA community. Hosts on the ARPA

Internet are eXPected to adopt and implement this standard.

1. Command Name and Code

TIMING-MARK 6

2. Command Meanings

IAC DO TIMING-MARK

The sender of this command REQUESTS that the receiver of this

command return a WILL TIMING-MARK in the data stream at the

"appropriate place" as defined in section 4 below.

IAC WILL TIMING-MARK

The sender of this command ASSURES the receiver of this command

that it is inserted in the data stream at the "appropriate place"

to insure synchronization with a DO TIMING-MARK transmitted by the

receiver of this command.

IAC WON'T TIMING-MARK

The sender of this command REFUSES to insure that this command is

inserted in the data stream at the "appropriate place" to insure

synchronization.

IAC DON'T TIMING-MARK

The sender of this command notifies the receiver of this command

that a WILL TIMING-MARK (previously transmitted by the receiver of

this command) has been IGNORED.

3. Default

WON'T TIMING-MARK, DON'T TIMING-MARK

i.e., No explicit attempt is made to synchronize the activities at

the two ends of the TELNET connection.

4. Motivation for the Option

RFC860 May 1983

It is sometimes useful for a user or process at one end of a TELNET

connection to be sure that previously transmitted data has been

completely processed, printed, discarded, or otherwise disposed of.

This option provides a mechanism for doing this. In addition, even

if the option request (DO TIMING-MARK) is refused (by WON'T

TIMING-MARK) the requester is at least assured that the refuser has

received (if not processed) all previous data.

As an example of a particular application, imagine a TELNET

connection between a physically full duplex terminal and a "full

duplex" server system which permits the user to "type ahead" while

the server is processing previous user input. Suppose that both

sides have agreed to Suppress Go Ahead and that the server has agreed

to provide echoes. The server now discovers a command which it

cannot parse, perhaps because of a user typing error. It would like

to throw away all of the user's "type-ahead" (since failure of the

parsing of one command is likely to lead to incorrect results if

subsequent commands are executed), send the user an error message,

and resume interpretation of commands which the user typed after

seeing the error message. If the user were local, the system would

be able to discard the buffered input; but input may be buffered in

the user's host or elsewhere. Therefore, the server might send a DO

TIMING-MARK and hope to receive a WILL TIMING-MARK from the user at

the "appropriate place" in the data stream.

The "appropriate place", therefore (in absence of other information)

is clearly just before the first character which the user typed after

seeing the error message. That is, it should appear that the timing

mark was "printed" on the user's terminal and that, in response, the

user typed an answering timing mark.

Next, suppose that the user in the example above realized that he had

misspelled a command, realized that the server would send a DO

TIMING-MARK, and wanted to start "typing ahead" again without waiting

for this to occur. He might then instrUCt his own system to send a

WILL TIMING-MARK to the server and then begin "typing ahead" again.

(Implementers should remember that the user's own system must

remember that it sent the WILL TIMING-MARK so as to discard the

DO/DON'T TIMING-MARK when it eventually arrives.) Thus, in this case

the "appropriate place" for the insertion of the WILL TIMING-MARK is

the place defined by the user.

It should be noted, in both of the examples above, that it is the

responsibility of the system which transmits the DO TIMING-MARK to

discard any unwanted characters; the WILL TIMING-MARK only provides

help in deciding which characters are "unwanted".

5. Description of the Option

RFC860 May 1983

Suppose that Process A of Figure 1 wishes to synchronize with B. The

DO TIMING-MARK is sent from A to B. B can refuse by replying WON'T

TIMING-MARK, or agree by permitting the timing mark to flow through

his "outgoing" buffer, BUF2. Then, instead of delivering it to the

terminal, B will enter the mark into his "incoming" buffer BUF1, to

flow through toward A. When the mark has propagated through B's

incoming buffer, B returns the WILL TIMING-MARK over the TELNET

connection to A.

PROCESS A TELNETconnection PROCESS B Terminal

+-----------+ +---------------+ Timing+-------+

WILL TIMING MARK BUF 1 Mark

<------------------------<------

----- ^

BUF 2 ^

--------------->--------------->

DO TIMING MARK -----

+-----------+ +---------------+ +-------+

(NVT process).ME;

Figure 1

When A receives the WILL TIMING-MARK, he knows that all the

information he sent to B before sending the timing mark been

delivered, and all the information sent from B to A before turnaround

of the timing mark has been delivered.

Three typical applications are:

A. Measure round-trip delay between a process and a terminal or

another process.

B. Resynchronizing an interaction as described in section 4 above.

A is a process interpreting commands forwarded from a terminal

by B. When A sees an illegal command it:

i. Sends <carriage return>, <line feed>, <question mark>.

ii. Sends DO TIMING-MARK.

iii. Sends an error message.

iv. Starts reading input and throwing it away until it

receives a WILL TIMING-MARK.

v. Resumes interpretation of input.

RFC860 May 1983

This achieves the effect of flushing all "type ahead" after the

erroneous command, up to the point when the user actually saw

the question mark.

C. The dual of B above. The terminal user wants to throw away

unwanted output from A.

i. B sends DO TIMING-MARK, followed by some new command.

ii. B starts reading output from A and throwing it away until

it receives WILL TIMING-MARK.

iii. B resumes forwarding A's output to the terminal.

This achieves the effect of flushing all output from A, up to

the point where A saw the timing mark, but not output generated

in response to the following command.

 
 
 
免责声明:本文为网络用户发布,其观点仅代表作者个人观点,与本站无关,本站仅提供信息存储服务。文中陈述内容未经本站证实,其真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。
2023年上半年GDP全球前十五强
 百态   2023-10-24
美众议院议长启动对拜登的弹劾调查
 百态   2023-09-13
上海、济南、武汉等多地出现不明坠落物
 探索   2023-09-06
印度或要将国名改为“巴拉特”
 百态   2023-09-06
男子为女友送行,买票不登机被捕
 百态   2023-08-20
手机地震预警功能怎么开?
 干货   2023-08-06
女子4年卖2套房花700多万做美容:不但没变美脸,面部还出现变形
 百态   2023-08-04
住户一楼被水淹 还冲来8头猪
 百态   2023-07-31
女子体内爬出大量瓜子状活虫
 百态   2023-07-25
地球连续35年收到神秘规律性信号,网友:不要回答!
 探索   2023-07-21
全球镓价格本周大涨27%
 探索   2023-07-09
钱都流向了那些不缺钱的人,苦都留给了能吃苦的人
 探索   2023-07-02
倩女手游刀客魅者强控制(强混乱强眩晕强睡眠)和对应控制抗性的关系
 百态   2020-08-20
美国5月9日最新疫情:美国确诊人数突破131万
 百态   2020-05-09
荷兰政府宣布将集体辞职
 干货   2020-04-30
倩女幽魂手游师徒任务情义春秋猜成语答案逍遥观:鹏程万里
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案神机营:射石饮羽
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案昆仑山:拔刀相助
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案天工阁:鬼斧神工
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案丝路古道:单枪匹马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:与虎谋皮
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:李代桃僵
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案镇郊荒野:指鹿为马
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:小鸟依人
 干货   2019-11-12
倩女幽魂手游师徒任务情义春秋猜成语答案金陵:千金买邻
 干货   2019-11-12
 
推荐阅读
 
 
 
>>返回首頁<<
 
靜靜地坐在廢墟上,四周的荒凉一望無際,忽然覺得,淒涼也很美
© 2005- 王朝網路 版權所有