RFC 8313: Use of Multicast across Inter-domain Peering Points
In plain English — editorial summary, not part of the RFC
This document examines the use of Source-Specific Multicast (SSM) across inter-domain peering points for a specified set of deployment scenarios. The objectives are to (1) describe the setup process for multicast-based delivery across administrative domains for these scenarios and (2) document supporting functionality to enable this process.
Document record
- Document ID
- RFC8313
- Published
- January 2018
- Authors
- P. Tarapore; R. Sayko; G. Shepherd; T. Eckert; R. Krishnan
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 44
- Also known as
- BCP213
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9706TreeDN: Tree-Based Content Delivery Network (CDN) for Live Streaming to Mass AudiencesCurrent
January 2025
- RFC 8777DNS Reverse IP Automatic Multicast Tunneling (AMT) DiscoveryCurrent
April 2020
- RFC 8815Deprecating Any-Source Multicast (ASM) for Interdomain MulticastCurrent
August 2020
- RFC 7450Automatic Multicast TunnelingUpdated
February 2015
- RFC 8115DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 PrefixesCurrent
March 2017
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 7899Multicast VPN State DampingCurrent
June 2016
- RFC 6517Mandatory Features in a Layer 3 Multicast BGP/MPLS VPN SolutionCurrent
February 2012
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?