RFC 988: Host extensions for IP multicasting
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1054, RFC 1112.
Current document in this lineage: RFC 1112 — Host extensions for IP multicasting
In plain English — editorial summary, not part of the RFC
This memo specifies the extensions required of a host implementation of the Internet Protocol (IP) to support internetwork multicasting. This specification supersedes that given in RFC-966, and constitutes a proposed protocol standard for IP multicasting in the ARPA-Internet. The reader is directed to RFC-966 for a discussion of the motivation and rationale behind the multicasting extension specified here.
Document record
- Document ID
- RFC988
- Published
- July 1986
- Authors
- S.E. Deering
- Status
- UNKNOWN
- Stream
- Legacy
- Area
- —
- Pages
- 20
- Also known as
- —
- Obsoletes:
- RFC 966
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 966 (1985)
- RFC 988 (1986)
- RFC 1054 (1988)
- RFC 1112 (1989) ✓
Read the full history of Host extensions for IP multicasting →
Referenced by
2 later RFCs formally update or obsolete part of this document.
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 2327SDP: Session Description ProtocolObsoleted
April 1998
- RFC 2373IP Version 6 Addressing ArchitectureObsoleted
July 1998
- RFC 2375IPv6 Multicast Address AssignmentsCurrent
July 1998
- RFC 3513Internet Protocol Version 6 (IPv6) Addressing ArchitectureObsoleted
April 2003
- RFC 4566SDP: Session Description ProtocolObsoleted
July 2006
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?