PIM Flooding Protocol over Reliable Transport
draft-venaas-pim-port-pfm-00

Document Type Active Internet-Draft (individual)
Last updated 2019-03-11
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                          S. Venaas
Internet-Draft                                                 B. Ganesh
Intended status: Experimental                        K. Thiruvenkatasamy
Expires: September 12, 2019                          R. Chokkanathapuram
                                                     Cisco Systems, Inc.
                                                          March 11, 2019

             PIM Flooding Protocol over Reliable Transport
                      draft-venaas-pim-port-pfm-00

Abstract

   The PIM Flooding Protocol (PFM) defined in RFC8364 relies on sending
   periodic updates as it does not provide for any reliability.  If a
   message is lost, the information will be provided in the next
   periodic update.

   This document extends the Reliable Transport Mechanism for PIM in
   RFC6559 to allow for sending PFM messages.  This significantly
   reduces the PFM signaling by not requiring frequent periodic updates,
   and it provides for retransmission, allowing for quick recovery when
   an IP packet is dropped.

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 https://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 September 12, 2019.

Copyright Notice

   Copyright (c) 2019 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

Venaas, et al.         Expires September 12, 2019               [Page 1]
Internet-Draft                PIM PORT PFM                    March 2019

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Protocol specification  . . . . . . . . . . . . . . . . . . .   3
   4.  PFM over PORT message definitions . . . . . . . . . . . . . .   5
     4.1.  PORT PFM Update . . . . . . . . . . . . . . . . . . . . .   5
     4.2.  PORT PFM Request  . . . . . . . . . . . . . . . . . . . .   7
     4.3.  PORT PFM Update Option  . . . . . . . . . . . . . . . . .   8
     4.4.  PORT PFM Request Option . . . . . . . . . . . . . . . . .   8
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   6.  IANA considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   The PIM Flooding Protocol (PFM) defined in [RFC8364] relies on
   sending periodic updates as it does not provide for any reliability.
   If a message is lost, the information will be provided in the next
   periodic update.  With PFM, a router will typically originate a full
   update every 60 seconds.  This ensures that in case of packet drops,
   one usually will recover in 60 seconds.  There is a trade-off between
   the number of updates and the recovery time.

   This document extends the Reliable Transport Mechanism for PIM in
   [RFC6559] to allow for sending PFM messages.  We will refer to it as
   PORT (PIM Over Reliable Transport).  The use of PORT significantly
   reduces the PFM signaling by not requiring frequent periodic updates,
   and it provides for retransmission, allowing for quick recovery when
   an IP packet is dropped.  There will still be some full updates, but
   they can be sent much more rarely.  If there is a packet drop, the
   reliable transport (TCP/SCTP) will ensure retransmission.

   The PORT sessions are established as specified in [RFC6559] between
   PIM neighbors.  The sessions may be used to send other PORT messages,
   or they can be used only for PFM.  Unless all the neighbors support
   PFM over PORT, regular PFM is used.  How to signal support and how a
   router relays a PFM over PORT message as regular PFM and vice versa
   will be discussed in a later revision.
Show full document text