IETF Logo Mail Archive

[pim] RFC 8364 on PIM Flooding Mechanism (PFM) and Source Discovery (SD)

rfc-editor@rfc-editor.org Wed, 28 March 2018 23:29 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E30C12E898; Wed, 28 Mar 2018 16:29:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3SQc_cmmbss8; Wed, 28 Mar 2018 16:29:49 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9772129C70; Wed, 28 Mar 2018 16:29:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 051EBB812FB; Wed, 28 Mar 2018 16:28:56 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pim@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180328232856.051EBB812FB@rfc-editor.org>
Date: Wed, 28 Mar 2018 16:28:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/9fHc9xP4oJfb4sjtW-USJw_9MQo>
Subject: [pim] RFC 8364 on PIM Flooding Mechanism (PFM) and Source Discovery (SD)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Mar 2018 23:30:00 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8364

        Title:      PIM Flooding Mechanism (PFM) and 
                    Source Discovery (SD) 
        Author:     IJ. Wijnands,
                    S. Venaas,
                    M. Brig,
                    A. Jonasson
        Status:     Experimental
        Stream:     IETF
        Date:       March 2018
        Mailbox:    ice@cisco.com, 
                    stig@cisco.com, 
                    michael.brig@mda.mil,
                    anders@jomac.se
        Pages:      18
        Characters: 44640
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-pim-source-discovery-bsr-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8364

        DOI:        10.17487/RFC8364

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.

This document is a product of the Protocols for IP Multicast Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC

v2.23.0 | Report a Bug | By Email