RFC 8378: Signal-Free Locator/ID Separation Protocol (LISP) Multicast
In plain English — editorial summary, not part of the RFC
When multicast sources and receivers are active at Locator/ID Separation Protocol (LISP) sites, the core network is required to use native multicast so packets can be delivered from sources to group members. When multicast is not available to connect the multicast sites together, a signal-free mechanism can be used to allow traffic to flow between sites. The mechanism described in this document uses unicast replication and encapsulation over the core network for the data plane and uses the LISP mapping database system so encapsulators at the source LISP multicast site can find decapsulators at the receiver LISP multicast sites.
Document record
- Document ID
- RFC8378
- Published
- May 2018
- Authors
- V. Moreno; D. Farinacci
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- rtg
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9303Locator/ID Separation Protocol Security (LISP-SEC)Current
October 2022
- RFC 7215Locator/Identifier Separation Protocol (LISP) Network Element Deployment ConsiderationsCurrent
April 2014
- RFC 8111Locator/ID Separation Protocol Delegated Database Tree (LISP-DDT)Current
May 2017
- RFC 9299An Architectural Introduction to the Locator/ID Separation Protocol (LISP)Current
October 2022
- RFC 9306Vendor-Specific LISP Canonical Address Format (LCAF)Current
October 2022
- RFC 9437Publish/Subscribe Functionality for the Locator/ID Separation Protocol (LISP)Current
August 2023
- RFC 8973DDoS Open Threat Signaling (DOTS) Agent DiscoveryCurrent
January 2021
- RFC 9308Applicability of the QUIC Transport ProtocolCurrent
September 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?