RFC 8487: Mtrace Version 2: Traceroute Facility for IP Multicast
In plain English — editorial summary, not part of the RFC
This document describes the IP multicast traceroute facility, named Mtrace version 2 (Mtrace2). Unlike unicast traceroute, Mtrace2 requires special implementations on the part of routers. This specification describes the required functionality in multicast routers, as well as how an Mtrace2 client invokes a Query and receives a Reply.
Document record
- Document ID
- RFC8487
- Published
- October 2018
- Authors
- H. Asaeda; K. Meyer; W. Lee
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 41
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 7887Hierarchical Join/Prune AttributesCurrent
June 2016
- RFC 7411Multicast Listener Extensions for Mobile IPv6 (MIPv6) and Proxy Mobile IPv6 (PMIPv6) Fast HandoversCurrent
November 2014
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8777DNS Reverse IP Automatic Multicast Tunneling (AMT) DiscoveryCurrent
April 2020
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
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?