Reliable Transport For PIM Register States
draft-anish-pim-reliable-registers-00

Document Type Active Internet-Draft (individual)
Last updated 2018-11-20
Stream (None)
Intended RFC status (None)
Formats plain text 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)
Protocol Independent Multicast (pim)                       A. Peter, Ed.
Internet-Draft                                                  Infinera
Intended status: Standards Track                               R. Kebler
Expires: May 25, 2019                                       V. Nagarajan
                                                  Juniper Networks, Inc.
                                                               T. Eckert
                                Huawei USA - Futurewei Technologies Inc.
                                                               S. Venaas
                                                     Cisco Systems, Inc.
                                                       November 21, 2018

               Reliable Transport For PIM Register States
                 draft-anish-pim-reliable-registers-00

Abstract

   This document introduces a hard-state, reliable transport for the
   existing PIM-SM registers states.  This eliminates the needs for
   periodic NULL-registers and register-stop in response to each data-
   register or NULL-registers.

   This specification uses the existing PIM reliability mechanisms
   defined by PIM Over Reliable Transport [RFC6559].  This is simply a
   means to transmit reliable PIM messages and does not require the
   support for Join/Prune messages over PORT as defined in [RFC6559].

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC2119 [RFC2119].

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."

Peter, et al.             Expires May 25, 2019                  [Page 1]
Internet-Draft Reliable Transport For PIM Register States  November 2018

   This Internet-Draft will expire on May 25, 2019.

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
   2.  Reliable Register Overview  . . . . . . . . . . . . . . . . .   4
   3.  Targeted Hellos . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  New Hello Optional TLV's  . . . . . . . . . . . . . . . .   5
     3.2.  Differences from Link-Level hellos  . . . . . . . . . . .   6
     3.3.  Address in Hello message  . . . . . . . . . . . . . . . .   6
     3.4.  Timer Values  . . . . . . . . . . . . . . . . . . . . . .   6
     3.5.  Targeted Neighbor . . . . . . . . . . . . . . . . . . . .   6
   4.  Reliable Connection setup . . . . . . . . . . . . . . . . . .   7
     4.1.  Active FHR  . . . . . . . . . . . . . . . . . . . . . . .   7
     4.2.  Connection setup between two RP's . . . . . . . . . . . .   7
     4.3.  Hello Generation ID and reconnect . . . . . . . . . . . .   7
     4.4.  Handling Connection or reachability loss  . . . . . . . .   8
   5.  Anycast RP's  . . . . . . . . . . . . . . . . . . . . . . . .   8
     5.1.  Targeted Hellos and Neighbors . . . . . . . . . . . . . .   8
     5.2.  Anycast-RP connection setup . . . . . . . . . . . . . . .   8
     5.3.  Anycast-RP state sync . . . . . . . . . . . . . . . . . .   9
     5.4.  Anycast-RP change . . . . . . . . . . . . . . . . . . . .   9
     5.5.  Anycast-RP with MSDP  . . . . . . . . . . . . . . . . . .  10
   6.  PIM-registers and Interoperation with legacy PIM nodes  . . .  10
     6.1.  Initial packet-loss avoidance with PORT . . . . . . . . .  10
     6.2.  First-Hop-Router does not support PORT  . . . . . . . . .  10
     6.3.  RP does not support PORT  . . . . . . . . . . . . . . . .  10
     6.4.  Data-Register free operations . . . . . . . . . . . . . .  11
   7.  PORT message  . . . . . . . . . . . . . . . . . . . . . . . .  11
Show full document text