文档下载 文档下载导航
设为首页 | 加入收藏
搜索 请输入内容:  
 导航当前位置: 文档下载 > 所有分类 > IT/计算机 > 计算机软件及应用 > rfc893.Trailer Encapsulations
侵权投诉

rfc893.Trailer Encapsulations

rfc文档

aligned on a page boundary and must have a size which is a multiple of the hardware page size (or filled to a page boundary). The latter restriction assumes virtual memory protection is maintained at the page level; different architectures may alter these prerequisites. Data to be transmitted across a network may easily be segmented in the appropriate size, but unless the encapsulating protocol header information is fixed in size, alignment to a page boundary is

virtually impossible. Protocol header information may vary in size due to the use of multiple protocols (each with a different header), or it may vary in size by agreement (for example, when optional

information is included in the header). To insure page alignment the header information which prefixes data destined for the receiver must be reduced to a fixed size; this is normally the case at the link level of a network. By taking all (possibly) variable length header information and moving it after the data segment a sending host may "do its best" in allowing the receiving host the opportunity to

receive data on a page aligned boundary. This rearrangement of data at the link level to force variable length header information to "trail" the data is the substance of the trailer encapsulation. There are several implicit assumptions in the above argument.

1. The receiving host must be willing to accept trailers. As this is a link level encapsulation, unless a host to host negotiation is performed (preferably at the link level to avoid violating

layering principles), only certain hosts will be able to converse, or their communication may be significantly impaired if trailer packets are mixed with non-trailer packets.

2. The cost of receiving data on a page aligned boundary should be comparable to receiving data on a non-page aligned boundary. If the overhead of insuring proper alignment is too high, the savings in avoiding copy operations may not be cost effective.

3. The size of the variable length header information should be significantly less than that of the data segment being

transmitted. It is possible to move trailing information without physically copying it, but often implementation constraints and the characteristics of the underlying network hardware preclude merely remapping the header(s).

4. The memory to memory copying overhead which is expected to be performed by the receiver must be significant enough to warrant the added complexity in the both the sending and receiving host software.

The first point is well known and the motivation for this note.

Leffler & Karels [Page 2]

上一页第2页

你可能喜欢

热门文档

相关文档

  • RFC894

    组织:中国互动出版网(http://www.china-pub.com/) RFC文档中文翻译计划(http...Karels, "Trailer Encapsulations", RFC-893, University of California at ...

  • RFC895

    Karels, "Trailer Encapsulations", RFC-893, University of California at Berkeley, April 1984. RFC895——A Standard for the Transmission of IP Datagrams ...

  • RFC895_IP 数据包通过试验性以太网网络的传输标准

    Karels, "Trailer Encapsulations", RFC-893, University of California at Berkeley, April 1984. RFC 文档中文翻译计划 3 分享到: X 分享到: 使用一键分享...

  • RFC1483ATM上的多协议封装

    Abstract This memo describes two encapsulations methods for carrying network ...SAR sublayer will have the CPCS-PDU Trailer right justified in the cell. ...

  • RFC948

    "Trailer Encapsulations". RFC-893, University of California at Berkeley, April 1984. RFC948—Two methods for the transmission of IP datagrams over IEEE ...

  • 伊甸网TCP-IP技术大全附录A RFC及标准化

    RFC1027 RFC903 RFC895 RFC894 RFC893 RFC877 附录A RFC及标准化 使用 461 ...“Trailer Encapsulations,”)Leffler, S.; Karels, M.J.; 1984 在公用数据...

  • RFC895_IP 数据包通过试验性以太网网络的传输标准

    Karels, "Trailer Encapsulations", RFC-893, University of California at Berkeley, April 1984. RFC 文档中文翻译计划 3 分享到: X 分享到: 使用一键分享...

站点地图 | 文档上传 | 侵权投诉 | 手机版
本站所有资源均来自互联网,本站只负责收集和整理,均不承担任何法律责任,如有侵权等其它行为请联系我们.
文档下载 Copyright 2013 doc.guandang.net All Rights Reserved.  -  email