RFC 6450: Multicast Ping Protocol
In plain English — editorial summary, not part of the RFC
The Multicast Ping Protocol specified in this document allows for checking whether an endpoint can receive multicast -- both Source-Specific Multicast (SSM) and Any-Source Multicast (ASM). It can also be used to obtain additional multicast-related information, such as multicast tree setup time. This protocol is based on an implementation of tools called "ssmping" and "asmping". [STANDARDS-TRACK]
Document record
- Document ID
- RFC6450
- Published
- December 2011
- Authors
- S. Venaas
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 24
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6308Overview of the Internet Multicast Addressing ArchitectureCurrent
June 2011
- RFC 7450Automatic Multicast TunnelingUpdated
February 2015
- RFC 4609Protocol Independent Multicast - Sparse Mode (PIM-SM) Multicast Routing Security Issues and EnhancementsCurrent
October 2006
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
- RFC 7667RTP TopologiesCurrent
November 2015
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 8115DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 PrefixesCurrent
March 2017
- RFC 8638IPv4 Multicast over an IPv6 Multicast in Softwire Mesh NetworksCurrent
September 2019
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?