rfc文档
Thought has been given to negotiating the user of trailers on a per host basis using a variant of the Address Resolution Protocol [2] (actually augmenting the protocol), but at present all systems using trailers require hosts sharing a network medium to uniformly accept trailers or never transmit them. (The latter is easily carried out at boot time in 4.2BSD without modifying the operating system source code.)
The second point is (to our knowledge) insignificant. While a host may not be able to take advantage of the alignment and size
properties of a trailer packet, it should nonetheless never hamper it.
Regarding the third point, let us assume the trailing header
information is copied and not remapped, and consider the header
overhead in the TCP/IP protocols as a representative example [3]. If we assume both the TCP and IP protocol headers are part of the
variable length header information, then the smallest trailer packet (generated by a VAX) would have 512 bytes of data and 40+ bytes of header information (plus the trailer header described later). While the trailing header could have IP and/or TCP options included this would normally be rare (one would expect most TCP options, for
example, to be included in the initial connection setup exchange) and certainly much smaller than 512 bytes. If the data segment is
larger, the ratio decreases and the expected gain due to fewer copies on the receiving end increases. Given the relative overheads of a memory to memory copy operation and that of a page map manipulation (including translation buffer invalidation), the advantage is obvious.
The fourth issue, we believe, is actually a non-issue. In our
implementation the additional code required to support the trailer encapsulation amounts to about a dozen lines of code in each link level "network interface driver". The resulting performance
improvement more than warrants this minor investment in software. It should be recognized that modifying the network (and normal link) level format of a packet in the manner described forces the receiving host to buffer the entire packet before processing. Clever
implementations may parse protocol headers as the packet arrives to find out the actual size (or network level packet type) of an incoming message. This allows these implementations to avoid
preallocating maximum sized buffers to incoming packets which it can recognize as unacceptable. Implementations which parses the network level format on the fly are violating layering principles which have been extolled in design for some time (but often violated in
implementation). The problem of postponing link level type
Leffler & Karels [Page 3]
组织:中国互动出版网(http://www.china-pub.com/) RFC文档中文翻译计划(http...Karels, "Trailer Encapsulations", RFC-893, University of California at ...
Karels, "Trailer Encapsulations", RFC-893, University of California at Berkeley, April 1984. RFC895——A Standard for the Transmission of IP Datagrams ...
Karels, "Trailer Encapsulations", RFC-893, University of California at Berkeley, April 1984. RFC 文档中文翻译计划 3 分享到: X 分享到: 使用一键分享...
Abstract This memo describes two encapsulations methods for carrying network ...SAR sublayer will have the CPCS-PDU Trailer right justified in the cell. ...
"Trailer Encapsulations". RFC-893, University of California at Berkeley, April 1984. RFC948—Two methods for the transmission of IP datagrams over IEEE ...
RFC1027 RFC903 RFC895 RFC894 RFC893 RFC877 附录A RFC及标准化 使用 461 ...“Trailer Encapsulations,”)Leffler, S.; Karels, M.J.; 1984 在公用数据...
Karels, "Trailer Encapsulations", RFC-893, University of California at Berkeley, April 1984. RFC 文档中文翻译计划 3 分享到: X 分享到: 使用一键分享...
热门文档