Multicast VPN state damping
draft-ietf-bess-multicast-damping-05

The information below is for an old version of the document
Document Type Active Internet-Draft (bess WG)
Last updated 2016-05-05 (latest revision 2016-05-04)
Replaces draft-morin-bess-multicast-damping
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Martin Vigoureux
Shepherd write-up Show (last changed 2016-01-28)
IESG IESG state Approved-announcement to be sent
Consensus Boilerplate Yes
Telechat date
Responsible AD Alvaro Retana
Send notices to aretana@cisco.com
IANA IANA review state IANA OK - No Actions Needed
Network Working Group                                      T. Morin, Ed.
Internet-Draft                                              S. Litkowski
Updates: 6514 (if approved)                                       Orange
Intended status: Standards Track                                K. Patel
Expires: November 5, 2016                                  Cisco Systems
                                                                Z. Zhang
                                                               R. Kebler
                                                                 J. Haas
                                                        Juniper Networks
                                                            May 04, 2016

                      Multicast VPN state damping
                  draft-ietf-bess-multicast-damping-05

Abstract

   This document describes procedures to damp multicast VPN routing
   state changes and control the effect of the churn due to the
   multicast dynamicity in customer sites.  The procedures described in
   this document are applicable to BGP-based multicast VPN and help
   avoid uncontrolled control plane load increase in the core routing
   infrastructure.  New procedures are proposed inspired from BGP
   unicast route damping principles, but adapted to multicast.

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 RFC 2119 [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 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 November 5, 2016.

Morin, et al.           Expires November 5, 2016                [Page 1]
Internet-Draft                mVPN damping                      May 2016

Copyright Notice

   Copyright (c) 2016 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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Existing mechanisms . . . . . . . . . . . . . . . . . . . . .   5
     4.1.  Rate-limiting of multicast control traffic  . . . . . . .   5
     4.2.  Existing PIM, IGMP and MLD timers . . . . . . . . . . . .   5
     4.3.  BGP Route Damping . . . . . . . . . . . . . . . . . . . .   6
   5.  Procedures for multicast state damping  . . . . . . . . . . .   7
     5.1.  PIM procedures  . . . . . . . . . . . . . . . . . . . . .   7
     5.2.  Procedures for multicast VPN state damping  . . . . . . .  10
   6.  Procedures for P-tunnel state damping . . . . . . . . . . . .  11
     6.1.  Damping mVPN P-tunnel change events . . . . . . . . . . .  11
     6.2.  Procedures for Ethernet VPNs  . . . . . . . . . . . . . .  12
   7.  Operational considerations  . . . . . . . . . . . . . . . . .  12
     7.1.  Enabling multicast damping  . . . . . . . . . . . . . . .  12
     7.2.  Troubleshooting and monitoring  . . . . . . . . . . . . .  12
     7.3.  Default and maximum values  . . . . . . . . . . . . . . .  13
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  14
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   10. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  15
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     11.2.  Informative References . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  16

1.  Introduction

   In a multicast VPN [RFC6513] deployed with BGP-based procedures
   [RFC6514], when receivers in VPN sites join and leave a given
Show full document text