% Datatracker information for RFCs on the Legacy Stream is unfortunately often % incorrect. Please correct the bibtex below based on the information in the % actual RFC at https://rfc-editor.org/rfc/rfc934.txt @misc{rfc934, series = {Request for Comments}, number = 934, howpublished = {RFC 934}, publisher = {RFC Editor}, doi = {10.17487/RFC0934}, url = {https://www.rfc-editor.org/info/rfc934}, author = {}, title = {{Proposed standard for message encapsulation}}, pagetotal = 10, year = 1985, month = jan, abstract = {This memo concerns itself with message forwarding. Forwarding can be thought of as encapsulating one or more messages inside another. Although this is useful for transfer of past correspondence to new recipients, without a decapsulation process (which this memo terms "bursting"), the forwarded messages are of little use to the recipients because they can not be distributed, forwarded, replied-to, or otherwise processed as separate individual messages. In order to burst a message it is necessary to know how the component messages were encapsulated in the draft. At present there is no unambiguous standard for interest group digests. This RFC proposes a proposed protocol for the ARPA-Internet community, and requests discussion and suggestions for improvements.}, }