RFC 2588: IP Multicast and Firewalls
In plain English — editorial summary, not part of the RFC
In this document, we discuss the issues surrounding the traversal of IP multicast traffic across a firewall, and describe possible ways in which a firewall can implement and control this traversal. We also explain why some firewall mechanisms - such as SOCKS - that were designed specifically for unicast traffic, are less appropriate for multicast. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2588
- Published
- May 1999
- Authors
- R. Finlayson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2356Sun's SKIP Firewall Traversal for Mobile IPCurrent
June 1998
- RFC 2519A Framework for Inter-Domain Route AggregationCurrent
February 1999
- RFC 2407The Internet IP Security Domain of Interpretation for ISAKMPObsoleted
November 1998
- RFC 2406IP Encapsulating Security Payload (ESP)Obsoleted
November 1998
- RFC 2402IP Authentication HeaderObsoleted
November 1998
- RFC 2871A Framework for Telephony Routing over IPCurrent
June 2000
- RFC 2270Using a Dedicated AS for Sites Homed to a Single ProviderCurrent
January 1998
- RFC 2104HMAC: Keyed-Hashing for Message AuthenticationUpdated
February 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?