% 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/rfc1301.txt

@misc{rfc1301,
    series =    {Request for Comments},
    number =    1301,
    howpublished =  {RFC 1301},
    publisher = {RFC Editor},
    doi =       {10.17487/RFC1301},
    url =       {https://www.rfc-editor.org/info/rfc1301},
    author =    {Susan M. Armstrong and Keith A. Marzullo and Alan O. Freier},
    title =     {{Multicast Transport Protocol}},
    pagetotal = 38,
    year =      1992,
    month =     feb,
    abstract =  {This memo describes a protocol for reliable transport that utilizes the multicast capability of applicable lower layer networking architectures. The transport definition permits an arbitrary number of transport providers to perform realtime collaborations without requiring networking clients (aka, applications) to possess detailed knowledge of the population or geographical dispersion of the participating members. It is not network architectural specific, but does implicitly require some form of multicasting (or broadcasting) at the data link level, as well as some means of communicating that capability up through the layers to the transport. This memo provides information for the Internet community. It does not specify an Internet standard.},
}