RFC 2191: VENUS - Very Extensive Non-Unicast Service
In plain English — editorial summary, not part of the RFC
This document focuses exclusively on the problems associated with extending the MARS model to cover multiple clusters or clusters spanning more than one subnet. It describes a hypothetical solution, dubbed "Very Extensive NonUnicast Service" (VENUS), and shows how complex such a service would be. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2191
- Published
- September 1997
- Authors
- G. Armitage
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2121Issues affecting MARS Cluster SizeCurrent
March 1997
- RFC 2236Internet Group Management Protocol, Version 2Updated
November 1997
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2331ATM Signalling Support for IP over ATM - UNI Signalling 4.0 UpdateCurrent
April 1998
- RFC 2337Intra-LIS IP multicast among routers over ATM using Sparse Mode PIMCurrent
April 1998
- RFC 3259A Message Bus for Local CoordinationCurrent
May 2002
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
- RFC 3738Wave and Equation Based Rate Control (WEBRC) Building BlockCurrent
April 2004
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?