RFC 2102: Multicast Support for Nimrod : Requirements and Solution Approaches
In plain English — editorial summary, not part of the RFC
Nimrod does not specify a particular solution for multicasting. Rather, Nimrod may use any of a number of emerging multicast techniques. We identify the requirements that Nimrod has of a solution for multicast support. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2102
- Published
- February 1997
- Authors
- R. Ramanathan
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 23
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2374An IPv6 Aggregatable Global Unicast Address FormatObsoleted
July 1998
- RFC 2526Reserved IPv6 Subnet Anycast AddressesCurrent
March 1999
- RFC 3587IPv6 Global Unicast Address FormatCurrent
August 2003
- RFC 2103Mobility Support for Nimrod : Challenges and Solution ApproachesCurrent
February 1997
- RFC 2082RIP-2 MD5 AuthenticationObsoleted
January 1997
- RFC 2081RIPng Protocol Applicability StatementCurrent
January 1997
- RFC 2080RIPng for IPv6Current
January 1997
- RFC 2178OSPF Version 2Obsoleted
July 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?