BIER Ingress Multicast Flow Overlay using Multicast Listener Discovery Protocols
draft-ietf-bier-mld-03
Network Working Group P. Pfister
Internet-Draft IJ. Wijnands
Intended status: Standards Track S. Venaas
Expires: May 7, 2020 Cisco Systems
C. Wang
Z. Zhang
ZTE Corporation
M. Stenberg
November 4, 2019
BIER Ingress Multicast Flow Overlay using Multicast Listener Discovery
Protocols
draft-ietf-bier-mld-03
Abstract
This document specifies the ingress part of a multicast flow overlay
for BIER networks. Using existing multicast listener discovery
protocols, it enables multicast membership information sharing from
egress routers, acting as listeners, toward ingress routers, acting
as queriers. Ingress routers keep per-egress-router state, used to
construct the BIER bit mask associated with IP multicast packets
entering the BIER domain.
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."
This Internet-Draft will expire on May 7, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Pfister, et al. Expires May 7, 2020 [Page 1]
Internet-Draft MLD BIER overlay November 2019
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 . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Applicability Statement . . . . . . . . . . . . . . . . . . . 4
5. Querier and Listener Specifications . . . . . . . . . . . . . 4
5.1. Configuration Parameters . . . . . . . . . . . . . . . . 5
5.2. MLDv2 instances. . . . . . . . . . . . . . . . . . . . . 6
5.2.1. Sending Queries . . . . . . . . . . . . . . . . . . . 6
5.2.2. Sending Reports . . . . . . . . . . . . . . . . . . . 6
5.2.3. Receiving Queries . . . . . . . . . . . . . . . . . . 7
5.2.4. Receiving Reports . . . . . . . . . . . . . . . . . . 8
5.3. Packet Forwarding . . . . . . . . . . . . . . . . . . . . 8
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
9.1. Normative References . . . . . . . . . . . . . . . . . . 9
9.2. Informative References . . . . . . . . . . . . . . . . . 10
Appendix A. BIER Use Case in Data Centers . . . . . . . . . . . 11
A.1. Convention and Terminology . . . . . . . . . . . . . . . 12
A.2. BIER in data centers . . . . . . . . . . . . . . . . . . 13
A.3. A BIER MLD solution for Virtual Network information . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
The Bit Index Explicit Replication (BIER - [RFC8279]) forwarding
technique enables IP multicast transport across a BIER domain. When
receiving or originating a packet, ingress routers have to construct
a bit mask indicating which BIER egress routers located within the
same BIER domain will receive the packet. A stateless approach would
consist of forwarding all incoming packets toward all egress routers,
which would in turn make a forwarding decision based on local
Show full document text