Edge multicast replication for BGP IP VPNs.
draft-marques-l3vpn-mcast-edge-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-05-07
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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                                         P. Marques
Internet-Draft                                          Contrail Systems
Intended status: Standards Track                                 L. Fang
Expires: October 31, 2012                                  Cisco Systems
                                                            D. Winkworth
                                                                     FIS
                                                                  Y. Cai
                                                   Microsoft Corporation
                                                                May 2012

              Edge multicast replication for BGP IP VPNs.
                   draft-marques-l3vpn-mcast-edge-00

Abstract

   In data-center networks it is common to use Clos network topologies
   [clos] in order to provide a non-blocking switched network.  In these
   topologies it is often not desirable to provide native IP multicast
   service.

   This document defines a multicast replication algorithm along with
   its control and data forwarding procedures that provides a multicast
   service for a BGP IP VPN network without assuming that the underlying
   infrastructure supports IP multicast.

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 October 31, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Marques, et al.         Expires October 31, 2012                [Page 1]
Internet-DraftEdge multicast replication for BGP IP VPNs.       May 2012

   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.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  VPN Forwarder behavior . . . . . . . . . . . . . . . . . . . .  5
   4.  Multicast tree management  . . . . . . . . . . . . . . . . . .  7
   5.  BGP Protocol Extensions  . . . . . . . . . . . . . . . . . . . 11
     5.1.  Multicast Tree Route Type  . . . . . . . . . . . . . . . . 11
     5.2.  Multicast Edge Discovery Attribute . . . . . . . . . . . . 11
     5.3.  Multicast Edge Forwarding Attribute  . . . . . . . . . . . 12
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 12
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 13
     7.2.  Informational References . . . . . . . . . . . . . . . . . 13
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 13

1.  Introduction

   In Wide-Area Networks having native multicast service on hop-by-hop
   basis allows for more efficient use of scarse link bandwidth.  In
   Clos network topologies [clos] the trade-offs are different.

   A Clos network is often used to provide full cross-sectional
   bandwidth between all the ports on the network.  When used in a
   switching infrastructure it achieves this goal by spreading flows
   across multiple equal cost paths.

   For Clos topologies with multiple stages native multicast support
   within the switching infrastructure is both unnecessary and
   undesirable.  By definition the Clos network has enough bandwidth to
   deliver a packet from any input port to any output port.  Native
   multicast support would however make it such that the network would
   no longer be non-blocking.  Bringing with it the need to devise
   congestion management procedures.

   In this type of environments it is desirable to provide multicast
   service as an edge functionality on top of a unicast clos fabric.
   Early versions of IP VPN multicast services have used ingress
Show full document text