The Locator/ID Separation Protocol (LISP) for Multicast Environments

Abstract

This document describes how inter-domain multicast routing will function in an environment where Locator/ID Separation is deployed using the Locator/ID Separation Protocol (LISP) architecture.

A Framework for Multicast in Network Virtualization over Layer 3

“…Bidirectional PIM (BIDIR-PIM) would offer better scalability with the number of flows required being g. Unfortunately, many vendors still do not fully support BIDIR or have limitations on its implementation. [RFC6831] describes the use of SSM as an alternative to BIDIR, provided that the NVEs have a way to learn of each other's IP addresses so that they can join all of the SSM Shortest Path Trees (SPTs) to create/maintain an underlay SSM IP multicast tunnel solution.…”

Locator/ID Separation Protocol (LISP) Impact

“…LISP has native support for multicast [RFC6831]. From the data-plane perspective, at a multicast-enabled xTR, an EID-sourced multicast packet is encapsulated in another multicast packet and subsequently forwarded in an RLOC-level distribution tree.…”

Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block

“…This document does not introduce any new terms related to the set of LISP Specifications ([RFC6830], [RFC6831], [RFC6832], [RFC6833], [RFC6834], [RFC6835], [RFC6836], [RFC6837]), but assumes that the reader is familiar with the LISP terminology.…”

“…The Locator/ID Separation Protocol (LISP [RFC6830]) and related mechanisms ( [RFC6831], [RFC6832], [RFC6833], [RFC6834], [RFC6835], [RFC6836], [RFC6837]) separate the IP addressing space into two logical spaces, the Endpoint Identifier (EID) space and the Routing Locator (RLOC) space. The first space is used to identify communication endpoints, while the second is used to locate EIDs in the Internet routing infrastructure topology.…”