RFC 2149: Multicast Server Architectures for MARS-based ATM multicasting
In plain English — editorial summary, not part of the RFC
This memo provides details on the design and implementation of an MCS, building on the core mechanisms defined in RFC 2022. It also provides a mechanism for using multiple MCSs per group for providing fault tolerance. This approach can be used with RFC 2022 based MARS server and clients, without needing any change in their functionality. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2149
- Published
- May 1997
- Authors
- R. Talpade; M. Ammar
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 18
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2147TCP and UDP over IPv6 JumbogramsObsoleted
May 1997
- RFC 2153PPP Vendor ExtensionsUpdated
May 1997
- RFC 2136Dynamic Updates in the Domain Name System (DNS UPDATE)Updated
April 1997
- RFC 2165Service Location ProtocolUpdated
June 1997
- RFC 2133Basic Socket Interface Extensions for IPv6Obsoleted
April 1997
- RFC 2132DHCP Options and BOOTP Vendor ExtensionsUpdated
March 1997
- RFC 2131Dynamic Host Configuration ProtocolUpdated
March 1997
- RFC 2128Dial Control Management Information Base using SMIv2Current
March 1997
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?