• 软件测试技术
  • 软件测试博客
  • 软件测试视频
  • 开源软件测试技术
  • 软件测试论坛
  • 软件测试沙龙
  • 软件测试资料下载
  • 软件测试杂志
  • 软件测试人才招聘
    暂时没有公告

字号: | 推荐给好友 上一篇 | 下一篇

RFC534 - Lost message detection

发布: 2007-6-23 14:09 | 作者:   | 来源:   | 查看: 13次 | 进入软件测试论坛讨论

领测软件测试网

   
  Network Working Group David Walden
Request for Comments: 534 BBN-NET
NIC: 17453 17 July 1973
References: 512, 516, 533

Lost Message Detection

As an aside to RFC533, note that if sending Hosts do uniquely

identify messages on a given link using the extra four bits and
receiving Hosts do look at these bits, a lost message detection
system such as those suggested in RFCs 512 and 516 drops right out of
using of the unique message-id. These extra four bits can be treated
as Hathaway's SCB of RFC512 providing a 16 element sequence number
on a per connection basis. A 16 element sequence is sufficient as
the IMPs never allow more than four outstanding messages at one time
between a given pair of Hosts. As Hathaway also suggests, the 0
element in the sequence can be used to indicate to the receiving Host
that sequence numbers are not being used.

To summarize, there appear to be three modes of using the message-id
number under Host/Host protocol:

1. The sender can always set the extra four bits to 0 and only
transmit one message over a given link at a time -- this is slow
but it allows orderly retransmission of messages without any help
from the receiver.

2. The receiver can give no help to the sender. In this case it
doesn't matter whether the sender uses the extra four bits to
uniquely identify the messages or not -- the sender has no method
of orderly retransmission, although the sender can accurately
identify which message was lost if the sender has uniquely
identified the messages.

3. The sender can have multiple messages outstanding (i.e., RFNMs not
received) on a given link and the receiver can help the sender.
In this case, if the sender uses the extra four bits to uniquely
identify the messages in a way which can be synchronized with the
receiver (e.g., sequential id numbers), the receiver can reliably
detect lost messages.

Although it probably will seem insufficient to some, if the sender
and receiver use synchronized unique message-id numbers, very
reliable retransmission schemes are readily available. For instance,
the sender can retransmit the appropriate messages in response to
incomplete transmissions and the receiver can use the unique
message-ids to sort the retransmitted messages into the proper order

with the other received messages. Alternatively, the receiver can
discard all messages received out of order and the sender can back up
and retransmit a message for which an incomplete transmission was
received and all subsequent messages.

[ This RFCwas put into machine readable form for entry ]
[ into the online RFCarchives by Alex McKenzie with 10/99 ]

文章来源于领测软件测试网 https://www.ltesting.net/


关于领测软件测试网 | 领测软件测试网合作伙伴 | 广告服务 | 投稿指南 | 联系我们 | 网站地图 | 友情链接
版权所有(C) 2003-2010 TestAge(领测软件测试网)|领测国际科技(北京)有限公司|软件测试工程师培训网 All Rights Reserved
北京市海淀区中关村南大街9号北京理工科技大厦1402室 京ICP备10010545号-5
技术支持和业务联系:info@testage.com.cn 电话:010-51297073

软件测试 | 领测国际ISTQBISTQB官网TMMiTMMi认证国际软件测试工程师认证领测软件测试网