PIM Flooding Mechanism (PFM) and Source Discovery (SD)
RFC 8364
| Document | Type |
RFC - Experimental
(March 2018; No errata)
Updated by RFC 8736
|
|
|---|---|---|---|
| Last updated | 2018-03-28 | ||
| Replaces | draft-wijnands-pim-source-discovery-bsr | ||
| Stream | IETF | ||
| Formats | plain text html pdf htmlized bibtex | ||
| Reviews | |||
| Stream | WG state | Submitted to IESG for Publication | |
| Document shepherd | Mike McBride | ||
| Shepherd write-up | Show (last changed 2017-06-13) | ||
| IESG | IESG state | RFC 8364 (Experimental) | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | Alvaro Retana | ||
| Send notices to | Mike McBride <mmcbride7@gmail.com>, aretana.ietf@gmail.com | ||
| IANA | IANA review state | Version Changed - Review Needed | |
| IANA action state | RFC-Ed-Ack | ||
Internet Engineering Task Force (IETF) IJ. Wijnands
Request for Comments: 8364 S. Venaas
Category: Experimental Cisco Systems, Inc.
ISSN: 2070-1721 M. Brig
Aegis BMD Program Office
A. Jonasson
FMV
March 2018
PIM Flooding Mechanism (PFM) and Source Discovery (SD)
Abstract
Protocol Independent Multicast - Sparse Mode (PIM-SM) uses a
Rendezvous Point (RP) and shared trees to forward multicast packets
from new sources. Once Last-Hop Routers (LHRs) receive packets from
a new source, they may join the Shortest Path Tree (SPT) for the
source for optimal forwarding. This document defines a new mechanism
that provides a way to support PIM-SM without the need for PIM
registers, RPs, or shared trees. Multicast source information is
flooded throughout the multicast domain using a new generic PIM
Flooding Mechanism (PFM). This allows LHRs to learn about new
sources without receiving initial data packets.
Status of This Memo
This document is not an Internet Standards Track specification; it is
published for examination, experimental implementation, and
evaluation.
This document defines an Experimental Protocol for the Internet
community. This document is a product of the Internet Engineering
Task Force (IETF). It represents the consensus of the IETF
community. It has received public review and has been approved for
publication by the Internet Engineering Steering Group (IESG). Not
all documents approved by the IESG are candidates for any level of
Internet Standard; see Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8364.
Wijnands, et al. Experimental [Page 1]
RFC 8364 PFM and SD March 2018
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Conventions Used in This Document . . . . . . . . . . . . 4
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Testing and Deployment Experiences . . . . . . . . . . . . . 5
3. A Generic PIM Flooding Mechanism . . . . . . . . . . . . . . 5
3.1. PFM Message Format . . . . . . . . . . . . . . . . . . . 6
3.2. Administrative Boundaries . . . . . . . . . . . . . . . . 7
3.3. Originating PFM Messages . . . . . . . . . . . . . . . . 7
3.4. Processing PFM Messages . . . . . . . . . . . . . . . . . 9
3.4.1. Initial Checks . . . . . . . . . . . . . . . . . . . 9
3.4.2. Processing and Forwarding of PFM Messages . . . . . . 10
4. Distributing SG Mappings . . . . . . . . . . . . . . . . . . 11
4.1. Group Source Holdtime TLV . . . . . . . . . . . . . . . . 11
4.2. Originating Group Source Holdtime TLVs . . . . . . . . . 12
4.3. Processing GSH TLVs . . . . . . . . . . . . . . . . . . . 13
4.4. The First Packets and Bursty Sources . . . . . . . . . . 13
4.5. Resiliency to Network Partitioning . . . . . . . . . . . 14
5. Configurable Parameters . . . . . . . . . . . . . . . . . . . 15
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 16
8.1. Normative References . . . . . . . . . . . . . . . . . . 16
8.2. Informative References . . . . . . . . . . . . . . . . . 17
Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
Wijnands, et al. Experimental [Page 2]
RFC 8364 PFM and SD March 2018
1. Introduction
Show full document text