PIM flooding mechanism and source discovery
draft-ietf-pim-source-discovery-bsr-02

The information below is for an old version of the document
Document Type Active Internet-Draft (pim WG)
Last updated 2015-07-01
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       IJ. Wijnands
Internet-Draft                                                 S. Venaas
Intended status: Experimental                        Cisco Systems, Inc.
Expires: January 2, 2016                                         M. Brig
                                                Aegis BMD Program Office
                                                             A. Jonasson
                           Swedish Defence Material Administration (FMV)
                                                            July 1, 2015

              PIM flooding mechanism and source discovery
                 draft-ietf-pim-source-discovery-bsr-02

Abstract

   PIM Sparse-Mode uses a Rendezvous Point (RP) and shared trees to
   forward multicast packets to Last Hop Routers (LHR).  After the first
   packet is received by the LHR, the source of the multicast stream is
   learned and the Shortest Path Tree (SPT) can be joined.  This draft
   proposes a solution to support PIM Sparse Mode (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.  This mechanism is defined in this document, and
   is modeled after the PIM Bootstrap Router protocol.  By removing the
   need for RPs and shared trees, the PIM-SM procedures are simplified,
   improving router operations, management and making the protocol more
   robust.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on January 2, 2016.

Wijnands, et al.         Expires January 2, 2016                [Page 1]
Internet-Draft PIM flooding mechanism and source discovery     July 2015

Copyright Notice

   Copyright (c) 2015 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
   (http://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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Conventions used in this document . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  A generic PIM flooding mechanism  . . . . . . . . . . . . . .   3
     2.1.  PFP message format  . . . . . . . . . . . . . . . . . . .   4
     2.2.  Processing PFP messages . . . . . . . . . . . . . . . . .   5
       2.2.1.  Initial checks  . . . . . . . . . . . . . . . . . . .   5
       2.2.2.  Processing messages with known PFP type . . . . . . .   5
       2.2.3.  Processing messages with unknown PFP type . . . . . .   6
   3.  Distributing Source to Group Mappings . . . . . . . . . . . .   6
     3.1.  Group Source Holdtime TLV . . . . . . . . . . . . . . . .   6
     3.2.  Originating SG messages . . . . . . . . . . . . . . . . .   7
     3.3.  Processing SG messages  . . . . . . . . . . . . . . . . .   7
     3.4.  The first packets and bursty sources  . . . . . . . . . .   8
     3.5.  Resiliency to network partitioning  . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   5.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   9
   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   PIM Sparse-Mode uses a Rendezvous Point (RP) and shared trees to
   forward multicast packets to Last Hop Routers (LHR).  After the first
   packet is received by the LHR, the source of the multicast stream is
   learned and the Shortest Path Tree (SPT) can be joined.  This draft
Show full document text